So, by accident i bought SAS disk instead of SATA, i have no way to return it so i decided to buy SAS controller recommended by people (link).

 

I can see the disk in Unraid, but disk is greyed out, doesn't have temps visible and size is 0 B. If i open the disk log it's spamming this:

Jan 18 15:23:41 Amcro-Host kernel: sd 1:0:3:0: [sdb] Spinning up disk...
Jan 18 15:24:14 Amcro-Host kernel: sd 1:0:3:0: [sdb] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK
Jan 18 15:24:14 Amcro-Host kernel: sd 1:0:3:0: [sdb] Sense Key : 0x4 [current] [descriptor] 
Jan 18 15:24:14 Amcro-Host kernel: sd 1:0:3:0: [sdb] ASC=0x4c <<vendor>>ASCQ=0xab 
Jan 18 15:24:14 Amcro-Host kernel: sd 1:0:3:0: [sdb] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK
Jan 18 15:24:14 Amcro-Host kernel: sd 1:0:3:0: [sdb] Sense Key : 0x4 [current] [descriptor] 
Jan 18 15:24:14 Amcro-Host kernel: sd 1:0:3:0: [sdb] ASC=0x4c <<vendor>>ASCQ=0xab 
Jan 18 15:24:14 Amcro-Host kernel: sd 1:0:3:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
Jan 18 15:24:14 Amcro-Host kernel: sd 1:0:3:0: [sdb] 0-byte physical blocks
Jan 18 15:24:14 Amcro-Host kernel: sd 1:0:3:0: [sdb] Test WP failed, assume Write Enabled
Jan 18 15:24:14 Amcro-Host kernel: sd 1:0:3:0: [sdb] Asking for cache data failed
Jan 18 15:24:14 Amcro-Host kernel: sd 1:0:3:0: [sdb] Assuming drive cache: write through
Jan 18 15:24:14 Amcro-Host kernel: sd 1:0:3:0: [sdb] Attached SCSI disk
Jan 18 15:24:15 Amcro-Host emhttpd: device /dev/sdb has size zero

 

This is firmware version i get for my controller:

LSISAS2308: FWVersion(20.00.06.00), ChipRevision(0x05), BiosVersion(07.39.02.00)

 

I'm adding diagnostics too if it helps. I'm not sure if maybe it's broken controller or disk, any help would or information would be nice!

Thanks in advance

amcro-host-diagnostics-20250118-1612.zip

Edited January 18, 20251 yr by Amcro

Is the LSI in IT mode?

It should be, eBay listing said it's in IT mode, i can see disk and controller in Unraid, but i didn't manage to get working sas2flash so i can't confirm if it's in IT mode.

 

EDIT: Okay i did check and the card is in IT mode

LSI Corporation SAS2 Flash Utility
Version 20.00.00.00 (2014.09.18) 
Copyright (c) 2008-2014 LSI Corporation. All rights reserved 

        Adapter Selected is a LSI SAS: SAS2308_1(D1) 

        Controller Number              : 0
        Controller                     : SAS2308_1(D1) 
        PCI Address                    : 00:01:00:00
        SAS Address                    : 56c92bf-0-0017-825b
        NVDATA Version (Default)       : 14.01.00.06
        NVDATA Version (Persistent)    : 14.01.00.06
        Firmware Product ID            : 0x2214 (IT)
        Firmware Version               : 20.00.06.00
        NVDATA Vendor                  : LSI
        NVDATA Product ID              : SAS9207-8i
        BIOS Version                   : 07.39.02.00
        UEFI BSD Version               : N/A
        FCODE Version                  : N/A
        Board Name                     : SAS9207-8i
        Board Assembly                 : N/A
        Board Tracer Number            : N/A

        Finished Processing Commands Successfully.
        Exiting SAS2Flash.

 

Edited January 18, 20251 yr by Amcro
New info

Googled the errors... Looks like maybe a bad drive.  You could try and update the firmware in it.  Possibly even reformat it (keeping 512 byte size).  Both of these options will need to be done in a not unRAID environment.  Maybe you could somehow use VMs ... Thinking aloud for that.

 

Leave this up for a while and see if some bigger brains can deliver some better options than what I found.

Yeah, i've tried reformating but i couldn't even start the format but i get "MODE SENSE (10) command: Medium or hardware error"

 

Also tried changing the cable and plugging it in different port on SAS card just to be sure but results were the same.

 

I'm hoping there is something else i need to do to make it work but I'm pretty new to SAS world and got stuck.

SAS drives are different from SATA drives, in that a failed SATA drive will say 'hold on, something is wrong, let me try again', and the system waits and tries again, and that basically hangs the system until whatever is wrong is fixed.

SAS drives however, have their electronic and drive part separate, so they'll report an error, and not hang the system. That means that even a drive that doesn't spin up and doesn't work can still be talked with, just nothing will work.

For your drive, it is reporting a 'sense key' of 4 which means Hardware error, and an Additional Sense Code (asc) of 4c which means 'logical unit cannot be configured' So something maybe timing out.

Try listening to the drive to hear if it spins up at all, and if it doesn't, and you have a sata-power-connection, use a molex-to-sata adapter instead because it may be suffering from the 3.3v issue. If that doesn't fix it, the drive should be replaced.

 

Also, you should update the firmware on your card first, the latest version is 20.00.07 and is required, all previous versions have errors and bugs, like the 20.00.06 on your card.

Edited January 18, 20251 yr by Wody

Thank You, I didn't know the 3.3 V issue, I'm definitely going to grab Molex to SATA adapter and check if it fixes disk problems and will report results here.

Another thing is, I've tried to update firmware, but I get error "ERROR: Could not open file: 9207-8.bin" no matter what i try. Permissions, user ownership, renaming file, full path to file, everything gives me same error. I'm not sure if it's not possible to do update through Unraid.

 

EDIT: I've just realized i never put which disk i bought which also might be relevant to this case.

The disk in question is:

Toshiba MG09 MG09SCP18TA HDEPYA0SMB51 18TB 7.2K RPM SAS 12Gb/s 4Kn SED 3.5in Hard Drive

Edited January 19, 20251 yr by Amcro

Also make sure the device s not write protected, this can happen with SED drives.

 

https://forums.unraid.net/topic/110835-solved-help-with-a-sas-drive/#findComment-1011689

 

Thank you guys for help, disk wont spin up even with Molex to SATA adapter. It looks like the disk is the problem. I will try to return the disk and use the LSI card for SATA disk expansion.