10:51 a.m.
The command and error message are:
# time hdparm --verbose --user-master m --security-erase-enhanced
thepassword /dev/sdc
security_password="thepassword"
/dev/sdc:
Issuing SECURITY_ERASE command, password="thepassword", user=master
outgoing cdb: 85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00
SG_IO: ATA_16 status=0x0, host_status=0x0, driver_status=0x0
SG_IO: sb[]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
incoming_data: 7a 42 ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00 00 00 00
00 20 20 20 20 57 20 2d 44 58 57 31 56 35 45 4b 33 45 41 33 38 00 00 00
40 00 00 31 30 30 2e 41 31 31 30 44 57 20 43 44 57 30 32 50 4e 58 56 30
2d 45 30 34 41 30 54 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
20 20 20 10 80 00 40 00 2f 01 40 00 00 00 00 07 00 ff 3f 10 00 3f 00 10
fc fb 00 00 01 ff ff ff 0f 00 00 07 00 03 00 78 00 78 00 78 00 78 00 00
00 00 00 00 00 00 00 00 00 00 00 1f 00 0e ff 04 00 4c 00 44 00 fe 03 00
00 6b 74 69 7d 23 61 6b 74 49 bc 23 61 7f 40 bb 00 bb 00 80 00 fe ff 00
00 00 00 00 00 00 00 00 00 00 00 00 00 b0 88 e0 e8 00 00 00 00 00 00 00
00 03 60 00 00 01 50 e2 4e 90 5e 21 ff 00 00 00 00 00 00 00 00 00 00 00
00 00 00 18 40 18 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 27 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 35 70 00 00 00 00 00 40 00 00 00 00 00 00 00
00 00 00 00 00 00 00 50 14 00 00 00 00 00 00 00 00 3e 10 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 10 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 a5 bd
SG_IO: desc[]: 00 00
ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00
outgoing cdb: 85 06 20 00 00 00 00 00 00 00 00 00 00 40 f3 00
SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
SG_IO: sb[]: 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00 00 00 00
00 40 50 00 00 00 00 00 00 00 00 00 00
SG_IO: desc[]: 09 0c 00 00 00 00 00 00 00 00 00 00 40 50
ATA_16 stat=50 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=40
oflags.bits.lob_all=0x8a, flags={ feat nsect command }
oflags.bits.hob_all=0x00, flags={ }
outgoing cdb: 85 0a 06 00 00 00 01 00 00 00 00 00 00 40 f4 00
outgoing_data: 03 00 68 64 70 61 72 6d 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
SG_IO: sb[]: 72 0b 00 00 00 00 00 0e 09 0c 00 04 00 01 00 00 00 00 00
00 40 51 00 00 00 00 00 00 00 00 00 00
SG_IO: desc[]: 09 0c 00 04 00 01 00 00 00 00 00 00 40 51
ATA_16 stat=51 err=04 nsect=01 lbal=00 lbam=00 lbah=00 dev=40
I/O error, ata_op=0xf4 ata_status=0x51 ata_error=0x04
SECURITY_ERASE: Input/output error
real 0m3.56s
user 0m0.00s
sys 0m0.00s
However, I have no problem running
dd if=/dev/zero of=/dev/sdc bs=1G (PS: I have 8GB ram, and less that
1GB is used before I start the command).
So, am hoping an hdparm guru will offer some insight.
12:24 p.m.
On 03/20/2015 10:14 AM, jd1008 wrote:
On 03/20/2015 09:54 AM, jd1008 wrote:
>
>
> On 03/20/2015 09:51 AM, jd1008 wrote:
>> The command and error message are:
>>
>> # time hdparm --verbose --user-master m --security-erase-enhanced
>> thepassword /dev/sdc
>> security_password="thepassword"
>>
>> /dev/sdc:
>> Issuing SECURITY_ERASE command, password="thepassword", user=master
>> outgoing cdb: 85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00
>> SG_IO: ATA_16 status=0x0, host_status=0x0, driver_status=0x0
>> SG_IO: sb[]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> incoming_data: 7a 42 ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00 00 00
>> 00 00 20 20 20 20 57 20 2d 44 58 57 31 56 35 45 4b 33 45 41 33 38 00
>> 00 00 40 00 00 31 30 30 2e 41 31 31 30 44 57 20 43 44 57 30 32 50 4e
>> 58 56 30 2d 45 30 34 41 30 54 20 20 20 20 20 20 20 20 20 20 20 20 20
>> 20 20 20 20 20 20 20 10 80 00 40 00 2f 01 40 00 00 00 00 07 00 ff 3f
>> 10 00 3f 00 10 fc fb 00 00 01 ff ff ff 0f 00 00 07 00 03 00 78 00 78
>> 00 78 00 78 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 00 0e ff 04 00
>> 4c 00 44 00 fe 03 00 00 6b 74 69 7d 23 61 6b 74 49 bc 23 61 7f 40 bb
>> 00 bb 00 80 00 fe ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0 88
>> e0 e8 00 00 00 00 00 00 00 00 03 60 00 00 01 50 e2 4e 90 5e 21 ff 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 18 40 18 40 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 27 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 35 70 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 50 14 00 00 00 00 00 00 00 00 3e 10 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 10 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 a5 bd
>> SG_IO: desc[]: 00 00
>> ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00
>> outgoing cdb: 85 06 20 00 00 00 00 00 00 00 00 00 00 40 f3 00
>> SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
>> SG_IO: sb[]: 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00 00 00
>> 00 00 40 50 00 00 00 00 00 00 00 00 00 00
>> SG_IO: desc[]: 09 0c 00 00 00 00 00 00 00 00 00 00 40 50
>> ATA_16 stat=50 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=40
>> oflags.bits.lob_all=0x8a, flags={ feat nsect command }
>> oflags.bits.hob_all=0x00, flags={ }
>> outgoing cdb: 85 0a 06 00 00 00 01 00 00 00 00 00 00 40 f4 00
>> outgoing_data: 03 00 68 64 70 61 72 6d 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> 00 00 00 00 00 00 00 00 00 00 00
>> SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
>> SG_IO: sb[]: 72 0b 00 00 00 00 00 0e 09 0c 00 04 00 01 00 00 00 00
>> 00 00 40 51 00 00 00 00 00 00 00 00 00 00
>> SG_IO: desc[]: 09 0c 00 04 00 01 00 00 00 00 00 00 40 51
>> ATA_16 stat=51 err=04 nsect=01 lbal=00 lbam=00 lbah=00 dev=40
>> I/O error, ata_op=0xf4 ata_status=0x51 ata_error=0x04
>> SECURITY_ERASE: Input/output error
>>
>> real 0m3.56s
>> user 0m0.00s
>> sys 0m0.00s
>>
>>
>> However, I have no problem running
>> dd if=/dev/zero of=/dev/sdc bs=1G (PS: I have 8GB ram, and less
>> that 1GB is used before I start the command).
>>
>> So, am hoping an hdparm guru will offer some insight.
>>
> Update:
>
> Changing the command parameter m to u
> makes it work. Yet, I do want to use the parameter m .
> How do I make it accept the parameter m ???
>
Update:
# hdparm --user-master m --security-set-pass thepassword /dev/sdc
security_password="thepassword"
/dev/sdc:
Issuing SECURITY_SET_PASS command, password="thepassword",
user=master, mode=high
SECURITY_SET_PASS: Input/output error
Yet, if I use hdparm --user-master u .... etc
it works just fine. Why?? The manpage says that it can be u or m.
There are two passwords you can set, a user password and a master
password. Since the command works with "--user-master u", this
indicates that the password you're specifying is the user password.
You must set a master password via
hdparm --user-master m --set-security-pass <masterpassword>
and use that new password whenever you use "--user-master m".
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- Squawk! Pieces of Seven! Pieces of Seven! Parity Error! -
----------------------------------------------------------------------
2:32 p.m.
On 03/20/2015 12:04 PM, jd1008 wrote:
On 03/20/2015 11:24 AM, Rick Stevens wrote:
> hdparm --user-master m --set-security-pass
It is belching the usage at me:
# hdparm --user-master m --set-security-pass thepassword /dev/sdc
hdparm - get/set hard disk parameters - version v9.45, by Mark Lord.
Usage: hdparm [options] [device ...]
Options:
-a Get/set fs readahead
-A Get/set the drive look-ahead flag (0/1)
-b Get/set bus state (0 == off, 1 == on, 2 == tristate)
-B Set Advanced Power Management setting (1-255)
-c Get/set IDE 32-bit IO setting
-C Check drive power mode status
-d Get/set using_dma flag
-D Enable/disable drive defect management
-E Set cd/dvd drive speed
-f Flush buffer cache for device on exit
-F Flush drive write cache
-g Display drive geometry
-h Display terse usage information
-H Read temperature from drive (Hitachi only)
-i Display drive identification
-I Detailed/current information directly from drive
-J Get/set Western DIgital "Idle3" timeout for a WDC "Green"
drive
(DANGEROUS)
-k Get/set keep_settings_over_reset flag (0/1)
-K Set drive keep_features_over_reset flag (0/1)
-L Set drive doorlock (0/1) (removable harddisks only)
-m Get/set multiple sector count
-M Get/set acoustic management (0-254, 128: quiet, 254: fast)
-n Get/set ignore-write-errors flag (0/1)
-N Get/set max visible number of sectors (HPA) (VERY DANGEROUS)
-p Set PIO mode on IDE interface chipset (0,1,2,3,4,...)
-P Set drive prefetch count
-q Change next setting quietly
-Q Get/set DMA queue_depth (if supported)
-r Get/set device readonly flag (DANGEROUS to set)
-R Get/set device write-read-verify flag
-s Set power-up in standby flag (0/1) (DANGEROUS)
-S Set standby (spindown) timeout
-t Perform device read timings
-T Perform cache read timings
-u Get/set unmaskirq flag (0/1)
-U Obsolete
-v Use defaults; same as -acdgkmur for IDE drives
-V Display program version and exit immediately
-w Perform device reset (DANGEROUS)
-W Get/set drive write-caching flag (0/1)
-x Obsolete
-X Set IDE xfer mode (DANGEROUS)
-y Put drive in standby mode
-Y Put drive to sleep
-z Re-read partition table
-Z Disable Seagate auto-powersaving mode
--dco-freeze Freeze/lock current device configuration until next
power cycle
--dco-identify Read/dump device configuration identify data
--dco-restore Reset device configuration back to factory defaults
--dco-setmax Use DCO to set maximum addressable sectors
--direct Use O_DIRECT to bypass page cache for timings
--drq-hsm-error Crash system with a "stuck DRQ" error (VERY DANGEROUS)
--fallocate Create a file without writing data to disk
--fibmap Show device extents (and fragmentation) for a file
--fwdownload Download firmware file to drive (EXTREMELY
DANGEROUS)
--fwdownload-mode3 Download firmware using min-size segments
(EXTREMELY DANGEROUS)
--fwdownload-mode3-max Download firmware using max-size segments
(EXTREMELY DANGEROUS)
--fwdownload-mode7 Download firmware using a single segment
(EXTREMELY DANGEROUS)
--fwdownload-modee Download firmware using mode E (min-size
segments) (EXTREMELY DANGEROUS)
--fwdownload-modee-max Download firmware using mode E (max-size
segments) (EXTREMELY DANGEROUS)
--idle-immediate Idle drive immediately
--idle-unload Idle immediately and unload heads
--Istdin Read identify data from stdin as ASCII hex
--Istdout Write identify data to stdout as ASCII hex
--make-bad-sector Deliberately corrupt a sector directly on the media
(VERY DANGEROUS)
--offset use with -t, to begin timings at given offset (in
GiB) from start of drive
--prefer-ata12 Use 12-byte (instead of 16-byte) SAT commands when
possible
--read-sector Read and dump (in hex) a sector directly from the media
--repair-sector Alias for the --write-sector option (VERY DANGEROUS)
--security-help Display help for ATA security commands
--trim-sector-ranges Tell SSD firmware to discard unneeded data
sectors: lba:count ..
--trim-sector-ranges-stdin Same as above, but reads lba:count pairs
from stdin
--verbose Display extra diagnostics from some commands
--write-sector Repair/overwrite a (possibly bad) sector directly on
the media (VERY DANGEROUS)
I've never used this stuff, Joanne, but I know people who have, which
is why I suggested you have the user password set (the
"--set-security-password" command defaults to "--user-master u").
You may have to specify "--user-master m --set-security-password
thepassword --security-mode h" to actually set it, and if it's already
set, I don't know that you can change it. You could try "hdparm
--security-help" for details on what it expects.
As all of these commands are considered "dangerous", I'd only play with
them on a drive you can afford to turn into a doorstop or paperweight
if things go wrong.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- Try to look unimportant. The bad guys may be low on ammo. -
----------------------------------------------------------------------
11:32 p.m.
On Mon, Mar 23, 2015 at 9:53 PM, jd1008 <jd1008(a)gmail.com> wrote:
Every sector ???? Why would the drive which is supposed to be using
it's own internal logic to do the secure erase, report write errors to the
host?
Does the host request notifications of such errors?
I've never had any drive report anything other than completion even
when the drive had known bad sectors. There was no status of anykind,
the hdparm command has no progress reporting at all, so it just seems
to hang, and then it returns.
And for drives with bad sectors, they were still bad sectors after ATA
Secure Erase suggesting that while they're zero'd the firmware does no
confirmation read and as such isn't checking for persistent write
problems for the purpose of sector remapping. It's pretty much just a
fast way to zero out a drive. To ascertain bad sectors and cause them
to be remapped means using dd or badblocks with the proper blocksize
(a multiple of 4096 bytes).
--
Chris Murphy
10:53 p.m.
On 03/20/2015 03:16 PM, Joe Zeff wrote:
On 03/20/2015 02:13 PM, jd1008 wrote:
>
> It made no difference :(
If nothing else, the test took very little time and completely
eliminated a possibility. Thanx for letting us know.
The funny thing, is I ran a
thorough full disk drive stress test using a
stress tester I found online.
All tests passed (took many hours to stress test 2TB drive).
All tests passed without errors.
Yet, when I run the hdparm secure erase, drive reports write errors for
all sectors so far.
It has been running for many hours, and last time I looked, it was at
sector 115,744,312
Every sector ???? Why would the drive which is supposed to be using
it's own internal logic to do the secure erase, report write errors to
the host?
Does the host request notifications of such errors?
4:48 p.m.
On 03/20/2015 03:41 PM, Chris Murphy wrote:
Not applicable. I advise staying on the rails.
On Mar 20, 2015 3:22 PM, "jd1008" <jd1008(a)gmail.com
<mailto:jd1008@gmail.com>> wrote:
On 03/20/2015 03:19 PM, Chris Murphy wrote:
sudo hdparm --user-master u --security-set-pass Eins /dev/sdX
sudo time hdparm --user-master u --security-erase Eins /dev/sdX
OR
sudo time hdparm --user-master u --security-erase-enhanced
Eins /dev/sdX
Just copy and paste it. Two commands are needed. Just two. Not
three. Not one.
I want to change the master password.
I have already set the user password.
Rails????
Are you yourself on rails?? :) :)
Gee, what is going on in your mind?
I think you are exposing too much of how you think :) :)
4:41 p.m.
Not applicable. I advise staying on the rails.
On Mar 20, 2015 3:22 PM, "jd1008" <jd1008(a)gmail.com> wrote:
On 03/20/2015 03:19 PM, Chris Murphy wrote:
> sudo hdparm --user-master u --security-set-pass Eins /dev/sdX
>
> sudo time hdparm --user-master u --security-erase Eins /dev/sdX
> OR
> sudo time hdparm --user-master u --security-erase-enhanced Eins /dev/sdX
>
>
> Just copy and paste it. Two commands are needed. Just two. Not three. Not
> one.
>
I want to change the master password.
I have already set the user password.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
4:19 p.m.
sudo hdparm --user-master u --security-set-pass Eins /dev/sdX
sudo time hdparm --user-master u --security-erase Eins /dev/sdX
OR
sudo time hdparm --user-master u --security-erase-enhanced Eins /dev/sdX
Just copy and paste it. Two commands are needed. Just two. Not three. Not one.
4:22 p.m.
On 03/20/2015 03:19 PM, Chris Murphy wrote:
sudo hdparm --user-master u --security-set-pass Eins /dev/sdX
sudo time hdparm --user-master u --security-erase Eins /dev/sdX
OR
sudo time hdparm --user-master u --security-erase-enhanced Eins /dev/sdX
Just copy and paste it. Two commands are needed. Just two. Not three. Not one.
I
want to change the master password.
I have already set the user password.
4:13 p.m.
On 03/20/2015 02:59 PM, Joe Zeff wrote:
On 03/20/2015 01:49 PM, jd1008 wrote:
> Unfortunately, manpage says:
>
> -m Get/set sector count for multiple sector I/O on the drive.
>
> I have no need for this, and I do not see how it helps my situation
> where I cannot set the master password.
Yes, I understand that. What you don't understand is that the program
may be confusing the letter m for a (valid) option without the proper
dash. That's why I'm suggesting that you put that option last, to
avoid ambiguity.
It made no difference :(
4 p.m.
On 03/20/2015 02:55 PM, Rick Stevens wrote:
On 03/20/2015 01:11 PM, jd1008 wrote:
>
> It seems that setting the master password is not possible.
> Why is that?
> Could it be that the command itself has been hacked
> NOT to change the master password?
>
> Time to take a look at the source code :)
Yup. I did take a look at the page Chris cited and it does go into
things fairly well and describes the master password issue. Yes, all
examples are in "user" mode, but if it does the job then I don't really
see any need to go deeper (except to satisfy any morbid curiosity
streak you may have).
Morbid???
How is it morbid? Why do you have the need to
disparage people's choice of how they want to do things?
If the man page says it should work, I want to try it.
Why is that morbid?
3:59 p.m.
On 03/20/2015 01:49 PM, jd1008 wrote:
Unfortunately, manpage says:
-m Get/set sector count for multiple sector I/O on the drive.
I have no need for this, and I do not see how it helps my situation
where I cannot set the master password.
Yes, I understand that. What you don't understand is that the program
may be confusing the letter m for a (valid) option without the proper
dash. That's why I'm suggesting that you put that option last, to avoid
ambiguity.
3:55 p.m.
On 03/20/2015 01:11 PM, jd1008 wrote:
On 03/20/2015 01:32 PM, Rick Stevens wrote:
> I've never used this stuff, Joanne, but I know people who have, which
> is why I suggested you have the user password set (the
> "--set-security-password" command defaults to "--user-master
u").
>
> You may have to specify "--user-master m --set-security-password
> thepassword --security-mode h" to actually set it, and if it's already
> set, I don't know that you can change it. You could try "hdparm
> --security-help" for details on what it expects.
>
> As all of these commands are considered "dangerous", I'd only play
with
> them on a drive you can afford to turn into a doorstop or paperweight
> if things go wrong.
It seems that setting the master password is not possible.
Why is that?
Could it be that the command itself has been hacked
NOT to change the master password?
Time to take a look at the source code :)
Yup. I did take a look at the page Chris cited and it does go into
things fairly well and describes the master password issue. Yes, all
examples are in "user" mode, but if it does the job then I don't really
see any need to go deeper (except to satisfy any morbid curiosity
streak you may have).
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- To understand recursion, you must first understand recursion. -
----------------------------------------------------------------------
3:49 p.m.
On 03/20/2015 02:29 PM, Joe Zeff wrote:
On 03/20/2015 01:24 PM, jd1008 wrote:
> Forget it!!!
> Either you are mixing things up or making them up.
> I have all my messages in the sent folder.
> I never used -m argument.
I'm not saying that you did; I was saying that there is an option m,
and it needs a dash in front of it. The quote was from the list of
possible options showing the one in question. Now, it may be that in
your context m was an argument to an option, but if so, it's ambiguous
and the program (which I don't have installed) was confused. Maybe if
you re-ordered the options so that nothing comes after the m it might
work better.
Unfortunately, manpage says:
-m Get/set sector count for multiple sector I/O on the drive.
I have no need for this, and I do not see how it helps my situation
where I cannot set the master password.
3:30 p.m.
On 03/20/2015 02:24 PM, Chris Murphy wrote:
Is the drive in question in any kind of enclosure? If it is,
there's a
good chance using ATA Secure Erase will either not work, or will brick
the drive. There are many craptastic bridge chipsets out there.
Otherwise this might help.
http://mackonsti.wordpress.com/2011/11/22/ssd-secure-erase-ata-command
Chris Murphy
It is not in an enclosure. I connect it directly to the
eSATA port via eSATA cable.
Also the link only shows examples of --user-master u
no examples of --master-user m
3:29 p.m.
On 03/20/2015 01:24 PM, jd1008 wrote:
Forget it!!!
Either you are mixing things up or making them up.
I have all my messages in the sent folder.
I never used -m argument.
I'm not saying that you did; I was saying that there is an option m, and
it needs a dash in front of it. The quote was from the list of possible
options showing the one in question. Now, it may be that in your
context m was an argument to an option, but if so, it's ambiguous and
the program (which I don't have installed) was confused. Maybe if you
re-ordered the options so that nothing comes after the m it might work
better.
3:25 p.m.
And just to quality that source, I use it all the time, so I know it
works. Both SSD and HDD.
--
Chris Murphy
3:24 p.m.
On 03/20/2015 02:19 PM, Joe Zeff wrote:
On 03/20/2015 01:12 PM, jd1008 wrote:
>
>
> On 03/20/2015 02:05 PM, Joe Zeff wrote:
>> On 03/20/2015 12:53 PM, jd1008 wrote:
>>>
>>> Maybe you are using some other version???
>>> My hdparm is
>>> # rpm -q hdparm
>>> hdparm-9.45-1.fc21.x86_64
>>
>> From your earlier message:
>>
>> > -m Get/set multiple sector count
> Man - get a clue!!!!
>
> You are quoting yourself!!!
>
No, I'm not. The first time I replied, I'd trimmed all of that out of
my reply; I went back to your message, copied that line and pasted it
to show you what I was referring to. At this point, my only
suggestion is that you take that chip off your shoulder and don't be
so thin skinned because I have better things to do than to try and
help people who are so quick to take offense.
Forget it!!!
Either you are mixing things up or making them up.
I have all my messages in the sent folder.
I never used -m argument.
But I am willing to look at the unmodified message
you attribute to me, which you can forward to the list totally unmodified.
3:24 p.m.
Is the drive in question in any kind of enclosure? If it is, there's a
good chance using ATA Secure Erase will either not work, or will brick
the drive. There are many craptastic bridge chipsets out there.
Otherwise this might help.
http://mackonsti.wordpress.com/2011/11/22/ssd-secure-erase-ata-command
Chris Murphy
3:19 p.m.
On 03/20/2015 01:12 PM, jd1008 wrote:
On 03/20/2015 02:05 PM, Joe Zeff wrote:
> On 03/20/2015 12:53 PM, jd1008 wrote:
>>
>> Maybe you are using some other version???
>> My hdparm is
>> # rpm -q hdparm
>> hdparm-9.45-1.fc21.x86_64
>
> From your earlier message:
>
> > -m Get/set multiple sector count
Man - get a clue!!!!
You are quoting yourself!!!
No, I'm not. The first time I replied, I'd trimmed all of that out of
my reply; I went back to your message, copied that line and pasted it to
show you what I was referring to. At this point, my only suggestion is
that you take that chip off your shoulder and don't be so thin skinned
because I have better things to do than to try and help people who are
so quick to take offense.
3:11 p.m.
On 03/20/2015 01:32 PM, Rick Stevens wrote:
I've never used this stuff, Joanne, but I know people who have,
which
is why I suggested you have the user password set (the
"--set-security-password" command defaults to "--user-master u").
You may have to specify "--user-master m --set-security-password
thepassword --security-mode h" to actually set it, and if it's already
set, I don't know that you can change it. You could try "hdparm
--security-help" for details on what it expects.
As all of these commands are considered "dangerous", I'd only play with
them on a drive you can afford to turn into a doorstop or paperweight
if things go wrong.
It seems that setting the master password is not possible.
Why is that?
Could it be that the command itself has been hacked
NOT to change the master password?
Time to take a look at the source code :)
2:54 p.m.
On 03/20/2015 12:48 PM, jd1008 wrote:
On 03/20/2015 01:32 PM, Rick Stevens wrote:
>
> I've never used this stuff, Joanne, but I know people who have, which
> is why I suggested you have the user password set (the
> "--set-security-password" command defaults to "--user-master
u").
>
> You may have to specify "--user-master m --set-security-password
> thepassword --security-mode h" to actually set it, and if it's already
> set, I don't know that you can change it. You could try "hdparm
> --security-help" for details on what it expects.
>
> As all of these commands are considered "dangerous", I'd only play
with
> them on a drive you can afford to turn into a doorstop or paperweight
> if things go wrong.
Who is Joanne???!
Why do you assume my name Joanne?
Whoops! I mistook your address for someone else I know whose address is
quite similar. I should have been more careful and I do apologize. I
meant no offense.
I will now go sit in the corner with my dunce cap on.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- Okay, who put a "stop payment" on my reality check? -
----------------------------------------------------------------------
2:53 p.m.
On 03/20/2015 01:36 PM, Joe Zeff wrote:
On 03/20/2015 12:25 PM, jd1008 wrote:
> Man page says only choices are
> u
> and
> m
>
> Does not mention a - preceding either one.
Look at the usage you quoted, and I snipped. It lists -m, but not
simply m. In fact, I don't know off-hand of a command that allows you
to specify an option without either a single or double dash in front
of it.
What you say is weird!!
Here is that segment of the man page:
--user-master USER
Specifies which password (user/master) to select.
Defaults to user password. Only useful in combina‐
tion with --security-unlock, --security-set-pass,
--security-disable, --security-erase or --security-
erase-enhanced.
u user password
m master password
I do not see any hyphens preceding m or u
Also -m has a totally different usage effect:
-m Get/set sector count for multiple sector I/O on the
drive. A setting of 0 disables this feature. Mul‐
tiple sector mode (aka IDE Block Mode), is a feature of
most modern IDE hard drives, permitting the
transfer of multiple sectors per I/O interrupt, rather
than the usual one sector per interrupt. When
this feature is enabled, it typically reduces operating
system overhead for disk I/O by 30-50%. On
many systems, it also provides increased data throughput
of anywhere from 5% to 50%. Some drives, how‐
ever (most notably the WD Caviar series), seem to run
slower with multiple mode enabled. Your mileage
may vary. Most drives support the minimum settings of
2, 4, 8, or 16 (sectors). Larger settings may
also be possible, depending on the drive. A setting of
16 or 32 seems optimal on many systems. West‐
ern Digital recommends lower settings of 4 to 8 on many
of their drives, due tiny (32kB) drive buffers
and non-optimized buffering algorithms. The -i option
can be used to find the maximum setting sup‐
ported by an installed drive (look for MaxMultSect in the
output). Some drives claim to support multi‐
ple mode, but lose data at some settings. Under rare
circumstances, such failures can result in mas‐
sive filesystem corruption.
Maybe you are using some other version???
My hdparm is
# rpm -q hdparm
hdparm-9.45-1.fc21.x86_64
2:48 p.m.
On 03/20/2015 01:32 PM, Rick Stevens wrote:
I've never used this stuff, Joanne, but I know people who have, which
is why I suggested you have the user password set (the
"--set-security-password" command defaults to "--user-master u").
You may have to specify "--user-master m --set-security-password
thepassword --security-mode h" to actually set it, and if it's already
set, I don't know that you can change it. You could try "hdparm
--security-help" for details on what it expects.
As all of these commands are considered "dangerous", I'd only play with
them on a drive you can afford to turn into a doorstop or paperweight
if things go wrong.
Who is Joanne???!
Why do you assume my name Joanne?
2:25 p.m.
On 03/20/2015 01:18 PM, Joe Zeff wrote:
On 03/20/2015 12:04 PM, jd1008 wrote:
> On 03/20/2015 11:24 AM, Rick Stevens wrote:
>> hdparm --user-master m --set-security-pass
>
> It is belching the usage at me:
>
> # hdparm --user-master m --set-security-pass thepassword /dev/sdc
Have you tried using -m instead of just m? HTH, HAND.
Man page says only choices are
u
and
m
Does not mention a - preceding either one.
12:14 p.m.
On 03/20/2015 09:54 AM, jd1008 wrote:
On 03/20/2015 09:51 AM, jd1008 wrote:
> The command and error message are:
>
> # time hdparm --verbose --user-master m --security-erase-enhanced
> thepassword /dev/sdc
> security_password="thepassword"
>
> /dev/sdc:
> Issuing SECURITY_ERASE command, password="thepassword", user=master
> outgoing cdb: 85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00
> SG_IO: ATA_16 status=0x0, host_status=0x0, driver_status=0x0
> SG_IO: sb[]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> incoming_data: 7a 42 ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00 00 00
> 00 00 20 20 20 20 57 20 2d 44 58 57 31 56 35 45 4b 33 45 41 33 38 00
> 00 00 40 00 00 31 30 30 2e 41 31 31 30 44 57 20 43 44 57 30 32 50 4e
> 58 56 30 2d 45 30 34 41 30 54 20 20 20 20 20 20 20 20 20 20 20 20 20
> 20 20 20 20 20 20 20 10 80 00 40 00 2f 01 40 00 00 00 00 07 00 ff 3f
> 10 00 3f 00 10 fc fb 00 00 01 ff ff ff 0f 00 00 07 00 03 00 78 00 78
> 00 78 00 78 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 00 0e ff 04 00
> 4c 00 44 00 fe 03 00 00 6b 74 69 7d 23 61 6b 74 49 bc 23 61 7f 40 bb
> 00 bb 00 80 00 fe ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0 88
> e0 e8 00 00 00 00 00 00 00 00 03 60 00 00 01 50 e2 4e 90 5e 21 ff 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 18 40 18 40 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 27 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 35 70 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 50 14 00 00 00 00 00 00 00 00 3e 10 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 10 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 a5 bd
> SG_IO: desc[]: 00 00
> ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00
> outgoing cdb: 85 06 20 00 00 00 00 00 00 00 00 00 00 40 f3 00
> SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
> SG_IO: sb[]: 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00 00 00
> 00 00 40 50 00 00 00 00 00 00 00 00 00 00
> SG_IO: desc[]: 09 0c 00 00 00 00 00 00 00 00 00 00 40 50
> ATA_16 stat=50 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=40
> oflags.bits.lob_all=0x8a, flags={ feat nsect command }
> oflags.bits.hob_all=0x00, flags={ }
> outgoing cdb: 85 0a 06 00 00 00 01 00 00 00 00 00 00 40 f4 00
> outgoing_data: 03 00 68 64 70 61 72 6d 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00
> SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
> SG_IO: sb[]: 72 0b 00 00 00 00 00 0e 09 0c 00 04 00 01 00 00 00 00
> 00 00 40 51 00 00 00 00 00 00 00 00 00 00
> SG_IO: desc[]: 09 0c 00 04 00 01 00 00 00 00 00 00 40 51
> ATA_16 stat=51 err=04 nsect=01 lbal=00 lbam=00 lbah=00 dev=40
> I/O error, ata_op=0xf4 ata_status=0x51 ata_error=0x04
> SECURITY_ERASE: Input/output error
>
> real 0m3.56s
> user 0m0.00s
> sys 0m0.00s
>
>
> However, I have no problem running
> dd if=/dev/zero of=/dev/sdc bs=1G (PS: I have 8GB ram, and less
> that 1GB is used before I start the command).
>
> So, am hoping an hdparm guru will offer some insight.
>
Update:
Changing the command parameter m to u
makes it work. Yet, I do want to use the parameter m .
How do I make it accept the parameter m ???
Update:
# hdparm --user-master m --security-set-pass thepassword /dev/sdc
security_password="thepassword"
/dev/sdc:
Issuing SECURITY_SET_PASS command, password="thepassword",
user=master, mode=high
SECURITY_SET_PASS: Input/output error
Yet, if I use hdparm --user-master u .... etc
it works just fine. Why?? The manpage says that it can be u or m.
10:54 a.m.
On 03/20/2015 09:51 AM, jd1008 wrote:
The command and error message are:
# time hdparm --verbose --user-master m --security-erase-enhanced
thepassword /dev/sdc
security_password="thepassword"
/dev/sdc:
Issuing SECURITY_ERASE command, password="thepassword", user=master
outgoing cdb: 85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00
SG_IO: ATA_16 status=0x0, host_status=0x0, driver_status=0x0
SG_IO: sb[]: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
incoming_data: 7a 42 ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00 00 00
00 00 20 20 20 20 57 20 2d 44 58 57 31 56 35 45 4b 33 45 41 33 38 00
00 00 40 00 00 31 30 30 2e 41 31 31 30 44 57 20 43 44 57 30 32 50 4e
58 56 30 2d 45 30 34 41 30 54 20 20 20 20 20 20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 10 80 00 40 00 2f 01 40 00 00 00 00 07 00 ff 3f
10 00 3f 00 10 fc fb 00 00 01 ff ff ff 0f 00 00 07 00 03 00 78 00 78
00 78 00 78 00 00 00 00 00 00 00 00 00 00 00 00 00 1f 00 0e ff 04 00
4c 00 44 00 fe 03 00 00 6b 74 69 7d 23 61 6b 74 49 bc 23 61 7f 40 bb
00 bb 00 80 00 fe ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0 88
e0 e8 00 00 00 00 00 00 00 00 03 60 00 00 01 50 e2 4e 90 5e 21 ff 00
00 00 00 00 00 00 00 00 00 00 00 00 00 18 40 18 40 00 00 00 00 00 00
00 00 00 00 00 00 00 00 27 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 35 70 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00
00 00 50 14 00 00 00 00 00 00 00 00 3e 10 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 10 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 a5 bd
SG_IO: desc[]: 00 00
ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00
outgoing cdb: 85 06 20 00 00 00 00 00 00 00 00 00 00 40 f3 00
SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
SG_IO: sb[]: 72 01 00 1d 00 00 00 0e 09 0c 00 00 00 00 00 00 00 00 00
00 40 50 00 00 00 00 00 00 00 00 00 00
SG_IO: desc[]: 09 0c 00 00 00 00 00 00 00 00 00 00 40 50
ATA_16 stat=50 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=40
oflags.bits.lob_all=0x8a, flags={ feat nsect command }
oflags.bits.hob_all=0x00, flags={ }
outgoing cdb: 85 0a 06 00 00 00 01 00 00 00 00 00 00 40 f4 00
outgoing_data: 03 00 68 64 70 61 72 6d 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00
SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8
SG_IO: sb[]: 72 0b 00 00 00 00 00 0e 09 0c 00 04 00 01 00 00 00 00 00
00 40 51 00 00 00 00 00 00 00 00 00 00
SG_IO: desc[]: 09 0c 00 04 00 01 00 00 00 00 00 00 40 51
ATA_16 stat=51 err=04 nsect=01 lbal=00 lbam=00 lbah=00 dev=40
I/O error, ata_op=0xf4 ata_status=0x51 ata_error=0x04
SECURITY_ERASE: Input/output error
real 0m3.56s
user 0m0.00s
sys 0m0.00s
However, I have no problem running
dd if=/dev/zero of=/dev/sdc bs=1G (PS: I have 8GB ram, and less
that 1GB is used before I start the command).
So, am hoping an hdparm guru will offer some insight.
Update:
Changing the command parameter m to u
makes it work. Yet, I do want to use the parameter m .
How do I make it accept the parameter m ???
3:12 p.m.
On 03/20/2015 02:05 PM, Joe Zeff wrote:
On 03/20/2015 12:53 PM, jd1008 wrote:
>
> Maybe you are using some other version???
> My hdparm is
> # rpm -q hdparm
> hdparm-9.45-1.fc21.x86_64
From your earlier message:
> -m Get/set multiple sector count
Man - get a clue!!!!
You are quoting yourself!!!
2:36 p.m.
On 03/20/2015 12:25 PM, jd1008 wrote:
Man page says only choices are
u
and
m
Does not mention a - preceding either one.
Look at the usage you quoted, and I snipped. It lists -m, but not
simply m. In fact, I don't know off-hand of a command that allows you
to specify an option without either a single or double dash in front of it.
2:04 p.m.
On 03/20/2015 11:24 AM, Rick Stevens wrote:
hdparm --user-master m --set-security-pass
It is belching the usage at me:
# hdparm --user-master m --set-security-pass thepassword /dev/sdc
hdparm - get/set hard disk parameters - version v9.45, by Mark Lord.
Usage: hdparm [options] [device ...]
Options:
-a Get/set fs readahead
-A Get/set the drive look-ahead flag (0/1)
-b Get/set bus state (0 == off, 1 == on, 2 == tristate)
-B Set Advanced Power Management setting (1-255)
-c Get/set IDE 32-bit IO setting
-C Check drive power mode status
-d Get/set using_dma flag
-D Enable/disable drive defect management
-E Set cd/dvd drive speed
-f Flush buffer cache for device on exit
-F Flush drive write cache
-g Display drive geometry
-h Display terse usage information
-H Read temperature from drive (Hitachi only)
-i Display drive identification
-I Detailed/current information directly from drive
-J Get/set Western DIgital "Idle3" timeout for a WDC "Green" drive
(DANGEROUS)
-k Get/set keep_settings_over_reset flag (0/1)
-K Set drive keep_features_over_reset flag (0/1)
-L Set drive doorlock (0/1) (removable harddisks only)
-m Get/set multiple sector count
-M Get/set acoustic management (0-254, 128: quiet, 254: fast)
-n Get/set ignore-write-errors flag (0/1)
-N Get/set max visible number of sectors (HPA) (VERY DANGEROUS)
-p Set PIO mode on IDE interface chipset (0,1,2,3,4,...)
-P Set drive prefetch count
-q Change next setting quietly
-Q Get/set DMA queue_depth (if supported)
-r Get/set device readonly flag (DANGEROUS to set)
-R Get/set device write-read-verify flag
-s Set power-up in standby flag (0/1) (DANGEROUS)
-S Set standby (spindown) timeout
-t Perform device read timings
-T Perform cache read timings
-u Get/set unmaskirq flag (0/1)
-U Obsolete
-v Use defaults; same as -acdgkmur for IDE drives
-V Display program version and exit immediately
-w Perform device reset (DANGEROUS)
-W Get/set drive write-caching flag (0/1)
-x Obsolete
-X Set IDE xfer mode (DANGEROUS)
-y Put drive in standby mode
-Y Put drive to sleep
-z Re-read partition table
-Z Disable Seagate auto-powersaving mode
--dco-freeze Freeze/lock current device configuration until next
power cycle
--dco-identify Read/dump device configuration identify data
--dco-restore Reset device configuration back to factory defaults
--dco-setmax Use DCO to set maximum addressable sectors
--direct Use O_DIRECT to bypass page cache for timings
--drq-hsm-error Crash system with a "stuck DRQ" error (VERY DANGEROUS)
--fallocate Create a file without writing data to disk
--fibmap Show device extents (and fragmentation) for a file
--fwdownload Download firmware file to drive (EXTREMELY
DANGEROUS)
--fwdownload-mode3 Download firmware using min-size segments
(EXTREMELY DANGEROUS)
--fwdownload-mode3-max Download firmware using max-size segments
(EXTREMELY DANGEROUS)
--fwdownload-mode7 Download firmware using a single segment
(EXTREMELY DANGEROUS)
--fwdownload-modee Download firmware using mode E (min-size
segments) (EXTREMELY DANGEROUS)
--fwdownload-modee-max Download firmware using mode E (max-size
segments) (EXTREMELY DANGEROUS)
--idle-immediate Idle drive immediately
--idle-unload Idle immediately and unload heads
--Istdin Read identify data from stdin as ASCII hex
--Istdout Write identify data to stdout as ASCII hex
--make-bad-sector Deliberately corrupt a sector directly on the media
(VERY DANGEROUS)
--offset use with -t, to begin timings at given offset (in
GiB) from start of drive
--prefer-ata12 Use 12-byte (instead of 16-byte) SAT commands when
possible
--read-sector Read and dump (in hex) a sector directly from the media
--repair-sector Alias for the --write-sector option (VERY DANGEROUS)
--security-help Display help for ATA security commands
--trim-sector-ranges Tell SSD firmware to discard unneeded data
sectors: lba:count ..
--trim-sector-ranges-stdin Same as above, but reads lba:count pairs
from stdin
--verbose Display extra diagnostics from some commands
--write-sector Repair/overwrite a (possibly bad) sector directly on
the media (VERY DANGEROUS)
3321
days inactive
3325
days old
33 comments
4 participants
participants (4)
-
Chris Murphy -
JD -
Joe Zeff -
Rick Stevens