[Bug 909560] New: Boot Failure: Remount Root and Kernel File System (readonly root file system)
http://bugzilla.opensuse.org/show_bug.cgi?id=909560 Bug ID: 909560 Summary: Boot Failure: Remount Root and Kernel File System (readonly root file system) Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: freespacer@gmx.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- My intention is to install openSUSE 13.2 (DVD-Installation on USB-Stick) beside an existing production system openSUSE 12.3. I install openSUSE 13.2 on /dev/sdb8 (ext4) without Grub2 boot loader because I want to use the Grub2 boot loader from openSUSE 12.3. /etc/fstab from openSUSE 13.2: UUID=757d8266-0144-4016-ab8c-51a741d2d530 swap swap defaults 0 0 UUID=10c0137f-ebb8-4ae3-9207-678ed9772597 / ext4 acl,user_xattr 1 1 After reboot I execute grub2-mkconfig in openSUSE 12.3 and get this part in grub.cfg for openSUSE 13.2: menuentry 'openSUSE 13.2 (x86_64) (auf /dev/sdb8)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-10c0137f-ebb8-4ae3-9207-678ed9772597' { insmod part_msdos insmod ext2 set root='hd2,msdos8' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos8 --hint-efi=hd1,msdos8 --hint-baremetal=ahci1,msdos8 --hint='hd2,msdos8' 10c0137f-ebb8-4ae3-9207-678ed9772597 else search --no-floppy --fs-uuid --set=root 10c0137f-ebb8-4ae3-9207-678ed9772597 fi linux /boot/vmlinuz root=/dev/sdb8 } After booting into the fresh installed openSUSE 13.2. It mount the root file system as readonly. I get from systemd journal for the related part: ... Dec 11 20:46:08 linux-bm94 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz root=/dev/sdb8 boot_delay=1000 ... Dec 11 20:46:08 linux-bm94 kernel: sdb: sdb1 sdb2 sdb3 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 sdb11 > Dec 11 20:46:08 linux-bm94 kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Dec 11 20:46:08 linux-bm94 kernel: EXT4-fs (sdb8): couldn't mount as ext3 due to feature incompatibilities Dec 11 20:46:08 linux-bm94 kernel: EXT4-fs (sdb8): couldn't mount as ext2 due to feature incompatibilities Dec 11 20:46:08 linux-bm94 kernel: EXT4-fs (sdb8): mounted filesystem with ordered data mode. Opts: (null) Dec 11 20:46:08 linux-bm94 kernel: VFS: Mounted root (ext4 filesystem) readonly on device 8:24. ... Dec 11 20:46:08 linux-bm94 systemd-remount-fs[143]: mount: can't find UUID=10c0137f-ebb8-4ae3-9207-678ed9772597 Dec 11 20:46:08 linux-bm94 systemd-remount-fs[143]: /bin/mount for / exited with exit status 1. ... Dec 11 20:46:10 linux-bm94 systemd[1]: Starting Remount Root and Kernel File Systems... Dec 11 20:46:10 linux-bm94 systemd-remount-fs[202]: mount: can't find UUID=10c0137f-ebb8-4ae3-9207-678ed9772597 Dec 11 20:46:10 linux-bm94 systemd[1]: Failed to start Remount Root and Kernel File Systems. Dec 11 20:46:10 linux-bm94 systemd[1]: Unit systemd-remount-fs.service entered failed state. ... Next step I try to add a boot parameter rootfstype=ext4 and get also a readonly file system. I get from systemd journal for the related part now: ... Dec 11 20:59:45 linux-bm94 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz root=/dev/sdb8 rootfstype=ext4 ... Dec 11 20:59:45 linux-bm94 kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Dec 11 20:59:45 linux-bm94 kernel: EXT4-fs (sdb8): mounted filesystem with ordered data mode. Opts: (null) Dec 11 20:59:45 linux-bm94 kernel: VFS: Mounted root (ext4 filesystem) readonly on device 8:24. ... Dec 11 20:59:45 linux-bm94 systemd[1]: Starting Remount Root and Kernel File Systems... Dec 11 20:59:45 linux-bm94 systemd-remount-fs[145]: mount: can't find UUID=10c0137f-ebb8-4ae3-9207-678ed9772597 Dec 11 20:59:45 linux-bm94 systemd[1]: Failed to start Remount Root and Kernel File Systems. ... Dec 11 20:59:47 linux-bm94 systemd-remount-fs[217]: mount: can't find UUID=10c0137f-ebb8-4ae3-9207-678ed9772597 Dec 11 20:59:47 linux-bm94 systemd[1]: Failed to start Remount Root and Kernel File Systems. ... I try to chroot into the openSUSE 13.2 system and run "zypper update". After executing of mkinitrd I reboot the system again but the root file system is still mounted as readonly. This is very annoying for me and openSUSE 13.2 is absolutely unusable with this installation method. As a contributor of packaging script for AMD Catalyst Driver I need several fresh installed openSUSE installation on a real hardware to verify the package build and the package installation of the fglrx driver. I attach both journctl log files. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=909560
--- Comment #1 from Sebastian Siebert
http://bugzilla.opensuse.org/show_bug.cgi?id=909560
--- Comment #2 from Sebastian Siebert
http://bugzilla.opensuse.org/show_bug.cgi?id=909560
Bruno Friedmann
http://bugzilla.opensuse.org/show_bug.cgi?id=909560
Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=909560
--- Comment #5 from Andrei Borzenkov
linux /boot/vmlinuz root=/dev/sdb8 }
You do not have initrd; is it intentional? (In reply to Bernhard Wiedemann from comment #4)
I think the 2nd problem is mount: can't find UUID=10c0137f-ebb8-4ae3-9207-678ed9772597
which comes from the --set=root in grub2
C'mon, grub root has nothing to do with OS root. It looks like the problem is that systemd-remount-root runs before udev coldplug: Dec 11 20:46:08 linux-bm94 systemd-remount-fs[143]: mount: can't find UUID=10c0137f-ebb8-4ae3-9207-678ed9772597 Dec 11 20:46:08 linux-bm94 systemd-remount-fs[143]: /bin/mount for / exited with exit status 1. Dec 11 20:46:09 linux-bm94 systemd[1]: Starting udev Coldplug all Devices... Dec 11 20:46:09 linux-bm94 systemd[1]: Starting udev Wait for Complete Device Initialization... UUID= expects /dev/disk/by-uuid links which are created by coldplugging. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=909560
--- Comment #6 from Sebastian Siebert
http://bugzilla.opensuse.org/show_bug.cgi?id=909560
--- Comment #7 from Andrei Borzenkov
Can we get this fix for openSUSE 12.3?
Please show "ls -l /boot /boot/grub /boot/grub2" from 13.2 partition. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=909560
Sebastian Siebert
(In reply to Sebastian Siebert from comment #6)
Can we get this fix for openSUSE 12.3?
Please show "ls -l /boot /boot/grub /boot/grub2" from 13.2 partition.
openSUSE 13.2 ll /boot/ /boot/grub /boot/grub2 /boot/: insgesamt 27180 lrwxrwxrwx 1 root root 1 11. Dez 01:15 boot -> . -rw-r--r-- 1 root root 1484 22. Okt 06:41 boot.readme -rw-r--r-- 1 root root 148204 22. Okt 08:06 config-3.16.6-2-desktop drwxr-xr-x 2 root root 4096 27. Nov 15:27 dracut drwxr-xr-x 2 root root 4096 11. Dez 01:15 grub drwxr-xr-x 4 root root 4096 11. Dez 01:17 grub2 lrwxrwxrwx 1 root root 23 11. Dez 01:18 initrd -> initrd-3.16.6-2-desktop -rw------- 1 root root 8936748 12. Dez 21:43 initrd-3.16.6-2-desktop -rw-r--r-- 1 root root 424448 26. Okt 10:12 message -rw-r--r-- 1 root root 885009 22. Okt 09:05 symtypes-3.16.6-2-default.gz -rw-r--r-- 1 root root 886028 22. Okt 09:14 symtypes-3.16.6-2-desktop.gz -rw-r--r-- 1 root root 858293 22. Okt 09:40 symtypes-3.16.6-2-xen.gz -rw-r--r-- 1 root root 309455 22. Okt 09:08 symvers-3.16.6-2-desktop.gz -rw-r--r-- 1 root root 516 22. Okt 09:08 sysctl.conf-3.16.6-2-desktop -rw-r--r-- 1 root root 3001645 22. Okt 08:52 System.map-3.16.6-2-desktop -rw-r--r-- 1 root root 6662593 22. Okt 09:15 vmlinux-3.16.6-2-desktop.gz lrwxrwxrwx 1 root root 24 11. Dez 01:18 vmlinuz -> vmlinuz-3.16.6-2-desktop -rw-r--r-- 1 root root 5679784 22. Okt 10:33 vmlinuz-3.16.6-2-desktop I have reinstall the grub2 packages on openSUSE 12.3 and try again grub2-mkconfig -o /boot/grub2/grub.cfg. Now the initrd was added in the boot entry. Very strange. It seems that I have a broken grub2 packages installed. Hm... In the YaST/zypper log I did not figured out from where the last grub2 packages comes. Anyway, now it was fixed. Thanks all for the hints in the right direction. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com