FS#28569 - linux 3.2.7-1 renders system unbootable when root is ext3
Attached to Project:
Arch Linux
Opened by Dave Morgan (loafer) - Tuesday, 21 February 2012, 20:44 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 22 February 2012, 15:01 GMT
Opened by Dave Morgan (loafer) - Tuesday, 21 February 2012, 20:44 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 22 February 2012, 15:01 GMT
|
Details
Description:
Upgrading to linux 3.2.7-1 renders the system unbootable. I am dropped to a recovery shell with the error ext3 filesystem unknown. Downgrading to 3.2.6-2 fixes the problem. The upgrade appears to go smoothly and the initramfs reports it is successfully generated. Steps to reproduce: Upgrade to linux 3.2.7-1. |
This task depends upon
Closed by Dave Reisner (falconindy)
Wednesday, 22 February 2012, 15:01 GMT
Reason for closing: Fixed
Additional comments about closing: mkinitcpio 0.8.2-3
Wednesday, 22 February 2012, 15:01 GMT
Reason for closing: Fixed
Additional comments about closing: mkinitcpio 0.8.2-3

Please post the contents of the "broken" initramfs with
'lsinitcpio -v'

File attached.

Add ext4 to MODULES and regenerate. That will at least give you a
bootable image with 3.2.7-1. This is a fairly annoying bug which
only happens in this one specific case because an alias exists as
a module name.

Alternatively, the fallback image should work as is.

Confirmed. Adding ext4 to modules allows 3.2.7-1 to boot.

mkinitcpio-0.8.2-3 in testing should fix this.

Thanks. mkinitcpio-0.8.2-3 does fix this.