no longer boots because ext4 /home lost its UUID
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Hi
I encountered the same issue described by other users but can t find the solution :
After grub loading, whichever the recovery mode i use, i get the message
One or more of the mounts listed in /etc/fstab cannot yet mounted: (ESC for recover shell)
/home : waiting for UUID 67d51bb0-
# blkid give :
/dev/loop0: TYPE="squashfs"
/dev/sda1: UUID="2c112151-
/dev/sda2: UUID="3285efe0-
suggesting that the line /dev/sda3: UUID="67d51bb0-
When i boot the live CD Ubuntu and
- go to Gparted, no UUID are given for sda3
- go to systeme/
When i boot puppy linux, i cannot mount sda3
When in the shell i type cat etc/fstab
the 3 sda are found with the right format and same UUID (ext 4 for my sda3 and the address given in the error message)
How can i solve the issue, especially that sda3 contain all my data for which i have no recent backup.
Thanks
Hi, created this bug from that question, because that's what also happened to my mom's laptop.
One day it stopped booting complaining that it could no longer mount /home partition (ext4).
Booting from external USB and debugging from 300km away I discover that blkid reports no UUID for /dev/sda7 partition (which is /home)
/sbin/tune2fs -l /dev/sda7 shows the UUID correctly.
To boot again I had to replace the UUID reference in /etc/fstab for the physical device (/dev/sda7)
IMHO, this behaviour should be investigated because it renders a computer unbootable and novice users are completely lost.
I may be able to provide more information if you need.
Thanks!