Bugzilla – Bug 460917
after installaton - nvalid root file system - exiting to /bin/sh
Last modified: 2009-07-17 12:50:48 UTC
--- SYSTEM: --- A) SMASUNG on ATA B) and two SEAGATEs on SATA in RAID0 C) openSUSE 11.1 GM 64 bit DVD --- ERROR --- After installaton process on /dev/md1 witn "/" system reboots and shows in console mode this information: _____________________ ... nvalid root file system - exiting to /bin/sh $ _____________________ wats going on? :(
Created attachment 261442 [details] /var/log/YAST2 from /dev/md1 installation directory
"invalid root file system - exiting to /bin/sh" not "nvalid root file system - exiting to /bin/sh"
openSUSE 11.1 32 bit DVD md0 RAID1 swap md1 RAID1 / After installation on /dev/md1 with "/" system reboots and shows: md: md1:raid array is not clean -- starting backround c raid1: raid set md1 active with 2 out of 2 mirrors md1: bitmap initialized from dist: read 30/30 pages, set 700520 bits created bitmap (465 pages) for md1 mdadm: /dev/md/1 hashem started with 2 drives Trying normal resume from /dev/md0 resume device /dev/md0 not found (ignor Trying normal resume from /dev/md0 resume device /dev/md0 not found (ignor Waiting for device /dev/md1 to appear: ok invalid root file system -- exiting to /bin/sh $
After booting rescue system from inst. dvd server3:~ # mdadm --detail /dev/md0 /dev/md0: Version : 1.00 Creation Time : Sun Dec 21 23:59:58 2008 Raid Level : raid1 Array Size : 2104500 (2.01 GiB 2.16 GB) Used Dev Size : 2104500 (2.01 GiB 2.16 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Mon Dec 22 00:17:09 2008 State : active Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Name : linux:0 UUID : 76a8e1d7:67c5eee5:38d2763a:35e65bc2 Events : 4 Number Major Minor RaidDevice State 0 8 1 0 active sync /dev/sda1 1 8 17 1 active sync /dev/sdb1 server3:~ # mdadm --detail /dev/md1 /dev/md1: Version : 1.00 Creation Time : Sun Dec 21 23:59:59 2008 Raid Level : raid1 Array Size : 974647348 (929.50 GiB 998.04 GB) Used Dev Size : 1949294696 (1858.99 GiB 1996.08 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Mon Dec 22 00:18:14 2008 State : active, resyncing Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Rebuild Status : 6% complete Name : linux:1 UUID : 34d671c8:c0aa1484:bc9d66af:5e963bbd Events : 5 Number Major Minor RaidDevice State 0 8 2 0 active sync /dev/sda2 1 8 18 1 active sync /dev/sdb2 server3:~ # cat /proc/mdstat Personalities : [raid1] [raid0] [raid6] [raid5] [raid4] md0 : active raid1 sda1[0] sdb1[1] 2104500 blocks super 1.0 [2/2] [UU] bitmap: 0/9 pages [0KB], 128KB chunk md1 : active raid1 sda2[0] sdb2[1] 974647348 blocks super 1.0 [2/2] [UU] [=>...................] resync = 6.3% (61884032/974647348) finish=234.8min speed=64774K/sec bitmap: 436/465 pages [1744KB], 1024KB chunk unused devices: <none> server3:~ # fdisk -l Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00041969 Device Boot Start End Blocks Id System /dev/sda1 * 2 263 2104515 fd Linux raid autodetect /dev/sda2 264 121601 974647485 fd Linux raid autodetect Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00052e3b Device Boot Start End Blocks Id System /dev/sdb1 2 263 2104515 fd Linux raid autodetect /dev/sdb2 264 121601 974647485 fd Linux raid autodetect Disk /dev/sdc: 750.1 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x35125939 Disk /dev/sdc doesn't contain a valid partition table Disk /dev/md1: 998.0 GB, 998038884352 bytes 2 heads, 4 sectors/track, 243661837 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk identifier: 0x00000000 Disk /dev/md1 doesn't contain a valid partition table Disk /dev/md0: 2155 MB, 2155008000 bytes 2 heads, 4 sectors/track, 526125 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk identifier: 0x00000000 Disk /dev/md0 doesn't contain a valid partition table
# e2fsck /dev/md1 e2fsck 1.41.1 (01-Sep-2008) /dev/md1: clean, 56103/60915712 files, 4159180/243661837 blocks # dumpe2fs /dev/md1 dumpe2fs 1.41.1 (01-Sep-2008) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: da5cdf7f-025e-4c48-8493-45a4f2c36602 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype sparse_super large_file Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 60915712 Block count: 243661837 Reserved block count: 12183091 Free blocks: 239502657 Free inodes: 60859609 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 965 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Filesystem created: Sun Dec 21 23:00:01 2008 Last mount time: Mon Dec 22 00:30:06 2008 Last write time: Mon Dec 22 00:33:11 2008 Mount count: 3 Maximum mount count: -1 Last checked: Sun Dec 21 23:00:01 2008 Check interval: 0 (<none>) Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 671f60a8-0a11-417e-a548-99caad3271f4 Journal backup: inode blocks Journal size: 128M
When I start the machine the Grub load and display the error mention here, I press "Enter" then type "exit" it will resume the boot process as usual. Any other workaround to fix this issue?
http://forums.opensuse.org/install-boot-login/402495-opensuse-11-1-invalid-root-file-system.html#post1913439
After booting boot.msg : Boot logging started on /dev/tty1(/dev/console) at Mon Dec 22 19:53:43 2008 mdadm: /dev/md/1 has been started with 2 drives. Trying manual resume from /dev/md0 resume device /dev/md0 not found (ignoring) Trying manual resume from /dev/md0 resume device /dev/md0 not found (ignoring) Waiting for device /dev/md1 to appear: ok invalid root filesystem -- exiting to /bin/sh $ $ $ $ $ exit exit Mounting root /dev/md1 Boot logging started on /dev/tty1(/dev/console (deleted)) at Mon Dec 22 19:54:04 2008 done Starting udevd: done Loading drivers, configuring devices: done Loading required kernel modules doneActivating swap-devices in /etc/fstab... failedChecking root file system... fsck 1.41.1 (01-Sep-2008) /dev/md1: clean, 131929/60915712 files, 4692702/243661837 blocks doneSetting up the hardware clockdone Activating device mapper... done Starting MD Raid mdadm: /dev/md/0 has been started with 2 drives. failed Checking file systems... fsck 1.41.1 (01-Sep-2008) donedone Mounting local file systems... /proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) nothing was mounted doneLoading fuse module done Swap problem # cat /proc/mdstat Personalities : [raid1] [raid0] [raid6] [raid5] [raid4] md0 : active (auto-read-only) raid1 sda1[0] sdb1[1] 2112504 blocks super 1.0 [2/2] [UU] bitmap: 0/9 pages [0KB], 128KB chunk md1 : active raid1 sda2[0] sdb2[1] 974647348 blocks super 1.0 [2/2] [UU] bitmap: 320/465 pages [1280KB], 1024KB chunk unused devices: <none # swapon -s Filename Type Size Used Priority /dev/md0 partition 2112496 0 -1
longer log <3>Unable to find swap-space signature <6>EXT3 FS on md1, internal journal <6>device-mapper: uevent: version 1.0.3 <6>device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com <6>md: md0 stopped. <6>md: bind<sdb1> <6>md: bind<sda1> <6>raid1: raid set md0 active with 2 out of 2 mirrors <6>md0: bitmap initialized from disk: read 1/1 pages, set 0 bits <6>created bitmap (9 pages) for device md0 <6>loop: module loaded <4>fuse init (API version 7.9) Kernel logging (ksyslog) stopped. Kernel log daemon terminating. Boot logging started on /dev/tty1(/dev/console) at Tue Dec 23 09:49:47 2008 mdadm: /dev/md/1 has been started with 2 drives. Trying manual resume from /dev/md0 resume device /dev/md0 not found (ignoring) Trying manual resume from /dev/md0 resume device /dev/md0 not found (ignoring) Waiting for device /dev/md1 to appear: ok invalid root filesystem -- exiting to /bin/sh $ $ exit exit Mounting root /dev/md1 Boot logging started on /dev/tty1(/dev/console (deleted)) at Tue Dec 23 09:51:15 2008 done Starting udevd: done Loading drivers, configuring devices: done Loading required kernel modules doneActivating swap-devices in /etc/fstab... failedChecking root file system... fsck 1.41.1 (01-Sep-2008) /dev/md1: clean, 131936/60915712 files, 4692702/243661837 blocks doneSetting up the hardware clockdone Activating device mapper... done Starting MD Raid mdadm: /dev/md/0 has been started with 2 drives. failed Checking file systems... fsck 1.41.1 (01-Sep-2008) donedone Mounting local file systems... /proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) nothing was mounted doneLoading fuse module done Mounting fuse control filesystemdone <notice>killproc: kill(614,29) Creating /var/log/boot.msg doneSetting current sysctl status from /etc/sysctl.conf net.ipv4.icmp_echo_ignore_broadcasts = 1 net.ipv4.conf.all.rp_filter = 1 fs.inotify.max_user_watches = 65536 net.ipv4.conf.default.promote_secondaries = 1 net.ipv4.conf.all.promote_secondaries = 1 done Activating remaining swap-devices in /etc/fstab... doneMounting securityfs on /sys/kernel/security done Loading AppArmor profiles Enabling syn flood protectiondone Disabling IP forwardingdone done Setting up hostname 'server3'done Setting up loopback interface lo lo IP address: 127.0.0.1/8 IP address: 127.0.0.2/8 done done System Boot Control: The system has been set up Failed features: boot.md Skipped features: boot.cycle System Boot Control: Running /etc/init.d/boot.local
Created attachment 262218 [details] boot.msg
Created attachment 262219 [details] YaST2 logs
Dear Petr Matula, I am getting confused. What are those attachments? I know that they are the log, but am I suppose to do something with them to solve my problem or does it contains a solutions and I don't see it? I look forward to hearing from you Mamdoh
https://bugzilla.novell.com/show_bug.cgi?id=445490
I am experiencing a similar issue. Configuration details: OpenSUSE 11.1 final (x86) Root partition RAID1, ReiserFS Issue was repeatable on a partition I had updated from OpenSUSE 11.0 using "zypper dup", but not on a partition I had installed from scratch (network install). On further investigation, I found that the new install partition's initrd contained features resume.userspace and resume.kernel, but the updated install partition's initrd did not have these features, due to the absence of package "suspend". When I added these features to the updated partition's initrd, the issue stopped occurring (at least consistently). Apparently in my configuration the time consumed in processing the resume feature is enough alter the results of the race, even when using the "noresume" kernel parameter. I also was able to work around the issue by adding 2 lines to /lib/mkinitrd/scripts/boot-md.sh then running mkinitrd, as described in bug 445490, comment 19. The file to be modified is slightly different in 11.1 final: The line containing "wait_for_events" has been removed. For 11.1 final the 2 lines are inserted between the second-to-last "fi" and the last "fi" in the file.
"mee too" on openSuSE 11.1 final (x86_64), Root partition on Raid1, ext3, upgraded from openSuSE 10.2 (x86_64) (yes, this is weired, but works) the issue seems to be fixed after adding the package "suspend"
(In reply to comment #15 from Christian Fertig) > "mee too" > > on openSuSE 11.1 final (x86_64), Root partition on Raid1, ext3, upgraded from > openSuSE 10.2 (x86_64) (yes, this is weired, but works) > > the issue seems to be fixed after adding the package "suspend" > "suspend" don't impact the issue (for me)
*** This bug has been marked as a duplicate of bug 445490 ***
I had the same problem (after upgrade, the system was waiting for CTRL-D to continue) adding to boot-md.sh: sleep 1 echo change > /sys/block/md$md_minor/uevent wait_for_events solved the problem. I have the lastest patches from OpenSUSE maybe someone could add this ?