OpenSUSE 11.1 - invalid root file system

petrmatula · December 21, 2008, 4:49pm

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
$

marcus_magick · December 21, 2008, 5:07pm

Can you be more specific about your hardware? What chipset/controller are your drives connected to?

Are you traying to use fakeBIOS or you’ve created linux software raid volumes?

petrmatula · December 21, 2008, 5:20pm

software linux raid
2x sata hdd samsung 1TB
mb: VIA CX700M Chipset
http://http://www.jetway.com.tw/jw/ipcboard_view.asp?productid=387&proname=J7F5M1G2E-VDE

petrmatula · December 21, 2008, 5:26pm

https://bugzilla.novell.com/show_bug.cgi?id=460917

petrmatula · December 22, 2008, 1:13am

After booting from rescue system from 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

petrmatula · December 22, 2008, 11:27am

# 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

user · December 22, 2008, 4:40pm

I have the same problem. with my raid 1. However, in my case when I start the machine the Grub load and display the error mention here, I press “Enter” then type “exit” it will exit the busybox and resume the boot process as usual.

Any other workaround to fix this issue?

Mamdoh

user · December 22, 2008, 7:08pm

Also, some time I do the follwoing
Also some time I do the following:

Press Enter
mount=break
Press Enter
type Exit
5 Press Enter

Mamdoh

petrmatula · December 23, 2008, 11:45am

From boot.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

petrmatula · December 24, 2008, 4:01pm

This problem looks similarly.
%between%

user · December 29, 2008, 2:55am

petrmatula schrieb:
> openSUSE 11.1 32 bit DVD
> md0 RAID1 swap
> md1 RAID1 /

I always thought this wasn’t even supposed to work, and have
therefore created a non-RAID /boot partition if the root
partition was to reside on a RAID. Of course if YaST let you
create such a configuration it should work, too, but perhaps
the bug is really with YaST not asking for a separate /boot
partition in this case anymore.

HTH
T.

user · December 29, 2008, 6:05pm

i have the same problem, but i have a non-raid /boot partition, a raid0 (striped) root partition (md1) and a raid1 (mirrored) /home partition (md0). funnily enough, i just pressed ‘ctl-alt-del’ each time the boot failed and after about 4/5 attempts it booted ok.

btw i am running 11.1 x86_64.

user · December 29, 2008, 6:39pm

the patch at https://bugzilla.novell.com/show_bug.cgi?id=445490 (comment #19) seems to work

open a terminal
su to root
edit /lib/mkinitrd/scripts/boot-md.sh
change


        if  "$md_dev" ] ; then
            /sbin/mdadm $mdconf --auto=md $md_dev || /sbin/mdadm -Ac partitions $mdarg --auto=md $md_dev
        fi
        wait_for_events
fi

to…


        if  "$md_dev" ] ; then
            /sbin/mdadm $mdconf --auto=md $md_dev || /sbin/mdadm -Ac partitions $mdarg --auto=md $md_dev
        fi
        sleep 1
        echo change > /sys/block/md$md_minor/uevent
        wait_for_events
fi

run mkinitrd
reboot

hardy59 · January 1, 2009, 12:55pm

First: A Happy New Year to everybody here!

I do experience a very similar problem!
On the first reboot after installation (from 11.1 (32) DVD) I also do get some mdraid and file system errors and finally this one:

invalid root filesystem -- exiting to /bin/sh

My configuration is:

DELL Optiplex 8200
1 IDE disk on internal IDE controller
3 WD6400AAKS 640GB SATA2 disks connected to a Promise SATA300 TX4 (rev 02) controller (PDC40718)
On the IDE I just created the \boot partition (booting from the Promise controller seems not to be supported by my BIOS)
On each SATA disk I did create the following primary partitions during setup:
- sd[abc]1: 2 GB, swap
- sd[abc]2 20 GB, FileSystem: xFD (Linux RAID)
- sd[abc]3 570 GB, FileSystem: xFD (Linux RAID)

From these Linux Raid partitions I did create the following RAID5 disks:
- md0: RAID5 (sda2, sdb2, sdc2), 40 GB, Ext3, Mount:
- md1: RAID5 (sda3, sdb3, sdc3), 1.1 TB, Ext3, Mount: \home

After the first installation failed, I deleted all partition tables on the SATA disks and tried again with similar settings, but failed again.

When I looked into the actual partitioning with the partitioning tool provided in the emergency system (by selecting “Repair Installed System”), I found that none of the raid disks has been formatted at all… But I know that I did select ext3 when I did create the md disks…

Any comments are appreciated very much!

Cheers,
Hardy

hardy59 · January 2, 2009, 10:33am

I forgot to mention that hitting Ctrl+d (as described in the before mentioned https://bugzilla.novell.com/show_bug.cgi?id=445490)
helps in my case too. Nevertheless I do hope for a real fix of that bug.
Cheers,
Hardy

mhenry676 · January 10, 2009, 2:43pm

OOOO I HATE BUGS!!!

At least this fixed it, for now…

Thank you big_red for mentioning…

run mkinitrd

that bug#19 did not.

user · March 22, 2009, 9:56pm

Hi, I’m having the same problem.

Trying to install OpenSUSE 11.1 with a software raid 1 on a new Dell Inspiron with the 2.2GHz Celeron and 2 GB ram.

Onto 2 WD Green 500GB SATA drives, so far I’ve tried following the partition suggestions on this page here: How to install openSUSE on software RAID - openSUSE and I’ve also tried just partitioning a separate, 1GB non-raid swap partition on each disk and then creating 1 huge root partition from the remaining space on both disks.

Each time it complains that the raid is not clean, and then after fiddling around a bit, drops me at a severely crippled bash prompt. I can’t even su to root to shutdown because the sbin folder doesn’t contain su or shutdown.

I also tried allowing the installation disk to repair the damage, and this looked promising as I saw it found and seemed to repair some errors in fstab. But the result was the same.

Needless to say, the fix mentioned above that says to edit a file in /lib/mkinitrd/scripts is no use to me as no /lib/mkinitrd/ directory exists on this computer as yet.

Anyone have another suggestion?

user · April 8, 2009, 9:32pm

i wish i had found this issue earlier… i thought i had a bad hard drive dang bugs!