[Bug 786042] New: 20% of the time wrong drive mounted as / (root)
https://bugzilla.novell.com/show_bug.cgi?id=786042 https://bugzilla.novell.com/show_bug.cgi?id=786042#c0 Summary: 20% of the time wrong drive mounted as / (root) Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: a.vankaam@chello.nl QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.10.289 Version/12.02 I have 2 identical drives: Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ca231 Device Boot Start End Blocks Id System /dev/sda1 63 4209029 2104483+ 82 Linux swap / Solaris /dev/sda2 * 4209030 46154744 20972857+ 83 Linux /dev/sda3 46154745 675308339 314576797+ 83 Linux /dev/sda4 675308340 976768064 150729862+ 83 Linux Disk /dev/sdb: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ca231 Device Boot Start End Blocks Id System /dev/sdb1 63 4209029 2104483+ 82 Linux swap / Solaris /dev/sdb2 * 4209030 46154744 20972857+ 83 Linux /dev/sdb3 46154745 675308339 314576797+ 83 Linux /dev/sdb4 675308340 976768064 150729862+ 83 Linux sdb is simply a copy (made with g4l) which is roughly a week older, I know it's not raid and such but I like it that way, I can mess the whole thing up and simply copy sdb back to sda like nothing has changed and fiddle some more :) sdb is thus never used, grub2 does show it as the 3rd and 4th entry, I can remove it but every update when grub2-mkconfig runs it comes back so I don't really bother about it showing up. /etc/fdisk shows: /dev/disk/by-id/ata-WDC_WD5000AAKS-00D2B0_WD-WCASYA363695-part1 swap swap defaults 0 0 /dev/disk/by-id/ata-WDC_WD5000AAKS-00D2B0_WD-WCASYA363695-part2 / ext4 acl,user_xattr 1 1 /dev/disk/by-id/ata-WDC_WD5000AAKS-00D2B0_WD-WCASYA363695-part4 /backup ext4 defaults 1 2 /dev/disk/by-id/ata-WDC_WD5000AAKS-00D2B0_WD-WCASYA363695-part3 /home ext4 defaults 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 the normal bootup will show: Filesystem 1K-blocks Used Available Use% Mounted on rootfs 20641788 6345804 13247344 33% / devtmpfs 3048640 4 3048636 1% /dev tmpfs 3057420 0 3057420 0% /dev/shm tmpfs 3057420 744 3056676 1% /run /dev/sda2 20641788 6345804 13247344 33% / tmpfs 3057420 0 3057420 0% /sys/fs/cgroup tmpfs 3057420 744 3056676 1% /var/lock tmpfs 3057420 744 3056676 1% /var/run tmpfs 3057420 0 3057420 0% /media /dev/sda4 148364860 25412476 115415892 19% /backup /dev/sda3 309639060 98609044 195301180 34% /home now I would say 2 out of 10 boots grub2 will mount /dev/sdb2 as / and then continue with sda3 and sda4. This will give weird results like you just done a kernel update, reboot and system won't boot as sdb2 (which is a week old) does not have that kernel, reset and it will boot as it then mounts sda2. I can't reproduce it on demand but if I reboot enough times it will happen, not sure what more config files are needed but will gladly post them Reproducible: Sometimes Steps to Reproduce: 1. reboot, I would say 2 out of 10 times it will mount sdb2 as root 2. 3. Actual Results: as written once sdb2 is mounted system will boot using that root system, since its a copy of sda2 it will thus mount /sda3 and /sda4 Expected Results: it should leave sdb2 alone, sda2 is the root system to boot from -- 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=786042 https://bugzilla.novell.com/show_bug.cgi?id=786042#c Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsrain@suse.com |mchang@suse.com -- 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=786042 https://bugzilla.novell.com/show_bug.cgi?id=786042#c1 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |a.vankaam@chello.nl --- Comment #1 from Michael Chang <mchang@suse.com> 2012-10-23 04:54:54 UTC --- Did you try disabling os-prober? $ vim /etc/default/grub GRUB_DISABLE_OS_PROBER=true It should be os-prober which added sdb entry to the config. It considered it as an bootable distribution but not an redundancy, as no way to tell it. Let me know if you have problem or not with that option set? Thanks. -- 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=786042 https://bugzilla.novell.com/show_bug.cgi?id=786042#c2 --- Comment #2 from Michael Chang <mchang@suse.com> 2012-10-23 09:32:17 UTC --- Remember to run grub2-mkconfig -o /boot/grub2/grub.cfg after you making changes to /etc/default/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=786042 https://bugzilla.novell.com/show_bug.cgi?id=786042#c3 --- Comment #3 from Alexander van Kaam <a.vankaam@chello.nl> 2012-10-23 14:28:17 UTC --- hello Michael GRUB_DISABLE_OS_PROBER=true removes the sdb from the list of option in Grub2, thank you for that little gem of info :) however on the 3rd reboot it mounted sdb2 as root again, so that does not remove this strange behavior. I will add the new grub.cfg and device.map to the call just in case they are helpfull. -- 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=786042 https://bugzilla.novell.com/show_bug.cgi?id=786042#c4 --- Comment #4 from Alexander van Kaam <a.vankaam@chello.nl> 2012-10-23 14:29:13 UTC --- Created an attachment (id=510563) --> (http://bugzilla.novell.com/attachment.cgi?id=510563) grub.cfg after GRUB_DISABLE_OS_PROBER=true -- 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=786042 https://bugzilla.novell.com/show_bug.cgi?id=786042#c5 --- Comment #5 from Alexander van Kaam <a.vankaam@chello.nl> 2012-10-23 14:29:48 UTC --- Created an attachment (id=510564) --> (http://bugzilla.novell.com/attachment.cgi?id=510564) default device.map -- 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=786042 https://bugzilla.novell.com/show_bug.cgi?id=786042#c6 --- Comment #6 from Michael Chang <mchang@suse.com> 2012-10-24 08:32:05 UTC --- It's not grub2 but kernel who mounts the root file system. And your problem should be completely avoided as in the grub2 config, UUID is used to specify the root device to kernel. root=UUID=7c3692bd-0acf-49d0-bb08-08398c60b51e Is it only happened by cyclic "reboot"? Did cold start (power off your machine and power on) could reproduce the problem? The problem is somehow bios related, but will need help from kernel or udev guys to diagnose why mount by UUID could point to another disk .. -- 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=786042 https://bugzilla.novell.com/show_bug.cgi?id=786042#c7 --- Comment #7 from Michael Chang <mchang@suse.com> 2012-10-24 08:46:08 UTC --- Probably we could find some clue from output of "udisksctl dump" on normal and abnormal case. -- 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=786042 https://bugzilla.novell.com/show_bug.cgi?id=786042#c8 --- Comment #8 from Alexander van Kaam <a.vankaam@chello.nl> 2012-10-24 15:04:09 UTC --- hello Michael - it happens on a "cold" and on a "warm" bootup, there is little difference - I spend yesterday installing 12.2 on an older PC, this has the same sda/sdb setup but also an sdc which holds an old windows xp install. On this PC I can create the exact same behaviour. - this PC is an Asus P6T, I would say 3 years old - the older PC is an Asus P5W, I would say 6-7 years old - they got little incommen except an AMI bios, different hardware for the rest. will attach the 2 files you asked for. -- 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=786042 https://bugzilla.novell.com/show_bug.cgi?id=786042#c9 --- Comment #9 from Alexander van Kaam <a.vankaam@chello.nl> 2012-10-24 15:05:08 UTC --- Created an attachment (id=510715) --> (http://bugzilla.novell.com/attachment.cgi?id=510715) sda2 mounted -- normal -- 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=786042 https://bugzilla.novell.com/show_bug.cgi?id=786042#c10 --- Comment #10 from Alexander van Kaam <a.vankaam@chello.nl> 2012-10-24 15:05:38 UTC --- Created an attachment (id=510716) --> (http://bugzilla.novell.com/attachment.cgi?id=510716) sdb2 mounten -- error -- 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=786042 https://bugzilla.novell.com/show_bug.cgi?id=786042#c11 --- Comment #11 from Alexander van Kaam <a.vankaam@chello.nl> 2012-10-24 17:04:25 UTC --- hi Michael, your comment about root=UUID=7c3692bd-0acf-49d0-bb08-08398c60b51e got me thinking and with the help of the "udisksctl dump" I found that because sdb is a copy of sda this means that the UUID of sda2 is no longer unique and the "udisksctl dump" showed that. So I searched a bit more and found this option: GRUB_DISABLE_LINUX_UUID=true this still uses the UUID in most of the grub.cfg lines except in the linux line, that changed to: linux /boot/vmlinuz-3.4.11-2.16-desktop root=/dev/sda2 and that solved the issue. I am not sure if it can be considered a bug, but when using a redundancy disk like I do UUID is no longer unique unlike for example /dev/disk/by-id is. for my own I will write down to always use: GRUB_DISABLE_OS_PROBER=true GRUB_DISABLE_LINUX_UUID=true -- 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=786042 https://bugzilla.novell.com/show_bug.cgi?id=786042#c12 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|a.vankaam@chello.nl | Resolution| |FIXED --- Comment #12 from Michael Chang <mchang@suse.com> 2012-10-25 08:06:49 UTC --- Hi Alexander Glad to hear that you solved the issue. Lesson learned for me too. Just for your information, upstream had patch in reviewing that will allow you to use by-label or by-path device name. For now you could only disable UUID and use kernel device name. http://lists.gnu.org/archive/html/grub-devel/2012-09/msg00034.html Meanwhile, YaST2 bootloader had offered checkboxs to disable os-prober in factory, but it's not available in 12.2. I set this one to resolved, feel free to open if you think anything different. Thanks. -- 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.
participants (1)
-
bugzilla_noreply@novell.com