F5F Stay Refreshed Hardware Desktop Unable to set up certain SAS drives with the LSI 9207-8i unit

Unable to set up certain SAS drives with the LSI 9207-8i unit

Unable to set up certain SAS drives with the LSI 9207-8i unit

C
CupInCup
Junior Member
Find
10
08-15-2023, 04:01 PM
#1
I'm experimenting with some SAS HDDs I have on hand, but certain models aren't initializing properly. (Windows Server 2022: right-click the drive in Disk Management and select 'Initialize' results in 'The request could not be performed due to an I/O device error.' Drives are connected via a Supermicro backplane to an IBM M5110 (in IT Mode) based on LSI 9207-8i. Some drives function: ST1000NM0023, ST2000NM0023, ST32000645SS. Others don't: ST1000NM0001, ST3000NM0023. Oddly, two of the ST31000424SS units work while the rest don't... The 1TB drives that fail show ~917GB, while those that succeed display ~931GB. This suggests a possible 520 Byte versus 512 Byte sector issue I encountered earlier, though both models now list 512 Byte sectors.) Edit: It could be the difference between 520 and 512 byte sectors—perhaps the manufacturer formatted them as 520 bytes. I'm reformatting one now to test if it works, which will take a long time.)
Reply
Reply
C
CupInCup
08-15-2023, 04:01 PM #1

I'm experimenting with some SAS HDDs I have on hand, but certain models aren't initializing properly. (Windows Server 2022: right-click the drive in Disk Management and select 'Initialize' results in 'The request could not be performed due to an I/O device error.' Drives are connected via a Supermicro backplane to an IBM M5110 (in IT Mode) based on LSI 9207-8i. Some drives function: ST1000NM0023, ST2000NM0023, ST32000645SS. Others don't: ST1000NM0001, ST3000NM0023. Oddly, two of the ST31000424SS units work while the rest don't... The 1TB drives that fail show ~917GB, while those that succeed display ~931GB. This suggests a possible 520 Byte versus 512 Byte sector issue I encountered earlier, though both models now list 512 Byte sectors.) Edit: It could be the difference between 520 and 512 byte sectors—perhaps the manufacturer formatted them as 520 bytes. I'm reformatting one now to test if it works, which will take a long time.)

Reply
Reply
I
IVANSERS999
Junior Member
Find
40
08-15-2023, 05:24 PM
#2
It involved a 520 byte versus 512 byte sector issue. I applied sg3utils to convert the drives into 512 byte sectors. Using sg_scan ^ provided the drive identifiers (PD X). Then sg_format --format --size 512 PDX substituted the actual ID, formatting each drive. All data would be erased and it would require several hours—even large 1TB drives take about 4–5 hours.
Reply
Reply
I
IVANSERS999
08-15-2023, 05:24 PM #2

It involved a 520 byte versus 512 byte sector issue. I applied sg3utils to convert the drives into 512 byte sectors. Using sg_scan ^ provided the drive identifiers (PD X). Then sg_format --format --size 512 PDX substituted the actual ID, formatting each drive. All data would be erased and it would require several hours—even large 1TB drives take about 4–5 hours.

Reply
Reply