search

martijnvanbrummelen / nwipe

nwipe secure disk eraser
GNU General Public License v2.0
688 stars 79 forks source link

Help needed. HPA/DCO [Completed] #444

Closed PartialVolume closed 10 months ago

PartialVolume commented 1 year ago

I'm currently working on the HPA/DCO code and have come across an issue with hdparm incorrectly parsing the sense data when it tries to calculate the real max sectors, this bug exists in v9.60 and has since been fixed in v9.65 however I don't know exactly which version it was fixed in, irrespective nwipe will need to cope with this bug if it's run on a LTS distro in particular that's running older versions of hdparm.

So I plan on parsing the sense data myself when the real max sectors don't make any sense.

However the largest drive I have for testing is 2TB and I need some sense data from a 10TB or greater drive to make sure I decode the size correctly.

If somebody could run the following command on a drive that is larger than 10TB and post the output here that would be appreciated.

The command is sudo hdparm --verbose --dco-identify /dev/sdxxxx

Thanks

either reply here or over in ShredOS discussions discussions-Help-Needed

mdcato commented 1 year ago

I have a 10TB that I can run it on later today. I have Fedora Core 37 which likely has hdparm beyond v9.65. Do you also want it from the version prior to the fix?

(Sent from mobile)

From: PartialVolume @.> Sent: Friday, March 3, 2023 6:45:25 AM To: martijnvanbrummelen/nwipe @.> Cc: Subscribed @.***> Subject: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

I'm currently working on the HPA/DCO code and have come across an issue with hdparm incorrectly parsing the sense data when it tries to calculate the real max sectors, this bug exists in v9.60 and has since been fixed in v9.65 however I don't know exactly which version it was fixed in, irrespective nwipe will need to cope with this bug if it's run on a LTS distro in particular that's running older versions of hdparm.

So I plan on parsing the sense data myself when the real max sectors don't make any sense.

However the largest drive I have for testing is 2TB and I need some sense data from a 10TB or greater drive to make sure I decode the size correctly.

If somebody could run the following command on a drive that is larger than 10TB and post the output here that would be appreciated.

The command is sudo hdparm --verbose --dco-identify /dev/sdxxxx

Thanks

either reply here or over in ShredOS discussions discussions-Help-Neededhttps://github.com/PartialVolume/shredos.x86_64/discussions/129

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PXWMMIW2IJPSUVKAADW2HRWLANCNFSM6AAAAAAVOSGF7U. You are receiving this because you are subscribed to this thread.Message ID: @.***>

PartialVolume commented 1 year ago

@mdcato excellent, the version isn't important, however if you could let me know what version it is just for reference, it's really just the hex sense data I'm interested in that's spouted out by using the --verbose option, it will mostly be zeros except for the first line and a couple of non zero bytes at the end.

If you could post the whole output though including the real max sector info at the end.

Thanks 👍

mdcato commented 1 year ago

Using hdparm v9.65 on a Seagate ST10000NM0016 10TB drive:

/dev/sda: APT: No idVendor found -> not USB bridge device outgoing cdb: 85 08 0e 00 c2 00 01 00 00 00 00 00 00 40 b1 00 SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8 SG_IO: sb[]: 70 00 05 00 00 00 00 0a 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 incoming_data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: desc[]: 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ATA_16 stat=00 err=01 nsect=04 lbal=00 lbam=00 lbah=00 dev=00 DCO Checksum verified. DCO Revision: 0x0000 -- unknown, treating as 0002 The following features can be selectively disabled via DCO: Transfer modes:

  Real max sectors: 1
  ATA command/feature sets:

Since you mentioned 2TB was your largest, here’s a 4TB as well. Seagate ST4000NM0033

/dev/sda: APT: No idVendor found -> not USB bridge device outgoing cdb: 85 08 0e 00 c2 00 01 00 00 00 00 00 00 40 b1 00 SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8 SG_IO: sb[]: 70 00 05 00 00 00 00 0a 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 incoming_data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: desc[]: 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ATA_16 stat=00 err=01 nsect=04 lbal=00 lbam=00 lbah=00 dev=00 DCO Checksum verified. DCO Revision: 0x0000 -- unknown, treating as 0002 The following features can be selectively disabled via DCO: Transfer modes:

  Real max sectors: 1
  ATA command/feature sets:

Both of these had previously been nwipe’d, so no partitions.

Mike

From: PartialVolume @.> Sent: Friday, March 3, 2023 09:23 To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

@mdcatohttps://github.com/mdcato excellent, the version isn't important, however if you could let me know what version it is just for reference, it's really just the hex sense data I'm interested in that's spouted out by using the --verbose option, it will mostly be zeros except for the first line and a couple of non zero bytes at the end.

If you could post the whole output though including the real max sector info at the end.

Thanks 👍

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1453692253, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PXCPUCEZ4XDQVPYNMLW2IED5ANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.**@.>>

PartialVolume commented 1 year ago

Just checking but were both drives connected via SATA and not via USB?

Unfortunately that data hasn't provided the answer I was looking for, there is a couple of "SG_IO: bad/missing sense data" errors and the hex data doesn't contain anything other than zeros so hdparm is failing to get the data.

After the ninth byte after incoming data: I was expecting to see a hex value that represented the max sectors. The real max sectors is also reported a '1' should be about 19531250000 sectors for 10TB drive. In the sense data there should be a string much like 0x5039278c4

Here's an example of what it should look like, the highlighted hex value 0xaf88e0e8 which is 2000398933504 bytes (2.0TB)

outgoing cdb: 85 08 0e 00 c2 00 01 00 00 00 00 00 00 40 b1 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: 02 00 00 00 7f 00 af 88 e0 e8 00 00 00 00 88 00 15 00

The bad or missing sense data could be because of the interface being used or maybe these drives don't conform which I think is unlikely.

mdcato commented 1 year ago

PartialVolume,

First, the system I’m using has a Gigabyte Z370 Ultra Gaming 2.0 Rev 1 motherboard circa 2018 with an i5-8400 processor. (I also have a PCIe board with 5 more SATA ports, which is what gave me pause when you asked if I was using a USB---SATA adapter. But I confirmed I had the drives attached to the Intel SATA ports on the motherboard.) It is running Fedora Core 37 with all updates; Linux kernel 6.14.1.

I also tried Ubuntu 22.10 on a flash drive, and even though it had hdparm v9.60, instead of 9.65, I got the same results.

I even added a WD 20EZRX 2TB drive to the mix in case there was a difference in the way manufacturers responded to hdparm, or a difference between Enterprise & Consumer lines. Same/similar results.

So, I decided to move the three drives to the PCIe SATA controller. Same results.

At this point I’m perplexed. I may dig up an older computer to see if there are differences there.

Here’s the output running Ubuntu 22.10 with the Seagate ST10000NM0016 10TB on /dev/sda, Seagate ST4000NM0033 4TB on /dev/sdb, and WD 20EZRX 2TB on /dev/sdc:

@.:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:0 0 2.6G 1 loop /rofs loop1 7:1 0 4K 1 loop /snap/bare/5 loop2 7:2 0 63.2M 1 loop /snap/core20/1623 loop3 7:3 0 238.5M 1 loop /snap/firefox/1969 loop4 7:4 0 346.3M 1 loop /snap/gnome-3-38-2004/119 loop5 7:5 0 91.7M 1 loop /snap/gtk-common-themes/1535 loop6 7:6 0 45.9M 1 loop /snap/snap-store/599 loop7 7:7 0 284K 1 loop /snap/snapd-desktop-integration/14 loop8 7:8 0 48M 1 loop /snap/snapd/17336 sda 8:0 0 9.1T 0 disk sdb 8:16 0 3.6T 0 disk sdc 8:32 0 1.8T 0 disk sdd 8:48 1 59.8G 0 disk └─sdd1 8:49 1 59.8G 0 part /cdrom nvme1n1 259:0 0 232.9G 0 disk ├─nvme1n1p1 259:1 0 200M 0 part ├─nvme1n1p2 259:2 0 1G 0 part └─nvme1n1p3 259:3 0 231.7G 0 part ├─fedora_localhost--live-swap │ 253:0 0 7.8G 0 lvm ├─fedora_localhost--live-home │ 253:1 0 173.9G 0 lvm └─fedora_localhost--live-root 253:2 0 50G 0 lvm nvme0n1 259:4 0 232.9G 0 disk ├─nvme0n1p1 259:5 0 499M 0 part ├─nvme0n1p2 259:6 0 99M 0 part ├─nvme0n1p3 259:7 0 16M 0 part └─nvme0n1p4 259:8 0 232.3G 0 part @.:~# hdparm --verbose --dco-identify /dev/sda

/dev/sda: APT: No idVendor found -> not USB bridge device outgoing cdb: 85 08 0e 00 c2 00 01 00 00 00 00 00 00 40 b1 00 SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8 SG_IO: sb[]: 70 00 05 00 00 00 00 0a 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 incoming_data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: desc[]: 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ATA_16 stat=00 err=01 nsect=04 lbal=00 lbam=00 lbah=00 dev=00 DCO Checksum verified. DCO Revision: 0x0000 -- unknown, treating as 0002 The following features can be selectively disabled via DCO: Transfer modes:

  Real max sectors: 1
  ATA command/feature sets:

@.***:~# hdparm --verbose --dco-identify /dev/sdb

/dev/sdb: APT: No idVendor found -> not USB bridge device outgoing cdb: 85 08 0e 00 c2 00 01 00 00 00 00 00 00 40 b1 00 SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8 SG_IO: sb[]: 70 00 05 00 00 00 00 0a 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 incoming_data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: desc[]: 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ATA_16 stat=00 err=01 nsect=04 lbal=00 lbam=00 lbah=00 dev=00 DCO Checksum verified. DCO Revision: 0x0000 -- unknown, treating as 0002 The following features can be selectively disabled via DCO: Transfer modes:

  Real max sectors: 1
  ATA command/feature sets:

@.***:~# hdparm --verbose --dco-identify /dev/sdc

/dev/sdc: APT: No idVendor found -> not USB bridge device outgoing cdb: 85 08 0e 00 c2 00 01 00 00 00 00 00 00 40 b1 00 SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8 SG_IO: 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 incoming_data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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: 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: desc[]: 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ATA_16 stat=00 err=01 nsect=04 lbal=00 lbam=00 lbah=00 dev=00 DCO Checksum verified. DCO Revision: 0x0000 -- unknown, treating as 0002 The following features can be selectively disabled via DCO: Transfer modes:

  Real max sectors: 1
  ATA command/feature sets:

-- Mike

From: PartialVolume @.> Sent: Friday, March 3, 2023 13:37 To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

Just checking but were both drives connected via SATA and not via USB?

Unfortunately that data hasn't provided the answer I was looking for, there is a couple of "SG_IO: bad/missing sense data" errors and the hex data doesn't contain anything other than zeros so hdparm is failing to get the data.

After the ninth byte after incoming data: I was expecting to see a hex value that represented the max sectors. The real max sectors is also reported a '1' should be about 19531250000 sectors for 10TB drive. In the sense data there should be a string much like 0x5039278c4

Here's an example of what it should look like, the highlighted hex value 0xaf88e0e8 which is 2000398933504 bytes (2.0TB)

outgoing cdb: 85 08 0e 00 c2 00 01 00 00 00 00 00 00 40 b1 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: 02 00 00 00 7f 00 af 88 e0 e8 00 00 00 00 88 00 15 00

The bad or missing sense data could be because of the interface being used or maybe these drives don't conform which I think is unlikely.

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1454036181, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PWWMCRJUWVHGPH64YLW2JB5PANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.**@.>>

PartialVolume commented 1 year ago

Very odd, maybe something in the bios that's messing with access to the SATA bus?

What's the output of lspci, is there a clue as to the chipset being used for SATA?

Would be interesting to see whether this USB unitek USB to SATA adapter works where the motherboards SATA doesn't! This adapter works perfectly for me and uses the same SATA chip used in some laptops.

Below is the dco-identify output from hdparm v9.65 having parsed the sense data correctly and showing the correct real max sectors and no SG_IO: bad/missing sense data errors, on a 2TB Western Digital Green WDC WD20EURS-63SPKY0. Also works on a Dell Optiplex 9010.

sudo ./hdparm --verbose --dco-identify /dev/sd /dev/sda: APT: USB ID = 0x174c:0x55aa (0x100) APT: Unsupported device outgoing cdb: 85 08 0e 00 c2 00 01 00 00 00 00 00 00 40 b1 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: 02 00 00 00 7f 00 af 88 e0 e8 00 00 00 00 88 00 15 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 3e SG_IO: desc[]: 00 00 ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00 DCO Checksum verified. DCO Revision: 0x0002 The following features can be selectively disabled via DCO: Transfer modes: udma0 udma1 udma2 udma3 udma4 udma5 udma6 Real max sectors: 3907029168 ATA command/feature sets: security HPA SATA command/feature sets: NCQ interface_power_management SSP

PartialVolume commented 1 year ago

@mdcato Is this your bios?, anything in the SATA configuration that could be causing it?

Aggresive LPM if enabled, maybe the drive is in lower power state and hdparm isn't hanging around to see if it wakes up? but then on the second attempt it should work.

https://youtu.be/5PYroA_whjU?t=411

Screenshot_20230304_172602

PartialVolume commented 1 year ago

Decoding the sense response with the command sg_decode_sense 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

produces the response

Fixed format, current; Sense key: Illegal Request Additional sense: Unaligned write command

Exit code 5 : the device reports an "illegal request" with an additional sense code other than "invalid operation code". This is often a supported command with a field set requesting an unsupported capability. For commands that require a "service action" field (e.g. READ CAPACITY(16) ) this value can indicate that the command is not supported

So if that is decoded correctly it's saying the command being issued is an illegal request. Doesn't help much does seem to point to something blocking access much like you would get with a USB adapter that doesn't support the full ATA specification. I don't know whether it's the drive, controller or bios but like you say, try those discs on a different motherboard and if they work at least you know it's nothing to do with the discs.

mdcato commented 1 year ago

PartialVolume, I tried the 10TB on a USB adapter, Inateck FD2002, same results on 3 different systems. Then pulled out an old Dell Inspiron 3847 w/ i5-4460 and chipset 8/220 running the Ubuntu live USB. Same result. I’ve run out of things to try. Any suggestions?

Mike

From: PartialVolume @.> Sent: Saturday, March 4, 2023 13:48 To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

Decoding the sense response with the command sg_decode_sense 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

produces the response

Fixed format, current; Sense key: Illegal Request Additional sense: Unaligned write command

Exit code 5 : the device reports an "illegal request" with an additional sense code other than "invalid operation code". This is often a supported command with a field set requesting an unsupported capability. For commands that require a "service action" field (e.g. READ CAPACITY(16) ) this value can indicate that the command is not supported

So if that is decoded correctly it's saying the command being issued is an illegal request. Doesn't help much does seem to point to something blocking access much like you would get with a USB adapter that doesn't support the full ATA specification. I don't know whether it's the drive, controller or bios but like you say, try those discs on a different motherboard and if they work at least you know it's nothing to do with the discs.

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1454854937, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PWNXFVJMUDAQSPGXPTW2OL6RANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.**@.>>

PartialVolume commented 1 year ago

It's a puzzle, how about sudo hdparm -I /dev/sda. Just found a 3TB Western Digital. Do you get all this info when you just run the -I option

/dev/sda:

ATA device, with non-removable media
        Model Number:       WDC WD30EURX-63T0FY0                    
        Serial Number:      WD-XXXXXXXXXXXXXX
        Firmware Revision:  80.00A80
        Transport:          Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
        Supported: 9 8 7 6 5 
        Likely used: 9
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:  5860533168
        Logical  Sector size:                   512 bytes
        Physical Sector size:                  4096 bytes
        Logical Sector-0 offset:                  0 bytes
        device size with M = 1024*1024:     2861588 MBytes
        device size with M = 1000*1000:     3000592 MBytes (3000 GB)
        cache/buffer size  = unknown
        Nominal Media Rotation Rate: 5400
Capabilities:
        LBA, IORDY(can be disabled)
        Queue depth: 32
        Standby timer values: spec'd by Standard, with device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 0
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
             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
                Power-Up In Standby feature set
           *    SET_FEATURES required to spinup after power up
                SET_MAX security extension
           *    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
           *    URG for READ_STREAM[_DMA]_EXT
           *    URG for WRITE_STREAM[_DMA]_EXT
           *    IDLE_IMMEDIATE with UNLOAD
           *    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)
           *    Gen3 signaling speed (6.0Gb/s)
           *    Native Command Queueing (NCQ)
           *    Host-initiated interface power management
           *    Phy event counters
           *    Idle-Unload when NCQ is active
           *    NCQ priority information
           *    READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
                DMA Setup Auto-Activate optimization
                Device-initiated interface power management
           *    Software settings preservation
           *    SMART Command Transport (SCT) feature set
           *    SCT Write Same (AC2)
           *    SCT Features Control (AC4)
           *    SCT Data Tables (AC5)
                unknown 206[12] (vendor specific)
                unknown 206[13] (vendor specific)
                unknown 206[14] (vendor specific)
Security: 
        Master password revision code = 65534
                supported
        not     enabled
        not     locked
        not     frozen
        not     expired: security count
                supported: enhanced erase
        442min for SECURITY ERASE UNIT. 442min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50014ee25f01493d
        NAA             : 5
        IEEE OUI        : 0014ee
        Unique ID       : 25f01493d
Checksum: correct
mdcato commented 1 year ago

Yes.

@.*** ~]# hdparm -I /dev/sdb

/dev/sdb:

ATA device, with non-removable media Model Number: ST10000NM0016-1TT101 Serial Number: ZA20SSAR Firmware Revision: SNB0 Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0 Standards: Used: unknown (minor revision code 0x006d) Supported: 10 9 8 7 6 5 Likely used: 10 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: 19532873728
  Logical  Sector size:                   512 bytes
  Physical Sector size:                  4096 bytes
  Logical Sector-0 offset:                  0 bytes
  device size with M = 1024*1024:     9537536 MBytes
  device size with M = 1000*1000:    10000831 MBytes (10000 GB)
  cache/buffer size  = unknown
  Form Factor: 3.5 inch
  Nominal Media Rotation Rate: 7200

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 Recommended acoustic management value: 254, current value: 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 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:

From: PartialVolume @.> Sent: Saturday, March 4, 2023 19:28 To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

It's a puzzle, how about sudo hdparm -I /dev/sda. Just found a 3TB Western Digital. Do you get all this info when you just run the -I option

/dev/sda:

ATA device, with non-removable media

    Model Number:       WDC WD30EURX-63T0FY0

    Serial Number:      WD-XXXXXXXXXXXXXX

    Firmware Revision:  80.00A80

    Transport:          Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0

Standards:

    Supported: 9 8 7 6 5

    Likely used: 9

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:  5860533168

    Logical  Sector size:                   512 bytes

    Physical Sector size:                  4096 bytes

    Logical Sector-0 offset:                  0 bytes

    device size with M = 1024*1024:     2861588 MBytes

    device size with M = 1000*1000:     3000592 MBytes (3000 GB)

    cache/buffer size  = unknown

    Nominal Media Rotation Rate: 5400

Capabilities:

    LBA, IORDY(can be disabled)

    Queue depth: 32

    Standby timer values: spec'd by Standard, with device specific minimum

    R/W multiple sector transfer: Max = 16  Current = 0

    DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6

         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

            Power-Up In Standby feature set

       *    SET_FEATURES required to spinup after power up

            SET_MAX security extension

       *    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

       *    URG for READ_STREAM[_DMA]_EXT

       *    URG for WRITE_STREAM[_DMA]_EXT

       *    IDLE_IMMEDIATE with UNLOAD

       *    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)

       *    Gen3 signaling speed (6.0Gb/s)

       *    Native Command Queueing (NCQ)

       *    Host-initiated interface power management

       *    Phy event counters

       *    Idle-Unload when NCQ is active

       *    NCQ priority information

       *    READ_LOG_DMA_EXT equivalent to READ_LOG_EXT

            DMA Setup Auto-Activate optimization

            Device-initiated interface power management

       *    Software settings preservation

       *    SMART Command Transport (SCT) feature set

       *    SCT Write Same (AC2)

       *    SCT Features Control (AC4)

       *    SCT Data Tables (AC5)

            unknown 206[12] (vendor specific)

            unknown 206[13] (vendor specific)

            unknown 206[14] (vendor specific)

Security:

    Master password revision code = 65534

            supported

    not     enabled

    not     locked

    not     frozen

    not     expired: security count

            supported: enhanced erase

    442min for SECURITY ERASE UNIT. 442min for ENHANCED SECURITY ERASE UNIT.

Logical Unit WWN Device Identifier: 50014ee25f01493d

    NAA             : 5

    IEEE OUI        : 0014ee

    Unique ID       : 25f01493d

Checksum: correct

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1454950316, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PWBWNOIAFRXBDGWEYDW2PTZNANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.**@.>>

PartialVolume commented 1 year ago

One thing that I noticed was your drive is frozen. All my drives when I run this command are not frozen. I wonder if that's got something to do with it?

mdcato commented 1 year ago

Alas, no. Suspended system, unsuspended, did hdparm -I to verify not frozen, but hdparm –verbose –dco-identify returned the same results.

From: PartialVolume @.> Sent: Saturday, March 4, 2023 19:50 To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

One thing that I noticed was your drive is frozen. All my drives when I run this command are not frozen. I wonder if that's got something to do with it?

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1454955083, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PSNNJHFL6K2HTITCTLW2PWLNANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.**@.>>

PartialVolume commented 1 year ago

I just had a read of the Seagate ST10000NM0016 product manual. It makes no mention of the host protected area (HPA) or device configuration overlay (DCO). Presumably it's been dropped? The maximum logical addressable sector is available using the 0xEC command which is what hdparm uses to display it's output for the sudo hdparm --verbose -N /dev/sdx. Unless something else is going on here, that command should work and it should display the max addressable sectors or at least if it doesn't if the block of incoming data is there I can decode it from that.

So if you could run sudo hdparm --verbose -N /dev/sdx and post the output.

Here's a section from the Seagate manual, word 100-103 Screenshot_20230305_180653

PartialVolume commented 1 year ago

According to ATA_Command_Matrix the 0xB1 device configuration overlay was dropped in ACS-2, I think we are at ACS-5 now.

Screenshot_20230305_182103

PartialVolume commented 1 year ago

All useful information as I expected HPA/DCO to exist in all drives up to the present but apparently not. I can bear that in mind when figuring out how I work out whether a HPA exists or not. I tell you, it's a mine field ! :-)

PartialVolume commented 1 year ago

One thing I have realised about the existence of an HPA is if anybody is using hdparm and thinks that running hdparm -N /dev/sdx and it responds with the message "HPA is disabled" and that means there is no hidden area then they are being misled as the statement "HPA is disabled" may be completely inaccurate. Screenshot_20230305_192816

By using the dco-setmax command to reduce the apparent size of the disc by say 512 bytes, it changes both the 1st and 2nd max sector sizes as displayed by sudo hdparm -N /dev/sdx and because both values match hdparm responds with HPA disabled. Yet I just created a hidden block where I stored some data, then hid it then showed it. So you cannot trust the message HPA disabled!, you have to reference the real max sectors value with the command sudo hdparm --dco-identify /dev/sdx and unless all three values match then there is a hidden area at the end of the disc.

Makes me wonder how many people get confused by that message 'HPA is disabled', without referencing the real max sectors.

mdcato commented 1 year ago

This may be superfluous info, but since you mentioned the -N options, thought I’d capture the hdparm output on the 10TB, 4TB and 1TB drives I have, in case I don’t have them in the future. sda: Seagate ST4000NM0033 4TB sdb: Seagate ST10000NM0016 10TB sdc: Seagate ST1000DM003 1TB

/dev/sda: APT: No idVendor found -> not USB bridge device 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: 5a 0c ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00 00 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20 31 5a 37 5a 56 4e 37 46 00 00 00 00 00 00 4e 53 34 30 20 20 20 20 54 53 30 34 30 30 4d 4e 30 30 33 33 39 2d 4d 5a 37 31 20 30 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 00 40 00 02 00 02 07 00 ff 3f 10 00 3f 00 10 fc fb 00 10 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 8d 06 00 cc 00 44 00 f0 03 00 00 6b 34 01 75 63 61 69 34 01 b4 63 61 7f 40 e8 00 e8 00 00 00 fe ff 00 00 00 fe 00 00 00 00 00 00 00 00 00 00 b0 be c0 d1 01 00 00 00 00 00 00 00 00 40 00 00 00 50 00 c5 6b 7a 41 9c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 de 40 dc 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 29 00 b0 be c0 d1 b0 be c0 d1 20 20 02 00 40 01 08 01 00 50 06 3c 0a 3c 00 00 3c 00 00 00 08 00 00 00 00 00 ff 7d 80 02 00 00 70 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 8d 00 00 63 48 88 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 bd 50 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 1c 00 00 00 00 00 00 00 00 20 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 00 00 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 e4 SG_IO: desc[]: 00 00 ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00 oflags.bits.lob_all=0xc0, flags={ dev command } oflags.bits.hob_all=0x00, flags={ } using LBA48 taskfile outgoing cdb: 85 07 20 00 00 00 00 00 00 00 00 00 00 40 27 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 01 00 00 00 d1 af 01 be 00 c0 40 50 00 00 00 00 00 00 00 00 00 00 SG_IO: desc[]: 09 0c 01 00 00 00 d1 af 01 be 00 c0 40 50 ATA_16 stat=50 err=00 nsect=00 lbal=af lbam=be lbah=c0 dev=40 READ_NATIVE_MAX_ADDRESS_EXT response: hob={00 01 d1} lob={c0 be af} max sectors = 7814037168/7814037168, HPA is disabled @.*** ~]# hdparm --verbose -N /dev/sdb

/dev/sdb: APT: No idVendor found -> not USB bridge device 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: 5a 0c ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00 00 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20 41 5a 30 32 53 53 52 41 00 00 00 00 00 00 4e 53 30 42 20 20 20 20 54 53 30 31 30 30 4e 30 30 4d 31 30 2d 36 54 31 31 54 31 30 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 00 40 00 02 00 02 07 00 ff 3f 10 00 3f 00 10 fc fb 00 10 5d ff ff ff 0f 00 00 07 00 03 00 78 00 78 00 78 00 78 00 08 00 00 00 00 00 00 00 00 00 00 00 1f 00 0e 8d 46 00 cc 08 44 00 f0 07 6d 00 6b 30 61 75 73 61 69 30 41 b4 73 61 7f 40 af 81 af 81 00 00 fe ff 00 00 00 fe 00 10 00 00 00 00 10 27 00 00 00 00 40 8c 04 00 00 00 00 00 00 00 03 60 00 00 00 50 00 c5 88 93 5f 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 de 41 dc 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 29 00 00 00 40 8c 00 00 40 8c 20 20 02 00 40 01 00 01 00 50 06 3c 0a 3c 00 00 3c 00 00 00 08 00 00 00 00 00 ff fd 80 02 00 00 70 01 08 00 00 00 00 00 33 0c 00 00 00 80 00 00 a5 01 00 97 68 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 bd 50 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 1c 00 00 00 00 00 00 00 00 7f 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 8c 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 a5 d9 SG_IO: desc[]: 00 00 ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00 oflags.bits.lob_all=0x82, flags={ feat command } oflags.bits.hob_all=0x00, flags={ } using LBA48 taskfile outgoing cdb: 85 07 20 00 00 00 00 00 00 00 00 00 00 40 78 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 01 00 00 00 8c ff 04 ff 00 3f 40 50 00 00 00 00 00 00 00 00 00 00 SG_IO: desc[]: 09 0c 01 00 00 00 8c ff 04 ff 00 3f 40 50 ATA_16 stat=50 err=00 nsect=00 lbal=ff lbam=ff lbah=3f dev=40 GET_NATIVE_MAX_ADDRESS_EXT response: hob={00 04 8c} lob={3f ff ff} max sectors = 19532873728/19532873728, ACCESSIBLE MAX ADDRESS disabled @.*** ~]# hdparm --verbose -N /dev/sdc

/dev/sdc: APT: No idVendor found -> not USB bridge device 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: 5a 04 ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00 00 00 00 00 20 20 20 20 20 20 20 20 20 20 37 20 4f 35 4d 4b 33 4b 53 58 03 00 c8 b8 38 00 53 4d 4f 32 37 41 30 53 4f 54 48 53 42 49 20 41 54 44 31 30 43 41 31 41 30 30 20 20 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 00 40 00 02 00 02 07 00 ff 3f 10 00 3f 00 10 fc fb 00 10 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 17 06 00 5e 00 44 00 fc 01 29 00 6b 74 69 7d 73 47 69 74 41 bc 63 47 7f 40 4e 00 4f 00 00 00 fe ff 00 00 00 00 08 00 ca 00 f9 00 10 27 00 00 b0 6d 70 74 00 00 00 00 ca 00 00 00 03 60 87 5a 00 50 9f 03 d6 e1 35 1b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9c 40 9c 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 29 00 0b 00 00 00 00 00 80 21 f1 0d 20 fa 01 00 00 40 04 28 21 01 00 00 00 00 08 06 09 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 05 00 44 32 37 42 00 00 02 68 00 00 bd 5d c8 7b 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 45 44 4c 4c 74 28 29 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 3d 00 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 1c 00 00 00 00 00 00 00 00 3f 10 21 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 e0 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 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 38 SG_IO: desc[]: 00 00 ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00 oflags.bits.lob_all=0xc0, flags={ dev command } oflags.bits.hob_all=0x00, flags={ } using LBA48 taskfile outgoing cdb: 85 07 20 00 00 00 00 00 00 00 00 00 00 40 27 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 01 00 00 00 74 af 00 6d 00 70 44 50 00 00 00 00 00 00 00 00 00 00 SG_IO: desc[]: 09 0c 01 00 00 00 74 af 00 6d 00 70 44 50 ATA_16 stat=50 err=00 nsect=00 lbal=af lbam=6d lbah=70 dev=44 READ_NATIVE_MAX_ADDRESS_EXT response: hob={00 00 74} lob={70 6d af} max sectors = 1953525168/1953525168, HPA is disabled

From: PartialVolume @.> Sent: Sunday, March 5, 2023 13:40 To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

One thing I have realised about the existence of an HPA is if anybody is using hdparm and thinks that running hdparm -N /dev/sdx and it responds with the message "HPA is disabled", that may be completely inaccurate. [Screenshot_20230305_192816]https://user-images.githubusercontent.com/22084881/222981578-5f2babca-74f6-4395-b166-2f594ca88923.png

By using the dco-setmax command to reduce the apparent size of the disc by say 512 bytes, it changes both the 1st and 2nd max sector sizes as displayed by sudo hdparm -N /dev/sdx and because both values match hdparm responds with HPA disabled. Yet I just created a hidden block where I stored some data, then hid it then showed it. So you cannot trust the message HPA disabled!, you have to reference the real max sectors value with the command sudo hdparm --dco-identify /dev/sdx and unless all three values match then there is a hidden area at the end of the disc.

Makes me wonder how many people get confused by that message 'HPA is disabled', without referencing the real max sectors.

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1455183958, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PQOCJU4RSQB5KDG4P3W2TTZ5ANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.**@.>>

PartialVolume commented 1 year ago

Thanks, that's useful. The message output by the 10TB drive, I've not come across before.

max sectors = 19532873728/19532873728, ACCESSIBLE MAX ADDRESS disabled

I'm surprised the 1TB doesn't work with --dco-identify but then maybe it's less than 4 or 5 years old?

mdcato commented 1 year ago

The 1TB’s date of manufacture is 26-Apr-2019

From: PartialVolume @.> Sent: Monday, March 6, 2023 06:22 To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

Thanks, that's useful. The message output by the 10TB drive, I've not come across before.

max sectors = 19532873728/19532873728, ACCESSIBLE MAX ADDRESS disabled

I'm surprised the 1TB doesn't work with --dco-identify but then maybe it's less than 4 or 5 years old?

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1456037758, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PSJW4OUOFMJMLNAMZLW2XJHDANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.**@.>>

PartialVolume commented 1 year ago

@mdcato I'm getting very close to completing the two page PDF report that nwipe generates. I've tested on the drives I have which are all old and all support HPA/DCO. However I need to see how nwipe works with one of your drives that don't have HPA/DCO.

I don't know whether you have time for this but if you do, any chance you could download the latest master and compile it, then run it on say your 2TB to start with. The one that didn't work with the hdparm --dco-identify command.

What I'm interested in are two things to start with.

Start nwipe with the -q option if you want to anonymize the data.

At the end of each wipe a PDF report will be generated.

Can you post the PDF report and also the first few lines of the nwipe log that's displayed in the terminal, basically the drive enumeration detail as shown below:

[2023/03/11 22:38:23]    info: nwipe 0.34.5 Development code, not for production use!
[2023/03/11 22:38:23]    info: Linux version 5.19.0-32-generic (buildd@lcy02-am
                               d64-026) (x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1
                               ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for
                                Ubuntu) 2.38) #33~22.04.1-Ubuntu SMP PREEMPT_D
                               YNAMIC Mon Jan 30 17:03:34 UTC 2
[2023/03/11 22:38:23]  notice: Found /dev/sdb,  USB, ST350031 2CS, 512 KB, S/N=XXXXXXXXXXXXXXX
[2023/03/11 22:38:23]    info: HPA values 1000 / 976773168 on /dev/sdb
[2023/03/11 22:38:23]    info: hdparm:DCO Real max sectors reported as 976773168 on /dev/sdb
[2023/03/11 22:38:23]    info: NWipe: DCO Real max sectors reported as 976773168 on /dev/sdb
[2023/03/11 22:38:23] warning: HIDDEN AREA DETECTED! on /dev/sdb
[2023/03/11 22:38:23]    info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 976773168
[2023/03/11 22:38:23]    info:  
[2023/03/11 22:38:23]    info: bios-version = 1.07.02TNO

If it works as it's supposed to, bearing in mind this is the first test on a non HPA/DCO device, you should see a sea of green text and a green tick icon in the top right corner with no red text, unlike the PDF below where I created an enormous hidden area and only wiped the visible part of the disc.

Much appreciated.

PDF nwipe_report_2023-03-11-22-38-43_Model_ST350031_2CS_Serial_XXXXXXXXXXXXXXX.pdf

Screenshot_20230311_231026

Screenshot_20230311_224351

mdcato commented 1 year ago

Will do. I'll use the 10TB 4TB 2TB and 1TB drives that I have. Considering the size (and thus the amount of time) is it OK just to do a zero, or better to use the default wipe for your purposes?

(Sent from mobile)

From: PartialVolume @.> Sent: Saturday, March 11, 2023 5:14:58 PM To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

@mdcatohttps://github.com/mdcato I'm getting very close to completing the two page PDF report that nwipe generates. I've tested on the drives I have which are all old and all support HPA/DCO. However I need to see how nwipe works with one of your drives that don't have HPA/DCO.

I don't know whether you have time for this but if you do, any chance you could download the latest master and compile it, then run it on say your 2TB to start with. The one that didn't work with the hdparm --dco-identify command.

What I'm interested in are two things to start with.

Start nwipe with the -q option if you want to anonymize the data.

At the end of each wipe a PDF report will be generated.

Can you post the PDF report and also the first few line of the nwipe log that's displayed in the terminal, basically the drive enumeration detail as shown below:

[2023/03/11 22:38:23] info: nwipe 0.34.5 Development code, not for production use! [2023/03/11 22:38:23] info: Linux version 5.19.0-32-generic @.*** d64-026) (x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1 ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #33~22.04.1-Ubuntu SMP PREEMPT_D YNAMIC Mon Jan 30 17:03:34 UTC 2 [2023/03/11 22:38:23] notice: Found /dev/sdb, USB, ST350031 2CS, 512 KB, S/N=XXXXXXXXXXXXXXX [2023/03/11 22:38:23] info: HPA values 1000 / 976773168 on /dev/sdb [2023/03/11 22:38:23] info: hdparm:DCO Real max sectors reported as 976773168 on /dev/sdb [2023/03/11 22:38:23] info: NWipe: DCO Real max sectors reported as 976773168 on /dev/sdb [2023/03/11 22:38:23] warning: HIDDEN AREA DETECTED! on /dev/sdb [2023/03/11 22:38:23] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 976773168 [2023/03/11 22:38:23] info: [2023/03/11 22:38:23] info: bios-version = 1.07.02TNO

If it works as it's supposed to, bearing in mind this is the first test on a non HPA/DCO device, you should see a sea of green text and a green tick icon in the top right corner with no red text, unlike the PDF below where I created an enormous hidden area and only wiped the visible part of the disc.

Much appreciated.

PDF nwipe_report_2023-03-11-22-38-43_Model_ST350031_2CS_Serial_XXXXXXXXXXXXXXX.pdfhttps://github.com/martijnvanbrummelen/nwipe/files/10949664/nwipe_report_2023-03-11-22-38-43_Model_ST350031_2CS_Serial_XXXXXXXXXXXXXXX.pdf

[Screenshot_20230311_231026]https://user-images.githubusercontent.com/22084881/224515478-8f572976-07f9-46a4-bfbe-68fedf3a373c.png

[Screenshot_20230311_224351]https://user-images.githubusercontent.com/22084881/224515433-394d06c9-7a81-4548-bb6b-a4a4dac39dca.png

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1465047218, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PX7KL6RIVLH742WWS3W3UBPFANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.***>

PartialVolume commented 1 year ago

Zero will be fine, I wouldn't worry about verification unless you really want to.

Also can you check the GUI it should be showing this, alternating with the drive model/serial no.

Screenshot_20230311_232311

mdcato commented 1 year ago

PartialVolume, Attached are the log, 3 PDF erasure reports, and some screenshots running nwipe 0.34.5 on 1TB, 4TB and 10TB Seagate drives. The 1TB drive is a retail drive, the 4TB & 10TB are “Enterprise” series. Things I noticed on the PDF reports is that the “Size(Apparent)” seems correct, the “Size(Real) showed 512B, however in the Disk Erasure Details the “Bytes Erased” matches the Apparent size and what the wiping actually performed. Also in the Disk Erasure Details, in Bytes Erased in parentheses is a large percentage, and the HPA/DCO Size is a negative (large) value. In the log, nwipe complained about the 10TB drive of HIDDEN AREA INDETERMINATE and asks if using a USB bridge or memory stick; all drive were attached to SATA-III ports on the mainboard. Another potential anomaly on the GUI is the two Enterprise drives’ temperature is always red and flashing. They do run hot, both 50C at the end of the wipe, but Seagate manual says operating temperature is 5—60C. Also attached are 4 screenshots, start, start w/HPA/DOC, 1 hour status, and end (17 hours).

Mike

From: PartialVolume @.> Sent: Saturday, March 11, 2023 17:29 To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

Zero will be fine, I wouldn't worry about verification unless you really want to.

Also can you check the GUI it should be showing this, alternating with the drive model/serial no.

[Screenshot_20230311_232311]https://user-images.githubusercontent.com/22084881/224516079-09f173cc-27af-4928-8560-85be14825aae.png

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1465049136, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PREJX42ZDKHCASKIS3W3UDDBANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.**@.>>

PartialVolume commented 1 year ago

@mdcato not sure what happened there, there's no screenshots or files, either in the GitHub pages or the email.

mdcato commented 1 year ago

Ok, email attachments must "confuse" the system. I'll try pasting them in instead.

(Sent from mobile)

From: PartialVolume @.> Sent: Sunday, March 12, 2023 4:53:55 PM To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

@mdcatohttps://github.com/mdcato not sure what happened there, there's no screenshots or files, either in the GitHub pages or the email.

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1465309473, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PUR4AOFIJNWBFVCQGLW3ZAXHANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.***>

mdcato commented 1 year ago

PartialVolume, OK, second try at using email - such a new-fangled technology, you have to excuse Github for getting confused by attachments. Repeating what I said earlier to keep everything together: [...] running nwipe 0.34.5 on 1TB, 4TB and 10TB Seagate drives. The 1TB drive is a retail drive, the 4TB & 10TB are "Enterprise" series. Things I noticed on the PDF reports is that the "Size(Apparent)" seems correct, the "Size(Real) showed 512B, however in the Disk Erasure Details the "Bytes Erased" matches the Apparent size and what the wiping actually performed. Also in the Disk Erasure Details, in Bytes Erased in parentheses is a large percentage, and the HPA/DCO Size is a negative (large) value. In the log, nwipe complained about the 10TB drive of HIDDEN AREA INDETERMINATE and asks if using a USB bridge or memory stick; all drive were attached to SATA-III ports on the mainboard. Another potential anomaly on the GUI is the two Enterprise drives' temperature is always red and flashing. They do run hot, both 50C at the end of the wipe, but Seagate manual says operating temperature is 5-60C.

Here's the log: [2023/03/11 18:40:39] notice: Found /dev/sda, ATA, ST1000DM003-1SB1, 1 TB, S/N=ZN15TA6Y [2023/03/11 18:40:39] info: HPA values 1953525168 / 1953525168 on /dev/sda [2023/03/11 18:40:39] info: hdparm:DCO Real max sectors reported as 1 on /dev/sda [2023/03/11 18:40:39] info: NWipe: DCO Real max sectors reported as 1 on /dev/sda [2023/03/11 18:40:39] warning: HIDDEN AREA DETECTED! on /dev/sda [2023/03/11 18:40:39] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 0 [2023/03/11 18:40:39] info: [2023/03/11 18:40:39] notice: Found /dev/sdb, ATA, ST10000NM0016-1T, 10 TB, S/N=ZA20SSAR [2023/03/11 18:40:39] warning: [UNKNOWN] We can't find the HPA line, has hdparm ouput changed? /dev/sdb [2023/03/11 18:40:39] info: hdparm:DCO Real max sectors reported as 1 on /dev/sdb [2023/03/11 18:40:39] info: NWipe: DCO Real max sectors reported as 1 on /dev/sdb [2023/03/11 18:40:39] warning: HIDDEN AREA INDETERMINATE! on /dev/sdb, are you using a USB bridge or memory stick? [2023/03/11 18:40:39] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 0 [2023/03/11 18:40:39] info: [2023/03/11 18:40:39] notice: Found /dev/sdc, ATA, ST4000NM0033-9ZM, 4 TB, S/N=Z1Z7NVF7 [2023/03/11 18:40:39] info: HPA values 7814037168 / 7814037168 on /dev/sdc [2023/03/11 18:40:39] info: hdparm:DCO Real max sectors reported as 1 on /dev/sdc [2023/03/11 18:40:39] info: NWipe: DCO Real max sectors reported as 1 on /dev/sdc [2023/03/11 18:40:39] warning: HIDDEN AREA DETECTED! on /dev/sdc [2023/03/11 18:40:39] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 0 [2023/03/11 18:40:39] info: [2023/03/11 18:40:40] notice: Found /dev/nvme0n1, NVME, Samsung SSD 970 EVO 250GB, 250 GB, S/N=S465NB0K580541L [2023/03/11 18:40:40] info: [2023/03/11 18:40:40] notice: Found /dev/nvme1n1, NVME, Samsung SSD 970 EVO 250GB, 250 GB, S/N=S465NB0K580543E [2023/03/11 18:40:40] info: [2023/03/11 18:40:40] info: Automatically enumerated 5 devices. [2023/03/11 18:40:40] info: bios-version = F15b [2023/03/11 18:40:40] info: bios-release-date = 03/23/2021 [2023/03/11 18:40:40] info: system-manufacturer = Gigabyte Technology Co., Ltd. [2023/03/11 18:40:40] info: system-product-name = Z370 AORUS ULTRA GAMING 2.0 [2023/03/11 18:40:40] info: system-version = Default string [2023/03/11 18:40:40] info: system-serial-number = Default string [2023/03/11 18:40:40] info: system-uuid = 03d502e0-045e-0583-4206-af0700080009 [2023/03/11 18:40:40] info: baseboard-manufacturer = Gigabyte Technology Co., Ltd. [2023/03/11 18:40:40] info: baseboard-product-name = Z370 AORUS ULTRA GAMING 2.0-CF [2023/03/11 18:40:40] info: baseboard-version = x.x [2023/03/11 18:40:40] info: baseboard-serial-number = Default string [2023/03/11 18:40:40] info: baseboard-asset-tag = Default string [2023/03/11 18:40:40] info: chassis-manufacturer = Default string [2023/03/11 18:40:40] info: chassis-type = Desktop [2023/03/11 18:40:40] info: chassis-version = Default string [2023/03/11 18:40:40] info: chassis-serial-number = Default string [2023/03/11 18:40:40] info: chassis-asset-tag = Default string [2023/03/11 18:40:40] info: processor-family = Core i5 [2023/03/11 18:40:40] info: processor-manufacturer = Intel(R) Corporation [2023/03/11 18:40:40] info: processor-version = Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz [2023/03/11 18:40:40] info: processor-frequency = 3800 MHz [2023/03/11 18:40:40] notice: Opened entropy source '/dev/urandom'. [2023/03/11 18:40:40] notice: hwmon: Module drivetemp loaded, drive temperatures available [2023/03/11 18:40:40] notice: hwmon: sda has temperature monitoring [2023/03/11 18:40:40] notice: hwmon: sdb has temperature monitoring [2023/03/11 18:40:40] notice: hwmon: sdc has temperature monitoring [2023/03/11 18:40:40] notice: hwmon: nvme0n1 has temperature monitoring [2023/03/11 18:40:40] notice: hwmon: nvme1n1 has temperature monitoring [2023/03/11 18:41:32] notice: Program options are set as follows... [2023/03/11 18:41:32] notice: autonuke = 0 (off) [2023/03/11 18:41:32] notice: autopoweroff = 0 (off) [2023/03/11 18:41:32] notice: do not perform a final blank pass [2023/03/11 18:41:32] notice: banner = nwipe 0.34.5 Development code, not for production use! [2023/03/11 18:41:32] notice: prng = Isaac64 [2023/03/11 18:41:32] notice: method = Fill With Zeros [2023/03/11 18:41:32] notice: quiet = 0 [2023/03/11 18:41:32] notice: rounds = 1 [2023/03/11 18:41:32] notice: sync = 100000 [2023/03/11 18:41:32] notice: verify = 0 (off) [2023/03/11 18:41:32] notice: /dev/sda has serial number ZN15TA6Y [2023/03/11 18:41:32] notice: /dev/sda, sect/blk/dev 512/4096/1000204886016 [2023/03/11 18:41:32] notice: /dev/sdb has serial number ZA20SSAR [2023/03/11 18:41:32] notice: /dev/sdb, sect/blk/dev 512/4096/10000831348736 [2023/03/11 18:41:32] notice: Invoking method 'Fill With Zeros' on /dev/sda [2023/03/11 18:41:32] notice: /dev/sdc has serial number Z1Z7NVF7 [2023/03/11 18:41:32] notice: /dev/sdc, sect/blk/dev 512/4096/4000787030016 [2023/03/11 18:41:32] notice: Starting round 1 of 1 on /dev/sda [2023/03/11 18:41:32] notice: Starting pass 1/1, round 1/1, on /dev/sda [2023/03/11 18:41:32] notice: Invoking method 'Fill With Zeros' on /dev/sdb [2023/03/11 18:41:32] notice: Starting round 1 of 1 on /dev/sdb [2023/03/11 18:41:32] notice: Starting pass 1/1, round 1/1, on /dev/sdb [2023/03/11 18:41:32] notice: Invoking method 'Fill With Zeros' on /dev/sdc [2023/03/11 18:41:32] notice: Starting round 1 of 1 on /dev/sdc [2023/03/11 18:41:32] notice: Starting pass 1/1, round 1/1, on /dev/sdc [2023/03/11 20:40:30] notice: 1000204886016 bytes written to /dev/sda [2023/03/11 20:40:30] notice: Finished pass 1/1, round 1/1, on /dev/sda [2023/03/11 20:40:30] notice: Finished final round 1 of 1 on /dev/sda [2023/03/12 04:44:09] notice: 4000787030016 bytes written to /dev/sdc [2023/03/12 04:44:09] notice: Finished pass 1/1, round 1/1, on /dev/sdc [2023/03/12 04:44:09] notice: Finished final round 1 of 1 on /dev/sdc [2023/03/12 12:44:30] notice: 10000831348736 bytes written to /dev/sdb [2023/03/12 12:44:30] notice: Finished pass 1/1, round 1/1, on /dev/sdb [2023/03/12 12:44:30] notice: Finished final round 1 of 1 on /dev/sdb

**** Error Summary ***** ! Device | Pass Errors | Verifications Errors | Fdatasync I\O Errors

   sda |           0 |                    0 |                    0
   sdb |           0 |                    0 |                    0
   sdc |           0 |                    0 |                    0

Drive Status ! Device | Status | Thru-put | HH:MM:SS | Model/Serial Number

   sda | Erased | 140 MB/s | 01:58:58 | ST1000DM003-1SB1/ZN15TA6Y
   sdb | Erased | 162 MB/s | 17:02:58 | ST10000NM0016-1T/ZA20SSAR
   sdc | Erased | 122 MB/s | 09:02:37 | ST4000NM0033-9ZM/Z1Z7NVF7

[2023/03/12 12:45:16] Total Throughput 425 MB/s, Fill With Zeros, 1R+NB+NV

[2023/03/12 12:45:16] info: Nwipe successfully completed. See summary table for details.

The 1TB erasure report: @.***

@.***

The 4TB erasure report: @.***

@.***

The 10TB erasure report: @.***

@.***

Screenshot before wiping, for settings; note no temperature info on the Enterprise-class drives: @.***

Screenshot before wiping w/HPA/DCO info: @.***

Screenshot at 1 hour: @.***

Screenshot at end: @.***

-- Mike

From: Mike Cato / Hays Technical Services @.> Sent: Sunday, March 12, 2023 16:56 To: martijnvanbrummelen/nwipe @.>; martijnvanbrummelen/nwipe @.> Cc: Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

Ok, email attachments must "confuse" the system. I'll try pasting them in instead.

(Sent from mobile)

From: PartialVolume @.**@.>> Sent: Sunday, March 12, 2023 4:53:55 PM To: martijnvanbrummelen/nwipe @.**@.>> Cc: Mike Cato / Hays Technical Services @.**@.>>; Mention @.**@.>> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

@mdcatohttps://github.com/mdcato not sure what happened there, there's no screenshots or files, either in the GitHub pages or the email.

- Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1465309473, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PUR4AOFIJNWBFVCQGLW3ZAXHANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.**@.>>

PartialVolume commented 1 year ago

PDF and snapshots still not coming through. The log has given me enough info to know what I need to change. I'll make the changes over the next few days and let you know when it's ready for testing again. Thanks for helping out with this. Saves me having to buy a 10TB drive !

PartialVolume commented 1 year ago

@mdcato

Another potential anomaly on the GUI is the two Enterprise drives' temperature is always red and flashing. They do run hot, both 50C at the end of the wipe, but Seagate manual says operating temperature is 5-60C.

I've committed some code to the master that logs the four temperatures that are obtained from the drive via the hwmon module. See PR for details

If you download and compile this and run nwipe, no need to start any wipes or select any drives, just immediately CNTRL C to abort and you'll see at the bottom of the log the high critical, highest, lowest and low critical temperatures. I have discovered one anomaly with the code. Basically to do with what I thought highest and lowest meant.

I'm sure I read in the HWMON docs that highest and lowest were the continuous running temperatures, but that's not what they are on this Seagate ST3500312CS. They change value and as they actually say are the highest temperature reached by the drive and the lowest. That means highest may start of at room temperature and then may exceed critical, but as the drive temperature drops highest stays at the highest temperature it reached. I think it's probably reset after a power cycle.

However what this could mean is that your drives, even a few seconds, reached critical, i.e 65 deg.C then so would highest and it would stay there. If the drive then cooled down, the red flashing temperature might change to solid red but it would never drop to white on blue text, it would stay at red on blue even if the drive temperature dropped to 20 deg.C

Does that behaviour ring any bells. It's easy enough to fix, I just ignore the highest and lowest values and just make the temperature flash when it reaches critical high or low.

Would be nice to see what your drives say their critical temperature limits are reported as in the nwipe log and if that matches the 65 deg.C specified in the data sheet.

PartialVolume commented 1 year ago

Just made the changes to the code, just uploading it now 0.34.6.

I've done away with the flashing red and just have non flashing text.

So if the drive temperature exceeds the high critical temperature the temperature in the GUI will change to red text on blue background.

If the drive temperature drops below the low critical value (if it exists) then the temperature changes to black text on blue background.

If the drive reports no critical temperatures, the temperature text defaults to white text on blue.

PartialVolume commented 1 year ago

BTW, If you run those wipes again and you get the red temperature or even if you don't, when the wipe completes and you exit if you scroll back you'll be able to see the absolute max temperature the drive reached during the wipe by looking at that Highest=xxxxx value.

info: Temperature limits for /dev/nvme0n1, critical=84c, highest=N/A, lowest=N/A, low critical=N/A.

mdcato commented 1 year ago

The log is below. GUI changes are as you described. It looks like the Seagate Enterprise drives have critical temp set to 0c rather than n/a; suggest equating to n/a if 0.

[2023/03/14 17:38:23] notice: Found /dev/sda, ATA, ST1000DM003-1SB1, 1 TB, S/N=ZN15TA6Y [2023/03/14 17:38:23] info: HPA values 1953525168 / 1953525168 on /dev/sda [2023/03/14 17:38:23] info: hdparm:DCO Real max sectors reported as 1 on /dev/sda [2023/03/14 17:38:23] info: NWipe: DCO Real max sectors reported as 1 on /dev/sda [2023/03/14 17:38:23] warning: HIDDEN AREA DETECTED! on /dev/sda [2023/03/14 17:38:23] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 0 [2023/03/14 17:38:23] info: [2023/03/14 17:38:23] notice: Found /dev/sdb, ATA, ST10000NM0016-1T, 10 TB, S/N=ZA20SSAR [2023/03/14 17:38:23] warning: [UNKNOWN] We can't find the HPA line, has hdparm ouput changed? /dev/sdb [2023/03/14 17:38:23] info: hdparm:DCO Real max sectors reported as 1 on /dev/sdb [2023/03/14 17:38:23] info: NWipe: DCO Real max sectors reported as 1 on /dev/sdb [2023/03/14 17:38:23] warning: HIDDEN AREA INDETERMINATE! on /dev/sdb, are you using a USB bridge or memory stick? [2023/03/14 17:38:23] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 0 [2023/03/14 17:38:23] info: [2023/03/14 17:38:23] notice: Found /dev/sdc, ATA, ST4000NM0033-9ZM, 4 TB, S/N=Z1Z7NVF7 [2023/03/14 17:38:23] info: HPA values 7814037168 / 7814037168 on /dev/sdc [2023/03/14 17:38:23] info: hdparm:DCO Real max sectors reported as 1 on /dev/sdc [2023/03/14 17:38:23] info: NWipe: DCO Real max sectors reported as 1 on /dev/sdc [2023/03/14 17:38:23] warning: HIDDEN AREA DETECTED! on /dev/sdc [2023/03/14 17:38:23] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 0 [2023/03/14 17:38:23] info: [2023/03/14 17:38:23] notice: Found /dev/nvme0n1, NVME, Samsung SSD 970 EVO 250GB, 250 GB, S/N=S465NB0K580541L [2023/03/14 17:38:23] info: [2023/03/14 17:38:23] notice: Found /dev/nvme1n1, NVME, Samsung SSD 970 EVO 250GB, 250 GB, S/N=S465NB0K580543E [2023/03/14 17:38:23] info: [2023/03/14 17:38:23] info: Automatically enumerated 5 devices. [2023/03/14 17:38:23] info: bios-version = F15b [2023/03/14 17:38:23] info: bios-release-date = 03/23/2021 [2023/03/14 17:38:23] info: system-manufacturer = Gigabyte Technology Co., Ltd. [2023/03/14 17:38:23] info: system-product-name = Z370 AORUS ULTRA GAMING 2.0 [2023/03/14 17:38:23] info: system-version = Default string [2023/03/14 17:38:23] info: system-serial-number = Default string [2023/03/14 17:38:23] info: system-uuid = 03d502e0-045e-0583-4206-af0700080009 [2023/03/14 17:38:23] info: baseboard-manufacturer = Gigabyte Technology Co., Ltd. [2023/03/14 17:38:23] info: baseboard-product-name = Z370 AORUS ULTRA GAMING 2.0-CF [2023/03/14 17:38:23] info: baseboard-version = x.x [2023/03/14 17:38:23] info: baseboard-serial-number = Default string [2023/03/14 17:38:23] info: baseboard-asset-tag = Default string [2023/03/14 17:38:23] info: chassis-manufacturer = Default string [2023/03/14 17:38:23] info: chassis-type = Desktop [2023/03/14 17:38:23] info: chassis-version = Default string [2023/03/14 17:38:23] info: chassis-serial-number = Default string [2023/03/14 17:38:23] info: chassis-asset-tag = Default string [2023/03/14 17:38:23] info: processor-family = Core i5 [2023/03/14 17:38:23] info: processor-manufacturer = Intel(R) Corporation [2023/03/14 17:38:23] info: processor-version = Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz [2023/03/14 17:38:23] info: processor-frequency = 3800 MHz [2023/03/14 17:38:23] notice: Opened entropy source '/dev/urandom'. [2023/03/14 17:38:23] notice: hwmon: Module drivetemp loaded, drive temperatures available [2023/03/14 17:38:23] notice: hwmon: sda has temperature monitoring [2023/03/14 17:38:23] info: Temperature limits for /dev/sda, critical=N/A, highest=45c, lowest=36c, low critical=N/A. [2023/03/14 17:38:23] notice: hwmon: sdb has temperature monitoring [2023/03/14 17:38:23] info: Temperature limits for /dev/sdb, critical=0c, highest=52c, lowest=38c, low critical=0c. [2023/03/14 17:38:23] notice: hwmon: sdc has temperature monitoring [2023/03/14 17:38:23] info: Temperature limits for /dev/sdc, critical=0c, highest=58c, lowest=48c, low critical=0c. [2023/03/14 17:38:23] notice: hwmon: nvme0n1 has temperature monitoring [2023/03/14 17:38:23] info: Temperature limits for /dev/nvme0n1, critical=83c, highest=N/A, lowest=N/A, low critical=N/A. [2023/03/14 17:38:23] notice: hwmon: nvme1n1 has temperature monitoring [2023/03/14 17:38:23] info: Temperature limits for /dev/nvme1n1, critical=83c, highest=N/A, lowest=N/A, low critical=N/A. [2023/03/14 17:38:44] info: Nwipe was aborted by the user prior to the wipe starting.

From: PartialVolume @.> Sent: Tuesday, March 14, 2023 17:14 To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

Just made the changes to the code, just uploading it now 0.34.6.

I've done away with the flashing red and just have non flashing text.

So if the drive temperature exceeds the high critical temperature the temperature in the GUI will change to red text on blue background.

If the drive temperature drops below the low critical value (if it exists) then the temperature changes to black text on blue background.

If the drive reports no critical temperatures, the temperature text defaults to white text on blue.

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1468911082, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PXCFN6NTAJQUTGQRNLW4DURNANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.**@.>>

PartialVolume commented 1 year ago

I've just realised that I'm missing an extra two temperatures in that log, there is min and max as well, should be six temperatures in all., min/max represent the continuous running temperature that shouldn't be exceeded.

Useful info, re the 0 deg.c for critical I'll make allowances for that in the code, that explains why it was flashing red on those drives.

I'll carry on with this tomorrow night and do another update.

Thanks for the help, much appreciated.

PartialVolume commented 1 year ago

Just for info, this is what my nvme drive reports,

info: Temperature limits for /dev/nvme0n1, critical=84c, max=79c, highest=N/A, lowest=N/A, min=-5c, low critical=N/A.

Note the -5c, one what happens when you first switch your laptop on outside and it's -20 in Alaska

PartialVolume commented 1 year ago

@mdcato

[2023/03/14 17:38:23] info: Temperature limits for /dev/sda, critical=N/A, highest=45c, lowest=36c, low critical=N/A. [2023/03/14 17:38:23] notice: hwmon: sdb has temperature monitoring [2023/03/14 17:38:23] info: Temperature limits for /dev/sdb, critical=0c, highest=52c, lowest=38c, low critical=0c. [2023/03/14 17:38:23] notice: hwmon: sdc has temperature monitoring [2023/03/14 17:38:23] info: Temperature limits for /dev/sdc, critical=0c, highest=58c, lowest=48c, low critical=0c.

As none of these drives are showing a proper critical values, it wouldn't surprise me that the max,min values have some proper limit values in, I wasn't checking those values in the code before. If critical values don't exist or are not valid check the max/min values and if they are valid use those instead.

PartialVolume commented 1 year ago

@mdcato I've committed another update, this one includes the full set of six temperature logged to nwipe's log should you wish to try that out.

PartialVolume commented 1 year ago

Just looked at the values output from a Seagate ST3500312CS below, this would suggest the Max, Min values are the biggest and smallest, not the critical values. Makes me wonder how consistent this is among vendors or even drive models from the same vendor. Will have to have the code check to see which is the highest, Critical high vs Max and then use them appropriately.

[2023/03/15 00:06:11] info: Temperature limits for /dev/sda, critical=60c, max=61c, highest=30c, lowest=19c, min=1c, low critical=2c.

mdcato commented 1 year ago

Here the latest log:

[2023/03/15 16:38:08] notice: Found /dev/sda, ATA, ST1000DM003-1SB1, 1 TB, S/N=ZN15TA6Y [2023/03/15 16:38:08] info: HPA values 1953525168 / 1953525168 on /dev/sda [2023/03/15 16:38:08] info: hdparm:DCO Real max sectors reported as 1 on /dev/sda [2023/03/15 16:38:08] info: NWipe: DCO Real max sectors reported as 1 on /dev/sda [2023/03/15 16:38:08] warning: HIDDEN AREA DETECTED! on /dev/sda [2023/03/15 16:38:08] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 0 [2023/03/15 16:38:08] info: [2023/03/15 16:38:08] notice: Found /dev/sdb, ATA, ST10000NM0016-1T, 10 TB, S/N=ZA20SSAR [2023/03/15 16:38:09] warning: [UNKNOWN] We can't find the HPA line, has hdparm ouput changed? /dev/sdb [2023/03/15 16:38:09] info: hdparm:DCO Real max sectors reported as 1 on /dev/sdb [2023/03/15 16:38:09] info: NWipe: DCO Real max sectors reported as 1 on /dev/sdb [2023/03/15 16:38:09] warning: HIDDEN AREA INDETERMINATE! on /dev/sdb, are you using a USB bridge or memory stick? [2023/03/15 16:38:09] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 0 [2023/03/15 16:38:09] info: [2023/03/15 16:38:09] notice: Found /dev/sdc, ATA, ST4000NM0033-9ZM, 4 TB, S/N=Z1Z7NVF7 [2023/03/15 16:38:09] info: HPA values 7814037168 / 7814037168 on /dev/sdc [2023/03/15 16:38:09] info: hdparm:DCO Real max sectors reported as 1 on /dev/sdc [2023/03/15 16:38:09] info: NWipe: DCO Real max sectors reported as 1 on /dev/sdc [2023/03/15 16:38:09] warning: HIDDEN AREA DETECTED! on /dev/sdc [2023/03/15 16:38:09] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 0 [2023/03/15 16:38:09] info: [2023/03/15 16:38:09] notice: Found /dev/nvme0n1, NVME, Samsung SSD 970 EVO 250GB, 250 GB, S/N=S465NB0K580541L [2023/03/15 16:38:09] info: [2023/03/15 16:38:09] notice: Found /dev/nvme1n1, NVME, Samsung SSD 970 EVO 250GB, 250 GB, S/N=S465NB0K580543E [2023/03/15 16:38:09] info: [2023/03/15 16:38:09] info: Automatically enumerated 5 devices. [2023/03/15 16:38:09] info: bios-version = F15b [2023/03/15 16:38:09] info: bios-release-date = 03/23/2021 [2023/03/15 16:38:09] info: system-manufacturer = Gigabyte Technology Co., Ltd. [2023/03/15 16:38:09] info: system-product-name = Z370 AORUS ULTRA GAMING 2.0 [2023/03/15 16:38:09] info: system-version = Default string [2023/03/15 16:38:09] info: system-serial-number = Default string [2023/03/15 16:38:09] info: system-uuid = 03d502e0-045e-0583-4206-af0700080009 [2023/03/15 16:38:09] info: baseboard-manufacturer = Gigabyte Technology Co., Ltd. [2023/03/15 16:38:09] info: baseboard-product-name = Z370 AORUS ULTRA GAMING 2.0-CF [2023/03/15 16:38:09] info: baseboard-version = x.x [2023/03/15 16:38:09] info: baseboard-serial-number = Default string [2023/03/15 16:38:09] info: baseboard-asset-tag = Default string [2023/03/15 16:38:09] info: chassis-manufacturer = Default string [2023/03/15 16:38:09] info: chassis-type = Desktop [2023/03/15 16:38:09] info: chassis-version = Default string [2023/03/15 16:38:09] info: chassis-serial-number = Default string [2023/03/15 16:38:09] info: chassis-asset-tag = Default string [2023/03/15 16:38:09] info: processor-family = Core i5 [2023/03/15 16:38:09] info: processor-manufacturer = Intel(R) Corporation [2023/03/15 16:38:09] info: processor-version = Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz [2023/03/15 16:38:09] info: processor-frequency = 3800 MHz [2023/03/15 16:38:09] notice: Opened entropy source '/dev/urandom'. [2023/03/15 16:38:09] notice: hwmon: Module drivetemp loaded, drive temperatures available [2023/03/15 16:38:09] notice: hwmon: sda has temperature monitoring [2023/03/15 16:38:09] info: Temperature limits for /dev/sda, critical=N/A, max=N/A, highest=45c, lowest=36c, min=N/A, low critical=N/A. [2023/03/15 16:38:09] notice: hwmon: sdb has temperature monitoring [2023/03/15 16:38:09] info: Temperature limits for /dev/sdb, critical=0c, max=0c, highest=52c, lowest=38c, min=0c, low critical=0c. [2023/03/15 16:38:09] notice: hwmon: sdc has temperature monitoring [2023/03/15 16:38:09] info: Temperature limits for /dev/sdc, critical=0c, max=0c, highest=58c, lowest=48c, min=0c, low critical=0c. [2023/03/15 16:38:09] notice: hwmon: nvme0n1 has temperature monitoring [2023/03/15 16:38:09] info: Temperature limits for /dev/nvme0n1, critical=83c, max=83c, highest=N/A, lowest=N/A, min=-273c, low critical=N/A. [2023/03/15 16:38:09] notice: hwmon: nvme1n1 has temperature monitoring [2023/03/15 16:38:09] info: Temperature limits for /dev/nvme1n1, critical=83c, max=83c, highest=N/A, lowest=N/A, min=-273c, low critical=N/A. [2023/03/15 16:38:49] info: Nwipe was aborted by the user prior to the wipe starting.

From: PartialVolume @.> Sent: Tuesday, March 14, 2023 19:00 To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

@mdcatohttps://github.com/mdcato I've committed another update, this one includes the full set of six temperature logged to nwipe's log should you wish to try that out.

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1469023497, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PXD6EVEXTEDD66VL63W4EA67ANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.**@.>>

PartialVolume commented 1 year ago

@mdcato, thanks useful info, so looks like those drives don't have temperature limits, or maybe hwmon isn't accessing them properly or maybe there is something different about the hwmon directories that are generated and I'm not retrieving the data.

Any chance you could post the output with sudo ./nwipe --verbose. It will generate a big log file but it will contain the directory structure that we search for the hwmon data.

I'm just running various test cases on the new code that handles all these varying temperature fields. Hopefully I'll commit it in an hour or so.

mdcato commented 1 year ago

The –verbose log: [2023/03/15 17:33:55] debug: Readlink: ../devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sda [2023/03/15 17:33:55] info: smartctl: smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.14-200.fc37.x86_64] (local build) [2023/03/15 17:33:55] info: smartctl: copyright (c) 2002-22, bruce allen, christian franke, www.smartmontools.orghttp://www.smartmontools.org [2023/03/15 17:33:55] info: smartctl: === start of information section === [2023/03/15 17:33:55] info: smartctl: model family: Seagate Barracuda 7200.14 (AF) [2023/03/15 17:33:55] info: smartctl: device model: ST1000DM003-1SB102 [2023/03/15 17:33:55] info: smartctl: serial number: ZN15TA6Y [2023/03/15 17:33:55] info: smartctl: lu wwn device id: 5 000c50 0b5d6f509 [2023/03/15 17:33:55] info: smartctl: firmware version: CC63 [2023/03/15 17:33:55] info: smartctl: user capacity: 1,000,204,886,016 bytes [1.00 TB] [2023/03/15 17:33:55] info: smartctl: sector sizes: 512 bytes logical, 4096 bytes physical [2023/03/15 17:33:55] info: smartctl: rotation rate: 7200 rpm [2023/03/15 17:33:55] info: smartctl: form factor: 3.5 inches [2023/03/15 17:33:55] info: smartctl: device is: In smartctl database 7.3/5319 [2023/03/15 17:33:55] info: smartctl: ata version is: ACS-2, ACS-3 T13/2161-D revision 3b [2023/03/15 17:33:55] info: smartctl: sata version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) [2023/03/15 17:33:55] info: smartctl: local time is: Wed Mar 15 17:33:55 2023 CDT [2023/03/15 17:33:55] info: smartctl: smart support is: Available - device has SMART capability. [2023/03/15 17:33:55] info: smartctl: smart support is: Enabled [2023/03/15 17:33:55] notice: Found /dev/sda, ATA, ST1000DM003-1SB1, 1 TB, S/N=ZN15TA6Y [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 outgoing cdb: 85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 SG_IO: ATA_16 status=0x0, host_status=0x0, driver_status=0x0

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 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

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 incoming_data: 5a 0c ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00 00 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20 4e 5a 35 31 41 54 59 36 00 00 00 00 00 00 43 43 33 36 20 20 20 20 54 53 30 31 30 30 4d 44 30 30 2d 33 53 31 31 42 32 30 20 20 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 00 40 00 02 00 02 07 00 ff 3f 10 00 3f 00 10 fc fb 00 10 00 ff ff ff 0f 00 00 07 00 03 00 78 00 78 00 78 00 78 00 00 01 00 00 00 00 00 00 00 00 00 00 1f 00 0e 85 06 00 4c 00 44 00 e0 03 1f 00 6b [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 34 09 7d 63 41 69 34 09 bc 63 41 3f 20 37 00 37 00 80 80 fe ff 00 00 d0 d0 00 00 00 00 00 00 00 00 00 00 b0 6d 70 74 00 00 00 00 00 00 00 00 03 60 00 00 00 50 00 c5 d6 b5 09 f5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1e 40 1c 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 21 00 b0 6d 70 74 b0 6d 70 74 20 20 02 00 40 01 00 01 00 50 06 3c 0a 3c 00 00 3c 00 00 00 08 00 00 00 00 00 ff fd 80 02 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 80 00 00 84 01 00 94 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 85 10 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 1c 00 00 00 00 00 00 00 00 7f 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 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 00 00 00 00 00 a5 4e

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 SG_IO: desc[]: 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 using LBA48 taskfile

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 outgoing cdb: 85 07 20 00 00 00 00 00 00 00 00 00 00 40 27 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 SG_IO: sb[]: 72 01 00 1d 00 00 00 0e 09 0c 01 00 00 00 74 af 00 6d 00 70 40 50 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 SG_IO: desc[]: 09 0c 01 00 00 00 74 af 00 6d 00 70 40 50

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 ATA_16 stat=50 err=00 nsect=00 lbal=af lbam=6d lbah=70 dev=40

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 /dev/sda:

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 APT: No idVendor found -> not USB bridge device

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 oflags.bits.lob_all=0xc0, flags={ dev command }

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 oflags.bits.hob_all=0x00, flags={ }

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 READ_NATIVE_MAX_ADDRESS_EXT response: hob={00 00 74} lob={70 6d af}

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sda 2>&1 max sectors = 1953525168/1953525168, HPA is disabled

[2023/03/15 17:33:55] debug: hdparm says the host protected area is disabled on /dev/sda but this information may or may not be correct, as occurs when you get a SG_IO error and 0/1 sectors and it says HPA is enabled. Further checks are conducted below.. [2023/03/15 17:33:55] info: HPA values 1953525168 / 1953525168 on /dev/sda [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 outgoing cdb: 85 08 0e 00 c2 00 01 00 00 00 00 00 00 40 b1 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 sg_io: ata_16 status=0x0, host_status=0x0, driver_status=0x0

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 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

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 incoming_data: 02 00 07 00 3f 00 af 6d 70 74 00 00 00 00 8f 38 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 00 00 00 00 00 a5 18

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 sg_io: desc[]: 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 ata_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 /dev/sda:

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 apt: no idvendor found -> not usb bridge device

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 dco checksum verified.

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 dco revision: 0x0002

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 the following features can be selectively disabled via dco:

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 transfer modes:

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 mdma0 mdma1 mdma2

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 udma0 udma1 udma2 udma3 udma4 udma5

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sda 2>&1 real max sectors: 1953525168

[2023/03/15 17:33:55] info: hdparm:DCO Real max sectors reported as 1953525168 on /dev/sda [2023/03/15 17:33:55] info: NWipe: DCO Real max sectors reported as 1953525168 on /dev/sda [2023/03/15 17:33:55] info: No hidden areas on /dev/sda [2023/03/15 17:33:55] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 1953525168 [2023/03/15 17:33:55] info: [2023/03/15 17:33:55] debug: Readlink: ../devices/pci0000:00/0000:00:17.0/ata3/host2/target2:0:0/2:0:0:0/block/sdb [2023/03/15 17:33:55] info: smartctl: smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.14-200.fc37.x86_64] (local build) [2023/03/15 17:33:55] info: smartctl: copyright (c) 2002-22, bruce allen, christian franke, www.smartmontools.orghttp://www.smartmontools.org [2023/03/15 17:33:55] info: smartctl: === start of information section === [2023/03/15 17:33:55] info: smartctl: model family: Seagate Enterprise Capacity 3.5 HDD [2023/03/15 17:33:55] info: smartctl: device model: ST10000NM0016-1TT101 [2023/03/15 17:33:55] info: smartctl: serial number: ZA20SSAR [2023/03/15 17:33:55] info: smartctl: lu wwn device id: 5 000c50 09388455f [2023/03/15 17:33:55] info: smartctl: firmware version: SNB0 [2023/03/15 17:33:55] info: smartctl: user capacity: 10,000,831,348,736 bytes [10.0 TB] [2023/03/15 17:33:55] info: smartctl: sector sizes: 512 bytes logical, 4096 bytes physical [2023/03/15 17:33:55] info: smartctl: rotation rate: 7200 rpm [2023/03/15 17:33:55] info: smartctl: form factor: 3.5 inches [2023/03/15 17:33:55] info: smartctl: device is: In smartctl database 7.3/5319 [2023/03/15 17:33:55] info: smartctl: ata version is: ACS-3 T13/2161-D revision 5 [2023/03/15 17:33:55] info: smartctl: sata version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) [2023/03/15 17:33:55] info: smartctl: local time is: Wed Mar 15 17:33:55 2023 CDT [2023/03/15 17:33:55] info: smartctl: smart support is: Available - device has SMART capability. [2023/03/15 17:33:55] info: smartctl: smart support is: Enabled [2023/03/15 17:33:55] notice: Found /dev/sdb, ATA, ST10000NM0016-1T, 10 TB, S/N=ZA20SSAR [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 outgoing cdb: 85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 SG_IO: ATA_16 status=0x0, host_status=0x0, driver_status=0x0

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 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

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 incoming_data: 5a 0c ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00 00 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20 41 5a 30 32 53 53 52 41 00 00 00 00 00 00 4e 53 30 42 20 20 20 20 54 53 30 31 30 30 4e 30 30 4d 31 30 2d 36 54 31 31 54 31 30 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 00 40 00 02 00 02 07 00 ff 3f 10 00 3f 00 10 fc fb 00 10 5d ff ff ff 0f 00 00 07 00 03 00 78 00 78 00 78 00 78 00 08 00 00 00 00 00 00 00 00 00 00 00 1f 00 0e 8d 46 00 cc 08 44 00 f0 07 6d 00 6b [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 30 61 75 73 61 69 30 41 b4 73 61 7f 40 af 81 af 81 00 00 fe ff 00 00 00 fe 00 10 00 00 00 00 10 27 00 00 00 00 40 8c 04 00 00 00 00 00 00 00 03 60 00 00 00 50 00 c5 88 93 5f 45 00 00 00 00 00 00 00 00 00 00 00 00 00 00 de 41 dc 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 29 00 00 00 40 8c 00 00 40 8c 20 20 02 00 40 01 00 01 00 50 06 3c 0a 3c 00 00 3c 00 00 00 08 00 00 00 00 00 ff fd 80 02 00 00 70 01 08 00 00 00 00 00 33 0c 00 00 00 80 00 00 a5 01 00 97 68 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 bd 50 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 1c 00 00 00 00 00 00 00 00 7f 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 8c 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 [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 00 00 00 00 00 a5 d9

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 SG_IO: desc[]: 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 using LBA48 taskfile

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 outgoing cdb: 85 07 20 00 00 00 00 00 00 00 00 00 00 40 78 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 SG_IO: sb[]: 72 01 00 1d 00 00 00 0e 09 0c 01 00 00 00 8c ff 04 ff 00 3f 40 50 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 SG_IO: desc[]: 09 0c 01 00 00 00 8c ff 04 ff 00 3f 40 50

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 ATA_16 stat=50 err=00 nsect=00 lbal=ff lbam=ff lbah=3f dev=40

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 /dev/sdb:

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 APT: No idVendor found -> not USB bridge device

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 oflags.bits.lob_all=0x82, flags={ feat command }

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 oflags.bits.hob_all=0x00, flags={ }

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 GET_NATIVE_MAX_ADDRESS_EXT response: hob={00 04 8c} lob={3f ff ff}

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdb 2>&1 max sectors = 19532873728/19532873728, ACCESSIBLE MAX ADDRESS disabled

[2023/03/15 17:33:55] warning: [UNKNOWN] We can't find the HPA line, has hdparm ouput changed? /dev/sdb [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 outgoing cdb: 85 08 0e 00 c2 00 01 00 00 00 00 00 00 40 b1 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 sg_io: ata_16 status=0x2, host_status=0x0, driver_status=0x8

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 sg_io: sb[]: 70 00 05 00 00 00 00 0a 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 incoming_data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 sg_io: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 sg_io: desc[]: 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 ata_16 stat=00 err=01 nsect=04 lbal=00 lbam=00 lbah=00 dev=00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 /dev/sdb:

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 apt: no idvendor found -> not usb bridge device

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 dco checksum verified.

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 dco revision: 0x0000 -- unknown, treating as 0002

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 the following features can be selectively disabled via dco:

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 transfer modes:

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdb 2>&1 real max sectors: 1

[2023/03/15 17:33:55] info: hdparm:DCO Real max sectors reported as 1 on /dev/sdb [2023/03/15 17:33:55] info: NWipe: DCO Real max sectors reported as 1 on /dev/sdb [2023/03/15 17:33:55] warning: HIDDEN AREA INDETERMINATE! on /dev/sdb, are you using a USB bridge or memory stick? [2023/03/15 17:33:55] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 0 [2023/03/15 17:33:55] info: [2023/03/15 17:33:55] debug: Readlink: ../devices/pci0000:00/0000:00:17.0/ata4/host3/target3:0:0/3:0:0:0/block/sdc [2023/03/15 17:33:55] info: smartctl: smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.14-200.fc37.x86_64] (local build) [2023/03/15 17:33:55] info: smartctl: copyright (c) 2002-22, bruce allen, christian franke, www.smartmontools.orghttp://www.smartmontools.org [2023/03/15 17:33:55] info: smartctl: === start of information section === [2023/03/15 17:33:55] info: smartctl: model family: Seagate Constellation ES.3 [2023/03/15 17:33:55] info: smartctl: device model: ST4000NM0033-9ZM170 [2023/03/15 17:33:55] info: smartctl: serial number: Z1Z7NVF7 [2023/03/15 17:33:55] info: smartctl: lu wwn device id: 5 000c50 07a6b9c41 [2023/03/15 17:33:55] info: smartctl: firmware version: SN04 [2023/03/15 17:33:55] info: smartctl: user capacity: 4,000,787,030,016 bytes [4.00 TB] [2023/03/15 17:33:55] info: smartctl: sector size: 512 bytes logical/physical [2023/03/15 17:33:55] info: smartctl: rotation rate: 7200 rpm [2023/03/15 17:33:55] info: smartctl: form factor: 3.5 inches [2023/03/15 17:33:55] info: smartctl: device is: In smartctl database 7.3/5319 [2023/03/15 17:33:55] info: smartctl: ata version is: ACS-2 (minor revision not indicated) [2023/03/15 17:33:55] info: smartctl: sata version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) [2023/03/15 17:33:55] info: smartctl: local time is: Wed Mar 15 17:33:55 2023 CDT [2023/03/15 17:33:55] info: smartctl: smart support is: Available - device has SMART capability. [2023/03/15 17:33:55] info: smartctl: smart support is: Enabled [2023/03/15 17:33:55] notice: Found /dev/sdc, ATA, ST4000NM0033-9ZM, 4 TB, S/N=Z1Z7NVF7 [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 outgoing cdb: 85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 SG_IO: ATA_16 status=0x0, host_status=0x0, driver_status=0x0

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 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

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 incoming_data: 5a 0c ff 3f 37 c8 10 00 00 00 00 00 3f 00 00 00 00 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20 31 5a 37 5a 56 4e 37 46 00 00 00 00 00 00 4e 53 34 30 20 20 20 20 54 53 30 34 30 30 4d 4e 30 30 33 33 39 2d 4d 5a 37 31 20 30 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 00 40 00 02 00 02 07 00 ff 3f 10 00 3f 00 10 fc fb 00 10 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 8d 06 00 cc 00 44 00 f0 03 00 00 6b [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 34 01 75 63 61 69 34 01 b4 63 61 7f 40 e8 00 e8 00 00 00 fe ff 00 00 00 fe 00 00 00 00 00 00 00 00 00 00 b0 be c0 d1 01 00 00 00 00 00 00 00 00 40 00 00 00 50 00 c5 6b 7a 41 9c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 de 40 dc 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 29 00 b0 be c0 d1 b0 be c0 d1 20 20 02 00 40 01 08 01 00 50 06 3c 0a 3c 00 00 3c 00 00 00 08 00 00 00 00 00 ff 7d 80 02 00 00 70 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 8d 00 00 63 48 88 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 bd 50 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20 1c 00 00 00 00 00 00 00 00 20 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 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 00 00 00 00 00 a5 e4

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 SG_IO: desc[]: 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 using LBA48 taskfile

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 outgoing cdb: 85 07 20 00 00 00 00 00 00 00 00 00 00 40 27 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 SG_IO: sb[]: 72 01 00 1d 00 00 00 0e 09 0c 01 00 00 00 d1 af 01 be 00 c0 40 50 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 SG_IO: desc[]: 09 0c 01 00 00 00 d1 af 01 be 00 c0 40 50

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 ATA_16 stat=50 err=00 nsect=00 lbal=af lbam=be lbah=c0 dev=40

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 /dev/sdc:

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 APT: No idVendor found -> not USB bridge device

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 oflags.bits.lob_all=0xc0, flags={ dev command }

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 oflags.bits.hob_all=0x00, flags={ }

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 READ_NATIVE_MAX_ADDRESS_EXT response: hob={00 01 d1} lob={c0 be af}

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdc 2>&1 max sectors = 7814037168/7814037168, HPA is disabled

[2023/03/15 17:33:55] debug: hdparm says the host protected area is disabled on /dev/sdc but this information may or may not be correct, as occurs when you get a SG_IO error and 0/1 sectors and it says HPA is enabled. Further checks are conducted below.. [2023/03/15 17:33:55] info: HPA values 7814037168 / 7814037168 on /dev/sdc [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 outgoing cdb: 85 08 0e 00 c2 00 01 00 00 00 00 00 00 40 b1 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 sg_io: ata_16 status=0x2, host_status=0x0, driver_status=0x8

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 sg_io: sb[]: 70 00 05 00 00 00 00 0a 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 incoming_data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 sg_io: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 sg_io: desc[]: 04 53 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 ata_16 stat=00 err=01 nsect=04 lbal=00 lbam=00 lbah=00 dev=00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 /dev/sdc:

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 apt: no idvendor found -> not usb bridge device

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 dco checksum verified.

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 dco revision: 0x0000 -- unknown, treating as 0002

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 the following features can be selectively disabled via dco:

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 transfer modes:

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdc 2>&1 real max sectors: 1

[2023/03/15 17:33:55] info: hdparm:DCO Real max sectors reported as 1 on /dev/sdc [2023/03/15 17:33:55] info: NWipe: DCO Real max sectors reported as 1 on /dev/sdc [2023/03/15 17:33:55] warning: HIDDEN AREA DETECTED! on /dev/sdc [2023/03/15 17:33:55] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 0 [2023/03/15 17:33:55] info: [2023/03/15 17:33:55] debug: Readlink: ../devices/pci0000:00/0000:00:14.0/usb2/2-7/2-7:1.0/host11/target11:0:0/11:0:0:0/block/sdd [2023/03/15 17:33:55] info: smartctl: smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.14-200.fc37.x86_64] (local build) [2023/03/15 17:33:55] info: smartctl: copyright (c) 2002-22, bruce allen, christian franke, www.smartmontools.orghttp://www.smartmontools.org [2023/03/15 17:33:55] info: smartctl: /dev/sdd: Unknown USB bridge [0x090c:0x1000 (0x1100)] [2023/03/15 17:33:55] info: smartctl: please specify device type with the -d option. [2023/03/15 17:33:55] info: smartctl: use smartctl -h to get a usage summary [2023/03/15 17:33:55] warning: /dev/sdd USB bridge, no pass-through support [2023/03/15 17:33:55] notice: Found /dev/sdd, USB, Samsung Flash Drive FIT, 256 GB, S/N=(S/N: unknown) [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 outgoing cdb: 85 08 0e 00 00 00 01 00 00 00 00 00 00 40 ec 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 SG_IO: sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 incoming_data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 SG_IO: desc[]: 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 using LBA48 taskfile

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 outgoing cdb: 85 07 20 00 00 00 00 00 00 00 00 00 00 40 f8 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 SG_IO: sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 SG_IO: desc[]: 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 ATA_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 /dev/sdd:

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 APT: USB ID = 0x090c:0x1000 (0x1100)

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 APT: Unsupported device

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 oflags.bits.lob_all=0x80, flags={ command }

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 oflags.bits.hob_all=0x00, flags={ }

[2023/03/15 17:33:55] debug: hdparm --verbose -N /dev/sdd 2>&1 max sectors = 0/1, HPA is enabled

[2023/03/15 17:33:55] debug: hdparm says the host protected area is enabled on /dev/sdd but this information may or may not be correct, as occurs when you get a SG_IO error and 0/1 sectors and it says HPA is enabled. Further checks are conducted below.. [2023/03/15 17:33:55] info: HPA values 0 / 1 on /dev/sdd [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 outgoing cdb: 85 08 0e 00 c2 00 01 00 00 00 00 00 00 40 b1 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 sg_io: ata_16 status=0x2, host_status=0x0, driver_status=0x8

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 sg_io: sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 incoming_data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 sg_io: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 sg_io: desc[]: 00 00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 ata_16 stat=00 err=00 nsect=00 lbal=00 lbam=00 lbah=00 dev=00

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 /dev/sdd:

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 apt: usb id = 0x090c:0x1000 (0x1100)

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 apt: unsupported device

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 dco checksum verified.

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 dco revision: 0x0000 -- unknown, treating as 0002

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 the following features can be selectively disabled via dco:

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 transfer modes:

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1

[2023/03/15 17:33:55] debug: hdparm --verbose --dco-identify /dev/sdd 2>&1 real max sectors: 1

[2023/03/15 17:33:55] info: hdparm:DCO Real max sectors reported as 1 on /dev/sdd [2023/03/15 17:33:55] info: NWipe: DCO Real max sectors reported as 1 on /dev/sdd [2023/03/15 17:33:55] warning: HIDDEN AREA INDETERMINATE! on /dev/sdd, are you using a USB bridge or memory stick? [2023/03/15 17:33:55] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 0 [2023/03/15 17:33:55] info: [2023/03/15 17:33:55] debug: Readlink: ../devices/pci0000:00/0000:00:1b.4/0000:05:00.0/nvme/nvme0/nvme0n1 [2023/03/15 17:33:55] info: smartctl: smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.14-200.fc37.x86_64] (local build) [2023/03/15 17:33:55] info: smartctl: copyright (c) 2002-22, bruce allen, christian franke, www.smartmontools.orghttp://www.smartmontools.org [2023/03/15 17:33:55] info: smartctl: === start of information section === [2023/03/15 17:33:55] info: smartctl: model number: Samsung SSD 970 EVO 250GB [2023/03/15 17:33:55] info: smartctl: serial number: S465NB0K580541L [2023/03/15 17:33:55] info: smartctl: firmware version: 2B2QEXE7 [2023/03/15 17:33:55] info: smartctl: pci vendor/subsystem id: 0x144d [2023/03/15 17:33:55] info: smartctl: ieee oui identifier: 0x002538 [2023/03/15 17:33:55] info: smartctl: total nvm capacity: 250,059,350,016 [250 GB] [2023/03/15 17:33:55] info: smartctl: unallocated nvm capacity: 0 [2023/03/15 17:33:55] info: smartctl: controller id: 4 [2023/03/15 17:33:55] info: smartctl: nvme version: 1.3 [2023/03/15 17:33:55] info: smartctl: number of namespaces: 1 [2023/03/15 17:33:55] info: smartctl: namespace 1 size/capacity: 250,059,350,016 [250 GB] [2023/03/15 17:33:55] info: smartctl: namespace 1 utilization: 51,716,677,632 [51.7 GB] [2023/03/15 17:33:55] info: smartctl: namespace 1 formatted lba size: 512 [2023/03/15 17:33:55] info: smartctl: namespace 1 ieee eui-64: 002538 5581b35c46 [2023/03/15 17:33:55] info: smartctl: local time is: Wed Mar 15 17:33:55 2023 CDT [2023/03/15 17:33:55] notice: Found /dev/nvme0n1, NVME, Samsung SSD 970 EVO 250GB, 250 GB, S/N=S465NB0K580541L [2023/03/15 17:33:55] info: [2023/03/15 17:33:55] debug: Readlink: ../devices/pci0000:00/0000:00:1d.0/0000:0a:00.0/nvme/nvme1/nvme1n1 [2023/03/15 17:33:55] info: smartctl: smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.14-200.fc37.x86_64] (local build) [2023/03/15 17:33:55] info: smartctl: copyright (c) 2002-22, bruce allen, christian franke, www.smartmontools.orghttp://www.smartmontools.org [2023/03/15 17:33:55] info: smartctl: === start of information section === [2023/03/15 17:33:55] info: smartctl: model number: Samsung SSD 970 EVO 250GB [2023/03/15 17:33:55] info: smartctl: serial number: S465NB0K580543E [2023/03/15 17:33:55] info: smartctl: firmware version: 2B2QEXE7 [2023/03/15 17:33:55] info: smartctl: pci vendor/subsystem id: 0x144d [2023/03/15 17:33:55] info: smartctl: ieee oui identifier: 0x002538 [2023/03/15 17:33:55] info: smartctl: total nvm capacity: 250,059,350,016 [250 GB] [2023/03/15 17:33:55] info: smartctl: unallocated nvm capacity: 0 [2023/03/15 17:33:55] info: smartctl: controller id: 4 [2023/03/15 17:33:55] info: smartctl: nvme version: 1.3 [2023/03/15 17:33:55] info: smartctl: number of namespaces: 1 [2023/03/15 17:33:55] info: smartctl: namespace 1 size/capacity: 250,059,350,016 [250 GB] [2023/03/15 17:33:55] info: smartctl: namespace 1 utilization: 30,880,473,088 [30.8 GB] [2023/03/15 17:33:55] info: smartctl: namespace 1 formatted lba size: 512 [2023/03/15 17:33:55] info: smartctl: namespace 1 ieee eui-64: 002538 5581b35c48 [2023/03/15 17:33:55] info: smartctl: local time is: Wed Mar 15 17:33:55 2023 CDT [2023/03/15 17:33:55] notice: Found /dev/nvme1n1, NVME, Samsung SSD 970 EVO 250GB, 250 GB, S/N=S465NB0K580543E [2023/03/15 17:33:55] info: [2023/03/15 17:33:55] info: Automatically enumerated 6 devices. [2023/03/15 17:33:55] info: bios-version = F15b [2023/03/15 17:33:55] info: bios-release-date = 03/23/2021 [2023/03/15 17:33:55] info: system-manufacturer = Gigabyte Technology Co., Ltd. [2023/03/15 17:33:55] info: system-product-name = Z370 AORUS ULTRA GAMING 2.0 [2023/03/15 17:33:55] info: system-version = Default string [2023/03/15 17:33:55] info: system-serial-number = Default string [2023/03/15 17:33:55] info: system-uuid = 03d502e0-045e-0583-4206-af0700080009 [2023/03/15 17:33:55] info: baseboard-manufacturer = Gigabyte Technology Co., Ltd. [2023/03/15 17:33:55] info: baseboard-product-name = Z370 AORUS ULTRA GAMING 2.0-CF [2023/03/15 17:33:55] info: baseboard-version = x.x [2023/03/15 17:33:55] info: baseboard-serial-number = Default string [2023/03/15 17:33:55] info: baseboard-asset-tag = Default string [2023/03/15 17:33:55] info: chassis-manufacturer = Default string [2023/03/15 17:33:55] info: chassis-type = Desktop [2023/03/15 17:33:55] info: chassis-version = Default string [2023/03/15 17:33:55] info: chassis-serial-number = Default string [2023/03/15 17:33:55] info: chassis-asset-tag = Default string [2023/03/15 17:33:55] info: processor-family = Core i5 [2023/03/15 17:33:55] info: processor-manufacturer = Intel(R) Corporation [2023/03/15 17:33:55] info: processor-version = Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz [2023/03/15 17:33:55] info: processor-frequency = 3800 MHz [2023/03/15 17:33:55] notice: Opened entropy source '/dev/urandom'. [2023/03/15 17:33:55] notice: hwmon: Module drivetemp loaded, drive temperatures available [2023/03/15 17:33:55] debug: hwmon: [2023/03/15 17:33:55] debug: hwmon: Found /sys/class/hwmon/hwmon6/device/block [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon6/device/block/. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon6/device/block/.. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon6/device/block/sdc [2023/03/15 17:33:55] debug: hwmon: [2023/03/15 17:33:55] debug: hwmon: Found /sys/class/hwmon/hwmon4/device/block [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon4/device/block/. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon4/device/block/.. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon4/device/block/sda [2023/03/15 17:33:55] notice: hwmon: sda has temperature monitoring [2023/03/15 17:33:55] debug: hwmon: sda found in /sys/class/hwmon/hwmon4/device/block [2023/03/15 17:33:55] debug: hwmon: [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon2/device/block doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon2/device/nvme/nvme0 doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: Found /sys/class/hwmon/hwmon2/device [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/.. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/uevent [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/cntlid [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/address [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/reset_controller [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/sqsize [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/queue_count [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/transport [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/subsysnqn [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/power [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/ng1n1 [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/rescan_controller [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/numa_node [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/model [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/dev [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/hwmon2 [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/device [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/firmware_rev [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/dctype [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/cntrltype [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/subsystem [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/state [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/kato [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/nvme1n1 [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/serial [2023/03/15 17:33:55] debug: hwmon: [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon0/device/block doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon0/device/nvme/nvme0 doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: Found /sys/class/hwmon/hwmon0/device [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/.. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/uevent [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/mode [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/power [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/available_policies [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/device [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/policy [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/trip_point_1_type [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/k_d [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/sustainable_power [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/type [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/hwmon0 [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/offset [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/slope [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/trip_point_0_type [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/k_po [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/integral_cutoff [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/subsystem [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/k_i [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/trip_point_1_temp [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/k_pu [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/temp [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/trip_point_0_temp [2023/03/15 17:33:55] debug: hwmon: [2023/03/15 17:33:55] debug: hwmon: Found /sys/class/hwmon/hwmon5/device/block [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon5/device/block/. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon5/device/block/.. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon5/device/block/sdb [2023/03/15 17:33:55] debug: hwmon: [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon3/device/block doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon3/device/nvme/nvme0 doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: Found /sys/class/hwmon/hwmon3/device [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/.. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/uevent [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/power [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/driver [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/driver_override [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/subsystem [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/hwmon [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/modalias [2023/03/15 17:33:55] debug: hwmon: [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon1/device/block doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon1/device/nvme/nvme0 doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: Found /sys/class/hwmon/hwmon1/device [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/.. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/uevent [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/nvme0n1 [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/cntlid [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/address [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/reset_controller [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/sqsize [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/queue_count [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/transport [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/subsysnqn [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/power [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/rescan_controller [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/numa_node [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/model [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/dev [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/device [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/firmware_rev [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/dctype [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/cntrltype [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/ng0n1 [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/subsystem [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/state [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/kato [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/serial [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon1/device/hwmon1 [2023/03/15 17:33:55] notice: hwmon: Device /dev/sda hwmon path = /sys/class/hwmon/hwmon4 [2023/03/15 17:33:55] notice: hwmon: Unable to open /sys/class/hwmon/hwmon4/temp1_crit [2023/03/15 17:33:55] notice: hwmon: /sys/class/hwmon/hwmon4/temp1_highest 45C [2023/03/15 17:33:55] notice: hwmon: /sys/class/hwmon/hwmon4/temp1_input 45C [2023/03/15 17:33:55] notice: hwmon: Unable to open /sys/class/hwmon/hwmon4/temp1_lcrit [2023/03/15 17:33:55] notice: hwmon: /sys/class/hwmon/hwmon4/temp1_lowest 44C [2023/03/15 17:33:55] notice: hwmon: Unable to open /sys/class/hwmon/hwmon4/temp1_max [2023/03/15 17:33:55] notice: hwmon: Unable to open /sys/class/hwmon/hwmon4/temp1_min [2023/03/15 17:33:55] info: Temperature limits for /dev/sda, critical=N/A, max=N/A, highest=45c, lowest=44c, min=N/A, low critical=N/A. [2023/03/15 17:33:55] debug: hwmon: [2023/03/15 17:33:55] debug: hwmon: Found /sys/class/hwmon/hwmon6/device/block [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon6/device/block/. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon6/device/block/.. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon6/device/block/sdc [2023/03/15 17:33:55] debug: hwmon: [2023/03/15 17:33:55] debug: hwmon: Found /sys/class/hwmon/hwmon4/device/block [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon4/device/block/. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon4/device/block/.. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon4/device/block/sda [2023/03/15 17:33:55] debug: hwmon: [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon2/device/block doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon2/device/nvme/nvme0 doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: Found /sys/class/hwmon/hwmon2/device [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/.. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/uevent [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/cntlid [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/address [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/reset_controller [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/sqsize [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/queue_count [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/transport [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/subsysnqn [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/power [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/ng1n1 [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/rescan_controller [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/numa_node [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/model [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/dev [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/hwmon2 [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/device [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/firmware_rev [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/dctype [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/cntrltype [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/subsystem [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/state [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/kato [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/nvme1n1 [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon2/device/serial [2023/03/15 17:33:55] debug: hwmon: [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon0/device/block doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon0/device/nvme/nvme0 doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: Found /sys/class/hwmon/hwmon0/device [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/.. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/uevent [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/mode [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/power [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/available_policies [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/device [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/policy [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/trip_point_1_type [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/k_d [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/sustainable_power [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/type [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/hwmon0 [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/offset [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/slope [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/trip_point_0_type [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/k_po [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/integral_cutoff [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/subsystem [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/k_i [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/trip_point_1_temp [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/k_pu [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/temp [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon0/device/trip_point_0_temp [2023/03/15 17:33:55] debug: hwmon: [2023/03/15 17:33:55] debug: hwmon: Found /sys/class/hwmon/hwmon5/device/block [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon5/device/block/. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon5/device/block/.. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon5/device/block/sdb [2023/03/15 17:33:55] notice: hwmon: sdb has temperature monitoring [2023/03/15 17:33:55] debug: hwmon: sdb found in /sys/class/hwmon/hwmon5/device/block [2023/03/15 17:33:55] debug: hwmon: [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon3/device/block doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon3/device/nvme/nvme0 doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: Found /sys/class/hwmon/hwmon3/device [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/.. [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/uevent [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/power [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/driver [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/driver_override [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/subsystem [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/hwmon [2023/03/15 17:33:55] debug: hwmon: dirpath_tmp=/sys/class/hwmon/hwmon3/device/modalias [2023/03/15 17:33:55] debug: hwmon: [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon1/device/block doesn't exist, trying next path [2023/03/15 17:33:55] debug: hwmon: /sys/class/hwmon/hwmon1

PartialVolume commented 1 year ago

Are you able to list the contents of the files & folders in /sys/class/hwmon/hwmon4/device/block/sda. I'm just wondering if the naming convention might of changed for these drives.

I'm looking for these files, maybe the names are different?

char temperature_label[NUMBER_OF_FILES][20] = { "temp1_crit", "temp1_highest", "temp1_input", "temp1_lcrit", "temp1_lowest", "temp1_max", "temp1_min" };

mdcato commented 1 year ago

I’m unsure if I followed your directions correctly as the file names don’t have something similar to what you requested, but here is the “ls -A -l -R” output in case that helps narrow in on the target. (So, not only drives not adhering to a spec nor convention, but Linux distributions as well.)

@.*** sda]# ls -A -l -R .: total 0 -r--r--r--. 1 root root 4096 Mar 11 18:36 alignment_offset lrwxrwxrwx. 1 root root 0 Mar 15 17:57 bdi -> ../../../../../../../../virtual/bdi/8:0 -r--r--r--. 1 root root 4096 Mar 15 17:57 capability -r--r--r--. 1 root root 4096 Mar 11 18:40 dev lrwxrwxrwx. 1 root root 0 Mar 11 18:35 device -> ../../../1:0:0:0 -r--r--r--. 1 root root 4096 Mar 15 17:57 discard_alignment -r--r--r--. 1 root root 4096 Mar 15 17:57 diskseq -r--r--r--. 1 root root 4096 Mar 15 17:57 events -r--r--r--. 1 root root 4096 Mar 15 17:57 events_async -rw-r--r--. 1 root root 4096 Mar 15 17:57 events_poll_msecs -r--r--r--. 1 root root 4096 Mar 11 18:36 ext_range -r--r--r--. 1 root root 4096 Mar 15 17:57 hidden drwxr-xr-x. 2 root root 0 Mar 11 18:35 holders -r--r--r--. 1 root root 4096 Mar 15 17:57 inflight drwxr-xr-x. 2 root root 0 Mar 11 18:36 integrity drwxr-xr-x. 3 root root 0 Mar 11 18:36 mq drwxr-xr-x. 2 root root 0 Mar 11 18:36 power drwxr-xr-x. 3 root root 0 Mar 11 18:35 queue -r--r--r--. 1 root root 4096 Mar 15 17:57 range -r--r--r--. 1 root root 4096 Mar 11 18:35 removable -r--r--r--. 1 root root 4096 Mar 11 18:35 ro -r--r--r--. 1 root root 4096 Mar 11 18:35 size drwxr-xr-x. 2 root root 0 Mar 11 18:36 slaves -r--r--r--. 1 root root 4096 Mar 11 18:35 stat lrwxrwxrwx. 1 root root 0 Mar 11 18:35 subsystem -> ../../../../../../../../../class/block drwxr-xr-x. 2 root root 0 Mar 11 18:36 trace -rw-r--r--. 1 root root 4096 Mar 11 18:35 uevent

./holders: total 0

./integrity: total 0 -r--r--r--. 1 root root 4096 Mar 15 17:58 device_is_integrity_capable -r--r--r--. 1 root root 4096 Mar 15 17:58 format -r--r--r--. 1 root root 4096 Mar 15 17:58 protection_interval_bytes -rw-r--r--. 1 root root 4096 Mar 15 17:58 read_verify -r--r--r--. 1 root root 4096 Mar 15 17:58 tag_size -rw-r--r--. 1 root root 4096 Mar 15 17:58 write_generate

./mq: total 0 drwxr-xr-x. 8 root root 0 Mar 11 18:36 0

./mq/0: total 0 drwxr-xr-x. 2 root root 0 Mar 11 18:36 cpu0 drwxr-xr-x. 2 root root 0 Mar 11 18:36 cpu1 drwxr-xr-x. 2 root root 0 Mar 11 18:36 cpu2 drwxr-xr-x. 2 root root 0 Mar 11 18:36 cpu3 drwxr-xr-x. 2 root root 0 Mar 11 18:36 cpu4 drwxr-xr-x. 2 root root 0 Mar 11 18:36 cpu5 -r--r--r--. 1 root root 4096 Mar 15 18:10 cpu_list -r--r--r--. 1 root root 4096 Mar 15 18:10 nr_reserved_tags -r--r--r--. 1 root root 4096 Mar 15 18:10 nr_tags

./mq/0/cpu0: total 0

./mq/0/cpu1: total 0

./mq/0/cpu2: total 0

./mq/0/cpu3: total 0

./mq/0/cpu4: total 0

./mq/0/cpu5: total 0

./power: total 0 -rw-r--r--. 1 root root 4096 Mar 15 17:58 autosuspend_delay_ms -rw-r--r--. 1 root root 4096 Mar 15 17:58 control -r--r--r--. 1 root root 4096 Mar 15 17:58 runtime_active_time -r--r--r--. 1 root root 4096 Mar 15 17:58 runtime_status -r--r--r--. 1 root root 4096 Mar 15 17:58 runtime_suspended_time

./queue: total 0 -rw-r--r--. 1 root root 4096 Mar 15 17:58 add_random -r--r--r--. 1 root root 4096 Mar 15 17:58 chunk_sectors -r--r--r--. 1 root root 4096 Mar 11 18:36 dax -r--r--r--. 1 root root 4096 Mar 15 17:58 discard_granularity -rw-r--r--. 1 root root 4096 Mar 15 17:58 discard_max_bytes -r--r--r--. 1 root root 4096 Mar 15 17:58 discard_max_hw_bytes -r--r--r--. 1 root root 4096 Mar 15 17:58 discard_zeroes_data -r--r--r--. 1 root root 4096 Mar 15 17:58 dma_alignment -r--r--r--. 1 root root 4096 Mar 15 17:58 fua -r--r--r--. 1 root root 4096 Mar 15 17:58 hw_sector_size -rw-r--r--. 1 root root 4096 Mar 15 17:58 io_poll -rw-r--r--. 1 root root 4096 Mar 15 17:58 io_poll_delay drwxr-xr-x. 2 root root 0 Mar 11 18:36 iosched -rw-r--r--. 1 root root 4096 Mar 15 17:58 iostats -rw-r--r--. 1 root root 4096 Mar 15 17:58 io_timeout -r--r--r--. 1 root root 4096 Mar 11 18:35 logical_block_size -r--r--r--. 1 root root 4096 Mar 15 17:58 max_discard_segments -r--r--r--. 1 root root 4096 Mar 15 17:58 max_hw_sectors_kb -r--r--r--. 1 root root 4096 Mar 15 17:58 max_integrity_segments -rw-r--r--. 1 root root 4096 Mar 15 17:58 max_sectors_kb -r--r--r--. 1 root root 4096 Mar 15 17:58 max_segments -r--r--r--. 1 root root 4096 Mar 15 17:58 max_segment_size -r--r--r--. 1 root root 4096 Mar 11 18:36 minimum_io_size -rw-r--r--. 1 root root 4096 Mar 15 17:58 nomerges -rw-r--r--. 1 root root 4096 Mar 15 17:58 nr_requests -r--r--r--. 1 root root 4096 Mar 15 17:58 nr_zones -r--r--r--. 1 root root 4096 Mar 11 18:36 optimal_io_size -r--r--r--. 1 root root 4096 Mar 11 18:36 physical_block_size -rw-r--r--. 1 root root 4096 Mar 15 17:58 read_ahead_kb -rw-r--r--. 1 root root 4096 Mar 11 18:35 rotational -rw-r--r--. 1 root root 4096 Mar 15 17:58 rq_affinity -rw-r--r--. 1 root root 4096 Mar 15 17:58 scheduler -rw-r--r--. 1 root root 4096 Mar 15 17:58 stable_writes -r--r--r--. 1 root root 4096 Mar 15 17:58 virt_boundary_mask -rw-r--r--. 1 root root 4096 Mar 15 17:58 wbt_lat_usec -rw-r--r--. 1 root root 4096 Mar 15 17:58 write_cache -r--r--r--. 1 root root 4096 Mar 15 17:58 write_same_max_bytes -r--r--r--. 1 root root 4096 Mar 15 17:58 write_zeroes_max_bytes -r--r--r--. 1 root root 4096 Mar 15 17:58 zone_append_max_bytes -r--r--r--. 1 root root 4096 Mar 15 17:58 zoned -r--r--r--. 1 root root 4096 Mar 15 17:58 zone_write_granularity

./queue/iosched: total 0 -rw-r--r--. 1 root root 4096 Mar 15 18:10 back_seek_max -rw-r--r--. 1 root root 4096 Mar 15 18:10 back_seek_penalty -rw-r--r--. 1 root root 4096 Mar 15 18:10 fifo_expire_async -rw-r--r--. 1 root root 4096 Mar 15 18:10 fifo_expire_sync -rw-r--r--. 1 root root 4096 Mar 15 18:10 low_latency -rw-r--r--. 1 root root 4096 Mar 15 18:10 max_budget -rw-r--r--. 1 root root 4096 Mar 15 18:10 slice_idle -rw-r--r--. 1 root root 4096 Mar 15 18:10 slice_idle_us -rw-r--r--. 1 root root 4096 Mar 15 18:10 strict_guarantees -rw-r--r--. 1 root root 4096 Mar 15 18:10 timeout_sync

./slaves: total 0

./trace: total 0 -rw-r--r--. 1 root root 4096 Mar 15 17:58 act_mask -rw-r--r--. 1 root root 4096 Mar 15 17:58 enable -rw-r--r--. 1 root root 4096 Mar 15 17:58 end_lba -rw-r--r--. 1 root root 4096 Mar 15 17:58 pid -rw-r--r--. 1 root root 4096 Mar 15 17:58 start_lba

From: PartialVolume @.> Sent: Wednesday, March 15, 2023 17:54 To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

Are you able to list the contents of the files & folders in /sys/class/hwmon/hwmon4/device/block/sda. I'm just wondering if the naming convention might of changed for these drives.

I'm looking for these files, maybe the names are different?

char temperature_label[NUMBER_OF_FILES][20] = { "temp1_crit", "temp1_highest", "temp1_input", "temp1_lcrit", "temp1_lowest", "temp1_max", "temp1_min" };

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1470947582, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PVHIWSS52YTUDSNXELW4JB7DANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.**@.>>

PartialVolume commented 1 year ago

If you try

# cd /sys/class/hwmon/hwmon4
# ls
device  name  power  subsystem  temp1_alarm  temp1_crit  temp1_input  temp1_label  temp1_max  temp1_min  ueven

you should get some files, something like these, there maybe only one i.e temp1_input

mdcato commented 1 year ago

Nope, that’s why I did the full “ls -A -l -R” in case what you are looking for is in a subfolder. There is no file/folder in that tree that has “temp” as part of the name.

From: PartialVolume @.> Sent: Wednesday, March 15, 2023 18:53 To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

If you try

cd /sys/class/hwmon/hwmon4

ls

device name power subsystem temp1_alarm temp1_crit temp1_input temp1_label temp1_max temp1_min ueven

you should get some files, something like these, there maybe only one i.e temp1_input

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1470995253, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PQEM5PRPWADF7BPODTW4JI6HANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.**@.>>

PartialVolume commented 1 year ago

The files must be there as the logs report

[2023/03/15 17:33:55] notice: hwmon: sda has temperature monitoring [2023/03/15 17:33:55] debug: hwmon: sda found in /sys/class/hwmon/hwmon4/device/block

We're also getting the lowest and highest values so there must be a temp1_lowest file in that directory.

Does find / -name "temp1_lowest" -print find it?

PartialVolume commented 1 year ago

Not necessarily that directory /sys/class/hwmon/hwmon4/device/block but maybe one or two directories up from it.

mdcato commented 1 year ago

find output followed by those files contents:

@.*** device]# find / -name "temp1_lowest" -print /sys/devices/pci0000:00/0000:00:17.0/ata4/host3/target3:0:0/3:0:0:0/hwmon/hwmon6/temp1_lowest /sys/devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/hwmon/hwmon4/temp1_lowest /sys/devices/pci0000:00/0000:00:17.0/ata3/host2/target2:0:0/2:0:0:0/hwmon/hwmon5/temp1_lowest

@.*** device]# find / -name "temp1_lowest" -exec cat {} \; 48000 39000 38000

From: PartialVolume @.> Sent: Wednesday, March 15, 2023 19:29 To: martijnvanbrummelen/nwipe @.> Cc: Mike Cato / Hays Technical Services @.>; Mention @.> Subject: Re: [martijnvanbrummelen/nwipe] Help needed. (Issue #444)

The files must be there as the logs report

[2023/03/15 17:33:55] notice: hwmon: sda has temperature monitoring [2023/03/15 17:33:55] debug: hwmon: sda found in /sys/class/hwmon/hwmon4/device/block

We're also getting the lowest and highest values so there must be a temp1_lowest file in that directory.

Does find / -name "temp1_lowest" -print find it?

— Reply to this email directly, view it on GitHubhttps://github.com/martijnvanbrummelen/nwipe/issues/444#issuecomment-1471024513, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGK2PXCA2JYB47JDIJ7WVTW4JNDBANCNFSM6AAAAAAVOSGF7U. You are receiving this because you were mentioned.Message ID: @.**@.>>

PartialVolume commented 1 year ago

Are you able to list the contents of each of these directories to see what other files are in there

/sys/devices/pci0000:00/0000:00:17.0/ata4/host3/target3:0:0/3:0:0:0/hwmon/hwmon6/ /sys/devices/pci0000:00/0000:00:17.0/ata2/host1/target1:0:0/1:0:0:0/hwmon/hwmon4/ /sys/devices/pci0000:00/0000:00:17.0/ata3/host2/target2:0:0/2:0:0:0/hwmon/hwmon5/

PartialVolume commented 1 year ago

New code uploaded, I'm expecting the temperature code to not be red now on your discs with this new code as it shouldn't be getting confused by the zero values in critical and min/max.

Now validates temperatures rather than assuming the data is valid, checking for the following:

Meaning of color changes

Test code showing temperature cycling between +10 and -10 with critical at +8 and -8 and min/max at -5 & +5. The colors of the temperature text and background change when those settings are reached. As this is a test, those values are low, just for test purposes, on a actual disc they are more like critical +65, max +60, min -2 critical min -5

showing_new_temperature_style-2023-03-15_23 26 27 mp4

PartialVolume commented 1 year ago

@.*** device]# find / -name "temp1_lowest" -exec cat {} \; 48000 39000 38000

Dividing those values by 1000 give us our degrees C. In that same directory there must be another file containing the actual realtime drive temperature.