After a fresh install of Ubuntu 20.04 LTS on the ssd of an Acer Aspire 7, I moved the home directory to a separate partition on the hdd by following this guide : https://help.ubuntu.com/community/Partitioning/Home/Moving.
Following a system update, my computer will now only start in Emergency mode. By entering "mount -a" in the maintenance commande line, I am able to get to the login screen and login normaly. But now I alway have to mount the fstab file manualy like this at every restart.
Also, I don't know if it's related but at the same time I started having permission problem with Dropbox. I'm aksed for a password to start /bin/sh as a super-user when I try to start dropbox.
Edit:
Here are the "important" journal logs after I restart at 10:00 :
10:00:17 Initramfs unpacking failed: Decoding failed10:00:17 integrity: Problem loading X.509 certificate -6510:00:19 fsck failed with exit status 4.10:00:19 Failed to start File System Check on /dev/disk/by-uuid/9486c2a5-5489-4a55-8e8f-864de63a896e.Logs after I load fstab manualy from Emergency mode :
10:21:40 gkr-pam: unable to locate daemon control file 10:21:41 EXT4-fs error (device sdb2): __ext4_find_entry:1541: inode #41553027: comm tracker-extract: checksumming directory block 010:22:04 ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x0000000FF) is beyond end of object (length 0x11) (20190816/exoparg2-393)10:22:04 ACPI Error: Aborting method \_SB.TBFP due to previous error (AE_AML_PACKAGE_LIMIT) (20190816/psparse-529)10:22:04 ACPI Error: Aborting method \_SB.WMTF.WMTF due to previous error (AE_AML_PACKAGE_LIMIT) (20190816/psparse-529)10:22:14 EXT4-fs error (device sdb2): __ext4_find_entry:1541: inode #41684188: comm MainThread: checksumming directory block 010:22:53 EXT4-fs error (device sdb2): ext4_lookup:1701: inode #41555822: comm dropbox: iget: checksum invalidContent of fstab file :
# /etc/fstab: static file system information.## Use 'blkid' to print the universally unique identifier for a# device; this may be used with UUID= as a more robust way to name devices# that works even if disks are added and removed. See fstab(5).## <file system> <mount point> <type> <options> <dump> <pass># / was on /dev/sda2 during installationUUID=0041fcc9-6350-4e54-8e56-622a4b5249ca / ext4 errors=remount-ro 0 1# /boot/efi was on /dev/sda1 during installationUUID=DAAB-D931 /boot/efi vfat umask=0077 0 1/swapfile none swap sw 0 0# (identifier) (location, eg sda5) (format, eg ext3 or ext4) (some settings) UUID=9486c2a5-5489-4a55-8e8f-864de63a896e /home ext4 defaults 0 2 Output of blkid :
/dev/sda2: UUID="0041fcc9-6350-4e54-8e56-622a4b5249ca" TYPE="ext4" PARTUUID="6b0bc007-c7b9-4cd5-9c15-431dd33e73a8"