Re: RAID5 config / boot problem
Hi Alvin,
Thanks for taking the time to reply.
First of all, I should have clarified that I am booting from hda, which is
another drive that is not in the RAID system at all. Booting is fine apart
from stopping for the fsck failure - the system comes up and appears to
work.
>> e2fsck 1.37 (21-Mar-2005)
>> fsck.ext3: Invalid argument while trying to open /dev/md0
>> /dev/md0:
>
> not good ..
>
> - is the partition type set to "FD" and the boot flag ( a ) turned on
The partition type of /dev/md0 is ext3. The partition types of the four
component partitions are 'fd' - cfdisk reports them as "Linux raid
autodetect".
> - i assume you have the raid modules in your initrd for the
> kernel you're booting
No - not unless the Debian install put them there. I'm not sure how I
would know? Anyway, I specified this RAID setup using the Debian sarge
installer, so I assumed it would either pick an appropriate kernel or the
right modules for me. "uname -a" tells me my kernel is "2.6.8-2-386" - I
haven't compiled a new one since installing sarge.
>> /etc/mdadm/mdadm.conf contains:
>> DEVICE partitions
>> ARRAY /dev/md0 level=raid5 num-devices=4
>> UUID=ebdfaedf:59e64777:d81d8f6e:8d6b0392
>> devices=/dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
>
> sometimes, some distro, bootloaders cannot boot from raid5
> - you are guaranteed to be able to boot anything from raid1
>
> - for raid stuff, always use grub from cvs checkout and/or
> lilo from the primary lilo ftp site
>
> ( /boot on raid1 which is one of the few times oyu need
> a different explicit /boot partitions in todays PCs )
I guess this isn't relevant since I'm not trying to boot from the RAID array?
The aray is made of partition on four SATA dirves, plugged into all of the
ports on a Gigabyte k8ns pro motherboard. I looked at the dmesg output
again, and I saw this part:
==================================
hda: Maxtor 6K040L0, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: 80293248 sectors (41110 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(133)
/dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 >
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Adding 2931820k swap on /dev/hda7. Priority:-1 extents:1
EXT3 FS on hda1, internal journal
Generic RTC Driver v1.07
SCSI subsystem initialized
Capability LSM initialized
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: md0 stopped.
EXT3-fs: unable to read superblock
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
<snip>
eth1: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter
PrefPort:A RlmtMode:Check Link State
libata version 1.02 loaded.
sata_nv version 0.02
ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 22 (level, high) -> IRQ 177
PCI: Setting latency timer of device 0000:00:0a.0 to 64
ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xE400 irq 177
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xE408 irq 177
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4673 85:7c68 86:3e21 87:4663
88:007f
ata1: dev 0 ATA, max UDMA/133, 490234752 sectors: lba48
ata1: dev 0 configured for UDMA/133
scsi0 : sata_nv
ata2: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4673 85:7c68 86:3e21 87:4663
88:007f
ata2: dev 0 ATA, max UDMA/133, 490234752 sectors: lba48
ata2: dev 0 configured for UDMA/133
scsi1 : sata_nv
Vendor: ATA Model: Maxtor 6L250S0 Rev: BACE
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 490234752 512-byte hdwr sectors (251000 MB)
SCSI device sda: drive cache: write back
/dev/scsi/host0/bus0/target0/lun0: p1
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: ATA Model: Maxtor 6L250S0 Rev: BACE
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdb: 490234752 512-byte hdwr sectors (251000 MB)
SCSI device sdb: drive cache: write back
/dev/scsi/host1/bus0/target0/lun0: p1
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
sata_sil version 0.54
ACPI: PCI interrupt 0000:02:0d.0[A] -> GSI 17 (level, low) -> IRQ 217
ata3: SATA max UDMA/100 cmd 0xF881E080 ctl 0xF881E08A bmdma 0xF881E000 irq
217
ata4: SATA max UDMA/100 cmd 0xF881E0C0 ctl 0xF881E0CA bmdma 0xF881E008 irq
217
ata3: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4673 85:7c69 86:3e21 87:4663
88:207f
ata3: dev 0 ATA, max UDMA/133, 490234752 sectors: lba48
ata3: dev 0 configured for UDMA/100
scsi2 : sata_sil
ata4: dev 0 cfg 49:2f00 82:7869 83:7d09 84:4023 85:7849 86:3c21 87:4023
88:203f
ata4: dev 0 ATA, max UDMA/100, 488397168 sectors: lba48
ata4: dev 0 configured for UDMA/100
scsi3 : sata_sil
Vendor: ATA Model: Maxtor 6L250S0 Rev: BACE
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdc: 490234752 512-byte hdwr sectors (251000 MB)
SCSI device sdc: drive cache: write back
/dev/scsi/host2/bus0/target0/lun0: p1
Attached scsi disk sdc at scsi2, channel 0, id 0, lun 0
Vendor: ATA Model: Maxtor 6L250S0 Rev: BACE
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdd: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sdd: drive cache: write through
/dev/scsi/host3/bus0/target0/lun0: p1
Attached scsi disk sdd at scsi3, channel 0, id 0, lun 0
Linux agpgart interface v0.100 (c) Dave Jones
==================================
I could be reading this wrong, but doesn't it try to fsck the device above
the snip, but only initialises the sata drivers for the components below
the snip?
thanks again for any light you can shed,
James
Reply to: