Misidentifies ext4 as ext2 and fails to boot
Bug #441384 reported by
Tobias Wolf
This bug report is a duplicate of:
Bug #416636: fstype detects ext4 w/o journal as ext2.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
initramfs-tools |
Invalid
|
Undecided
|
Unassigned | ||
klibc (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Binary package hint: initramfs-tools
Because my laptop has a first-gen SSD, I tried to limit performance degradation over time by creating my root filesystem as ext4 with the option -O ^has_journal.
However the scripts/local script identifies my root fs as ext2, not as ext4. The result is that it fails to mount /root with "invalid args".
The value of $FSTYPE when mount command happens is ext2. When I hardcoded FSTYPE=ext4 in scripts/local it booted normally.
blkid identifies the file system correctly. I suppose the fstype tool from klibc-utils is wrong here.
To post a comment you must log in.
$ sudo /usr/lib/ klibc/bin/ fstype /dev/sda2
FSTYPE=ext2
FSSIZE=8002469888
but
$ sudo blkid -s TYPE -o value /dev/sda2
ext4