Bad message in /var/log/boot.msg... but arrays are working- how?



Hi all,

I started using SuSE since around v8 and find it is really showing it's
true colours now. Finally using Linux on my desktop and as one of my
server OSs of choice...

However I just built an OpenSuSE 10.0 box as a Samba server; running 2x
200GB SATA drives in a mirrored RAID as /dev/sda and /dev/sdb.

The box (a Shuttle SN61G2) runs a silicon Image RAID Sil3112 fake raid
controller with its BIOS configured as a 'RAID' controller within the
machine's BIOS. I've found the OpenSuSE installation goes by the book
on this type of kit, allowing configuring of the disks and arrays as it
should.

The only trouble is that on boot this is displayed-

Output from /var/log/boot.msg:
------------------------------------------------
Starting Firewall Initialization (phase 1 of 2) SuSEfirewall2: Warning:
ip6tables does not support state matching. Extended IPv6 support
disabled.
done
Creating /var/log/boot.msg
doneRestore device permissionsdone
<notice>killproc: kill(2099,29)
Disk /dev/md4 doesn't contain a valid partition table
Disk /dev/md3 doesn't contain a valid partition table
Disk /dev/md2 doesn't contain a valid partition table
Disk /dev/md1 doesn't contain a valid partition table
Activating remaining swap-devices in /etc/fstab...
doneSetting current sysctl status from /etc/sysctl.conf
------------------------------------------------
End output from /var/log/boot.msg:

All the erring arrays are formatted during install with reiserfs but
are running fine. The fdisk -l outputs are the same for both /dev/sda
and /dev/sdb. mdadm reports healthy in every respect and I can rebuild,
format, write files and so on without a problem. There seems to be no
other ill-effect and all checks work out so far.

You may notice /dev/md0 missing from the above. It is mounted as /boot
and is the only array that is not reiserfs (as I made it ext2 as is my
usual habit) and my swap space is not running as a RAID, instead it is
split (both enabled) accross 2 identical partitions on both drives.
AFAIK this is not unusual- but I get this problem. At first I though it
was me but I have rebuilt the machine 3 times now and each time it
displays the above errors in the boot message with no ill-effect.

I am worried as I need to be able to rebuild these arrays should a
problem occur. Is the data unsafe or is the message turning up because
some process is not reading the partition tables in the reiserfs
formatted arrays properly?

This all happens following a vanilla install (2.6.13-15.3) and also
following a live update for all the latest patches including kernel
2.6.13-15.8. I can't find any other errors

I've looked through the OpenSuse buglists, searched the FAQs, site and
web and find nothing similar anywhere. Can anyone suggest anything else
for me to check?

fstab is fine

Many thanks in advance for any hints given... :) Nick

FYI: Output from cat /etc/fstab:
/dev/md1 / reiserfs acl,user_xattr
1 1
/dev/md0 /boot ext2 acl,user_xattr
1 2
/dev/md4 /home reiserfs acl,user_xattr
1 2
/dev/md2 /usr reiserfs acl,user_xattr
1 2
/dev/md3 /var reiserfs acl,user_xattr
1 2
/dev/sda2 swap swap defaults
0 0
/dev/sdb2 swap swap defaults
0 0
proc /proc proc defaults
0 0
sysfs /sys sysfs noauto
0 0
usbfs /proc/bus/usb usbfs noauto
0 0
devpts /dev/pts devpts mode=0620,gid=5
0 0
/dev/cdrom /media/cdrom subfs
noauto,fs=cdfss,ro,procuid,

linux:~ # cat /etc/raidtab
# autogenerated /etc/raidtab by YaST2

raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
chunk-size 4
device /dev/sda1
raid-disk 0
device /dev/sdb1
raid-disk 1

raiddev /dev/md1
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
device /dev/sdb3
raid-disk 0
device /dev/sda3
raid-disk 1

(and so on for the other 3 arrays)

.



Relevant Pages

  • LVM on SW RAID for sarge - success
    ... I've just had success migrating Debian Sarge to root on LVM on RAID. ... First make sure the SCSI BIOS boots from the first disk. ... I made reiserfs on all the filesystem partitions and completed the ... The remaining two disks were partitioned and used to create RAID arrays ...
    (Debian-User)
  • Re: software raid: replace failing HD
    ... > wouldn't recommend you try hot swapping normal SCSI drives (50- or ... Feb 1 11:28:02 myservername kernel: md: updating md3 RAID superblock on ... Feb 1 11:28:02 myservername kernel: md3: no spare disk to reconstruct ... arrays. ...
    (comp.os.linux.misc)
  • RAID 5 or RAID 0+1
    ... We have 3 file servers running windows 2003 and 2008 on HP proliant servers. ... We need more disks in arrays. ... Is it possible to add extra disk to RAID 0+1 array and extend the size of the existing logical drive? ...
    (microsoft.public.windows.server.general)
  • RAID LICENSE - any one using and having fun with it?
    ... StorageWorksRAID Software for OpenVMSis a software product that uses RAID technology to manage groups of disk drives as arrays. ... The product supports RAID Level 0 arrays (Disk striping) for enhanced I/O performance and RAID Level 5 arrays for enhanced data availability on both VAXand Alpha platforms. ...
    (comp.os.vms)
  • Re: [opensuse] RAID 1 10.3 install doesnt boot
    ... (first time trying the RAID thing) ... I then discovered the moment in "install" where one has the ... Disk /dev/md0 doesn't contain a valid partition table ...
    (SuSE)