Activity for Mark Lord
-
Mark Lord posted a comment on discussion Open Discussion
No. Keeping this away from Microsoft.
-
fdevname memory leak
-
fdevname memory leak
-
Not a real issue with anything. The memory involved is tiny, and everything is freed when the program exits.
-
Try that and report back.
-
--- hdparm-9.65/hdparm.c 2022-09-06 13:02:56.000000000 -0400 +++ hdparm/hdparm.c 2024-03-25 20:30:28.873285139 -0400 @@ -2,7 +2,7 @@ * hdparm.c - Command line interface to get/set hard disk parameters. * - by Mark Lord (C) 1994-2022 -- freely distributable. */ -#define HDPARM_VERSION "v9.65" +#define HDPARM_VERSION "v9.65+" #define _LARGEFILE64_SOURCE /*for lseek64*/ #define _BSD_SOURCE /* for strtoll() */ @@ -3040,16 +3040,18 @@ static void get_security_password (int h } else if (!handle_NULL ||...
-
Sleep Now and Stand By Now.
-
I have no idea what you are asking. Both '-y' and '-Y' work as intended for me -- I use them regularly, and one can even verify them by using '-C' afterward to read back the (new) drive state.
-
I have no idea what you are asking. Both '-y' and '-Y' work as intended for me -- I use them regularly, and one can even verify them by using '-C' afterward to read back the (new) drive state.
-
hdparm-9.65 is released
-
Fix built with glibc 2.36
-
Okay, I'll put that #ifndef in place for v9.65 and hope that it does more good than harm. Thanks
-
`set-sector-size` out of range
-
Yes, that got fixed ages ago! :)
-
Thanks. But doing this will break builds with older versions. Can you make it conditional upon the version of GCC ?
-
hdparm-9.64 is released
-
hdparm-9.63 is released
-
I have renamed the new flag to be "--sanitize-overwrite-passes" to avoid confusion with existing flags where "-pass" refers to a password. Otherwise, applied for hdparm-9.63.
-
hdparm --sanitize-overwrite do not have an option to change the count parameter and default value
-
Not a bug. It does what one asks it to do. If one wants just a single-pass erase, then use "--security-erase" instead. But I'm totally open to anyone who wants to submit a patch which adds a command-line option to specify the exact number of sanitize cycles. Cheers
-
hdparm -I 12 says "(1 minutes)" and -I 242 "(1 hours)"
-
Applied, thanks. I especially like how it nicely handles "0" as well as "1". :)
-
hdparm -I /dev/sda crashes device
-
Kernel (libata) bug, not hdparm.
-
hdparm --dco-identify reports invalid value for Real max sectors
-
Fix this and similar bugs elsewhere in the code. hdparm-9.62 now available.
-
hdparm-9.62 is released
-
hdparm-9.61 is released
-
-J Get/set Western DIgital "Idle3" timeout for a WDC "Green" drive (DANGEROUS) There is support in there, but this was written many years ago, and WD may have changed the protocol. So it might still work, or it might brick your drive. Your call. WD doesn't tell us how it works, so that's the best shot at it for now.
-
hdparm-9.60 is released
-
hdparm-9.59 is released
-
identify.c: Decode word 69 lower bits properly
-
Looks good. Applied. Thanks.
-
Once the drive firmware has been programmed to "spin down" after inactivity (which is what -B does), then it will spin down so long as it is not being accessed by the system. So.. if you want it to spin-down, hack your copy of veracrypt to STOP continually accessing the drive.
-
close file handle before exit
-
Pointless and unneeded code bloat. Invoking exit(2) closes all open descriptors already, so there is no need to waste code to do it separately.
-
"The running kernel lacks CONFIG_IDE_TASK_IOCTL support for this device." Perhaps complain to your distro provider about that.
-
I think you forgot to include the actual command you issued that generated that message.
-
hdparm readahead max is only 2048 - could be higher
-
The -a parameter is for filesystem read-ahead, not the drive's own readahead (see man page, yes this is documented). The Linux kernel automatically tunes block device read-ahead on its own as well, so there is little (if any) real benefit to fiddling with this value.
-
DCO Identify Real Max Sectors Value incorrect
-
Thanks. Fixed for hdparm-9.59.
-
9.57 segfaults if drive identification fails
-
Fixed, and released: hdparm-9.58. Thanks Alex!
-
hdparm-9.58 is released
-
hdparm-9.57 is released
-
--read-sector: Add option for raw/binary output
-
Not going to happen. Working around it is easy enough I suppose.
-
--read-sector: Use SAT or other passthrough method if needed (for sg not block device)
-
Okay, hdparm-9.57 will skip the "is full device" check (which uses the HDIO_GETGEO call) when run on a character device node.
-
I think that both of these people are trying to use advanced SATA commands over a USB connection. The USB drivers do not implement the "missing" IOCTL --> it is very specific to libata and the IDE stack. Cheers
-
Due to other changes in the next release, the code is not yet "in shape" for passing along. For this bug, I just ensured that the loop does do depth++ each time around. The sysfs attr that it is looking for does not always (or even often?) exist, so it's not an error to not find it. Cheers
-
Fixed for next release (9.57).
-
Bug (endless loop with buffer overflow) in sysfs.c
-
Fixed for next release (hdparm-9.57)
-
hdparm-9.56 is released
-
--Istdin incorrectly byte-swaps (or fails to) hex identify data
-
fixed in hdparm-9.56
-
Options to output raw binary IDENTIFY DEVICE and DCO data
-
Fixed in hdparm-9.56
-
Good one! I wonder when that got broken.. I used it all the time when building up drive databases. Darn. will fix. Soon!
-
Good one! I wonder when that go broken.. I used it all the time when building up drive databases. Darn. will fix. Soon!
-
hdparm-9.55 is released
-
hdparm-9.55 is released
-
use sys/sysmacros.h in more places
-
This will be included in hdparm-9.55.
-
hdparm-9.54 is released
-
Fix error code handling on some JMicron USB to (S)ATA bridges
-
Isn't this already there? Eg. hdparm --sanitize-crypto-scramble and similar..
-
Nobody seems to have fixed it yet.
-
hdparm-9.53 is released
-
Patch conflict with others in the queue: emaiing Iestyn Walters directly to hopefully get this resolved.
-
Could you possibly fix that "code block" above to be more readable, and convert it into a patch so that I know where in the code it ought to be placed? Thanks.
-
Can't use hdparm on AF drive behind USB bridge
-
Thanks -- patch now merged into hdparm-9.52.
-
I lost track of this patch years ago and only just rediscovered it. MERGED.
-
hdparm-9.52 is released
-
hdparm-9.51 is released
-
Avoid password as cli parameter, show a prompt instead.
-
Good suggestion. Fixed with new --security-prompt-for-password flag in hdparm-9....
-
Perhaps the two SAS drives do not implement the SATA IDENTIFY command, which is what...
-
option to skip "set APM setting" (-B) operation on drives that don't support APM
-
hdparm is used to test/debug new/old drive features. As such, when I tell it to send...
-
hdparm is used to test/debug new/old drive features. As such, when I tell it to send...
-
bad make command in Makefile
-
Thanks. I have changed the "make" into $(MAKE). The -j is there for my convenience,...
-
typos in the code and man page
-
Thanks. Applied for the next release (9.51 and higher).
-
hdparm-9.50 is released
-
hdparm-9.49 is released
-
A patch is the best thing. And don't use this silly cloud interface to pass it along...
-
Missing information for NVME SSD disk
-
Most likely the device driver (Linux kernel) is not processing the IDENTIFY DEVICE...
-
Incorrectly checking Smart self test instead of security bit and skipping security section.
-
Fixed for the next release, thanks.
-
It has been a few years since anyone last checked/reported using hdparm on SAS drives,...
-
Okay, no version info provided. Try again with latest hdparm from thsi site, and...
-
cannot read / set parameters on sas drives
-
The "-i" (lowercase) flag is very specfic to the Linux ATA and IDE drivers. Use "-I"...
-
For this to move forward, somebody has to step up and volunteer to implement it,...
1 >