Re: can't mount raid 5 after installation
Stackpole, C [EMAIL PROTECTED] writes: Goswin...You are So my hero right now... Earlier I had I checked to make sure that the devices were listed, but I was unfamiliar with that command you gave, so a manpage'd it. I deleted the devices, reset them, and restarted...the whole thing is working now! Thank you so much, ~Stack~ Please file a installation report. The installer (for etch) should create those devices as needed and those report helps reminding the developers what is missing. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't mount raid 5 after installation
Stackpole, C [EMAIL PROTECTED] writes: Hey Guys, I am having a similar problem and not having much luck getting it to work either. I followed through the suggestions listed previous and am not getting anywhere. This is where I am at. I did a install with the 2.6 kernel on a system with a 60 gig drive (/dev/hda) set as my root and swap. I have 4 120 gig drives set up in a RAID5 (/dev/hde, /dev/hdg, /dev/hdi, /dev/hdk). I had the same problem where I would get it set up, and it would fail on reboot. I just tried the dpgk-reconfigure mdadm, and it failed saying that it could only find hde and hdg! So I looked, Debian is seeing all the drives (/proc/ide). All of the drives are listed as being setup for RAID. The /etc/mdadm/mdadm.conf have been setup as demonstrated earlier in the thread. If I try to mount the drives as individual drives, it has no problems whatsoever. Just doesn't like to see them when I set them up as RAID5. I have been going slightly insane these past few days trying to figure out why it can see all the drives but will not when I try to mount it as RAID5. I am not certain what to do next... Any suggestions would be greatly appreciated. ~Stack~ You are probably just missing the device nodes in /dev. The installer uses devfs, which creates device nodes automatically, while the installed system does not and only comes with hda - hdh. From memory: cd /dev MAKEDEV hdi MAKEDEV hdk MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: can't mount raid 5 after installation
Goswin...You are So my hero right now... Earlier I had I checked to make sure that the devices were listed, but I was unfamiliar with that command you gave, so a manpage'd it. I deleted the devices, reset them, and restarted...the whole thing is working now! Thank you so much, ~Stack~ From: Goswin von Brederlow [mailto:[EMAIL PROTECTED] Sent: Wed 11/9/2005 6:58 AM To: Stackpole, C Cc: debian-amd64@lists.debian.org Subject: Re: can't mount raid 5 after installation Stackpole, C [EMAIL PROTECTED] writes: Hey Guys, I am having a similar problem and not having much luck getting it to work either. I followed through the suggestions listed previous and am not getting anywhere. This is where I am at. I did a install with the 2.6 kernel on a system with a 60 gig drive (/dev/hda) set as my root and swap. I have 4 120 gig drives set up in a RAID5 (/dev/hde, /dev/hdg, /dev/hdi, /dev/hdk). I had the same problem where I would get it set up, and it would fail on reboot. I just tried the dpgk-reconfigure mdadm, and it failed saying that it could only find hde and hdg! So I looked, Debian is seeing all the drives (/proc/ide). All of the drives are listed as being setup for RAID. The /etc/mdadm/mdadm.conf have been setup as demonstrated earlier in the thread. If I try to mount the drives as individual drives, it has no problems whatsoever. Just doesn't like to see them when I set them up as RAID5. I have been going slightly insane these past few days trying to figure out why it can see all the drives but will not when I try to mount it as RAID5. I am not certain what to do next... Any suggestions would be greatly appreciated. ~Stack~ You are probably just missing the device nodes in /dev. The installer uses devfs, which creates device nodes automatically, while the installed system does not and only comes with hda - hdh. From memory: cd /dev MAKEDEV hdi MAKEDEV hdk MfG Goswin
RE: can't mount raid 5 after installation
Hey Guys, I am having a similar problem and not having much luck getting it to work either. I followed through the suggestions listed previous and am not getting anywhere. This is where I am at. I did a install with the 2.6 kernel on a system with a 60 gig drive (/dev/hda) set as my root and swap. I have 4 120 gig drives set up in a RAID5 (/dev/hde, /dev/hdg, /dev/hdi, /dev/hdk). I had the same problem where I would get it set up, and it would fail on reboot. I just tried the dpgk-reconfigure mdadm, and it failed saying that it could only find hde and hdg! So I looked, Debian is seeing all the drives (/proc/ide). All of the drives are listed as being setup for RAID. The /etc/mdadm/mdadm.conf have been setup as demonstrated earlier in the thread. If I try to mount the drives as individual drives, it has no problems whatsoever. Just doesn't like to see them when I set them up as RAID5. I have been going slightly insane these past few days trying to figure out why it can see all the drives but will not when I try to mount it as RAID5. I am not certain what to do next... Any suggestions would be greatly appreciated. ~Stack~
Re: can't mount raid 5 after installation
On Mon, Oct 17, 2005 at 11:20:03AM +0200, kohzak wrote: You mean that i should have /dev/md0/home fd defaults0 2 and not /dev/md0/home xfs defaults0 2 No, XFS is correct. But what does the partition table say? fdisk -l /dev/sda (hda, etc) Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't mount raid 5 after installation
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. # dmesg md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: md0 stopped. That's a problem, isn't it? # mount /dev/md0 mount: /dev/md0: can't read superblock How about 'cat /proc/mdstat'? Ps : i have installed raidtools2 and raidutils raidtools2 as well as mdadm? Probably bad to mix them. raidtools2 is gone in unstable. Use mdadm. So it looks like your RAID group is not active. Did you tell mdadm to activate it on startup? (It asks you the question when you install the package). You can reconfigure it with 'dpkg-reconfigure mdadm'. You should be able to activate it manually with some combination of mdadm --assemble --scan; I can never remember the parameters for that tool though. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't mount raid 5 after installation
You mean that i should have /dev/md0/home fd defaults0 2 and not /dev/md0/home xfs defaults0 2 ? Frederik Schueler a écrit : Hello, On Mon, Oct 17, 2005 at 11:11:50AM +0200, kohzak wrote: Ok, after reconfiguring mdadm i can mount my /home But after reboot, i still have the same problem. are the partitions of type fd (raid autodetect)? Best regards Frederik Schueler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't mount raid 5 after installation
Hello, On Mon, Oct 17, 2005 at 11:20:03AM +0200, kohzak wrote: You mean that i should have /dev/md0/home fd defaults0 2 and not /dev/md0/home xfs defaults0 2 no, the partition type must be fd, not the filesystem type in the fstab. you can easily find out with fdisk: fdisk -l should output something like this: Device Boot Start End Blocks Id System /dev/sda1 1393931639986 fd Linux raid autodetect then the kernel will autodetect and assemble the raid on boot. Best regards Frederik Schueler -- ENOSIG signature.asc Description: Digital signature
Re: can't mount raid 5 after installation
So, i've wait until it finish to create the raid. # cat /proc/mdstat Personalities : [raid5] md0 : active raid5 sda1[0] sdd1[3] sdc1[2] sdb1[1] 480238656 blocks level 5, 64k chunk, algorithm 2 [4/4] [] But same problem after rebooting : $ dmesg | grep md md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: md0 stopped. # mount /dev/md0 mount: /dev/md0: can't read superblock Hamish Moffatt a écrit : On Mon, Oct 17, 2005 at 11:34:06AM +0200, Frederik Schueler wrote: no, the partition type must be fd, not the filesystem type in the fstab. you can easily find out with fdisk: fdisk -l should output something like this: Device Boot Start End Blocks Id System /dev/sda1 1393931639986 fd Linux raid autodetect then the kernel will autodetect and assemble the raid on boot. Not if you use the Debian kernel with initrd. The initrd will make sure your root group (if any) is started, but you need the mdadm init.d script to start the rest. Hamish -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't mount raid 5 after installation
kohzak [EMAIL PROTECTED] writes: Hamish Moffatt a écrit : Ok, after reconfiguring mdadm i can mount my /home But after reboot, i still have the same problem. Reinstall the kernel-image so the initrd gets rebuild and includes the raid modules and mdadm. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't mount raid 5 after installation
Some forum / faq speak about /etc/raidtab Do i have to create that files ? Goswin von Brederlow a écrit : Frederik Schueler [EMAIL PROTECTED] writes: Hello, On Mon, Oct 17, 2005 at 11:11:50AM +0200, kohzak wrote: Ok, after reconfiguring mdadm i can mount my /home But after reboot, i still have the same problem. are the partitions of type fd (raid autodetect)? Best regards Frederik Schueler -- ENOSIG FYI: Raid autodetection only works with the raid modules buildin into the kernel. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't mount raid 5 after installation
On Mon, Oct 17, 2005 at 02:52:39PM +0200, kohzak wrote: Some forum / faq speak about /etc/raidtab Do i have to create that files ? No, it's for the old raidtools, not for mdadm. Your /etc/mdadm/mdadm.conf should look like this DEVICE /dev/sda* /dev/sdb* ARRAY /dev/md0 level=raid1 num-devices=2 UUID=e13cef12:a2742f19:acb223be:d5688af7 Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't mount raid 5 after installation
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 defaults0 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 :00:08.0[A] - GSI 18 (level, low) - IRQ 18 ata1: SATA max UDMA/133 cmd 0xFF163200 ctl 0xFF163238 bmdma 0x0 irq 18 ata2: SATA max UDMA/133 cmd 0xFF163280 ctl 0xFF1632B8 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 6L160M0Rev: 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[0011d81af8a1] Vendor: ATA Model: Maxtor 6B160M0Rev: 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 :00:0f.0[B] - GSI 20 (level, low) - IRQ 20 sata_via(: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 6L160M0Rev: 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 6L160M0Rev: 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 6B160M0Rev: 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 included in the initrd by listing them in /etc/mkinitrd/modules. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't mount raid 5 after installation
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 defaults0 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 :00:08.0[A] - GSI 18 (level, low) - IRQ 18 ata1: SATA max UDMA/133 cmd 0xFF163200 ctl 0xFF163238 bmdma 0x0 irq 18 ata2: SATA max UDMA/133 cmd 0xFF163280 ctl 0xFF1632B8 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 6L160M0Rev: 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[0011d81af8a1] Vendor: ATA Model: Maxtor 6B160M0Rev: 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 :00:0f.0[B] - GSI 20 (level, low) - IRQ 20 sata_via(: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 6L160M0Rev: 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 6L160M0Rev: 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 6B160M0Rev: 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
Re: can't mount raid 5 after installation
Hamish Moffatt [EMAIL PROTECTED] writes: On Mon, Oct 17, 2005 at 01:58:52PM +0200, Goswin von Brederlow wrote: kohzak [EMAIL PROTECTED] writes: Hamish Moffatt a écrit : Ok, after reconfiguring mdadm i can mount my /home But after reboot, i still have the same problem. Reinstall the kernel-image so the initrd gets rebuild and includes the raid modules and mdadm. But it won't since the root filesystem is not on raid. (At least, it doesn't need to, so I don't think the initrd will set up the md.) Hamish My bad. Then I have no idea. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't mount raid 5 after installation
i've added sata_via and sata_promise in /etc/modules and i got my raid mounted at each reboot. It work great. thks for all your answers koh Goswin von Brederlow a écrit : Hamish Moffatt [EMAIL PROTECTED] writes: On Mon, Oct 17, 2005 at 01:58:52PM +0200, Goswin von Brederlow wrote: kohzak [EMAIL PROTECTED] writes: Hamish Moffatt a écrit : Ok, after reconfiguring mdadm i can mount my /home But after reboot, i still have the same problem. Reinstall the kernel-image so the initrd gets rebuild and includes the raid modules and mdadm. But it won't since the root filesystem is not on raid. (At least, it doesn't need to, so I don't think the initrd will set up the md.) Hamish My bad. Then I have no idea. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't mount raid 5 after installation
On Mon, Oct 17, 2005 at 04:15:50PM +0200, kohzak wrote: i've added sata_via and sata_promise in /etc/modules and i got my raid mounted at each reboot. It work great. thks for all your answers OK that's good.. although if you have udev and hotplug installed, that should load sata_via / sata_promise for you well before the mdadm startup runs. udev runs as /etc/rcS.d/S04udev, while mdadm is S25mdadm-raid... Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't mount raid 5 after installation
On Mon, Oct 17, 2005 at 03:06:26PM +0200, kohzak wrote: 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. I meant, if your root disk is ide but your /home raid is sata, I would think perhaps your sata drivers are only being loaded when discover/hotplug/whatever gets around to checking which devices needs drivers loaded, which is most likely way after mdadm runs and tries to start the raid. 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 :) I would make sure the sata drivers are added to /etc/modules. That way to load early in the boot sequence, which is hopefulyl early enough for mdadm to be happy. modutils/module-init-tools runs at S20 (in rcS) whicle mdadm runs at S25. discover on the other hand runs at S36 which is to late for mdadm since it can't start the raid if the drives don't yet exist. That problably explains the md0 stopped message showing up just before the sata drives show up. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't mount raid 5 after installation
On Tue, Oct 18, 2005 at 12:28:16AM +1000, Hamish Moffatt wrote: OK that's good.. although if you have udev and hotplug installed, that should load sata_via / sata_promise for you well before the mdadm startup runs. udev runs as /etc/rcS.d/S04udev, while mdadm is S25mdadm-raid... Well discover runs at S36, and I am not sure udev (at least in sarge) does any driver loading. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't mount raid 5 after installation
This one time, at band camp, Hamish Moffatt said: On Mon, Oct 17, 2005 at 01:58:52PM +0200, Goswin von Brederlow wrote: kohzak [EMAIL PROTECTED] writes: Hamish Moffatt a écrit : Ok, after reconfiguring mdadm i can mount my /home But after reboot, i still have the same problem. Reinstall the kernel-image so the initrd gets rebuild and includes the raid modules and mdadm. But it won't since the root filesystem is not on raid. (At least, it doesn't need to, so I don't think the initrd will set up the md.) Put the names of the modules in /etc/mkinitrd/modules, one per line (just like /etc/modules) -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
RE: can't mount raid 5 after installation
you shouldnt have to load any modules as long as they are configured as modules, all you need to do is create a /etc/mdadm/mdadm.conf with the following (changed to your devices) DEVICE /dev/hd[bcd]1 ARRAY /dev/md0 UUID=3ab15009:10842ae2:c17e96db:d9376d90 And then modify /etc/default/mdadm and set AUTOSTART=true and hopefully if you have modified /etc/fstab to mount it correctly your system should mount home on start Thank you, Mark Adrian Coetser [EMAIL PROTECTED] http://www.tux-edo.co.za, http://www.thummb.com cel: +27 76 527 8789 tel: +27 11 805 2076 fax: +27 11 805 2330 -Original Message- From: Stephen Gran [mailto:[EMAIL PROTECTED] Sent: 17 October 2005 08:01 PM To: debian-amd64@lists.debian.org Subject: Re: can't mount raid 5 after installation This one time, at band camp, Hamish Moffatt said: On Mon, Oct 17, 2005 at 01:58:52PM +0200, Goswin von Brederlow wrote: kohzak [EMAIL PROTECTED] writes: Hamish Moffatt a écrit : Ok, after reconfiguring mdadm i can mount my /home But after reboot, i still have the same problem. Reinstall the kernel-image so the initrd gets rebuild and includes the raid modules and mdadm. But it won't since the root filesystem is not on raid. (At least, it doesn't need to, so I don't think the initrd will set up the md.) Put the names of the modules in /etc/mkinitrd/modules, one per line (just like /etc/modules) -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | -
Re: can't mount raid 5 after installation
On Mon, Oct 17, 2005 at 07:01:22PM +0100, Stephen Gran wrote: This one time, at band camp, Hamish Moffatt said: On Mon, Oct 17, 2005 at 01:58:52PM +0200, Goswin von Brederlow wrote: kohzak [EMAIL PROTECTED] writes: Hamish Moffatt a écrit : Ok, after reconfiguring mdadm i can mount my /home But after reboot, i still have the same problem. Reinstall the kernel-image so the initrd gets rebuild and includes the raid modules and mdadm. But it won't since the root filesystem is not on raid. (At least, it doesn't need to, so I don't think the initrd will set up the md.) Put the names of the modules in /etc/mkinitrd/modules, one per line (just like /etc/modules) That's unnecessary when the root is not on raid. When the root IS on raid, the initrd should do the right thing itself (it does here). Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
