LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   SATA RAID 0 errors on bootup -- invalid raid superblock (http://www.linuxquestions.org/questions/slackware-14/sata-raid-0-errors-on-bootup-invalid-raid-superblock-447514/)

vonst 05-22-2006 07:58 PM

SATA RAID 0 errors on bootup -- invalid raid superblock
 
I've been working on a new install of the 10.2 disks. The following has been keeping me from finishing my install! To start, here's my system:

NForce4U chipset on BFG mothergboard (4 SATA2 / RAID enabled)
nvraid (fakeraid) turned off.
3 WD2500 SATA HDD's + 1 WD3200 SATA HDD.
AMD Athlon 3200+

My RAID partitions are: /dev/sda1 + /dev/sdb1 + /dev/sdc3 + /dev/sdd1

Interesting note: the BIOS and WinXP (on another partition) see /dev/sdc as my 1st disk, but Linux sees /dev/sda as the first disk. I think it has something to do with SATA...

I was successful in creating /dev/md0. I actually installed Slack 10.2 into it. But I can't find it on boot, because I can't mount the partitions at boot. I can "mkraid" them back, every time I boot from the install disks, and Slackware is still there. The following is from the install disk load of "sata.i". The same thing happened with the LILO /boot install of sata.i and a 2.6.16.4 kernel I compiled on a differnent machine and moved over to the /boot directory.

Can someone look at this 'dmesg' for me and tell me why it can't find those superblocks?

Quote:

Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: After generic, caps: 078bfbff e3d3fbff 00000000 00000000
CPU: Common caps: 078bfbff e3d3fbff 00000000 00000000
CPU: AMD Athlon(tm) 64 Processor 3800+ stepping 02
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 3.00 entry at 0xfa780, last bus=5
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
Transparent bridge - PCI device 10de:005c (nVidia Corporation)
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Disk quotas vdquot_6.5.1
Journalled Block Device driver loaded
pty: 512 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10f
reset set in interrupt, calling c01e7840
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 6464K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE-CK804: IDE controller at PCI slot 00:06.0
NFORCE-CK804: chipset revision 242
NFORCE-CK804: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE-CK804: 00:06.0 (rev f2) UDMA133 controller
ide0: BM-DMA at 0xe800-0xe807, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xe808-0xe80f, BIOS settings: hdc:DMA, hdd:DMA
hda: DVD-ROM DDU1632, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: attached ide-cdrom driver.
hda: ATAPI 40X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
SCSI subsystem driver Revision: 1.00
libata version 1.10 loaded.
sata_nv version 0.6
PCI: Setting latency timer of device 00:07.0 to 64
PCI: Setting latency timer of device 00:08.0 to 64
ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD400 irq 11
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD408 irq 11
ata1: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 88:407f
ata1: dev 0 ATA, max UDMA/133, 488397168 sectors: lba48
ata1: dev 0 configured for UDMA/133
ata2: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 88:407f
ata2: dev 0 ATA, max UDMA/133, 488397168 sectors: lba48
ata2: dev 0 configured for UDMA/133
ata3: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xC000 irq 10
ata4: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xC008 irq 10
ata3: dev 0 cfg 49:2f00 82:746b 83:7f61 84:4023 85:7469 86:3c41 87:4023 88:407f
ata3: dev 0 ATA, max UDMA/133, 625142448 sectors: lba48
ata3: dev 0 configured for UDMA/133
ata4: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 88:407f
ata4: dev 0 ATA, max UDMA/133, 488397168 sectors: lba48
ata4: dev 0 configured for UDMA/133
scsi0 : sata_nv
scsi1 : sata_nv
scsi2 : sata_nv
scsi3 : sata_nv
Vendor: ATA Model: WDC WD2500KS-00M Rev: 02.0
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: WDC WD2500KS-00M Rev: 02.0
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: WDC WD3200KS-00P Rev: 21.0
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: WDC WD2500KS-00M Rev: 02.0
Type: Direct-Access ANSI SCSI revision: 05
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
Attached scsi disk sdc at scsi2, channel 0, id 0, lun 0
Attached scsi disk sdd at scsi3, channel 0, id 0, lun 0
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
Partition check:
sda: sda1 sda2 sda3
SCSI device sdb: 488397168 512-byte hdwr sectors (250059 MB)
sdb: sdb1 sdb2 sdb3
SCSI device sdc: 625142448 512-byte hdwr sectors (320073 MB)
sdc: sdc1 sdc2 sdc3
SCSI device sdd: 488397168 512-byte hdwr sectors (250059 MB)
sdd: sdd1 sdd2 sdd3
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: measuring checksumming speed
8regs : 3688.800 MB/sec
32regs : 2491.600 MB/sec
pIII_sse : 7682.800 MB/sec
pII_mmx : 5447.600 MB/sec
p5_mmx : 6838.400 MB/sec
raid5: using function: pIII_sse (7682.800 MB/sec)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
[events: 00000000]
md: invalid raid superblock magic on sda1
md: sda1 has invalid sb, not importing!
md: could not import sda1!
[events: 00000000]

md: invalid raid superblock magic on sdb1
md: sdb1 has invalid sb, not importing!
md: could not import sdb1!
[events: 00000000]
md: invalid raid superblock magic on sdc3
md: sdc3 has invalid sb, not importing!
md: could not import sdc3!
[events: 00000000]
md: invalid raid superblock magic on sdd1
md: sdd1 has invalid sb, not importing!
md: could not import sdd1!
md: autorun ...
md: ... autorun DONE.
LVM version 1.0.8(17/11/2003)
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 2583k freed
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 120k freed
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
PCI: Setting latency timer of device 00:02.1 to 64
ehci_hcd 00:02.1: PCI device 10de:005b (nVidia Corporation)
ehci_hcd 00:02.1: irq 11, pci mem f8829000
usb.c: new USB bus registered, assigned bus number 1
PCI: cache line size of 64 is not supported by device 00:02.1
ehci_hcd 00:02.1: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
hub.c: USB hub found
hub.c: 10 ports detected
PCI: Setting latency timer of device 00:02.0 to 64
usb-ohci.c: USB OHCI at membase 0xf8831000, IRQ 10
usb-ohci.c: usb-00:02.0, PCI device 10de:005a (nVidia Corporation)
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 10 ports detected
uhci.c: USB Universal Host Controller Interface driver v1.1
usb-uhci.c: $Revision: 1.275 $ time 18:53:41 Jun 5 2005
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usb.c: registered new driver usbkbd
usbkbd.c: :USB HID Boot Protocol keyboard driver
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
FAT: unable to read boot sector
UMSDOS: msdos_read_super failed, mount aborted.
FAT: unable to read boot sector
FAT: unable to read boot sector
Thanks!
--vonSt

ORBiTrus 05-26-2006 01:42 AM

I may not be much help, so I was going to PM you so this stayed as an "unreplied thread" and kept getting attention, but that's disabled. PM is handy sometimes... :)

Anyways, care to post your LILO config? And you are working with a custom kernel? What are the setting it has? If you are doing software raid, the raid drivers may require the filesystem driver to be loaded (I don't know RAID), so are the required filesystem modules loading before the RAID drivers? Also, don't forget to set your /boot partition separate from the raided partition.

vonst 05-26-2006 07:47 PM

Oh the little tricks I've learned! This is indeed why I am fiddling with this new concept.

In answer to the questions: I am using 10.2 install disks with the sata.i kernel. By using them, I can get to the CLI and (through a complex procedure that I've mostly automated) mkraid /dev/md0. That gets me to my RAID0 partition. /dev/md0 has a full vanilla install of Slack 10.2 on it. I generated a 2.6.16.16 kernel with NO MODULES. I put sata_nv in it and I turned on RAID 0. It's entirely possible that I didn't do everything I needed. I transferred that kernel from its "build computer" to its "use computer." Then, I made a special lilo menu line to load it. I also made a lilo line to load the /boot/vmlinuz -> /boot/sata.i kernel from the disk.

I can't hotplug my thumb drive into the USB port when I load Linux with the install disks. I just found out, however, that when I chroot into my RAID0 partition (which I mount as /raid: chroot /raid), all of the sudden I can mount my thumb drive! I didn't know that before!!!

So, since I can do that now, I've got my lilo.conf. Here it is:

Quote:

# LILO configuration file
#
# Start LILO global section
boot = /dev/sdc
prompt
timeout = 300
# VESA framebuffer console @ 1024x768x256
vga = 773
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/md0
label = Linux
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/sda1
label = Windows
table = /dev/sda
# Windows bootable partition config ends
# Another Linux bootable partition
image = /boot/toot/vmlinuz
root = /dev/md0
label = Special.kernel
read-only
# Linux bootable partition config ends
As a post note: I switched around my devices. cwwilson stated that I needed to put LILO on the first device. Consequently, I now run lilo -b /dev/sda because boot=/dev/sdc. Two days ago, it was reversed. It doesn't seem to matter, the answer is still the same.

--vonSt

vonst 07-04-2006 03:55 PM

*** SOLUTION *** SOLUTION *** SOLUTION ***

Thanks to everybody that helped me figure out this complicated and logic-defying problem.

I found the solution in the old Software-RAID-HOWTO, while searching for instructions for and applications for mdadm.

I installed Slackware on a single partition, ran mdadm, and have had a persistent /dev/md0 since! Here's the code I used:

Code:

mdadm --create --verbose /dev/md0 --level=raid0 --raid-devices=3 /dev/sdb2 /dev/sdc2 /dev/sdd2

--vonSt


All times are GMT -5. The time now is 11:22 AM.