Red Hat Bugzilla – Bug 505846
After upgrading root partition to ext4, Fedora will not boot
Last modified: 2010-01-12 11:25:18 EST
* Description of problem:
After upgrading root filesystem to ext4, the system will not boot.
* How reproducible:
Possibly always (haven't tried multiple times)
* Steps to Reproduce:
change ext3 to ext4 in /etc/fstab for the root partition
# telinit 1
# mount -o remount,ro /
# tune2fs -O extents,uninit_bg,dir_index /dev/device
# fsck -pf /dev/device
* Actual results:
Doesn't boot with a message like: "Cannot mount root filesystem, unsupported options(40)".
* Expected results:
* Additional info:
To solve the problem, I modified the initrd image manually - I changed "-t ext3" to "-t ext4" inside the "/init" file of the image.
I didn't run mkinitrd after filesystem upgrade, this might have helped.
I am adding this info in case somebody uses the same HOWTO and runs into problems.
This is a mass edit of all mkinitrd bugs.
Thanks for taking the time to file this bug report (and/or commenting on it).
As you may have heard in Fedora 12 mkinitrd has been replaced by dracut. In Fedora 12 the mkinitrd package is still around as some programs depend on
certain libraries it provides, but mkinitrd itself is no longer used.
In Fedora 13 mkinitrd will be removed completely. This means that all work
on initrd has stopped.
Rather then keeping mkinitrd bugs open and giving false hope they might get fixed we are mass closing them, so as to clearly communicate that no more work will be done on mkinitrd. We apologize for any inconvenience this may cause.
If you are using Fedora 11 and are experiencing a mkinitrd bug you cannot work around, please upgrade to Fedora 12. If you experience problems with the initrd in Fedora 12, please file a bug against dracut.
Are we yet sure the core issue is a mkinitrd one?
And that it won't harm dracut?
(In reply to comment #2)
> Are we yet sure the core issue is a mkinitrd one?
> And that it won't harm dracut?
> Please explain.
The core issue in this case is that the user changed its rootfs type, without regenerating the initrd, so the initrd will still try to mount / as ext3, which fails as the kernel ext3 code does not support ext4 filesystems.
So you are right in this case, that this is not a case of closed -> wontfix, but a case of closed notabug.
Note that dracut does not suffer from this as the dracut generated initrd is
much more flexible and will happily deal with a change such as going from ext3 to ext4 without requiring the initrd to be regenerated.