Re: [Wylug-help] Disc failure on a software RAID system has killed everything

2010-05-20 Thread Mogens Kjaer
On 05/20/2010 12:15 PM, Gary Stainburn wrote: ... > mdadm: cannot open device /dev/sde2: No such file or directory ... I guess this is your main problem. Start locating the disks before doing any assembling. Which /dev/sd[a-z]2 do you have? How are the disks connected to which controllers? What

Re: [Wylug-help] Disc failure on a software RAID system has killed everything

2010-05-20 Thread Gary Stainburn
On Thursday 20 May 2010 10:11:35 Gary Stainburn wrote: > Number Major Minor RaidDevice State >0 000 removed >1 001 removed >2 002 removed >3 8 343 acti

Re: Disc failure on a software RAID system has killed everything

2010-05-20 Thread Gary Stainburn
I've managed to boot up using systemrescuecd and I've managed to get the RAID1 boot (/dev/md0) partition to mount. I've also looked at the RAID5 swap partition that I had forgotten about and that looks fine. The problem is with the main RAID5 device /dev/md2 which should consist of 5 partition

Re: Disc failure on a software RAID system has killed everything

2010-05-19 Thread Roberto Ragusa
Gary Stainburn wrote: > Hi folks, > > I've got a PC with 5x500GB HDD's running software raid. On drive 0 and 1 I > had RAID0 for the boot partition and then on all 5 drives I had RAID 5 for > everything else. > > One of the first two drives has died causing the PC to hang, and then when I > r

Re: Disc failure on a software RAID system has killed everything

2010-05-19 Thread Bryn M. Reeves
On 05/19/2010 12:28 PM, Gary Stainburn wrote: > Sorry Bryn, I mean RAID1. > > I thought that with RAID1, if I disconnected the dead one it should either > just work, or i should be able to access both that and the RAID5 setup from > the bood DVD. Ah, that makes a lot more sense then! It's true

Re: Disc failure on a software RAID system has killed everything

2010-05-19 Thread Bruno Wolff III
On Wed, May 19, 2010 at 14:32:40 +0200, birger wrote: > > If this is your case (striping over slave and master on the same chain) > I would try with a physically sound disk to replace the failed drive so > the slave should work again, and check that only the slave has an > active, bootable part

Re: Disc failure on a software RAID system has killed everything

2010-05-19 Thread birger
Remember that if you use old ATA disks, the slave often gets completely braindead if the master on the same chain dies. Because of this, your boot device should be striped over two master disks (on 2 different chains of course). If this is your case (striping over slave and master on the same chai

Re: Disc failure on a software RAID system has killed everything

2010-05-19 Thread Gary Stainburn
On Wednesday 19 May 2010 12:13:12 Bryn M. Reeves wrote: > On 05/19/2010 12:04 PM, Gary Stainburn wrote: > > Hi folks, > > > > I've got a PC with 5x500GB HDD's running software raid. On drive 0 and 1 > > I had RAID0 for the boot partition and then on all 5 drives I had RAID 5 > > for everything els

Re: Disc failure on a software RAID system has killed everything

2010-05-19 Thread Bryn M. Reeves
On 05/19/2010 12:13 PM, Bryn M. Reeves wrote: > On 05/19/2010 12:04 PM, Gary Stainburn wrote: >> Hi folks, >> >> I've got a PC with 5x500GB HDD's running software raid. On drive 0 and 1 I >> had RAID0 for the boot partition and then on all 5 drives I had RAID 5 for >> everything else. > > Why u

Re: Disc failure on a software RAID system has killed everything

2010-05-19 Thread Bryn M. Reeves
On 05/19/2010 12:04 PM, Gary Stainburn wrote: > Hi folks, > > I've got a PC with 5x500GB HDD's running software raid. On drive 0 and 1 I > had RAID0 for the boot partition and then on all 5 drives I had RAID 5 for > everything else. Why use RAID0 for the boot partition? That means that a failu

Disc failure on a software RAID system has killed everything

2010-05-19 Thread Gary Stainburn
Hi folks, I've got a PC with 5x500GB HDD's running software raid. On drive 0 and 1 I had RAID0 for the boot partition and then on all 5 drives I had RAID 5 for everything else. One of the first two drives has died causing the PC to hang, and then when I rebooted it couldn't get past GRUB. I