I sitting here watching error messages scroll by fast and furious. And that's OK. It's all good. The errors are fine. Which in a way is a bit refreshing.

I had a disk fail in the RAID1 array of my main fileserver this morning, and I'm rebuilding the mirror. But Linux's IDE drivers on my Asus SD11 motherboard can't handle UDMA66, and so I'm getting a lot of dma_intr: status=0x51 { DriveReady SeekComplete Error } and dma_intr: error=0x84 { DriveStatusError BadCRC } errors. It's not bad, per se. Not good, certainly, but not bad. The data will be there in the end; it'll just take a lot longer to rebuild the mirror. I'm at 56% now, and have been at it about an hour:

[wee@server wee]$ cat /proc/mdstat
Personalities : [raid1]
read_ahead 1024 sectors
md0 : active raid1 hdb1[2] hdd1[1]
      78148096 blocks [2/1] [_U]
      [===========>.........] recovery = 56.3% (44044372/78148096) finish=27.5min speed=20653K/sec
unused devices: <none>

I went and found a couple old 40pin, 40 conductor IDE cables which I'll use instead. That will force the drives into DMA33 mode, and prevent the errors. That'll mean lessened performance, but when you consider that this machines's sole purpose is to safely store data sent to it over NFS and Samba, the bottleneck isn't the IDE controller and having slower disk access won't matter in the slightest. I'll put the new cables in later. Now it's time for bed.

RAID1 is terribly cool.