On Monday 26 January 2009 10:11:12 Lars Marowsky-Bree wrote:
On 2009-01-25T09:44:21, Bob Williams <linux@barrowhillfarm.org.uk> wrote:
Trigger only one side of the array each time - IMO.
Both disks passed the extended (long) test (whew!), so that narrows down the problem to the cabling, or maybe the controller card.
Well, not necessarily.
If it was a read error, rebuilding the error may have rewritten the sector, and that might have caused it to be remapped to one of the spares; so the error may now be "gone".
Cabling errors may be flukes though, maybe you pressed the connector in better now ;-)
Well, I did a reboot this morning, and /dev/md0 failed the automatic fsck, forcing me to do a manual fsck. There was a whole heap of lost inodes, bad block mapping, multiple block mapping etc. So maybe the array instability was a software problem, not hardware related. Anyway, all's well now, thanks. Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.1, Kernel 2.6.27.7-9-default, KDE 3.5.10 Intel Core2 Quad Q9400 2.66GHz, 4GB DDR RAM, nVidia GeForce 9200GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org