LSI SAS2008 PCI-Express Issues with 5+ Drives

[Mkeating]

Hello! I'm having an issue with my LSI SAS2008. I have 5 drives currently connected but unraid isn't recognizing my 5th drive as unassigned. I cannot find any information on why this issue is happening. Unraid shows a drive is connected, but won't allow me to assign it. Thoughts?

[JorgeB]

Please post the diagnostics: Tools- diagnostics 

[Mkeating]

6 hours ago, JorgeB said:

Please post the diagnostics: Tools- diagnostics 

Post the syslog.txt?

[ChatNoir]

The syslog is better than nothing but the diagnostics provide the syslogs and plenty of other informations about the system that help to understand the situation better and provide better advice.

It is available in the Tools tab, the Diagnostics. Just attach the archive in your next post.

[Mkeating]

Okay, here is the Diagnostics.

diagnostics-20210316-1110.zip

[JorgeB]

Drive is failing to initialize:

 

Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Sense Key : 0x2 [current] [descriptor]
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] ASC=0x4 ASCQ=0x0
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Sense Key : 0x2 [current] [descriptor]
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] ASC=0x4 ASCQ=0x0
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] 0-byte physical blocks
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Asking for cache data failed
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Spinning up disk...

 

Post a manual SMART report for that drive since the one in the diags is incomplete.

[Mkeating]

6 hours ago, JorgeB said:

Drive is failing to initialize:

 

Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Sense Key : 0x2 [current] [descriptor]
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] ASC=0x4 ASCQ=0x0
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Sense Key : 0x2 [current] [descriptor]
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] ASC=0x4 ASCQ=0x0
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] 0-byte physical blocks
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Test WP failed, assume Write Enabled
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Asking for cache data failed
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through
Mar 15 20:17:46 KEATING kernel: sd 7:0:0:0: [sdb] Spinning up disk...

 

Post a manual SMART report for that drive since the one in the diags is incomplete.

How do I do that when it isn't showing up in Unraid?

[JorgeB]

smartctl -x /dev/sdb

 

If it doesn't work swap cables with another drive, if it still doesn't it's likely a drive problem.

[ChatNoir]

Do you have a free SATA port on your MB ?

[JorgeB]

It's a SAS drive.

[Mkeating]

17 minutes ago, JorgeB said:

smartctl -x /dev/sdb

 

If it doesn't work swap cables with another drive, if it still doesn't it's likely a drive problem.

I ran the command, said the drive is spun down or busy, so it failed. I'll test a new cable next, then if that fails it's probably a bad drive.