Re: mdadm error when trying to replace a failed drive in RAID5 array

2008-01-21 Thread Ask Bjørn Hansen
On Jan 20, 2008, at 1:21 PM, Steve Fairbairn wrote: So the device I was trying to add was about 22 blocks too small. Taking Neils suggestion and looking at /proc/partitions showed this up incredibly quickly. Always leave a little space in the end; it makes sure you don't run into that pa

RE: mdadm error when trying to replace a failed drive in RAID5 array

2008-01-20 Thread Steve Fairbairn
> -Original Message- > From: Neil Brown [mailto:[EMAIL PROTECTED] > Sent: 20 January 2008 20:37 > > > md: hdd1 has invalid sb, not importing! > > md: md_import_device returned -22 > > In 2.6.18, the only thing that can return this message > without other more explanatory messages are: >

Re: mdadm error when trying to replace a failed drive in RAID5 array

2008-01-20 Thread Robin Hill
On Sat Jan 19, 2008 at 11:08:43PM -, Steve Fairbairn wrote: > > Hi All, > > I have a Software RAID 5 device configured, but one of the drives > failed. I removed the drive with the following command... > > mdadm /dev/md0 --remove /dev/hdc1 > > Now, when I try to insert the replacement driv

RE: mdadm error when trying to replace a failed drive in RAID5 array

2008-01-20 Thread Steve Fairbairn
Thanks for the response Bill. Neil has responded to me a few times, but I'm more than happy to try and keep it on this list instead as it feels like I'm badgering Neil which really isn't fair... Since my initial email, I got to the point of believing it was down to the superblock, and that --zer

mdadm error when trying to replace a failed drive in RAID5 array

2008-01-19 Thread Steve Fairbairn
Hi All, Firstly, I must express my thanks to Neil Brown for being willing to respond to the direct email I sent him as I couldn't for the life of me find any forums on mdadm or this list... I have a Software RAID 5 device configured, but one of the drives failed. I removed the drive with the fol