Unraid/SAS Drive issues

[FredRed315]

First time setting up Unraid, complete newbie, so bear with me please - 

 

Using an old computer as a NAS, here's the pertinent bits and parts:

Motherboard - Asrock Z77 Extreme4

CPU - i7-3770

Memory - 16Gb (4x4) Gskil Ripjaw PC3-12800 DDR3-1600 

LSI SAS 9201-8i

1 x Kingston 480GB A400 Sata3 2.5" Internal SSD

3 x Seagate Constellation ES.2 ST33000650SS 3TB 7.2KRPM 3.5" SAS HDD

 

Have all four hard drives connected to the 9201 via this cord.

 

Booted/installed Unraid from a USB, everything seemed to go fine, but it only sees the Kingston SSD, which I planned on using as a cache drive. The Seagate drives aren't showing up, except in Tools > System Devices > SCSI Devices. I just can't seem to do anything with them in Unraid.

 

In the boot sequence, I jumped into the LSI 9201 config, tried to format the drives though that, but it fails for all of them.

 

Tried using Gparted, it doesn't see the drives either.

 

I'm not thinking this is necessarily an Unraid problem, but I have no clue where to go from here.

 

On another note, one of the Seagates sounds like absolute trash/grinding for the first 20 seconds after booting, then quiets down. I'm sure there's an issue somewhere with (hopefully only) one of them, but I can't even get far enough to run tests on them.

 

Diagnostics Zip attached. 

tower-diagnostics-20200411-1856.zip

[JorgeB]

There's a problem identifiing the drives:

 

Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Sense Key : 0x2 [current] [descriptor]
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] ASC=0x4 ASCQ=0x0
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Sense Key : 0x2 [current] [descriptor]
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] ASC=0x4 ASCQ=0x0
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] 0 512-byte logical blocks: (0 B/0 B)
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] 0-byte physical blocks
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Test WP failed, assume Write Enabled
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Asking for cache data failed
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Assuming drive cache: write through
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Spinning up disk...

 

You can (and should) update LSI to latest firmware, but doubt it will help, looks like some issue with the disks, some times SAS devices come with unsupported features, like format protection, unsupported sector size, etc, can't see in these since even SMART reports aren't working.

[FredRed315]

2 hours ago, johnnie.black said:

There's a problem identifiing the drives:

 

Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Sense Key : 0x2 [current] [descriptor]
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] ASC=0x4 ASCQ=0x0
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Sense Key : 0x2 [current] [descriptor]
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] ASC=0x4 ASCQ=0x0
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] 0 512-byte logical blocks: (0 B/0 B)
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] 0-byte physical blocks
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Test WP failed, assume Write Enabled
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Asking for cache data failed
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Assuming drive cache: write through
Apr 11 15:04:42 Tower kernel: sd 9:0:2:0: [sdd] Spinning up disk...

 

You can (and should) update LSI to latest firmware, but doubt it will help, looks like some issue with the disks, some times SAS devices come with unsupported features, like format protection, unsupported sector size, etc, can't see in these since even SMART reports aren't working.

So, I tried formatting the drives to see if the sector size was the issue, followed the instructions here: 

 

I get this, and I'm not sure what to do from here:

 

root@Tower:~# sg_scan -i
/dev/sg0: scsi10 channel=0 id=0 lun=0 [em]
    Kingston  DataTraveler 2.0  PMAP [rmb=1 cmdq=0 pqual=0 pdev=0x0] 
/dev/sg1: scsi9 channel=0 id=0 lun=0
    ATA       KINGSTON SA400S3  K1B3 [rmb=0 cmdq=1 pqual=0 pdev=0x0] 
/dev/sg2: scsi9 channel=0 id=1 lun=0
    SEAGATE   ST33000650SS      0005 [rmb=0 cmdq=1 pqual=0 pdev=0x0] 
/dev/sg3: scsi9 channel=0 id=2 lun=0
    SEAGATE   ST33000650SS      0005 [rmb=0 cmdq=1 pqual=0 pdev=0x0] 
/dev/sg4: scsi9 channel=0 id=3 lun=0
    SEAGATE   ST33000650SS      0005 [rmb=0 cmdq=1 pqual=0 pdev=0x0] 
root@Tower:~# sg_format --format --size=512 -v /dev/sg2
    SEAGATE   ST33000650SS      0005   peripheral_type: disk [0x0]
      PROTECT=1
      << supports protection information>>
VPD_UNIT_SERIAL_NUM gave res=5
    mode sense(10) cdb: [5a 00 01 00 00 00 00 00 fc 00]
mode sense(10):
Descriptor format, current; Sense key: Not Ready
Additional sense: Logical unit not ready, cause not reportable
  Descriptor type: Field replaceable unit code: 0x0
  Descriptor type: Vendor specific [0x80]
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 
MODE SENSE (10) command: Device not ready, type: sense key

 

[bcbgboy13]

I am not sure if you can mix SATA and SAS drives on the same breakout cable.

They use a different signaling scheme, which also allows for much longer cables for the SAS drives.

I believe that if you mix them on the same cable this will force the controller to use the SATA signaling and this may not be liked by the SAS drives

 

The cable you are using is already 1m long anyway which is the max for a SATA cable.  It is better to use a shorter regular SATA cable attached to one of the MB ports for the SATA drive and keep the SAS drives separate.

[JorgeB]

9 hours ago, bcbgboy13 said:

I am not sure if you can mix SATA and SAS drives on the same breakout cable.

That's not a problem.

[FredRed315]

2 hours ago, johnnie.black said:

That's not a problem.

Soooo... Where do I go from here? Take a loss and toss the drives in the trash bin?

Edited April 13, 2020 by FredRed315

[JorgeB]

Did you update the LSI HBA? Do you have another controller you can test with? Other than that don't have more ideas.

[Frank1940]

Google    pin3 +3V problem   and make sure you don't have this problem.

[FredRed315]

1 hour ago, Frank1940 said:

Google    pin3 +3V problem   and make sure you don't have this problem.

I tried it with some scotch tape (for a temp fix) and it didn't change anything.

[FredRed315]

6 hours ago, johnnie.black said:

Did you update the LSI HBA? Do you have another controller you can test with? Other than that don't have more ideas.

No, I had issues trying to flash the firmware, I don't know command line/linux commands enough to get through the process if it doesn't go exactly as laid out. I don't have another controller, but I'm about to buy one that is already updated.

Edited April 13, 2020 by FredRed315