14 replies
tomspark wrote:
Hey m2elite, welcome! Let's narrow this down — is that Linux VM something you set up yourself in your NAS's own VM manager (like Synology's Virtual Machine Manager), separate from SparkBox itself? First thing to check: open that VM manager and see if the VM is actually shown as running there. If it's stopped, that's why SparkBox can't come up either. If it does say running, tell me exactly what happens when you try to SSH — refused, timed out, or wrong password — and we'll go from there.
m2elite wrote:
it is a vm on Proxmox keeps stating wrong password
Chris wrote:
Hey m2elite, that wrong password is actually about logging into the VM itself, not SparkBox -- SparkBox can't run until you're able to get into that machine. In Proxmox's web dashboard, click on the VM in the list and open the Console tab: that gets you straight onto the VM's screen without needing SSH or a password, like a monitor plugged in directly. From there you can double check the username you're using is right, or see if you actually got locked out. Once you're in, SparkBox should be able to start normally -- let us know what you find!
m2elite wrote:
yes i am at the console it will not accept my creds
Chris wrote:
Hey m2elite -- at this point that's a Proxmox login issue, not SparkBox (it can't start until you're actually in). One thing that trips people up in the Proxmox console specifically: the keyboard layout can be different from what you're used to, so a password can type out wrong even though you're sure it's right. Try typing it into a text field you can see first (like the search box) to confirm it's really coming out the way you expect. Also double check you're using the exact VM username, not your NAS login. If both check out and it still won't take it, that's a real lockout on the VM itself, and resetting it goes through Proxmox's own tools -- outside anything SparkBox can fix, sorry!
m2elite wrote:
Quick question is the account like root or something we create
m2elite wrote:
I got in docker will not run
Chris wrote:
Hey m2elite -- that account isn't something SparkBox creates, it's whatever OS username and password you set up when you first installed the operating system inside that Proxmox VM (during the Ubuntu/Debian setup wizard or similar). It's not automatically root either -- most installers make a regular user and set root up separately. If you genuinely don't remember setting one, that VM's own OS won't have a record for you to recover since Proxmox doesn't track it -- reinstalling the OS in that VM to start clean is usually fastest, and SparkBox will install fine once you're logged in.
m2elite wrote:
g 13 00:22:01 sparkboxworld systemd[1]: Dependency failed for docker.service - Docker Application Container Engine. Aug 13 00:22:01 sparkboxworld systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'. Aug 13 00:22:01 sparkboxworld systemd[1]: Dependency failed for docker.service - Docker Application Container Engine. Aug 13 00:22:01 sparkboxworld systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'. Aug 13 00:22:01 sparkboxworld systemd[1]: Dependency failed for docker.service - Docker Application Container Engine. Aug 13 00:22:01 sparkboxworld systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'. Aug 13 00:22:01 sparkboxworld systemd[1]: Dependency failed for docker.service - Docker Application Container Engine. Aug 13 00:22:01 sparkboxworld systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'. Aug 13 01:04:36 sparkboxworld systemd[1]: Dependency failed for docker.service - Docker Application Container Engine. Aug 13 01:04:36 sparkboxworld systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'.
Chris wrote:
Hey m2elite -- good news, you're past the login wall! This new error is Docker itself failing to start on the VM, and that log snippet only tells us Docker's dependency failed, not which one. Can you run sudo systemctl status docker.service and paste what shows under Active: (plus any red lines above it)? That'll point at exactly what's blocking it -- once Docker is actually running, SparkBox will install fine on top of it.
m2elite wrote:
This is all i get Aug 13 01:12:47 sparkboxworld systemd[1]: Dependency failed for docker.service - Docker Application Container Engine. Aug 13 01:12:47 sparkboxworld systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'.
Chris wrote:
Hey m2elite -- that log only tells us Docker's dependency failed, not which one, so we're still missing the real reason. Can you run sudo systemctl status docker.service and paste everything after the word Active: at the top (not just the two dependency-failed lines)? Also worth checking sudo systemctl status docker.socket and sudo systemctl status containerd.service right after -- Docker needs both of those, and whichever one shows failed is the actual culprit. Once we know that, getting Docker running (and SparkBox installing on top of it) should be quick.
m2elite wrote:
i got it some nas mounts were missing
Chris wrote:
Nice, glad you tracked it down -- missing NAS mounts are a classic reason docker.service fails at boot on a VM, since it can't find its storage yet. Sounds like you're all set now, but shout if SparkBox itself acts up once Docker's staying up cleanly.