Solved: "nofail" was a good workaround; but the problem was in the fstab, outside the viewing area, /dev/sdg1 was in the same line with the main drives partition SSD2 entry. Once I removed that errant entry, it behaved normally. I also removed any reference to the external ext4 USB from the fstab
Backup program created a binding hook in the mount on boot, how do get rid of it? Two desktops with the exact problem. Installed the backup program but after learning that it made the computer dependent upon having a ext4 format drive inserted to shut down and boot. Uninstalled the program, it left the hooks. Do you know how to remove the bindings?
Kubuntu and Ubuntu 22.04 machines with same issue.
Here is the boot up error message.
( 13.098039) EXT4-fs (sdc1): VFS: Can't find ext4 filesystem
( 14.437082)
You are in emergency mode. After logging in type "Journalctl -xb"
to view
system logs. "systemctl reboot" to reboot "systemctl default" or "exit"
to boot into default mode.
(or press Control-D to continue):
Here is Kubuntu 22.04 fstab.
fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda5 during installation
UUID=8256fca0-2723-4e9a-bc64-ac669b1cdd7d / ext4 errors=remount-ro>
# /boot/efi was on /dev/sda2 during installation
UUID=A9EF-3FF7 /boot/efi vfat umask=0077 >
/swapfile none swap sw >
/dev/sda1 /mnt/SSD2 ext4 defaults >
/dev/sdg1 /media/unity/sdg1 ext4 defaults >
Machine will hang at boot, will not boot. Put a ext4 USB in, and it will boot, if not it eventually will go to error and try to repair/instruct. Same with shut down. Pulled readme file off of the root in the offending program giving details of the mount and bindings.
Tried using this fix, did not work.

Answer: *adding the "nofail" option to the fstab on the /dev/sdg1 fixed the problem.*
Note: uninstalled errant Timeshift (TeeJee) mount hook is still there, the "nofail" option is a effective "work around".
Here are some of the error msg. in "journalctl log"
- ACPI BIOS Warning (bug) : Optional FADT field Pm2ControlBlock
- pc1 0000:02;00.0: (Firmware Bug) : disabling VPD access (can***?
- device-mapper: core: CONFIG_IMA_DISABLE_HTABALE is disabled
-platform eisa-0: EISA Cannot allocate resource for mainboard
(which I guess is regarding a EISA card, there is only one ISA card that is a nvidia card)
*I will add more as I go.
Backup program created a binding hook in the mount on boot, how do get rid of it? Two desktops with the exact problem. Installed the backup program but after learning that it made the computer dependent upon having a ext4 format drive inserted to shut down and boot. Uninstalled the program, it left the hooks. Do you know how to remove the bindings?
Kubuntu and Ubuntu 22.04 machines with same issue.
Here is the boot up error message.
( 13.098039) EXT4-fs (sdc1): VFS: Can't find ext4 filesystem
( 14.437082)
You are in emergency mode. After logging in type "Journalctl -xb"
to view
system logs. "systemctl reboot" to reboot "systemctl default" or "exit"
to boot into default mode.
(or press Control-D to continue):
Here is Kubuntu 22.04 fstab.
fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda5 during installation
UUID=8256fca0-2723-4e9a-bc64-ac669b1cdd7d / ext4 errors=remount-ro>
# /boot/efi was on /dev/sda2 during installation
UUID=A9EF-3FF7 /boot/efi vfat umask=0077 >
/swapfile none swap sw >
/dev/sda1 /mnt/SSD2 ext4 defaults >
/dev/sdg1 /media/unity/sdg1 ext4 defaults >
Machine will hang at boot, will not boot. Put a ext4 USB in, and it will boot, if not it eventually will go to error and try to repair/instruct. Same with shut down. Pulled readme file off of the root in the offending program giving details of the mount and bindings.
Tried using this fix, did not work.
Answer: *adding the "nofail" option to the fstab on the /dev/sdg1 fixed the problem.*
Note: uninstalled errant Timeshift (TeeJee) mount hook is still there, the "nofail" option is a effective "work around".
Here are some of the error msg. in "journalctl log"
- ACPI BIOS Warning (bug) : Optional FADT field Pm2ControlBlock
- pc1 0000:02;00.0: (Firmware Bug) : disabling VPD access (can***?
- device-mapper: core: CONFIG_IMA_DISABLE_HTABALE is disabled
-platform eisa-0: EISA Cannot allocate resource for mainboard
(which I guess is regarding a EISA card, there is only one ISA card that is a nvidia card)
*I will add more as I go.
Comment