Hey All, I am trying to install a new SAS HDD into my array (not my first SAS drive but most are SATA).  When I reboot the unraid, I can see it as an unallocated blue square drive.  I stop the array, bring up disk 22 (the next open slot), pull down to the drive.  Things go gray for a bit and then it comes back with no device in slot 22 and no unallocated drive.

 

In the syslog I get buffer i/o error on dev sdk.  I've attached the diagnostics and syslog.

 

Thanks ahead of time

 

Panos

syslog servme-diagnostics-20210128-1817.zip

How is that drive connected?   I do not have personal experience of SAS drives but I think a SAS drive will require different cable type to a SATA drive.

 

FYI:  the syslog is included in the diagnostics - no need normally to provide it separately.

Disk is failing to read:

 

Jan 28 18:12:47 Servme kernel: sd 12:0:0:0: [sdk] tag#434 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jan 28 18:12:47 Servme kernel: sd 12:0:0:0: [sdk] tag#434 Sense Key : 0x3 [current] [descriptor]
Jan 28 18:12:47 Servme kernel: sd 12:0:0:0: [sdk] tag#434 ASC=0x11 ASCQ=0x0
Jan 28 18:12:47 Servme kernel: sd 12:0:0:0: [sdk] tag#434 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00
Jan 28 18:12:47 Servme kernel: print_req_error: critical medium error, dev sdk, sector 0
Jan 28 18:12:50 Servme kernel: sd 12:0:0:0: [sdk] tag#434 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Jan 28 18:12:50 Servme kernel: sd 12:0:0:0: [sdk] tag#434 Sense Key : 0x3 [current] [descriptor]
Jan 28 18:12:50 Servme kernel: sd 12:0:0:0: [sdk] tag#434 ASC=0x11 ASCQ=0x0
Jan 28 18:12:50 Servme kernel: sd 12:0:0:0: [sdk] tag#434 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
Jan 28 18:12:50 Servme kernel: print_req_error: critical medium error, dev sdk, sector 0
Jan 28 18:12:50 Servme kernel: Buffer I/O error on dev sdk, logical block 0, async page read
Jan 28 18:12:50 Servme emhttpd: error: ckmbr, 2030: Input/output error (5): read: /dev/sdk

 

Not sure why, but SMART has a lot of logged issues, possibly a device problem.

9 hours ago, itimpi said:

How is that drive connected?   I do not have personal experience of SAS drives but I think a SAS drive will require different cable type to a SATA drive.

 

FYI:  the syslog is included in the diagnostics - no need normally to provide it separately.

True, the SAS drives have a slightly different connector than SATA.  In most cases a SATA can fit into a SAS connector, but not the other way around.  I am using this drive cage for my disks:

https://www.amazon.com/gp/product/B00DGZ42SM/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

 

The odd thing for me is that the drive populates in the list of drives and only dies when I try to add it to the array.  I am using this controller card for the interface:

https://www.amazon.com/Supermicro-AOC-SAS2LP-MV8-8-Channel-Adapter-Channel/dp/B005B0Z2I4/ref=sr_1_2?dchild=1&keywords=supermicro+sas+card&qid=1611928253&s=electronics&sr=1-2

 

As for more information, this is the 3rd SAS drive I have tried with this.  I am starting to wonder if it is my controller card

1 hour ago, panospatacos said:

I am starting to wonder if it is my controller card

Probably.

 

1 hour ago, panospatacos said:

The odd thing for me is that the drive populates in the list of drives and only dies when I try to add it to the array.  I am using this controller card for the interface:

https://www.amazon.com/Supermicro-AOC-SAS2LP-MV8-8-Channel-Adapter-Channel/dp/B005B0Z2I4/ref=sr_1_2?dchild=1&keywords=supermicro+sas+card&qid=1611928253&s=electronics&sr=1-2

 

this card has not been recommended for use with Unraid for some time as it has a propensity to drop drives for no obvious reason.    If you are not running VMs with hardware pass-through then disabling IOMMU seems to help.