Hello,

 

In the main section one of my drives are showing as emulated and if I click spin down I can here it power down and then spin it backup it does not change the status. I have looked at the logs for the drive and that is below. From reading it and not really knowing a lot it looks like its there so where else can I look to check.

 

Sep 12 09:03:14 Tower kernel: ata5: SATA max UDMA/133 abar m512@0xf7210000 port 0xf7210100 irq 122
Sep 12 09:03:14 Tower kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 12 09:03:14 Tower kernel: ata5.00: ATA-10: ST4000DM004-2CV104, WFN3N5K7, 0001, max UDMA/133
Sep 12 09:03:14 Tower kernel: ata5.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Sep 12 09:03:14 Tower kernel: ata5.00: configured for UDMA/133
Sep 12 09:03:14 Tower kernel: sd 5:0:0:0: [sdf] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Sep 12 09:03:14 Tower kernel: sd 5:0:0:0: [sdf] 4096-byte physical blocks
Sep 12 09:03:14 Tower kernel: sd 5:0:0:0: [sdf] Write Protect is off
Sep 12 09:03:14 Tower kernel: sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00
Sep 12 09:03:14 Tower kernel: sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 12 09:03:14 Tower kernel: sdf: sdf1
Sep 12 09:03:14 Tower kernel: sd 5:0:0:0: [sdf] Attached SCSI disk
Sep 12 09:03:24 Tower emhttpd: ST4000DM004-2CV104_WFN3N5K7 (sdf) 512 7814037168
Sep 12 09:03:24 Tower kernel: mdcmd (4): import 3 sdf 64 3907018532 0 ST4000DM004-2CV104_WFN3N5K7
Sep 12 09:03:24 Tower kernel: md: import disk3: (sdf) ST4000DM004-2CV104_WFN3N5K7 size: 3907018532
Sep 12 09:04:32 Tower kernel: ata5: SATA link down (SStatus 0 SControl 300)
Sep 12 09:04:34 Tower kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 12 09:04:34 Tower kernel: ata5.00: configured for UDMA/133

 

 

Since the disk is being emulated it's not up or down, all the other disks plus parity are being used instead, you should post the diagnostics to see what happened, ideally after the disk got disabled and before rebooting.

Well it was all ok it was only after a reboot that it started to display the error. I had to reboot to enable VXD so I could create some VM. I think I have attached the correct log as requested

tower-diagnostics-20200912-0937.zip

Because the diags are after rebooting we can't see what happened, but disk looks mostly healthy, so you can rebuild on top (disk appears to be empty though), still recommend replacing/swapping cables just to rule them out in case it happens again to the same disk.

Just a question being a massive newbie to this and so I dont make things worse how do I do this rebuild on top. I could not see anything obvious in the various setting apart from New Config but as far as I know this would start form afresh which is not what I want

 

I will shut it down and replace the cables aswell.

 

And thanks next time I know to grab some logs before I reboot. I just tried the normal turn it off and on again

2 minutes ago, Craig Horne said:

apart from New Config

No, that's not what you want, see here:

https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive

OK I have replaced the cables started the process as in the wiki (many Thanks) it was looking promising as it started to say rebuild then came up with errors and now has the same red cross. I have got the logs this time and not rebooted I would be most great full if you could look again.

tower-diagnostics-20200912-1029.zip

Still looks like a connection problem, if check/replace cables again, make sure also power cable.

well I have replaced every cable now I am wondering if its the SATA controller. Would it be a good idea or NOT to try plugging this drive into one of the currently OK sata sockets which is on the motherboard to see if it is the board / slot. Then plug a drive that is currently working and all ok into the PCIe sata board. Or is this just a horrible idea ?

 

It is on a PCIe board that is new and on the list of working boards and was all ok before the reboot to enable the VXD-t. I guess if the board is faulty I need to send it back but I would need to confirm this somehow but I dont want to mess the whole system up.

It could be the controller, or some controller incompatibly with that drive if this is a new device, though Asmedia controllers usually work fine.

 

You can try for example swap it with the SSD.

Interesting well I have as suggest put the SSD into the PCIe card and now it seems to be happily at the moment rebuilding the HD drive and the SSD is showing green. It is however showing this on the log for the drive is this something I need to be concerned about and also any idea why the SSD works in the card and not the Drive when it was will ok before reboot and I have not changed the drive I know this is a bit of finger in the air question.

 

I know its only a cheap SSD but I wanted to see if I could get all this working before I invested fully in my little project.

 

Your help in all this is very much appreciated by the way.

 

Sep 12 11:22:47 Tower kernel: ata6.00: exception Emask 0x10 SAct 0x80 SErr 0x400000 action 0x6 frozen
Sep 12 11:22:47 Tower kernel: ata6.00: irq_stat 0x08000000, interface fatal error
Sep 12 11:22:47 Tower kernel: ata6: SError: { Handshk }
Sep 12 11:22:47 Tower kernel: ata6.00: failed command: WRITE FPDMA QUEUED
Sep 12 11:22:47 Tower kernel: ata6.00: cmd 61/00:38:f8:2b:5c/02:00:01:00:00/40 tag 7 ncq dma 262144 out
Sep 12 11:22:47 Tower kernel: ata6.00: status: { DRDY }
Sep 12 11:22:47 Tower kernel: ata6: hard resetting link

tower-diagnostics-20200912-1131.zip

Those ATA errors suggest the SSD also isn't very happy there, so probably a good idea to replace that controller ASAP, since the SSD shouldn't normally be as stressed as an array device during a rebuild it might be OK to use it there for some time.

O right ok I will get that sorted then

 

Many thanks for all you help and assistance in this and being very quick on helping.  

I just wanted to say I have now replaced the PCIe card with one that has the JMB585 Chipset which was recommended and the errors have gone away and all seems to be fine. So thanks Again JorgeB