Cannot Shutdown, hangs of Sync Filesystem

[mikesp18]

Hi, I'm pretty new. This is my second thread, and I am still having similar problems from the first thread here.

 

I'll attache some recent Syslogs that are still getting numerous errors.

 

Biggest problems are recently when trying to restart or stop the array (I usually use the GUI, similar when running shutdown from telnet), it hands when saying "Sync Filesystem".  The the only way to restart the system is to hard power off the system and restart.  Then the Parity has to recheck, which takes about 7 hours to do, but doesn't find any errors.

 

This system is still in close to the factory set up shape, having only received this system about 3 weeks ago.  The only real customizations I've done are adding a few packages from unMenu, including Powerdown, Screen, and Mail. In the previous thread, Helmonder suggested rechecking the cabling to my parity drive, which is loaded as "ata1.00: ATA-9: ST4000DM000-1F2168,            Z302NTZJ, CC54, max UDMA/133".  There were no loose cables or anything, still in the factory shipped state

 

These I suspect are relevant error lines from the log:

Apr 15 14:59:05 Orcrist kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen (Errors)
Apr 15 14:59:05 Orcrist kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)
Apr 15 14:59:05 Orcrist kernel: ata1: SError: { UnrecovData 10B8B BadCRC } (Errors)
Apr 15 14:59:05 Orcrist kernel:         res 50/00:00:df:5e:25/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) (Errors)
Apr 15 15:00:08 Orcrist kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen (Errors)
Apr 15 15:00:08 Orcrist kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)
Apr 15 15:00:08 Orcrist kernel: ata1: SError: { UnrecovData 10B8B BadCRC } (Errors)
Apr 15 15:00:08 Orcrist kernel:         res 50/00:00:7f:97:2e/00:00:01:00:00/e1 Emask 0x10 (ATA bus error) (Errors)
Apr 15 15:00:55 Orcrist kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen (Errors)
Apr 15 15:00:55 Orcrist kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)
Apr 15 15:00:55 Orcrist kernel: ata1: SError: { UnrecovData 10B8B BadCRC } (Errors)
Apr 15 15:00:55 Orcrist kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen (Errors)
Apr 15 15:00:55 Orcrist kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)
Apr 15 15:00:55 Orcrist kernel: ata1: SError: { UnrecovData 10B8B BadCRC } (Errors)
Apr 15 15:00:55 Orcrist kernel:         res 50/00:00:9f:bd:f2/00:00:01:00:00/e1 Emask 0x10 (ATA bus error) (Errors)
Apr 15 15:01:22 Orcrist kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen (Errors)
Apr 15 15:01:22 Orcrist kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)
Apr 15 15:01:22 Orcrist kernel: ata1: SError: { UnrecovData 10B8B BadCRC } (Errors)
Apr 15 15:01:22 Orcrist kernel:         res 50/00:00:ff:3f:5f/00:00:02:00:00/e2 Emask 0x10 (ATA bus error) (Errors)

 

I'm very new to this, and not great at trouble shooting.  I'm still able to use the shares, though there are very sluggish at times.  Since I keep getting ATA1.00 errors, could this be a faulty drive?

 

syslog-2015-04-15.txt

[morbidpete]

I have the same issue sometimes. I think my plex causes it, when unraid tries to kill the stream, plex starts it right back up and keeps the array going. I personally stop plex, then stop the array and dont have many issues.

[CHBMB]

I have the same issue sometimes. I think my plex causes it, when unraid tries to kill the stream, plex starts it right back up and keeps the array going. I personally stop plex, then stop the array and dont have many issues.

 

I run the Plex docker and have no problems, might be something worth considering..

[MortenSchmidt]

If you have a screen session running, that can prevent array stop. Even when the screen session doesn't seem to be accessing user/drive/cache shares. But it will be stuck  unmounting, not during sync.

 

Since this is during sync and you still have drive errors, you will need to proceed to replace the cable or drive or controller. If you don't have spare cables, swap it around and see if the problem moves with the cable, the drive or the controller port. Most likely (and hopefully) a bad cable.

[Squid]

I believe that even at the local terminal if its current directory is in a share / disk it will stop the disks from unmounting (since they are "in-use")