Re: USB RAID - sdb keeps failing
- My experience has been that software raid does not work reliably on NSLU2's for hard drive. The reason being is software raid requires a significant amount of non-swapable memory. You don't have that much memory on an NSLU2 to begin with. Swap does wonders, but when you only have a small amount of physical memory sometimes there is not even enough available to use swap. In which case the kernel will randomly kill processes or halt (depending on your settings) eventually.
Even worse, try using LVM on couple of 1.5TB drives.... You'll quickly conclude for an LVM you are best off trying to just use raw partitions, and adjust your file allocation stradegy's accordingly.
--- In email@example.com, "Mike Westerhof (mwester)" <mwester@...> wrote:
> On 1/18/2011 11:39 PM, biodiesel_bri wrote:
> > I can't seem to get my second HD to work on this raid array. I tested the HD using the WD utility many times and got no errors. Anyone have any idea why this keeps happening or a way to fix it?
> > The drives are identical WD Scorpio Blue 500gb drives and identical USB enclosures. I have the same setup on /two/ other slugs and it works fine.
> Looks like a failed hard drive.
> The vendor-provided utilities are often inadequate; in order to test it
> properly, you'll have to take the HDD itself out of the enclosure, put
> it on an IDE or SATA cable, and run a full disk diagnostic suite on it.
> In the meantime, what happens if you repartition the drive (with fdisk),
> put a filesystem on it with e2mkfs, and then run fsck with the option to
> do full bad-block checking? You should be able to do that in the USB
> enclosure, although its doubtful that the NSLU2 has the memory to
> complete the fsck operation without extra swapspace -- best do this on a
> real host.
> -Mike (mwester)