[Bug 729667] New: grub error after each kernel-update: "Error 16: Inconsistent filesystem structure"
https://bugzilla.novell.com/show_bug.cgi?id=729667 https://bugzilla.novell.com/show_bug.cgi?id=729667#c0 Summary: grub error after each kernel-update: "Error 16: Inconsistent filesystem structure" Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i686 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: Yarny@public-files.de QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Short summary: I'm running 4 32bit machines with openSUSE 11.4 and each time there is a kernel update, at least one or two of those (different ones each time) refuse to (re)boot afterwards. Grub shows its menu for a few seconds and then immediately says "Error 16: Inconsistent filesystem structure". On each machine, the boot partition is ~80MiB ext2. fsck.ext2 (from LiveCD) says everything's OK. Recreating the boot partition with mkfs.ext2 fixes the problem until the next update arrives. A bit more details. (This is mostly a copy from URL:http://forums.opensuse.org/forums/english/get-technical-help-here/instal...) Here's what I did/observed this Tuesday: * "zypper update", which (besides other stuff) listed kernel-default. I confirm. * After this is done, I did "shutdown -r now" to reboot. * Grub shows its menu (text mode only, I don't have the graphical bootsplash installed). After 3 sec or so timeout, it tries to boot as always, but immediately says "Error 16: Inconsistent filesystem structure". Unfortunately, this problem occurs only randomly. I'm running 4 64bit machines and 4 32bit machines. Up to now it happened only on 32bit machines and at every kernel-update, it occurs on 1 or 2 of my machines. To fix this, I have to boot from external media and recreate the broken boot-partition (i.e. copy files to some temporary place and do a "mkfs.ext2 /dev/sda1", then copy back on the new filesystem). Then I mount everything, chroot in my to-be-fixed system and run "grub-install". After that I can boot from harddisk again. The filesystem which is inconsistent according to grub is ok according to fsck.ext2. I checked this before rewriting the filesystem with mkfs.ext2. The system where it happened yesterday contains only one harddisk with two partitions: sda1 is /boot, ext2, 80MiB; sda2 is a luks-encrypted lvm container. Partition table is gpt, grub is installed in the mbr (I think). The way I installed these systems I a bit unorthodox: I basically set up the partitioning scheme by hand and mounted everything, then did a "zypper -R /mnt/root install ..". While this might contribute to the triggering of this behavior, it still believe there is an underlying bug that is causing this mess. I have no other explanation for this to happen only randomly, but not always. In the last months I always just "fixed" this as fast as possible to move on. On Tuesday I made a copy of /dev/sda1 ("cat /dev/sda1 > file") right after booting my rescue system. I also updated two other 32bit machines without problems. Another 32bit machine is still awaiting the kernel update (I did not "zypper update" yet). Sadly, I don't see an obvious way to reliably reproduce the problem (without waiting for the next kernel update). I can share my boot-partition-image with you which I created before fixing it, also log-files and other data. But since all 4 32bit machines are production systems my ability to do experimentation with them is limited. But if it would be helpful I can try to collect more data when updating my remaining not-updated machine. Reproducible: Sometimes -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c2
Torsten Duwe
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c3
--- Comment #3 from Yarny Yarny
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c4
--- Comment #4 from Yarny Yarny
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c5
--- Comment #5 from Yarny Yarny
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c6
--- Comment #6 from Yarny Yarny
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c7
--- Comment #7 from Yarny Yarny
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c8
--- Comment #8 from Yarny Yarny
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c9
Yarny Yarny
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c10
--- Comment #10 from Yarny Yarny
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c11
Yarny Yarny
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c12
Torsten Duwe
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c13
--- Comment #13 from Yarny Yarny
I found the time now to reproduce this Did you use oS 11.4 or 12.1 for this? I couldn't reproduce it with oS 12.1. Maybe it got fixed somehow in 12.1?
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c14
--- Comment #14 from Torsten Duwe
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c15
--- Comment #15 from Torsten Duwe
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c16
--- Comment #16 from Torsten Duwe
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c17
--- Comment #17 from Yarny Yarny
The bug is reproducible entirely within the partition image [..] Ah, I thought you used the script of Comment #10.
I applied fsck.ext2 of openSUSE 12.1 and 12.2 (last RC) to the disk image and they didn't find any problems. So it seems to be a grub problem. I attached the disk image (plus MBR) to an openSUSE 12.1 machine as /dev/sdb and modified the menu.lst on /dev/sda to boot from the partition on /dev/sdb1=(hd1,0). The grub of openSUSE 12.1 had no problems loading the kernel and initrd of the bacoc partition. My humble interpretation is that there has been a bug in grub's ext2 filesystem parsing module in openSUSE 11.4, but it got fixed in openSUSE 12.1's grub. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c18
--- Comment #18 from Yarny Yarny
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c19
Olaf Hering
This bug report is now inactive for more than a year. I'm haven't seen the bug since I moved to openSUSE 12.1. openSUSE 11.4 is no longer maintained.
Should we close this report (as FIXED/WONTFIX/NORESPONSE)?
I still see this with Factory grub. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c20
--- Comment #20 from Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=729667
https://bugzilla.novell.com/show_bug.cgi?id=729667#c21
--- Comment #21 from Olaf Hering
participants (1)
-
bugzilla_noreply@novell.com