Hello there

I have some kind of a random issue. I Mounted a 3To disk under an unassigned device to save my deluge download outside the array. The drive is mounted on a clear server start, and few time after, minutes, hours (very random) Unraid unmount the disk. Which is an issue for me...

If I try to mount it back, it's not working, I have to reboot the server to resolve it but it's an infernal loop. SMART is perfect, the disk in new (few weeks) it is a ST3000M007 from Seagate.

Have you ever encounter that king of thing and can it be solved?

Thanks in advance for your answers!

Post diagnostics so we can help.

Ok, Here it is

tower-diagnostics-20190510-1319.zip

15 minutes ago, Florent73 said:

Ok, Here it is

tower-diagnostics-20190510-1319.zip 213.97 kB · 1 download

Looks like a disk or disk controller problem.

May 10 13:18:50 Tower unassigned.devices: Adding disk '/dev/sdk1'...
May 10 13:18:50 Tower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdk1' '/mnt/disks/Deluge_Downloads'
May 10 13:18:55 Tower kernel: XFS (sdk1): Filesystem has duplicate UUID 64b6e186-d938-450c-bada-11b490de3b6b - can't mount
May 10 13:18:55 Tower unassigned.devices: Mount of '/dev/sdk1' failed. Error message: mount: /mnt/disks/Deluge_Downloads: wrong fs type, bad option, bad superblock on /dev/sdk1, missing codepage or helper program, or other error. 
May 10 13:18:55 Tower unassigned.devices: Partition 'ST3000DM007-1WY10G_ZFN1P6PN' could not be mounted...
May 10 13:18:55 Tower kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1
May 10 13:18:55 Tower kernel: sas: ata19: end_device-1:0: cmd error handler
May 10 13:18:55 Tower kernel: sas: ata19: end_device-1:0: dev error handler
May 10 13:18:55 Tower kernel: sas: ata16: end_device-1:1: dev error handler
May 10 13:18:55 Tower kernel: sas: ata17: end_device-1:2: dev error handler
May 10 13:18:55 Tower kernel: sas: ata18: end_device-1:3: dev error handler
May 10 13:18:55 Tower kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 1 tries: 1

 

There are constant timeout errors on that disk:

May 10 01:42:05 Tower kernel: ata15.00: status: { DRDY }
May 10 01:42:05 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED
May 10 01:42:05 Tower kernel: ata15.00: cmd 60/08:00:b8:05:6c/00:00:d7:00:00/40 tag 30 ncq dma 4096 in
May 10 01:42:05 Tower kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 10 01:42:05 Tower kernel: ata15.00: status: { DRDY }
May 10 01:42:05 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED
May 10 01:42:05 Tower kernel: ata15.00: cmd 60/00:00:78:ee:2b/04:00:5d:01:00/40 tag 31 ncq dma 524288 in
May 10 01:42:05 Tower kernel:         res 40/00:ff:81:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)

Try swapping cables with another disk, if it's the same with another one of the SCU SATA ports try one of the Intel PCH ports.

Ok, I use to have issues with some sata connectors (or controller) in the past, I moved those on SCU SATA which correct it. I was planning to replace it with an LSI 9207 8i to bypass the motherboard.

Thanks both of you for your support

 

I'm not an expert in this diag stuff, do you see if my other disks (of the array) get issues with my disk controller?

I saw ata15.00 get a recurent problem

I saw too 

What does it mean?

5 minutes ago, Florent73 said:

What does it mean?

That's normal and not a problem.