Guest Posted March 19, 2019 Share Posted March 19, 2019 I need help to remove and disable the lock on the hard drives with hdparm, i am not savy with command prompt. I can unlocked it but didn’t disable the lock so it needs unlocking each boot. Quote Link to comment
trurl Posted March 19, 2019 Share Posted March 19, 2019 Are you interested in Unraid? Your post doesn't mention Unraid, which is the purpose of our forum. Quote Link to comment
Guest Posted March 19, 2019 Share Posted March 19, 2019 i installed unraid yesterday. Quote Link to comment
trurl Posted March 19, 2019 Share Posted March 19, 2019 What does ReadyNAS locked drives have to do with Unraid? How are you planning to use these drives with Unraid? Quote Link to comment
Guest Posted March 19, 2019 Share Posted March 19, 2019 i am trying to unlock and disable the lock that readynas has put on the drive so i can use with unraid Quote Link to comment
JorgeB Posted March 19, 2019 Share Posted March 19, 2019 I doubt you'll find many users here with ReadyNAS experience, best bet it to try their forum, e.g. quick google search: https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/Password-for-Locked-Hard-Drives/m-p/983619/highlight/true#M93821 Quote Link to comment
Guest Posted March 19, 2019 Share Posted March 19, 2019 i dont need anyone with experience with ReadyNAS just with hdparm for Windows. Quote Link to comment
JorgeB Posted March 19, 2019 Share Posted March 19, 2019 2 minutes ago, wheelhouse20 said: just with hdparm for Windows Still unlikely to find them here, though hdparm is also on Unraid, and should behave the same. Quote Link to comment
Guest Posted March 19, 2019 Share Posted March 19, 2019 is hdparm an addon in unraid ? Quote Link to comment
trurl Posted March 19, 2019 Share Posted March 19, 2019 How do you know this is what you need to do in order to use the drive with Unraid? 2 hours ago, wheelhouse20 said: remove and disable the lock on the hard drives with hdparm If you found that information somewhere it seems like the answer to your question would be in the same place. Quote Link to comment
trurl Posted March 19, 2019 Share Posted March 19, 2019 Just now, wheelhouse20 said: is hdparm an addon in unraid ? Builtin Quote Link to comment
Guest Posted March 19, 2019 Share Posted March 19, 2019 i tryed to unlock the hard drives through unraid but i kept on getting could some one tell what this mean please. SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Quote Link to comment
Squid Posted March 20, 2019 Share Posted March 20, 2019 Try connecting them direct to the motherboard instead of an HBA Quote Link to comment
Guest Posted March 20, 2019 Share Posted March 20, 2019 whats an HBA ? And i do have them connect to the motherboard via sata. Quote Link to comment
Vr2Io Posted March 20, 2019 Share Posted March 20, 2019 9 hours ago, wheelhouse20 said: i tryed to unlock the hard drives through unraid but i kept on getting could some one tell what this mean please. SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Does you type correct, I notice it show "sb[]", it shoud sd'x' BTW, hdparm which buildin Unraid could do lock/unlock etc. Quote Link to comment
Guest Posted March 20, 2019 Share Posted March 20, 2019 1 hour ago, Benson said: Does you type correct, I notice it show "sb[]", it shoud sd'x' BTW, hdparm which buildin Unraid could do lock/unlock etc. Does this look correct ? root@NAS:~# hdparm -I /dev/sdd /dev/sdd: ATA device, with non-removable media Model Number: SAMSUNG HD154UI Serial Number: S1Y6J1KS742452 Firmware Revision: 1AG01118 Standards: Used: ATA-8-ACS revision 3b Supported: 7 6 5 4 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 2930277168 Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 1430799 MBytes device size with M = 1000*1000: 1500301 MBytes (1500 GB) cache/buffer size = unknown Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Advanced power management level: disabled Recommended acoustic management value: 254, current value: 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 udma7 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set * Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE Advanced Power Management feature set Power-Up In Standby feature set * SET_FEATURES required to spinup after power up SET_MAX security extension Automatic Acoustic Management feature set * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test Media Card Pass-Through * General Purpose Logging feature set * 64-bit World wide name * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * Gen1 signaling speed (1.5Gb/s) * Gen2 signaling speed (3.0Gb/s) * Native Command Queueing (NCQ) * Host-initiated interface power management * Phy event counters * NCQ priority information * DMA Setup Auto-Activate optimization Device-initiated interface power management * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Read/Write Long (AC1), obsolete * SCT Write Same (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) Security: Master password revision code = 65534 supported enabled not locked frozen not expired: security count supported: enhanced erase Security level high 310min for SECURITY ERASE UNIT. 310min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 50024e9001d0f597 NAA : 5 IEEE OUI : 0024e9 Unique ID : 001d0f597 Checksum: correct root@NAS:~# hdparm --security-unlock NETGEAR /dev/sdd security_password: "NETGEAR" /dev/sdd: Issuing SECURITY_UNLOCK command, password="NETGEAR", user=user SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 root@NAS:~# hdparm --security-disable NETGEAR /dev/sdd security_password: "NETGEAR" /dev/sdd: Issuing SECURITY_DISABLE command, password="NETGEAR", user=user SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 root@NAS:~# # hdparm -I /dev/sdf root@NAS:~# hdparm -I /dev/sdf Quote Link to comment
Vr2Io Posted March 20, 2019 Share Posted March 20, 2019 (edited) OK, I make test on a Samsung drive, your problem was incorrect password use. /dev/sdb: ATA device, with non-removable media Model Number: SAMSUNG SP2504C Serial Number: S09QJ1CP211970 Firmware Revision: VT100-50 - With "security disable" disk, then set the password to "TEST" and enable then disable it. Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count root@Q851:~# hdparm --security-set-pass TEST /dev/sdb security_password: "TEST" /dev/sdb: Issuing SECURITY_SET_PASS command, password="TEST", user=user, mode=high root@Q851:~# - Now disk in security enable Security: Master password revision code = 65534 supported enabled not locked not frozen not expired: security count root@Q851:~# hdparm --security-disable TEST /dev/sdb security_password: "TEST" /dev/sdb: Issuing SECURITY_DISABLE command, password="TEST", user=user Then enable it again but disable with a wrong password "NETGEAR" root@Q851:~# hdparm --security-set-pass TEST /dev/sdb security_password: "TEST" /dev/sdb: Issuing SECURITY_SET_PASS command, password="TEST", user=user, mode=high root@Q851:~# hdparm --security-disable NETGEAR /dev/sdb security_password: "NETGEAR" /dev/sdb: Issuing SECURITY_DISABLE command, password="NETGEAR", user=user SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1 hour ago, wheelhouse20 said: Security: Master password revision code = 65534 supported enabled not locked frozen not expired: security count But I note your drive in "frozen", it may be in securtiy erase or other state. If you can't make it to "not frozen", then you may need let it power-on and don't touch anything for "310min" then check its frozen state. Edited March 20, 2019 by Benson Quote Link to comment
Guest Posted March 27, 2019 Share Posted March 27, 2019 On 3/20/2019 at 10:22 AM, Benson said: OK, I make test on a Samsung drive, your problem was incorrect password use. /dev/sdb: ATA device, with non-removable media Model Number: SAMSUNG SP2504C Serial Number: S09QJ1CP211970 Firmware Revision: VT100-50 - With "security disable" disk, then set the password to "TEST" and enable then disable it. Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count root@Q851:~# hdparm --security-set-pass TEST /dev/sdb security_password: "TEST" /dev/sdb: Issuing SECURITY_SET_PASS command, password="TEST", user=user, mode=high root@Q851:~# - Now disk in security enable Security: Master password revision code = 65534 supported enabled not locked not frozen not expired: security count root@Q851:~# hdparm --security-disable TEST /dev/sdb security_password: "TEST" /dev/sdb: Issuing SECURITY_DISABLE command, password="TEST", user=user Then enable it again but disable with a wrong password "NETGEAR" root@Q851:~# hdparm --security-set-pass TEST /dev/sdb security_password: "TEST" /dev/sdb: Issuing SECURITY_SET_PASS command, password="TEST", user=user, mode=high root@Q851:~# hdparm --security-disable NETGEAR /dev/sdb security_password: "NETGEAR" /dev/sdb: Issuing SECURITY_DISABLE command, password="NETGEAR", user=user SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 But I note your drive in "frozen", it may be in securtiy erase or other state. If you can't make it to "not frozen", then you may need let it power-on and don't touch anything for "310min" then check its frozen state. i was unable to remove the password on boot up in the end. cheers for your help. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.