March 4, 201214 yr was running TerraCopy overnight moving things over to the array. Array has been up for 3 days with no issues, moving things over. When I got up this morning, found this in the log Mar 4 06:04:10 Burbank kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen Mar 4 06:04:10 Burbank kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen Mar 4 06:04:10 Burbank kernel: ata6: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen Mar 4 06:04:10 Burbank kernel: ata5: irq_stat 0x00400000, PHY RDY changed Mar 4 06:04:10 Burbank kernel: ata6: irq_stat 0x00400000, PHY RDY changed Mar 4 06:04:10 Burbank kernel: ata5: SError: { RecovComm Persist PHYRdyChg 10B8B } Mar 4 06:04:10 Burbank kernel: ata6: SError: { RecovComm Persist PHYRdyChg 10B8B } Mar 4 06:04:10 Burbank kernel: ata5: hard resetting link Mar 4 06:04:10 Burbank kernel: ata4: irq_stat 0x00400000, PHY RDY changed Mar 4 06:04:10 Burbank kernel: ata6: hard resetting link Mar 4 06:04:10 Burbank kernel: ata4: SError: { RecovComm Persist PHYRdyChg 10B8B } Mar 4 06:04:10 Burbank kernel: ata4: hard resetting link Mar 4 06:04:11 Burbank kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 4 06:04:11 Burbank kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 4 06:04:11 Burbank kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 4 06:04:11 Burbank kernel: ata4.00: configured for UDMA/133 Mar 4 06:04:11 Burbank kernel: ata5.00: configured for UDMA/133 Mar 4 06:04:11 Burbank kernel: ata4: EH complete Mar 4 06:04:11 Burbank kernel: ata6.00: configured for UDMA/133 Mar 4 06:04:11 Burbank kernel: ata6: EH complete Mar 4 06:04:11 Burbank kernel: ata5: EH complete Mar 4 06:08:49 Burbank kernel: ata6: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen Mar 4 06:08:49 Burbank kernel: ata6: irq_stat 0x00400000, PHY RDY changed Mar 4 06:08:49 Burbank kernel: ata6: SError: { RecovComm Persist PHYRdyChg 10B8B } Mar 4 06:08:49 Burbank kernel: ata6: hard resetting link Mar 4 06:08:50 Burbank kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 4 06:08:50 Burbank kernel: ata6.00: configured for UDMA/133 Mar 4 06:08:50 Burbank kernel: ata6: EH complete Terracopy verify finished with no errors, those ports are on the m'board (M5A78L-M LX), Hitachi 2TB, SMART showing no errors. And Parity showing good, haven't run a re-check yet. UnRAID 4.7
March 4, 201214 yr Yes it is... provide a full syslog, and get smart reports from each drive. Also would help to have full system stats (particularly the size and model power supply, number and type of hard drives). May also want to try running a Parity check NOCORRECT.
March 4, 201214 yr What motherboard are you using? I have the same issue, doesn't affect the array though. Odd. Parity check passes every time.
March 4, 201214 yr Author ok everytime I try to post a response with the pastbin links I get this Forbidden You don't have permission to access /forum/index.php on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. so the hard way full log on pastebin - 6jVJFSAv smarts on pastebin - WJZ4CJCL M'board Asus M5A78L-M LX Maxtop ICX-4889B-20 4U Rackmount Server Case CPU AMD Athlon II X3 455 (which the M'Board unlocked to a Phenom II X4 B55) CoolerMaster SilentProM 700w Power Supply 2x Crucial 4 GB DDR3-1333 (CT51264BA1339) 6x Hitachi 2k3000, 2tb (soon to be 10x when controller cards come in the mail)
March 4, 201214 yr Could be power supply issue; although yours is a single 12v rail with 600W available for the 12v so shouldn't be an issue. I had similar errors when all drives would spin up at the same time - how I learned about the need for a single 12v rail with enough Amps; soon as I switched power supplies I have not seen the issue. Test it... tell unraid to spin down all drives (make sure nothing is writing to the array or keeping files open), wait a min, then tell unraid to spin up all drives; see if those errors pop back up right after you tell the drives to spin up.
March 4, 201214 yr Author trying that now, funny thing is that only 2 drives were spinning at the time.. the other four were down... and stayed down... I've had all 6 spinning at one many time (XBMC streamer pointed at this and have run media scans several times... ) hang on... spinning down now.... ok spun down Mar 4 15:59:58 Burbank kernel: mdcmd (83): spindown 0 (Routine) Mar 4 15:59:58 Burbank kernel: (Routine) Mar 4 15:59:58 Burbank kernel: mdcmd (84): spindown 1 (Routine) Mar 4 15:59:58 Burbank kernel: (Routine) Mar 4 15:59:58 Burbank kernel: mdcmd (85): spindown 2 (Routine) Mar 4 15:59:58 Burbank kernel: (Routine) Mar 4 15:59:58 Burbank kernel: mdcmd (86): spindown 3 (Routine) Mar 4 15:59:58 Burbank kernel: (Routine) Mar 4 15:59:58 Burbank kernel: mdcmd (87): spindown 4 (Routine) Mar 4 15:59:58 Burbank kernel: (Routine) Mar 4 15:59:58 Burbank kernel: mdcmd (88): spindown 5 (Routine) Mar 4 15:59:58 Burbank kernel: (Routine) spun up... Mar 4 16:03:03 Burbank kernel: mdcmd (89): spinup 0 (Routine) Mar 4 16:03:03 Burbank kernel: (Routine) Mar 4 16:03:03 Burbank kernel: mdcmd (90): spinup 1 (Routine) Mar 4 16:03:03 Burbank kernel: (Routine) Mar 4 16:03:03 Burbank kernel: mdcmd (91): spinup 2 (Routine) Mar 4 16:03:03 Burbank kernel: (Routine) Mar 4 16:03:03 Burbank kernel: mdcmd (92): spinup 3 (Routine) Mar 4 16:03:03 Burbank kernel: (Routine) Mar 4 16:03:03 Burbank kernel: mdcmd (93): spinup 4 (Routine) Mar 4 16:03:03 Burbank kernel: (Routine) Mar 4 16:03:03 Burbank kernel: mdcmd (94): spinup 5 (Routine) Mar 4 16:03:03 Burbank kernel: (Routine) (edit, was a little fast on the refresh there ) WHAT IT WAS DOING AT THE TIME... Terracopy from a WHS box to drive 5 (specifically there not letting it move things around)... this was the verify pass, so it was just reading the smeg out of the drive... 1,2,3,4 SHOULD have been spun down (for a while) with no access....
March 4, 201214 yr Not surprised it didn't show anything; as I said, PSU should have more than enough "juice" perhaps some of the guru's will have better ideas as to what those message are. Only other thing I can think of is an IRQ conflict; but have no idea how to check/correct for that. if its not corrupting parity and doesn't show very often; likely don't have to worry.
March 4, 201214 yr Author Was the first time I've seen it and I've been watching it like a hawk, transferred about 8tb to it so far (and moved things around on it..) I'm paranoid about it
March 4, 201214 yr I have a 660W Seasonic. I don't the erros are power related. I also have a large UPS attached to the system.
March 5, 201214 yr Author I. Did. stupid forum won't let me put in the pastbin link but it's up there.
March 5, 201214 yr I see no attachments. Please don't use pastebin. It's not only that the URLs don't work but my text editor is always open and it's much easier to search and use macros in a text editor. Please attach text files to a post. zip if needed.
March 6, 201214 yr This usually indicates a cable or power problem. See here: http://lime-technology.com/wiki/index.php?title=The_Analysis_of_Drive_Issues#Drive_Interface_Issues
Archived
This topic is now archived and is closed to further replies.