So there i was, copying a big chunk of data from the cache disk to the array when the power drops out...on reboot, the array automatically starts and finds 64 disk errors.  Write errors.  Can i just run a parity check and recopy that data over after?

 

Thanks!

 

EDIT:  Not write errors, nothing was taken out of service, but there wer 64 errors in the right-hand column at first, now 53, and I am almost done with the parity check with 2016 errors.  Also, the cache mover ran again cause i forgot to disable, and finished the fil copy...dont know how reliable that will be!

No UPS?

 

A UPS is one of the most important things to have.

Please follow these instructions: http://lime-technology.com/forum/index.php?topic=9880.0

 

And then we can help.

 

Get a UPS ASAP.

Quite.  Too bad mine's backordered from the Good Deals thread...I'll just put the beagles on hamster wheels till officemax gets their act together, it's cool...

 

The errors turned out to be reads, but most of the red in here is greek to me.  Using 4.7 Pro.

syslog-2011-03-11.txt

Quite.  Too bad mine's backordered from the Good Deals thread...I'll just put the beagles on hamster wheels till officemax gets their act together, it's cool...

 

The errors turned out to be reads, but most of the red in here is greek to me.  Using 4.7 Pro.

Read errors (media errors) are un-readable sectors on the disk.  If you do a SMART report on the disk you'll see either sectors that have been re-allocated, or sectors pending re-allocation. 

 

You can try

smartctl -d ata -a /dev/sde

 

The errors seem to be on disk2.

Mar 11 14:32:03 Tower kernel: md: import disk2: [8,64] (sde) WDC WD20EARS-00M WD-WMAZA2801211 size: 1953514552

Mar 11 16:02:23 Tower kernel: ata5.00: irq_stat 0x40000001

Mar 11 16:02:23 Tower kernel: ata5.00: failed command: READ DMA EXT

Mar 11 16:02:23 Tower kernel: ata5.00: cmd 25/00:00:68:76:e2/00:04:68:00:00/e0 tag 0 dma 524288 in

Mar 11 16:02:23 Tower kernel:          res 51/40:9f:c0:78:e2/00:01:68:00:00/e0 Emask 0x9 (media error)

Mar 11 16:02:23 Tower kernel: ata5.00: status: { DRDY ERR }

Mar 11 16:02:23 Tower kernel: ata5.00: error: { UNC }

Mar 11 16:02:23 Tower kernel: ata5.00: configured for UDMA/133

Mar 11 16:02:23 Tower kernel: sd 4:0:0:0: [sde] Unhandled sense code

Mar 11 16:02:23 Tower kernel: sd 4:0:0:0: [sde] Result: hostbyte=0x00 driverbyte=0x08

Mar 11 16:02:23 Tower kernel: sd 4:0:0:0: [sde] Sense Key : 0x3 [current] [descriptor]

Mar 11 16:02:23 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Mar 11 16:02:23 Tower kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Mar 11 16:02:23 Tower kernel:        68 e2 78 c0

Mar 11 16:02:23 Tower kernel: sd 4:0:0:0: [sde] ASC=0x11 ASCQ=0x4

Mar 11 16:02:23 Tower kernel: sd 4:0:0:0: [sde] CDB: cdb[0]=0x28: 28 00 68 e2 76 68 00 04 00 00

Mar 11 16:02:23 Tower kernel: end_request: I/O error, dev sde, sector 1759672512

Mar 11 16:02:23 Tower kernel: ata5: EH complete

Mar 11 16:02:23 Tower kernel: md: disk2 read error

Mar 11 16:02:23 Tower kernel: handle_stripe read error: 1759672448/2, count: 1

Mar 11 16:02:23 Tower kernel: md: disk2 read error