jljude Posted May 12, 2018 Share Posted May 12, 2018 Hello, been an Unraid'er for quite some time, but not overly technical. I've scanned multiple pages on the forum to help troubleshoot my issue but not finding a solution that fixes my issue. I was getting notification of UDMA CRC errors (mainly because the upgrade on the OS notifies it now of this). The cache drive is less than 6 months old, and after the UDMA errors, I replaced the SATA cable, cleaned all terminals, and resat the power cable too. I'm also noticing that files aren't being moved to the disk from the cache drive. I can manually move them via Windows, but wanted someone's help to translate my diagnostics. Thought these may be related given they all involve the cache drive. tower-diagnostics-20180512-0823.zip Link to comment
JorgeB Posted May 12, 2018 Share Posted May 12, 2018 6 minutes ago, jljude said: I'm also noticing that files aren't being moved to the disk from the cache drive. Check that that or those shares have use cache set to "Yes" 6 minutes ago, jljude said: I have a new cache drive, and I replaced the SATA cables. Your still getting ATA errors on the cache device, most likely the SATA cable. May 12 08:19:04 Tower kernel: ata6.00: exception Emask 0x10 SAct 0x7ffffffe SErr 0x0 action 0x6 frozen May 12 08:19:04 Tower kernel: ata6.00: irq_stat 0x08000000, interface fatal error May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/40:08:48:69:f7/05:00:11:00:00/40 tag 1 ncq dma 688128 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/38:10:88:6e:f7/00:00:11:00:00/40 tag 2 ncq dma 28672 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/40:18:c0:6e:f7/05:00:11:00:00/40 tag 3 ncq dma 688128 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/40:20:00:74:f7/05:00:11:00:00/40 tag 4 ncq dma 688128 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/40:28:40:79:f7/05:00:11:00:00/40 tag 5 ncq dma 688128 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/40:30:80:7e:f7/00:00:11:00:00/40 tag 6 ncq dma 32768 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/40:38:c0:7e:f7/05:00:11:00:00/40 tag 7 ncq dma 688128 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/48:40:00:84:f7/05:00:11:00:00/40 tag 8 ncq dma 692224 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/78:48:48:89:f7/05:00:11:00:00/40 tag 9 ncq dma 716800 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/00:50:c0:8e:f7/0a:00:11:00:00/40 tag 10 ncq dma 1310720 ou May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/00:58:c0:98:f7/06:00:11:00:00/40 tag 11 ncq dma 786432 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/d0:60:c0:9e:f7/09:00:11:00:00/40 tag 12 ncq dma 1286144 ou May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/30:68:90:a8:f7/06:00:11:00:00/40 tag 13 ncq dma 811008 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/00:70:c0:ae:f7/0a:00:11:00:00/40 tag 14 ncq dma 1310720 ou May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/00:78:c0:b8:f7/06:00:11:00:00/40 tag 15 ncq dma 786432 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/00:80:c0:be:f7/0a:00:11:00:00/40 tag 16 ncq dma 1310720 ou May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/00:88:c0:c8:f7/06:00:11:00:00/40 tag 17 ncq dma 786432 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/e0:90:c0:ce:f7/09:00:11:00:00/40 tag 18 ncq dma 1294336 ou May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/20:98:a0:d8:f7/06:00:11:00:00/40 tag 19 ncq dma 802816 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/a8:a0:c0:de:f7/09:00:11:00:00/40 tag 20 ncq dma 1265664 ou May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/58:a8:68:e8:f7/06:00:11:00:00/40 tag 21 ncq dma 831488 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/00:b0:c0:ee:f7/0a:00:11:00:00/40 tag 22 ncq dma 1310720 ou May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/00:b8:c0:f8:f7/06:00:11:00:00/40 tag 23 ncq dma 786432 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/00:c0:c0:fe:f7/0a:00:11:00:00/40 tag 24 ncq dma 1310720 ou May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/60:c8:c0:08:f8/06:00:11:00:00/40 tag 25 ncq dma 835584 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/e0:d0:c0:0e:fb/05:00:11:00:00/40 tag 26 ncq dma 770048 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/40:d8:a0:14:fb/05:00:11:00:00/40 tag 27 ncq dma 688128 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/e0:e0:e0:19:fb/04:00:11:00:00/40 tag 28 ncq dma 638976 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/40:e8:c0:1e:fb/05:00:11:00:00/40 tag 29 ncq dma 688128 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED May 12 08:19:04 Tower kernel: ata6.00: cmd 61/48:f0:00:24:fb/05:00:11:00:00/40 tag 30 ncq dma 692224 out May 12 08:19:04 Tower kernel: res 40/00:10:88:6e:f7/00:00:11:00:00/40 Emask 0x10 (ATA bus error) May 12 08:19:04 Tower kernel: ata6.00: status: { DRDY } May 12 08:19:04 Tower kernel: ata6: hard resetting link May 12 08:19:05 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) May 12 08:19:05 Tower kernel: ata6.00: supports DRM functions and may not be fully accessible May 12 08:19:05 Tower kernel: ata6.00: supports DRM functions and may not be fully accessible May 12 08:19:05 Tower kernel: ata6.00: configured for UDMA/133 May 12 08:19:05 Tower kernel: ata6: EH complete May 12 08:19:05 Tower kernel: ata6.00: Enabling discard_zeroes_data Link to comment
jljude Posted May 12, 2018 Author Share Posted May 12, 2018 The share that isn't moving "Testing" from cache has been set to "Yes". I don't think I've changed anything to cause this, but it has normally worked. I just noticed the CACHE drive was filling up and not emptying a day or so ago. I just powered down, and replaced the SATA cable again (replaced it yesterday as I bought 3 new ones from Amazon and I assume they're good). I'll try another one. On the last pic you posted, showing the below, is that related, or did you mean to post something that I need to address to resolve the repeating error? ata6.00: failed command: WRITE FPDMA QUEUED Thanks for the quick responses Johnnie.Black. You seem to be very helpful to many uses on the forum. Link to comment
JorgeB Posted May 12, 2018 Share Posted May 12, 2018 1 minute ago, jljude said: On the last pic you posted, showing the below, is that related, or did you mean to post something that I need to address to resolve the repeating error? Those are the SSD errors, if you see those on the log there's still problem. Link to comment
jljude Posted May 12, 2018 Author Share Posted May 12, 2018 when I set to power down, it was sitting powered on for a while and I couldn't access the gui page. So, I had no choice but to manually power off so the parity is rebuilding. I probably should have hooked a monitor up to it to see what was going on, but wasn't convenient. After it booted back up, I selected Move Now, and seems the data is writing to the disk/array. Attached is the new set of diagnostics. tower-diagnostics-20180512-0850.zip Link to comment
jljude Posted May 12, 2018 Author Share Posted May 12, 2018 I got another UDMA CRC error and the count increased again. Link to comment
JorgeB Posted May 12, 2018 Share Posted May 12, 2018 If it's not the cable the next candidate would be the controller, try a different port or another one if available. Link to comment
jljude Posted May 12, 2018 Author Share Posted May 12, 2018 johnnie.black When I replaced the SATA cable, and then booted up, I had a UDMA CRC error, but I think it was left over as it hasn't shown that error again and the MOVER seems to be working ok. Not sure if the new cable I replaced the first time was bad, or if I just didn't have it seated properly, but all is well now. Thanks again for all of your help. Link to comment
jljude Posted May 14, 2018 Author Share Posted May 14, 2018 Johnnie.black. I went through and cleaned out all cables (sata and power) and also switched ports on the motherboard. The UDMA CRC errors seems to have gone away, but I'm still getting the Mover not working. I show it runs, skips the files, and then finishes. I can't see why they're skipping the files. I've gone in and changed Share settings, rebooted a few time, and still getting this symptom. I have mover logging turned on so hopefully it points out some areas of the cause. Justin tower-diagnostics-20180514-0754.zip Link to comment
JorgeB Posted May 14, 2018 Share Posted May 14, 2018 You share settings look correct, but in case something got confused, remove the included disks in both the testing share (disk1) and the global share settings (disk1,2,3,4), leave everything blank, so all disks are included and try again, if it works you can include again the disks you want. Link to comment
jljude Posted May 24, 2018 Author Share Posted May 24, 2018 johnnie.black I've replaced the sata cable and the actual SSD drive. I am no longer getting the udma crc errors. Old drive was a new Samsung Evo, and it kept erring out. I replaced with a Crucial and no issues so far. However, the Mover isn't working. It just keeps showing it has skipped the files I expect it to move. tower-diagnostics-20180523-2002.zip Link to comment
bonienl Posted May 24, 2018 Share Posted May 24, 2018 Mover will not move any file in use. You can try to stop the docker service and initiate a manual move from the Main page. Link to comment
jljude Posted May 24, 2018 Author Share Posted May 24, 2018 Are you saying the 3 files were in use, as I don't show they were. Also, I stopped all dockers and then manually set the mover again, and got the same results. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.