Hi Bruce, > Jul 14 08:24:43 files3 kernel: 3w-xxxx: Received AEN 0xb > Jul 14 08:24:48 files3 3w-xxxx[583]: Rebuild started on unit > 0 on controller > ID:0. (0xb) > Jul 14 08:25:02 files3 kernel: 3w-xxxx: Received AEN 0x4 > Jul 14 08:25:04 files3 3w-xxxx[583]: Rebuild/Initialization > failed on unit 0 > on controller ID:0. Check drives for media errors. (0x4) > > I tried swapping out the controller w/ another from a > spare/test server, > same result. Running 2.4.9-31 Red Hat kernel under 7.1. Anyone have a > suggestion as to how to get this array rebuilt? thanks. This means that there's either a write error on the target disk or a read error on the source disk for the rebuild; First step now should be to back up your data if you haven't done so :-) Next, I'd check the target disk for errors; best you can do would be to hook it up to an onboard ide interface and run a manufacturer-provided disgnostic test on the drive (like DFT for IBM drives for example). If this test of the target drive turns up nothing you most probably have read errors on the source drive - not good. Writing the damaged sectors can give the drive electronics a chance to remap them to good areas; alternatively you might want to just replace the drive. To avoid getting into this situation in the first place, it's a good idea to regularely scan your raid devices for media damage - recent versions of the 3dmd device manager (I'm running 1.11.00.006) offer an option to schedule regular scans: Configure => Media Scan. Bye, Martin - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
