Red Hat Bugzilla – Bug 415991
dirty partition could hang init on boot. seen error: init trap divide error rip:338c0058a4 ...
Last modified: 2007-12-10 14:57:34 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:220.127.116.11) Gecko/20071128 Fedora/18.104.22.168-2.fc8 Firefox/22.214.171.124
Description of problem:
i have a pc with 2 identical sata hdd. after reorganizing partitions on
the second driver (/dev/sdb) i had the machine unable to boot.
i found that the content of /dev/sdb2 was creating problem (i found this
after the reorganization /dev/sdb2 start few sector after and old partition.
at boot (remove "quite" from grub cmd line) i can see:
init trap divide error rip:338c0058a4 rsp:7ffff88a2fa0 error:0
printk: 4821310 messages suppressed.
(and so on forever...)
to fix the problem i can boot from rescue cd and i have 2 option both working:
1) remove the offending partition from disk
2) erasing the content of the partition ( i just overwritten the first MB)
before erasing the content i saved the first MB of /dev/sdb2
(dd if=/dev/sdb2 of=sdb2.dump count=2048) and i tried to create
another parition in a new area of the disk, i copied
the first MB and i found the same error at boot but with different rsp offset.
i will attach the dump of the first MB because i think the problem i reproducible.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create an empy Linux partition (type 83)
2. fill it with the dirty first MB i will attach:
dd if=sdb2.dump of=/dev/sdXY count=2048
3. reboot the host
init hang (it seems to restart forever)
init should be able to boot even if some partition have dirty content
Created attachment 281531 [details]
first MB of dirty data that make init crash at boot
There's nothing in init that reads partitions - this is more likely the kernel
Is the e2fsprogs package up-to-date on this system?
e2fsprogs-1.40.2-10.fc8 is installed.
kernel version is kernel-126.96.36.199-63.fc8
(i run a system update few hours ago)
fyi: i tried to mount the root with roto=/dev/sda1 and root=LABEL=/12
but in both case i can hit the problem.
the rescue cd does not have problem with the dirty partition and is able
to find and mount automatically my root partition on the first drive.
let me know if you are able to reproduce the bug.
(In reply to comment #4)
> e2fsprogs-1.40.2-10.fc8 is installed.
> kernel version is kernel-188.8.131.52-63.fc8
> (i run a system update few hours ago)
> fyi: i tried to mount the root with roto=/dev/sda1 and root=LABEL=/12
> but in both case i can hit the problem.
> the rescue cd does not have problem with the dirty partition and is able
> to find and mount automatically my root partition on the first drive.
Current e2fsprogs is 1.40.2-11 and that should fix the bug.
i just did un update this morning and i have installed the new
i made a test now and i still get the error. What i don't understand is:
after the installation of e2fsprogs the initrd image was not touched
so initrd-184.108.40.206-63.fc8.img is still the one installed by the last kernel
update and if i get it right the error present when init is run and the
actual root (with the e2fsprogs utility) provided by the initrd image.
maybe the e2fsprogs-1.40.2-11.fc8 contain the fix but then i should manually
update the initrd image or wait for the next kernel package update.
can you confirm?
meanwhile i'll try to make some other test.
(In reply to comment #6)
> maybe the e2fsprogs-1.40.2-11.fc8 contain the fix but then i should manually
> update the initrd image or wait for the next kernel package update.
> can you confirm?
Yes, that needs to be done too.
There are directions for rebuilding the initrd here:
i just did another test now with the initrd image updated and
it works fine! no more hang at boot.
for me this bug can be closed. thank you very much
*** This bug has been marked as a duplicate of 398281 ***