NetBSD RAIDFRAME Recovery
Posted: Fri May 01, 2009 2:41 am
I've got a 4x250G RAID 5 array that I'm trying to recover after a bad sector in the superblock of one of the drive partitions. I've got the RAID array loaded into a machine that I'm dual-booting between NetBSD and Windows XP.
The configuration of the array is 1 row, 4 columns, 0 spares, 63 sectors per Stripe Unit, 1 SU per Parity Unit, 1 SU per recon unit, and RAID-5 parity. We chose 63 sectors per stripe unit because that's the size of 1 track.
On the raid there are two partitions, one starting at 3024 sectors for 20971520 sector (10 Gig) and one starting at 20974544 sectors and running through the end of the disk. (1444216582 sectors).
The second partition had the bad superblock, and when I set a region so that it corresponds to that partition, the system finds a Superblock some negative number of sectors away )I didn't right the number down, but it seems to me it was something like -168 sectors).
I'm in the process of copying the RAID array onto a 1G drive, but that takes about 20 hours. Once I'm done copying the fs image to the new drive, I expect the software will be able to handle the drive just fine (since the RAID components will be obscured).
Am I on the right track? Is the software just misinterpreting the block size (32 k instead of 31.5k)? Or am I completely going the wrong way. I really need to get started pulling the files off this disk ASAP, and waiting 22 hours for a 1 TB disk-to-disk copy is just a lot of time if there is some other solution.
The configuration of the array is 1 row, 4 columns, 0 spares, 63 sectors per Stripe Unit, 1 SU per Parity Unit, 1 SU per recon unit, and RAID-5 parity. We chose 63 sectors per stripe unit because that's the size of 1 track.
On the raid there are two partitions, one starting at 3024 sectors for 20971520 sector (10 Gig) and one starting at 20974544 sectors and running through the end of the disk. (1444216582 sectors).
The second partition had the bad superblock, and when I set a region so that it corresponds to that partition, the system finds a Superblock some negative number of sectors away )I didn't right the number down, but it seems to me it was something like -168 sectors).
I'm in the process of copying the RAID array onto a 1G drive, but that takes about 20 hours. Once I'm done copying the fs image to the new drive, I expect the software will be able to handle the drive just fine (since the RAID components will be obscured).
Am I on the right track? Is the software just misinterpreting the block size (32 k instead of 31.5k)? Or am I completely going the wrong way. I really need to get started pulling the files off this disk ASAP, and waiting 22 hours for a 1 TB disk-to-disk copy is just a lot of time if there is some other solution.