Just got a couple of more easystores for a server and got one installed and preclearing, the other i just shucked and installed, decided I wanted it in a different bay, moved it, and it did not mount. I didn't think anything of it and so I moved it back to the original spot thinking I would just preclear it and replace a faulty cable/test the current connection. Then the drive did not mount in the original bay. I checked the logs and saw the following, when I removed the drive again the errors stopped.

 

(the server and all dockers are still running, checked fix common problems and nothing and I will not have another drive to test with until later today. Just want to make sure my other data is not in danger) 

 

Dec 1 11:48:28 Helios kernel: ata5: limiting SATA link speed to 1.5 Gbps
Dec 1 11:48:28 Helios kernel: ata5: hard resetting link
Dec 1 11:48:29 Helios kernel: ata5: SATA link down (SStatus 0 SControl 310)
Dec 1 11:48:29 Helios kernel: ata5: EH complete
Dec 1 11:48:29 Helios kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen
Dec 1 11:48:29 Helios kernel: ata5: irq_stat 0x00400040, connection status changed
Dec 1 11:48:29 Helios kernel: ata5: SError: { PHYRdyChg CommWake DevExch }
Dec 1 11:48:29 Helios kernel: ata5: limiting SATA link speed to 1.5 Gbps
Dec 1 11:48:29 Helios kernel: ata5: hard resetting link
Dec 1 11:48:30 Helios kernel: ata5: SATA link down (SStatus 0 SControl 310)
Dec 1 11:48:30 Helios kernel: ata5: EH complete
Dec 1 11:48:30 Helios kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
Dec 1 11:48:30 Helios kernel: ata5: irq_stat 0x00000040, connection status changed
Dec 1 11:48:30 Helios kernel: ata5: SError: { CommWake DevExch }
Dec 1 11:48:30 Helios kernel: ata5: limiting SATA link speed to 1.5 Gbps
Dec 1 11:48:30 Helios kernel: ata5: hard resetting link
Dec 1 11:48:32 Helios kernel: ata5: SATA link down (SStatus 0 SControl 310)
Dec 1 11:48:32 Helios kernel: ata5: EH complete
Dec 1 11:48:32 Helios kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen
Dec 1 11:48:32 Helios kernel: ata5: irq_stat 0x00400040, connection status changed
Dec 1 11:48:32 Helios kernel: ata5: SError: { PHYRdyChg CommWake DevExch }
Dec 1 11:48:32 Helios kernel: ata5: limiting SATA link speed to 1.5 Gbps
Dec 1 11:48:32 Helios kernel: ata5: hard resetting link
Dec 1 11:48:33 Helios kernel: ata5: SATA link down (SStatus 0 SControl 310)
Dec 1 11:48:33 Helios kernel: ata5: EH complete
Dec 1 11:48:34 Helios kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 1 11:48:34 Helios kernel: ata5: irq_stat 0x08000000, interface fatal error
Dec 1 11:48:34 Helios kernel: ata5: hard resetting link
Dec 1 11:48:35 Helios kernel: ata5: SATA link down (SStatus 0 SControl 310)
Dec 1 11:48:35 Helios kernel: ata5: EH complete

System- CPU: Ryzen 1700x, MOBO: ASUS X370 Pro, unRAID version: 6.4.0_rc14

Edited December 1, 20178 yr by gcalaway
can't type :)

It's a SATA cable or connection problem or possibly but not very likely a bad SATA port.

 

The SATA link is so bad that it can't maintain even a 1.5 Gb/s link, let alone a 3 or 6 Gb/s one, and keeps resetting it. The standard issue red SATA leads leave a lot to be desired - plugs that fall out of their sockets, unnecessarily stiff cables, susceptibility to crosstalk. I always use latching connectors, flexible "figure of eight" cables and I loosely bundle them together rather than fastidiously lacing them in perfect parallel runs.

Edited December 1, 20178 yr by John_M
More info

Thanks for the information @John_M, I guess its possible I had two cables fail, just surprising to me.

 

I have been keeping an eye on my logs, upades:

 

Dec 1 14:25:56 Helios rc.diskinfo[9637]: SIGHUP received, forcing refresh of disks info.
Dec 1 14:25:58 Helios rc.diskinfo[9637]: SIGHUP received, forcing refresh of disks info.

More strange things I don't understand:

 

Dec 1 16:57:58 Helios php-fpm[9258]: [WARNING] [pool www] child 14422 exited on signal 7 (SIGBUS) after 217.012773 seconds from start
Dec 1 16:57:58 Helios nginx: 2017/12/01 16:57:58 [error] 9280#9280: *13310 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.1.65, server: , request: "POST /webGui/include/DeviceList.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.88", referrer: "http://192.168.1.88/Main"

3 hours ago, gcalaway said:

Thanks for the information @John_M, I guess its possible I had two cables fail, just surprising to me.

 

I have been keeping an eye on my logs, upades:

 

Dec 1 14:25:56 Helios rc.diskinfo[9637]: SIGHUP received, forcing refresh of disks info.
Dec 1 14:25:58 Helios rc.diskinfo[9637]: SIGHUP received, forcing refresh of disks info.

 

Yes, especially if they are the crappy red ones, it's very possible. I believe the message you're seeing is a feature of the Preclear plugin. It's probably caused by your disk coming and going offline. Fix the SATA link problem and see if it goes away.

 

The other strange things look as though they're related to the GUI. Fix your known problem - you'll need to power down to replace cables - and see how it is when you restart. If you still have problems post diagnostics.

Check your PSU too.

 

I had messages very simliar before and someone mentioned to change PSU.

I left it till last, changed SATA, PSU cables, SATA ports, even RMA'd my mobo.

 

Ended up being PSU, swapped it and not seen a message like it since (a few months now).