That's good enough for me! I've ordered one from eBay, it should by Friday.I'm not 100% sure, but I'm positive enough that your case is completely similar as far as I can see
I'll keep you posted and thanks so much for all your efforts so far!
That's good enough for me! I've ordered one from eBay, it should by Friday.I'm not 100% sure, but I'm positive enough that your case is completely similar as far as I can see
perccli can detect the H700, but it fails to show the IBM SAS SSD (I assume this is to be expected considering the drive is not detected in the controller's BIOS either). I did attach another drive to the H700 so I could confirm the commands work. Even though perccli would not display the IBM SAS SSD, I ran the 'secureerase' command at the location I knew it was physically attached too, but this ultimately failed.What you can try to do next is to load Windows with your drive attached to H700 and see how perccli (or MegaCli for older controllers) will show this drive.
This showed some promise, which surprises me as the sedutil for FreeBSD appears to be a port of the Linux tool.If this fails too there was a post somewhere in other topic that sedutil fails into linux but works correctly into TrueNas. Try this (with HBA) into TrueNas.
Scanning for Opal compliant disks
/dev/ada0 E IBM SSG IBM SSGSVW800 7201
sedutil-cli --yesIreallywanttoERASEALLmydatausingthePSID redacted /dev/da0
revertTper completed successfully
sedutil-cli --PSIDrevert redacted /dev/da0
revertTper completed successfully
sedutil-cli --PSIDrevertAdminSP redacted /dev/da0
was not recognised)sg_format -v --format --size=512 /dev/da0
returns the same failure messages as before.dd if=/dev/zero of=/dev/da0 bs=1m count=32
or via the TrueNAS UI results in the same error as described here.Good, if PSID revert was succesful, LBA ranges has to be unlocked now. Format commands may fail now because those LBA ranges are unclaimed and drive has zero available capacity for format. Can you please list the output of smartctl utility to prove of deny this assumption?I feel as if we got much closer, but not quite there!
Trysg_format -v --format --size=512 /dev/da0
returns the same failure messages as before.
sg_format --resize --count=-1 /dev/da0
prior to formatCan you please list the output of smartctl utility to prove of deny this assumption?
smartctl 7.1 2019-12-30 r5022 [FreeBSD 12.2-RELEASE-p2 amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: IBM-SSG
Product: IBM-SSGMSVW800
Revision: 7201
Compliance: SPC-4
User Capacity: 800,166,073,344 bytes [800 GB]
Logical block size: 528 bytes
Physical block size: 4224 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5000c500ad704fd8
Serial number: redacted
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Mon Feb 8 23:46:24 2021 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Percentage used endurance indicator: 0%
Current Drive Temperature: 33 C
Drive Trip Temperature: 65 C
Elements in grown defect list: 0
Error counter log:
Errors Corrected by Total Correction Gigabytes Total
ECC rereads/ errors algorithm processed uncorrected
fast | delayed rewrites corrected invocations [10^9 bytes] errors
read: 248218036 0 12261420 248218036 0 6173.867 0
write: 0 0 0 0 0 5079.482 0
smartctl 7.1 2019-12-30 r5022 [FreeBSD 12.2-RELEASE-p2 amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: IBM-SSG
Product: IBM-SSGMSVW800
Revision: 7201
Compliance: SPC-4
User Capacity: 800,166,073,344 bytes [800 GB]
Logical block size: 528 bytes
Physical block size: 4224 bytes
LU is resource provisioned, LBPRZ=1
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Logical Unit id: 0x5000c500ad704fd8
Serial number: redacted
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Mon Feb 8 23:54:27 2021 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
Read Cache is: Enabled
Writeback Cache is: Disabled
=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Percentage used endurance indicator: 0%
Current Drive Temperature: 33 C
Drive Trip Temperature: 65 C
Elements in grown defect list: 0
Error counter log:
Errors Corrected by Total Correction Gigabytes Total
ECC rereads/ errors algorithm processed uncorrected
fast | delayed rewrites corrected invocations [10^9 bytes] errors
read: 248218036 0 12261420 248218036 0 6173.867 0
write: 0 0 0 0 0 5079.482 0
verify: 0 0 0 0 0 3200.664 0
Non-medium error count: 0
No Self-tests have been logged
Background scan results log
Status: waiting until BMS interval timer expires
Accumulated power on time, hours:minutes 321:51 [19311 minutes]
Number of background scans performed: 34, scan progress: 0.00%
Number of background medium scans performed: 0
Protocol Specific port log page for SAS SSP
relative target port id = 1
generation code = 0
number of phys = 1
phy identifier = 0
attached device type: SAS or SATA device
attached reason: power on
reason: loss of dword synchronization
negotiated logical link rate: phy enabled; 6 Gbps
attached initiator port: ssp=1 stp=1 smp=1
attached target port: ssp=0 stp=0 smp=0
SAS address = 0x5000c500ad704fd9
attached SAS address = 0x5000ea62a0058d00
attached phy identifier = 4
Invalid DWORD count = 5
Running disparity error count = 5
Loss of DWORD synchronization = 2
Phy reset problem = 0
Phy event descriptors:
Invalid word count: 5
Running disparity error count: 5
Loss of dword synchronization count: 2
Phy reset problem count: 0
relative target port id = 2
generation code = 0
number of phys = 1
phy identifier = 1
attached device type: no device attached
attached reason: unknown
reason: unknown
negotiated logical link rate: phy enabled; unknown
attached initiator port: ssp=0 stp=0 smp=0
attached target port: ssp=0 stp=0 smp=0
SAS address = 0x5000c500ad704fda
attached SAS address = 0x0
attached phy identifier = 0
Invalid DWORD count = 0
Running disparity error count = 0
Loss of DWORD synchronizati
Trysg_format --resize --count=-1 /dev/da0
prior to format
IBM-SSG IBM-SSGMSVW800 7201 peripheral_type: disk [0x0]
Unit serial number: redacted
LU name: 5000c500ad704fd8
Mode Sense (block descriptor) data, prior to changes:
Number of blocks=1515466048 [0x5a542d40]
Block size=528 [0x210]
Resize operation seems to have been successful
IBM-SSG IBM-SSGMSVW800 7201 peripheral_type: disk [0x0]
PROTECT=0
Unit serial number: redacted
LU name: 5000c500ad704fd8
mode sense(10) cdb: [5a 00 01 00 00 00 00 00 fc 00]
Mode Sense (block descriptor) data, prior to changes:
Number of blocks=1515466048 [0x5a542d40]
Block size=528 [0x210]
mode select(10) cdb: [55 11 00 00 00 00 00 00 1c 00]
mode select(10):
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
Field replaceable unit code: 17
Sense Key Specific: Error in Data parameters: byte 13 bit 7
Try MODE SELECT again with SP=0 this time
mode select(10) cdb: [55 10 00 00 00 00 00 00 1c 00]
I did actually try this under FreeBSD (TrueNAS) previously, though I didn't list it above. Here is the same command under Linux though:How about--six
option?
IBM-SSG IBM-SSGMSVW800 7201 peripheral_type: disk [0x0]
PROTECT=0
Unit serial number: redacted
LU name: 5000c500ad704fd8
mode sense(6) cdb: [1a 00 01 00 fc 00]
Mode Sense (block descriptor) data, prior to changes:
Number of blocks=1515466048 [0x5a542d40]
Block size=528 [0x210]
mode select(6) cdb: [15 11 00 00 18 00]
mode select(6):
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
Field replaceable unit code: 17
Sense Key Specific: Error in Data parameters: byte 9 bit 7
Try MODE SELECT again with SP=0 this time
mode select(6) cdb: [15 10 00 00 18 00]
mode select(6):
Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in parameter list
Field replaceable unit code: 17
Sense Key Specific: Error in Data parameters: byte 9 bit 7
MODE SELECT command: Illegal request, type: sense key, apart from Invalid opcode
I have just tried this now, however the outcome is the same as the previous attempts, for example:Have you tried to change the firmware this time?
Write buffer: pass-through os error: Invalid argument
Write buffer failed: Invalid argument
sg_write_buffer failed: Invalid argument
Accept my sincere condolences. Did you try to format the second one with Seachest?I'm just got two IBM SSD drives. One is a Micron S630DC 3.8T (MTFDJAL3T8MBT), the other one is a Seagate Nytro 7.68T (XS7680SE70014).
formatUnit not working either, enabled verbose mode to get more infowrong option,--formatUnit
is what you need, --setSectorSize is fast format change from 512e to 4096 and will not work for your case even if the drive supports it.
Thank for the correction! I've just cloned the iprutils git repo. After the build I can run it without any errors, but cant find any controllers/disks Do I need to make some extra steps to get it work? I tried with LSI SAS2008 and LSI 3108 alsoBad, drive requires vendor specific fields to be filled with only IBM knows what. Try to format using Iprutils, I've nowhere to test it, but if you can make it work in linux with your HBA, it will do whatever required to a drive loaded with IBM firmware
Not the ~170 USD makes me sad, what I paid for the 8TB drive. The fact that I can't use a very cheap 8TB SSD Moreover it has only two hours and a few MB(!!) TBW... So it's actualy unused...Thank for the correction! I've just cloned the iprutils git repo. After the build I can run it without any errors, but cant find any controllers/disks Do I need to make some extra steps to get it work? I tried with LSI SAS2008 and LSI 3108 also
The difference is that IBM hdds are not locked for reformatting from 520bps, so you wouldn't need to update firmware. SSD is a different story and you can find firmware download port is locked as well, but it worth trying anywayAs for the firmware flashing I saw the somebody flash back OEM (seagate) firmware for HP sas drives (HDD). Whats the difference in my case?
If the IBM SSDs locked for formatting, we are wasting time for the reformatting with sg_format, seachest, etc...The difference is that IBM hdds are not locked for reformatting from 520bps, so you wouldn't need to update firmware. SSD is a different story and you can find firmware download port is locked as well, but it worth trying anyway