March 24, 201313 yr Hello All, I encountered a drive error during the mover operation last night. I updated to V5.0rc12 yesterday and after reading about some issues with SF decided to remove it and work with unMenu and the basic webGUI more. I really like unMenu's color-coding of the Syslog, but this morning looking over the Syslog I see a string of drive related errors. I spent some time trying to make more sense of what happened. The drive in question is identified as ATA1.00 and I'm going to assume it's my parity drive at /DEV/SDA. The reading I've done sounds like it might have been a connector problem. Here's a little clip from unMenu's view of Syslog showing the errors: Mar 24 03:40:20 Tower logger: ./TV-Shows/BBC Sprial/Season 04/BBC Spiral State Of Terror S04E12.avi (Errors) Mar 24 03:40:20 Tower logger: .d..t...... TV-Shows/ Mar 24 03:40:20 Tower logger: .d..t...... TV-Shows/BBC Sprial/ Mar 24 03:40:20 Tower logger: .d..t...... TV-Shows/BBC Sprial/Season 04/ Mar 24 03:40:20 Tower logger: >f+++++++++ TV-Shows/BBC Sprial/Season 04/BBC Spiral State Of Terror S04E12.avi (Errors) Mar 24 03:40:21 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen (Errors) Mar 24 03:40:21 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors) Mar 24 03:40:21 Tower kernel: ata1: SError: { UnrecovData Handshk } (Errors) Mar 24 03:40:21 Tower kernel: ata1.00: failed command: WRITE DMA EXT (Minor Issues) Mar 24 03:40:21 Tower kernel: ata1.00: cmd 35/00:00:40:48:f4/00:04:39:00:00/e0 tag 0 dma 524288 out (Drive related) Mar 24 03:40:21 Tower kernel: res 50/00:00:4f:bb:38/00:00:3a:00:00/e0 Emask 0x10 (ATA bus error) (Errors) Mar 24 03:40:21 Tower kernel: ata1.00: status: { DRDY } (Drive related) Mar 24 03:40:21 Tower kernel: ata1: hard resetting link (Minor Issues) Mar 24 03:40:22 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Mar 24 03:40:22 Tower kernel: ata1.00: configured for UDMA/133 (Drive related) Mar 24 03:40:22 Tower kernel: ata1: EH complete (Drive related) Mar 24 03:40:45 Tower logger: ./TV-Shows/BBC Sprial/Season 04/BBC Spiral State Of Terror S04E12.sfv (Errors) Mar 24 03:40:45 Tower logger: .d..t...... TV-Shows/BBC Sprial/Season 04/ Mar 24 03:40:45 Tower logger: >f+++++++++ TV-Shows/BBC Sprial/Season 04/BBC Spiral State Of Terror S04E12.sfv (Errors) Mar 24 03:40:45 Tower logger: ./TV-Shows/BBC Sprial/Season 04 Mar 24 03:40:45 Tower logger: .d..t...... TV-Shows/BBC Sprial/Season 04/ Mar 24 03:40:45 Tower logger: ./TV-Shows/BBC Sprial Mar 24 03:40:45 Tower logger: .d..t...... TV-Shows/BBC Sprial/ The rest of the log is attached. Earlier in the evening there had been a brief power outage and thankfully the UPS covered it nicely (and logged it!). I tried running a short SMART test on the parity drive and it came back as good. I'm still getting used to the unMenu interface and I'd appreciate any thoughts as to where to go from here. I plan to power the server down and re-seat drive connectors later today and see how things go. Thanks!! syslog-20130324.zip
March 24, 201313 yr Keep checking the logs. If ATA1 keeps acting up then post again. The other lines are a result of having the word "error" in the file name, i.e., in terror.
March 24, 201313 yr Author Thanks dgaschk for checking in! Earlier I kicked off a read-only parity check and it should finish in about 90 minutes. But I'll keep a close eye on the logs.
March 25, 201313 yr Author The Mover ran without issues this morning. I'm sure it's not a "mover" problem. Hopefully it was a "one-of" occurrence involving writing to a drive. The key here is I'm trying to understand how to read the Syslog properly and make some sense of it. Thanks again!!
Archived
This topic is now archived and is closed to further replies.