Lennart Sorensen a écrit :
>On Mon, Oct 17, 2005 at 10:54:23AM +0200, kohzak wrote: > > >>I'm installing a debian server with 4 sata drive on A8V motherboard. >> >>My system is on a 40 go ide hard disk and i've created a raid 5 during >>installation for my /home with the 4 sata drive. >> >>After reboot, i got this : >> >># cat /etc/fstab | grep /home >> >>/dev/md0 /home xfs defaults 0 2 >> >># cat /etc/mdadm/mdadm.conf >>DEVICE partitions >>ARRAY /dev/md0 level=raid5 num-devices=4 >>UUID=06d1127c:93799654:8d865636:3fb5f9f1 >> devices=/dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1 >> >># dmesg >> >>md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 >>md: md0 stopped. >>[...] >>libata version 1.02 loaded. >>sata_promise version 1.00 >>ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 18 (level, low) -> IRQ 18 >>ata1: SATA max UDMA/133 cmd 0xFFFFFF0000163200 ctl 0xFFFFFF0000163238 >>bmdma 0x0 irq 18 >>ata2: SATA max UDMA/133 cmd 0xFFFFFF0000163280 ctl 0xFFFFFF00001632B8 >>bmdma 0x0 irq 18 >>ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4673 85:7c69 86:3e01 87:4663 >>88:407f >>ata1: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48 >>ata1: dev 0 configured for UDMA/133 >>scsi0 : sata_promise >>ata2: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4063 85:7c69 86:3e01 87:4063 >>88:407f >>ata2: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48 >>ata2: dev 0 configured for UDMA/133 >>scsi1 : sata_promise >> Vendor: ATA Model: Maxtor 6L160M0 Rev: BANC >> Type: Direct-Access ANSI SCSI revision: 05 >>SCSI device sda: 320173056 512-byte hdwr sectors (163929 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 >>ieee1394: Host added: ID:BUS[0-00:1023] GUID[0011d800001af8a1] >> Vendor: ATA Model: Maxtor 6B160M0 Rev: BANC >> Type: Direct-Access ANSI SCSI revision: 05 >>SCSI device sdb: 320173056 512-byte hdwr sectors (163929 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 >>ip1394: $Rev: 1224 $ Ben Collins <[EMAIL PROTECTED]> >>ip1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) >>sata_via version 0.20 >>ACPI: PCI interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 20 >>sata_via(0000:00:0f.0): routed to hard irq line 10 >>ata3: SATA max UDMA/133 cmd 0xD000 ctl 0xC802 bmdma 0xB800 irq 20 >>ata4: SATA max UDMA/133 cmd 0xC400 ctl 0xC002 bmdma 0xB808 irq 20 >>ata3: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4673 85:7c69 86:3e01 87:4663 >>88:407f >>ata3: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48 >>ata3: dev 0 configured for UDMA/133 >>scsi2 : sata_via >>ata4: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4063 85:7c69 86:3e01 87:4063 >>88:407f >>ata4: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48 >>ata4: dev 0 configured for UDMA/133 >>scsi3 : sata_via >> Vendor: ATA Model: Maxtor 6L160M0 Rev: BANC >> Type: Direct-Access ANSI SCSI revision: 05 >>SCSI device sdc: 320173056 512-byte hdwr sectors (163929 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 >>ata4: dev 0 configured for UDMA/133 >>scsi3 : sata_via >> Vendor: ATA Model: Maxtor 6L160M0 Rev: BANC >> Type: Direct-Access ANSI SCSI revision: 05 >>SCSI device sdc: 320173056 512-byte hdwr sectors (163929 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 6B160M0 Rev: BANC >> Type: Direct-Access ANSI SCSI revision: 05 >>SCSI device sdd: 320173056 512-byte hdwr sectors (163929 MB) >>SCSI device sdd: drive cache: write back >> /dev/scsi/host3/bus0/target0/lun0: p1 >>Attached scsi disk sdd at scsi3, channel 0, id 0, lun 0 >> >># mount /dev/md0 >>mount: /dev/md0: can't read superblock >> >>I have the same error (bad superblock) with reiserfs or ext3 fs on /home. >>So does any one know why can't i mount my /home and why do i have that >>kind of error ? >>I don't know how where to check for that superblock problem. >> >> > >Is the raid even started? (/proc/mdstat should tell you). > > > >>Ps : i have installed raidtools2 and raidutils >> >> > >Install mdadm instead. It is much better and easier to use. Although >given your mdadm.conf above, you probably don't even need raidtools* at >all. > >Certainly above I see 'md0 stopped' and then it loads sata drivers. >Does it ever start md0? Maybe you are starting mdadm before you load >the sata drivers. List the sata drivers in /etc/modules, or have them > > Here is my /etc/modules : # cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file should contain the names of kernel modules that are # to be loaded at boot time, one per line. Comments begin with # a "#", and everything on the line after them are ignored. ide-cd ide-disk ide-generic psmouse sbp2 sd_mod sr_mod No, md, that's may be why it don't start at boot. i will try in few minutes. >included in the initrd by listing them in /etc/mkinitrd/modules. > Do i have to add md in /etc/modules and /etc/mkinitrd/modules or just /etc/modules ? Thanks all for your help since this morning :) >Len Sorensen > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
