8TB SAS 25 USD + 13USD shipping, great deal for lot
- Thread starter BackupProphet
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
I had to put my Dell T330 back into service, so I'll have to play with this later. Something interesting to note. I have a Dell T30 that, if I install the H730 from the T330 into the T30 and plug in the HGST drives, they do not spin up, at all. They only spin up in the T330. I dont get that part, its like the idrac is needed to initialize the locked drives.
I need a new server for the colo, so I'll order another T330 and continue to play with these.
I need a new server for the colo, so I'll order another T330 and continue to play with these.
Looks like this person on reddit was able to remove lock
see
see
Code:
[–]dev_hmmmmm 2 points 2 years ago
https://www.truenas.com/docs/hub/tasks/advanced/sed-drives/
Go here. On the bottom of the page, there should be command to remove encryption without password.
You'd your drive's psid, which is pretty long but you can scan the bar code on the bottom of it and copy past it with Evernote. That's what I did.
Note:you have to do use the command from freenas console. I tried using windows bin but didn't work.
permalinkembedsaveparentreportgive awardreply
[–]chavu[S] 1 point 2 years ago
Thanks for this, it worked! No idea why FreeNas must be used. I was able to wipe the drives and then format them under windows server without issue.My package is still stuck in KENT,WA , no est date.
To prepare for unlocking the drive.
I have a test mule machine running ubuntu 18.x
Download and install sedutil-cli , need to update libc
./sedutil-cli: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by ./sedutil-cli)
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt update
sudo apt install gcc-9
sudo apt install libstdc++6
strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBC
fix The Kernel flag libata.allow_tpm is not set correctly
/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="libata.allow_tpm=1"
-----------------------------------------------------------------------------------
trying out sedutil command
./sedutil-cli --query /dev/sda
/dev/sda SAS ST4000NM0043 C1 EC54 IBM-XIV
TPer function (0x0001)
ACKNAK = N, ASYNC = N. BufferManagement = N, comIDManagement = N, Streaming = Y, SYNC = Y
Locking function (0x0002)
Locked = N, LockingEnabled = Y, LockingSupported = Y, MBRDone = N, MBREnabled = N, MediaEncrypt = Y
Geometry function (0x0003)
Align = N, Alignment Granularity = 1 (512), Logical Block size = 512, Lowest Aligned LBA = 0
Enterprise function (0x0100)
Range crossing = Y, Base comID = 0x07fe, comIDs = 2
To prepare for unlocking the drive.
I have a test mule machine running ubuntu 18.x
Download and install sedutil-cli , need to update libc
./sedutil-cli: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by ./sedutil-cli)
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt update
sudo apt install gcc-9
sudo apt install libstdc++6
strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBC
fix The Kernel flag libata.allow_tpm is not set correctly
/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="libata.allow_tpm=1"
-----------------------------------------------------------------------------------
trying out sedutil command
./sedutil-cli --query /dev/sda
/dev/sda SAS ST4000NM0043 C1 EC54 IBM-XIV
TPer function (0x0001)
ACKNAK = N, ASYNC = N. BufferManagement = N, comIDManagement = N, Streaming = Y, SYNC = Y
Locking function (0x0002)
Locked = N, LockingEnabled = Y, LockingSupported = Y, MBRDone = N, MBREnabled = N, MediaEncrypt = Y
Geometry function (0x0003)
Align = N, Alignment Granularity = 1 (512), Logical Block size = 512, Lowest Aligned LBA = 0
Enterprise function (0x0100)
Range crossing = Y, Base comID = 0x07fe, comIDs = 2
Seller must give you partial refund; buyer is not obliged the remove encryption.
Newer version of sedutil-cli
root@albany:/home/fun/hdtest/SEDUTIL/NEWER# ./sedutil-cli --query /dev/sdb
Invalid or unsupported disk /dev/sdb
Older version of sedutil-cli works better
./sedutil-cli --query /dev/sdb
/dev/sdb SAS ST4000NM0043 C1 EC54 IBM-XIV
TPer function (0x0001)
ACKNAK = N, ASYNC = N. BufferManagement = N, comIDManagement = N, Streaming = Y, SYNC = Y
Locking function (0x0002)
Locked = N, LockingEnabled = Y, LockingSupported = Y, MBRDone = N, MBREnabled = N, MediaEncrypt = Y
Geometry function (0x0003)
Align = N, Alignment Granularity = 1 (512), Logical Block size = 512, Lowest Aligned LBA = 0
Enterprise function (0x0100)
Range crossing = Y, Base comID = 0x07fe, comIDs = 2
use this download older version
github.com
Newer version of sedutil-cli
github.com
root@albany:/home/fun/hdtest/SEDUTIL/NEWER# ./sedutil-cli --query /dev/sdb
Invalid or unsupported disk /dev/sdb
Older version of sedutil-cli works better
./sedutil-cli --query /dev/sdb
/dev/sdb SAS ST4000NM0043 C1 EC54 IBM-XIV
TPer function (0x0001)
ACKNAK = N, ASYNC = N. BufferManagement = N, comIDManagement = N, Streaming = Y, SYNC = Y
Locking function (0x0002)
Locked = N, LockingEnabled = Y, LockingSupported = Y, MBRDone = N, MBREnabled = N, MediaEncrypt = Y
Geometry function (0x0003)
Align = N, Alignment Granularity = 1 (512), Logical Block size = 512, Lowest Aligned LBA = 0
Enterprise function (0x0100)
Range crossing = Y, Base comID = 0x07fe, comIDs = 2
use this download older version
Executable Distributions
DTA sedutil Self encrypting drive software. Contribute to Drive-Trust-Alliance/sedutil development by creating an account on GitHub.
github.com
Newer version of sedutil-cli
Releases · ChubbyAnt/sedutil
SEDutil: For Intel and AMD Ryzen Systems. Contribute to ChubbyAnt/sedutil development by creating an account on GitHub.
github.com
just check you have a PSID on the drives, I've gotten sedlocked drives off ebay WITHOUT it (samsung pm983) and .. it cost me hours on hours and no fix
Trying again this evening with again, no luck. Booted the T330 with one HGST plugged into my H330. iDrac can see the drive and is complaining about it. Used the SEDUTIL iso and it does not see the drive. I can see every other drive in the system. Same with truenas, can't see the drive. Very very odd.
The annoying thing is that megaraid can see the drive and yet I can't give megaraid the PSID to unlock it. I don't see a megaraidcli command for a psid unlock. Supposedly parted magic can do this, but I don't want to spend $13 when a) I shouldn't have to and b) with no guarantee of an unlock/seeing the drive.
Perccli also sees the drive, but I can't find a command to unlock it using the PSID. Typical "secureerase" commands fail, as expected.
Perccli also sees the drive, but I can't find a command to unlock it using the PSID. Typical "secureerase" commands fail, as expected.
Last edited:
Ultimate boot cd has a parted magic live cd on it. It's what I use for my smart tests:
Thanks @Samir , unfortunately the UBCD version didn't have PSID unlock.
So in stubbornness, I purchased parted magic, and it has the PSID unlock. Interestingly, with a HGST plugged into the H730, parted magic still doesn't see the drive (idrac still sees it). I plugged in my adaptec ASR8405, and it sees the drive, and now so does parted magic.
Using the PSID unlocker, I see the drive, however when I enter the PSID it still fails. Sigh.
So in stubbornness, I purchased parted magic, and it has the PSID unlock. Interestingly, with a HGST plugged into the H730, parted magic still doesn't see the drive (idrac still sees it). I plugged in my adaptec ASR8405, and it sees the drive, and now so does parted magic.
Using the PSID unlocker, I see the drive, however when I enter the PSID it still fails. Sigh.
I've given up. Unless someone has a different method, I can not get these to unlock no matter what I do. I've already reached out to the seller for resolution.
Using the adaptec 8405, sedutil will now see the drive but statys it is not locked/opal compatible. Parted Magic sees the drive, but even with the psid, it doesn't want to unlock.
@Marsh If you are successful, i'd love to know how you did it.
Using the adaptec 8405, sedutil will now see the drive but statys it is not locked/opal compatible. Parted Magic sees the drive, but even with the psid, it doesn't want to unlock.
@Marsh If you are successful, i'd love to know how you did it.
Just received the HD package last 15 min.
There is ZERO packing bubble warp between each drives.
Good news is : I just unlocked the first drive.
./sedutil-cli --yesIreallywanttoERASEAllmydatausingthePSID nXVPZZv60MS897jAm1x9 /dev/sg0
TPer function (0x0001)
revertTper completed successfully
------------------------------------------------------------
root@albany:/home/fun/hdtest/SEDUTIL# ./sedutil-cli --query /dev/sg0
/dev/sg0 SAS HUH728080AL5205 D907 HGST
Locking function (0x0002)
Locked = N, LockingEnabled = Y, LockingSupported = Y, MBRDone = N, MBREnabled = N, MediaEncrypt = Y
------------------------------------------------------------
Created EXT4 filesystem
mkfs.ext4 -m 0 -T largefile4 -L hd1 /dev/sda1
mke2fs 1.44.1 (24-Mar-2018)
Creating filesystem with 1953506385 4k blocks and 1907744 inodes
Filesystem UUID: 695275e2-cdf1-4bf0-9643-47f56e8430d7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544, 1934917632
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
There is ZERO packing bubble warp between each drives.
Good news is : I just unlocked the first drive.
./sedutil-cli --yesIreallywanttoERASEAllmydatausingthePSID nXVPZZv60MS897jAm1x9 /dev/sg0
TPer function (0x0001)
revertTper completed successfully
------------------------------------------------------------
root@albany:/home/fun/hdtest/SEDUTIL# ./sedutil-cli --query /dev/sg0
/dev/sg0 SAS HUH728080AL5205 D907 HGST
Locking function (0x0002)
Locked = N, LockingEnabled = Y, LockingSupported = Y, MBRDone = N, MBREnabled = N, MediaEncrypt = Y
------------------------------------------------------------
Created EXT4 filesystem
mkfs.ext4 -m 0 -T largefile4 -L hd1 /dev/sda1
mke2fs 1.44.1 (24-Mar-2018)
Creating filesystem with 1953506385 4k blocks and 1907744 inodes
Filesystem UUID: 695275e2-cdf1-4bf0-9643-47f56e8430d7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544, 1934917632
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
disks/HUH728080AL5205_VJG4R91X
(standard input): Accumulated power on time, hours:minutes 48620:12 [2917212 minutes]
SMART output
=== START OF INFORMATION SECTION ===
Vendor: HGST
Product: HUH728080AL5205
Revision: D907
Compliance: SPC-4
User Capacity: 8,001,563,222,016 bytes [8.00 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
LU is fully provisioned
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Logical Unit id: 0x5000cca2610894a8
Serial number: VJG4R91X
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Tue Feb 14 11:33:38 2023 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
Read Cache is: Enabled
Writeback Cache is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Current Drive Temperature: 26 C
Drive Trip Temperature: 85 C
Manufactured in week 45 of year 2016
Specified cycle count over device lifetime: 50000
Accumulated start-stop cycles: 14
Specified load-unload count over device lifetime: 600000
Accumulated load-unload cycles: 1946
Elements in grown defect list: 0
Vendor (Seagate) cache information
Blocks sent to initiator = 54470704661266432
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: 0 1 0 1 102350695 1202399.188
0
write: 0 29 0 29 10462146 1227841.455
0
verify: 0 0 0 0 827 0.000
0
Non-medium error count: 28
SMART Self-test log
Num Test Status segment LifeTime LBA_first_e
rr [SK ASC ASQ]
Description number (hours)
# 1 Background short Completed - 26
- [- - -]
Long (extended) Self Test duration: 65535 seconds [1092.2 minutes]
Background scan results log
Status: scan is active
Accumulated power on time, hours:minutes 48620:12 [2917212 minutes]
Number of background scans performed: 7, scan progress: 0.77%
Number of background medium scans performed: 7
Protocol Specific port log page for SAS SSP
relative target port id = 1
generation code = 1
number of phys = 1
phy identifier = 0
attached device type: SAS or SATA device
attached reason: loss of dword synchronization
reason: unknown
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 = 0x5000cca2610894a9
attached SAS address = 0x500605b00603ff00
attached phy identifier = 1
Invalid DWORD count = 0
Running disparity error count = 0
Loss of DWORD synchronization = 0
Phy reset problem = 0
Phy event descriptors:
Invalid word count: 0
Running disparity error count: 0
Loss of dword synchronization count: 0
Phy reset problem count: 0
relative target port id = 2
generation code = 1
number of phys = 1
phy identifier = 1
attached device type: no device attached
attached reason: unknown
reason: power on
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 = 0x5000cca2610894aa
attached SAS address = 0x0
attached phy identifier = 0
Invalid DWORD count = 0
Running disparity error count = 0
Loss of DWORD synchronization = 0
Phy reset problem = 0
Phy event descriptors:
Invalid word count: 0
Running disparity error count: 0
Loss of dword synchronization count: 0
Phy reset problem count: 0
(standard input): Accumulated power on time, hours:minutes 48620:12 [2917212 minutes]
SMART output
=== START OF INFORMATION SECTION ===
Vendor: HGST
Product: HUH728080AL5205
Revision: D907
Compliance: SPC-4
User Capacity: 8,001,563,222,016 bytes [8.00 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
LU is fully provisioned
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Logical Unit id: 0x5000cca2610894a8
Serial number: VJG4R91X
Device type: disk
Transport protocol: SAS (SPL-3)
Local Time is: Tue Feb 14 11:33:38 2023 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
Read Cache is: Enabled
Writeback Cache is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Current Drive Temperature: 26 C
Drive Trip Temperature: 85 C
Manufactured in week 45 of year 2016
Specified cycle count over device lifetime: 50000
Accumulated start-stop cycles: 14
Specified load-unload count over device lifetime: 600000
Accumulated load-unload cycles: 1946
Elements in grown defect list: 0
Vendor (Seagate) cache information
Blocks sent to initiator = 54470704661266432
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: 0 1 0 1 102350695 1202399.188
0
write: 0 29 0 29 10462146 1227841.455
0
verify: 0 0 0 0 827 0.000
0
Non-medium error count: 28
SMART Self-test log
Num Test Status segment LifeTime LBA_first_e
rr [SK ASC ASQ]
Description number (hours)
# 1 Background short Completed - 26
- [- - -]
Long (extended) Self Test duration: 65535 seconds [1092.2 minutes]
Background scan results log
Status: scan is active
Accumulated power on time, hours:minutes 48620:12 [2917212 minutes]
Number of background scans performed: 7, scan progress: 0.77%
Number of background medium scans performed: 7
Protocol Specific port log page for SAS SSP
relative target port id = 1
generation code = 1
number of phys = 1
phy identifier = 0
attached device type: SAS or SATA device
attached reason: loss of dword synchronization
reason: unknown
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 = 0x5000cca2610894a9
attached SAS address = 0x500605b00603ff00
attached phy identifier = 1
Invalid DWORD count = 0
Running disparity error count = 0
Loss of DWORD synchronization = 0
Phy reset problem = 0
Phy event descriptors:
Invalid word count: 0
Running disparity error count: 0
Loss of dword synchronization count: 0
Phy reset problem count: 0
relative target port id = 2
generation code = 1
number of phys = 1
phy identifier = 1
attached device type: no device attached
attached reason: unknown
reason: power on
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 = 0x5000cca2610894aa
attached SAS address = 0x0
attached phy identifier = 0
Invalid DWORD count = 0
Running disparity error count = 0
Loss of DWORD synchronization = 0
Phy reset problem = 0
Phy event descriptors:
Invalid word count: 0
Running disparity error count: 0
Loss of dword synchronization count: 0
Phy reset problem count: 0
Using Ubuntu 18.x , I used this machine to run badblock testing of SAS drives
I forgot which OEM card that was flashed to LSI firmware
lspci
04:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
dmesg | grep LSI
mpt2sas_cm0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00)
I won't be able to stop testing and take apart to find the OEM model card
Not very helpfull Pictures:
I forgot which OEM card that was flashed to LSI firmware
lspci
04:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
dmesg | grep LSI
mpt2sas_cm0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00)
I won't be able to stop testing and take apart to find the OEM model card
Not very helpfull Pictures:
Attachments
I just unlocked all 12 drives , the only problem is confused between 1 (one ) vs l ( L ) with PSID label
Starting badblocks testing on 8 drives.
sudo sg_readcap /dev/sg0
READ CAPACITY (10) indicates device capacity too large
now trying 16 byte cdb variant
Read Capacity results:
Protection: prot_en=0, p_type=0, p_i_exponent=0
Logical block provisioning: lbpme=0, lbprz=0
Last logical block address=15628053167 (0x3a3812aaf), Number of logical blocks=15628053168
Logical block length=512 bytes
Logical blocks per physical block exponent=3 [so physical block length=4096 bytes]
Lowest aligned logical block address=0
Hence:
Device size: 8001563222016 bytes, 7630885.3 MiB, 8001.56 GB
Starting badblocks testing on 8 drives.
sudo sg_readcap /dev/sg0
READ CAPACITY (10) indicates device capacity too large
now trying 16 byte cdb variant
Read Capacity results:
Protection: prot_en=0, p_type=0, p_i_exponent=0
Logical block provisioning: lbpme=0, lbprz=0
Last logical block address=15628053167 (0x3a3812aaf), Number of logical blocks=15628053168
Logical block length=512 bytes
Logical blocks per physical block exponent=3 [so physical block length=4096 bytes]
Lowest aligned logical block address=0
Hence:
Device size: 8001563222016 bytes, 7630885.3 MiB, 8001.56 GB
Following up on this, I did get these drives unlocked, but man was it a pain!
First, a big shout out to @Marsh who helped me through some DMs. I was having trouble with the drive spinning up in anything other than the T330, which made my troubleshooting process incredibly frustrating. He remember (as I had forgotten) that some drives have the 3.3v shut off, so I modified some sata cables to no longer provide 3.3v and the drives now spin up in the T30 without issues. After that....
I had to buy a Dell H310 and convert it to IT mode, then plug the H310 into my Dell T7820 (other thread here), and then install truenas 13. Truenas saw the drives were locked and allowed me to unlock them using sedutil-cli via shell. Annoyingly, parted magic and sedutil rescue iso did not work with the H310/T7820 and parted magic has no customer service to request a refund. I tried truenas in the T330/H330 and that didn't work, so some magical combination of the H310/T7820/TN13 worked for these.
Running badblocks now and 55 hours in, all 4 are clean.
First, a big shout out to @Marsh who helped me through some DMs. I was having trouble with the drive spinning up in anything other than the T330, which made my troubleshooting process incredibly frustrating. He remember (as I had forgotten) that some drives have the 3.3v shut off, so I modified some sata cables to no longer provide 3.3v and the drives now spin up in the T30 without issues. After that....
I had to buy a Dell H310 and convert it to IT mode, then plug the H310 into my Dell T7820 (other thread here), and then install truenas 13. Truenas saw the drives were locked and allowed me to unlock them using sedutil-cli via shell. Annoyingly, parted magic and sedutil rescue iso did not work with the H310/T7820 and parted magic has no customer service to request a refund. I tried truenas in the T330/H330 and that didn't work, so some magical combination of the H310/T7820/TN13 worked for these.
Running badblocks now and 55 hours in, all 4 are clean.
Obviously, we all loooove tinkering and a great deal, but I wonder if you were to evaluate the cost of the time you spent you to make these drives actually work, what was your actual purchase price for these drives? Was it worth it?
I ask, because I’m starting down the path of building from scratch a beast of a home server and I’m wondering money vs time…