April 2, 20188 yr Hi, I've been putting together my NAS build for 6 or so months, and today I finished putting it together and decided to go with unRAID and have begun the install process. Unfortunately, I've been stuck for hours trying to recognise all my drives. I can only see one of my two 8 TB WD Red drives, despite the fact that they are both visible in BIOS (please see attached images). Things I have tried: swapping SATA cables swapping SATA port using a different SATA power cable header (on the same chain of 3 which powers the other 8 TB WD Red). I probably should've gone with the trial rather than being super confident that unRAID would be the silver bullet... Please find my diagnostics attached. Here is a link to my system components: https://au.pcpartpicker.com/list/4hfjyX Thank you in advance to anyone who can help. nas-diagnostics-20180402-1933.rar
April 2, 20188 yr The first disk is detected just fine. The second one is seen briefly and then lost. The SATA port is reset to a slower speed and then disabled. The fault is either the port, the cable or the drive electronics. Change the SATA cable (again) and check the power to the disk (again). Quote Apr 2 19:25:01 NAS kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 2 19:25:01 NAS kernel: ata2.00: failed to read native max address (err_mask=0x100) Apr 2 19:25:01 NAS kernel: ata2.00: HPA support seems broken, skipping HPA handling Apr 2 19:25:01 NAS kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 2 19:25:01 NAS kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 2 19:25:01 NAS kernel: ata2.00: READ LOG DMA EXT failed, trying PIO Apr 2 19:25:01 NAS kernel: ata2.00: NCQ Send/Recv Log not supported Apr 2 19:25:01 NAS kernel: ata2.00: NCQ Send/Recv Log not supported Apr 2 19:25:01 NAS kernel: ata2.00: ATA-9: WDC WD80EFAX-68LHPN0, 7SGK33TC, 83.H0A83, max UDMA/133 Apr 2 19:25:01 NAS kernel: ata2.00: 15628053168 sectors, multi 0: LBA48 NCQ (depth 31/32) Apr 2 19:25:01 NAS kernel: ata2.00: failed to enable Sense Data Reporting, Emask 0x40 Apr 2 19:25:01 NAS kernel: ata2.00: failed to set xfermode (err_mask=0x40) Apr 2 19:25:01 NAS kernel: ata2: limiting SATA link speed to 3.0 Gbps Apr 2 19:25:01 NAS kernel: ata2.00: limiting speed to UDMA/133:PIO3 Apr 2 19:25:01 NAS kernel: ata2: SATA link down (SStatus 0 SControl 320) Apr 2 19:25:01 NAS kernel: ata2.00: disabled
April 2, 20188 yr A couple of other things. You're using a SATA M.2 SSD so when you're trying different SATA ports note that (from your Partpicker page): Quote The motherboard M.2 slot #2 shares bandwidth with a SATA 6.0 Gb/s port. When the M.2 slot is populated, one SATA 6.0 Gb/s port is disabled. It doesn't say which one but your motherboard manual should. Also, you're using a Ryzen CPU so (from these release notes - different version but it still applies): Quote We ported a simplified version of the zenstates.py utility to C (to avoid including python in bzroot) which may be used to disable Ryzen C6 states (as workaround for Ryzen idle freeze issue). We have found that sometimes bios option to disable C6 does not exist or does not do the right thing. If you want to use this utility, we suggest that you edit your 'config/go' file on your USB flash device. Add this line just before emhttp is invoked: zenstates --c6-disable
April 2, 20188 yr Author 21 minutes ago, John_M said: The first disk is detected just fine. The second one is seen briefly and then lost. The SATA port is reset to a slower speed and then disabled. The fault is either the port, the cable or the drive electronics. Change the SATA cable (again) and check the power to the disk (again). Thank you John. I've connected it to my main workstation, and it doesn't even recognise in the BIOS or within Windows (I was going to run WD LifeGuard). So I've tried a whole bunch of SATA cables, ports and power options now and it's a no go. Probably DOA and nothing to do with unRAID. 9 minutes ago, John_M said: A couple of other things. You're using a SATA M.2 SSD so when you're trying different SATA ports note that (from your Partpicker page): It doesn't say which one but your motherboard manual should. Also, you're using a Ryzen CPU so (from these release notes - different version but it still applies): I'm not using the shared port, good pick up though. Thank you for the Ryzen heads up, I'll make that change once I figure out what is going on with the drive. Edited April 2, 20188 yr by mcjfauser attach workstation image
April 2, 20188 yr The disk might have been dropped and damaged or zapped by static. Sounds like you need to get it replaced. Good luck!
Archived
This topic is now archived and is closed to further replies.