This is pretty dumb… every other hypervisor I’ve ever played with, if the boot drive is fine… the OS boots… period….<\/p>\n
Yet the other day I tried to boot my PVE host and it just won’t boot it would get stuck stating that a datastore (nothing that’s a dependency for the OS to actually boot) was causing the OS not to boot….<\/p>\n
I found this PVE thread that was more recent with a comment that worked for the OP.<\/p>\n
“if you created the partition via the gui, we create a systemd-mount unit under \/etc\/systemd\/system<\/p>\n
(e.g. mnt-datastore-foo.mount)<\/p>\n
you can disable that unit with ‘systemctl disable <unit>’<\/p>\n
or delete the file<\/p>\n
we’ll improve the docs in the near future and have planned to make the gui disk management a bit easier in regards to removing\/reusing”<\/p>\n
This was posted in 2021, yet when I checked that path (booting into Recovery mode) it didn’t contain any file with a ending of .mount… So not sure what this is about. I did however find this thread which was exactly my problem… and funny enough the OP literally posted their own answer (which is the answer here as well) and no other comments made on the post, which was created in\u00a0 2018…<\/p>\n
[SOLVED] – Reboot Proxmox Host now will not boot | Proxmox Support Forum<\/a><\/p>\n “So I had upgraded some packages and the proxmox host recommended rebooting the system. After rebooting the system hangs at the screen showing [DEPEND] in yellow for 3 lines: I tried running control-D to continue but it does not continue.<\/p>\n I’m guessing I need to clean up the entries how can i do that? I’m assuming I just need to boot into emergency and edit \/etc\/fstab and remove the entries?<\/p>\n OK yes removing those from \/etc\/fstab fixed it and now it boots.”<\/p>\n This is exactly what I did as well… I saw the offending entry which was a BTRFS storage I had configured in the past and that storage unit had been shutdown. (I thought I blogged this, but I only blogged about using LVM over iscsi.. Configuring shared LVM over iSCSI on Proxmox \u2013 Zewwy’s Info Tech Talks<\/a>)<\/p>\n Anyway, removing the entry from fstab and rebooting.. bam PVE host came right up.<\/p>\n Constructive criticism to PVE, while yes any knowledgeable Linux sysadmin will figure out how to fix this, as I just did here. However, how about NOT having the boot process fail simply cause a configured storage is not available… like all other hypervisors… BOOT the host and show the storage as failed in the management UI to clean it up that way…. Just.. food for thought….<\/p>\n","protected":false},"excerpt":{"rendered":" This is pretty dumb… every other hypervisor I’ve ever played with, if the boot drive is fine… the OS boots… period…. Yet the other day I tried to boot my PVE host and it just won’t boot it would get stuck stating that a datastore (nothing that’s a dependency for the OS to actually boot) … <\/p>\n
\nDependency failed for \/mnt\/Media
\nDependency failed for local file system
\nDependency failed for File system check on \/dev\/Data-Storage\/Media<\/p>\n