Shred OS freezing (same as in Issue #210)

[Trump125532]

Im having an issue here with multiple different Laptop models. Currently im trying to wipe the 512GB M.2 disk of a Fujitsu Lifebook U7410 and Shred OS just freezes after a couple of minutes (3-5m). The same issue was observerd on HP Elitebook 830 G6/G8. I tried a couple of different Shred OS releases but none seem to resolve this issue. All Laptops have an M.2 SSD. The Shred OS USB-Stick is the only thing connected to the Laptop and it doesnt matter which USB-Port I plug it in. The whole wiping process should take less than an hour, according to Shred OS's estimation and considering it crashing so early I dont think it's the USB-Controller overheating. I also opened one Laptop and there was no dust clogging the fan / heatpipes.

[PartialVolume]

I'm assuming you are wiping the internal M.2 drive?

What's the drive temperature reporting at the moment of the crash, if the screen is just freezing you should still be able to see the temperature. Can you take a picture.

[Trump125532]

Yes i am indeed wiping the internal M.2 drive. The temperature is between 45 and 55°C. (I am currently running Shred OS on 2 Laptops, one is at 45, the other at 54)

[PartialVolume]

What are the make and model of the M.2 SSDs on the laptop that freezes and once frozen is the estimated time changing over say 30 mins after freeze, i.e increasing? Is the spinning character at the end of the wipe line also frozen

[Trump125532]

Yes, the spinning character is also frozen and no, the estimated time doesnt change at all, I left it over night and nothing happend. The SSD is a Western Digital PC SN720 NVMe SSD with 512GB.

[Trump125532]

Quick update: Somehow using ShredOS version v2021.08.2_23_x86-64_0.34 resolved this issue for one Laptop at least. I have tried using this exact version before and it didnt work. But now the Laptop with this version is almost at 50% (It has never even gone above 10%) so I'd assume that this is working now. But the other one running the newest release (ShredOS version v2023.08.2_25_x86-64_0.35) still has this issue.

[PartialVolume]

It can't be anything to do with SSD then as the drive and screen are operating in different threads, the time to completion would be increasing to a much larger number. Is there a disc activity light on the laptop? Was that still blinking, if yes it would indicate the graphics has hung but not the CPU. I wonder what the CPU and motherboard temperature were at the time it hung. Might have to put that on the title bar of nwipe.

• What speed was was the disc wiping at?
• If you restart the wipe but switch over to a virtual terminal ALT F2 and run lspci and take a picture so we have more detail on the controllers used.
• Are these donated laptops that could already have faults?

[Trump125532]

Unfortunately this model does not have a disc activity light. The disc was wiping at around 700MB/s. Those Laptops are "old" laptops from our company which will be given away to the employes. All that I tested with Shred OS worked perfectly fine and none of them is older than 4 years, so I would asume that they dont have any defects. This is the result of lspci:

[PartialVolume]

Just thinking about what might cause this, the order is of no particular significance:

• A bug in the Intel graphics driver that affects Intel UHD ? That's possible, but if it was that, there isn't anything I can do about it that other than bump ShredOS to the next buildroot and kernel version and hope it's fixed, however if it was this I would have expected to see many issues with Intel graphics but you never know perhaps it's very specific to a certain Intel graphics chipset.

• The WD SN720 has a operating spec of 70 deg.C so the 50 deg.C is well within spec.

• Motherboard fault when the internal temperature increases ? It probably goes without saying but a secure erase using hdparm (provided with ShredOS) would most likely be much faster and not raise the temperature internally by any where near as much. So if a temperature related issue you may be able to get the drive wiped.

• What wipe method are you using on the SSD, hopefully not the default DOD short. I wouldn't do anything more than a ones wipe or PRNG with last pass verification and NO final blanking. Basically a single wipe and single verification read. My preference being PRNG as it would show stuck bits in the data channels that a ones or zeros might not. PRNG however does put a little more pressure on the CPU which ones doesn't.

This is where telemetry would be incredibly useful because we could see at a glance by going to shredos.com and looking at the database how many systems with VGA Intel UHD hardware were wiping successfully with no issues.

• If it was me and I was trying to rule out a temperature problem I would put it outside in the shade fully charged but using mains power so the battery doesn't add to the heat when it charges, outside where it's currently about 9 deg.C

[Trump125532]

I have tried pretty much every availible wiping Method, but the one im using is overwriting everyting with 0s. But ShredOS version v2021.08.2_23_x86-64_0.34 did work for me over night, however ShredOS version v2023.08.2_25_x86-64_0.35 still isnt working. I think for now using the older version is fine. I did put a Laptop outside at ~10°C but it still crashed with the newest version.

[PartialVolume]

Added lspci output so Google can find it a bit easier.

sh-5.18 Ispci 00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 UGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:12.0 Signal processing controller: Intel Corporation Conet Lake Thernal Subsyten 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM nenory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial 10 12C Host Controller 00:15.3 Serial bus controller [0c001: Intel Corporation Device 02eb 00:16.0 Communication controller: Intel Corporation Conet Lake Management Engine Interface 00:10.0 PCI bridge: Intel Corporation Device 0218 (rev f0) 00:10.7 PCI bridge: Intel Corporation Device 02hf (rev fo) 00:14.0 PCI bridge: Intel Corporation Device 0260 (rev 10) 00:14.4 PCI bridge: Intel Corporation Device 6264 (reu (0) 00:10.0 Communication controller: Intel Corporation Device 02a8 00:10.1 Communication controller: Intel Corporation Device 0249 00:11.0 ISA bridge: Intel Corporation Device 0284 00:11.3 Audio device: Intel Corporation Device 0208 00:10.4 SMB: Intel Corporation Device 0243 00:11.5 Serial bus controller [0600]: Intel Corporation Conet Lake SPI (flash) Controller 00:11.6 Ethernet controller: Intel Corporation Ethernet Connection (10) 1219-IM 06:00.0 SD Host controller: 02 Micro, Inc. SD/MMC Card Reader Controller (rev 01) 06:00.0 Mon-Volatile nenory controller: Sandisk Corp WD Black 2018/PC SN720 HUME SSD 10:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge (Titan Ridge 2C 2018] (rev 06) 11:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge (Titan Ridge 2C 2018] (rev 06) 11:01.0 PCI bridge: Intel Corporation JHL.7540 Thunderbolt 3 Bridge (Titan Ridge 2C 20181 (rev 06) 11:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge (Titan Ridge 20 20181 (rev 06) 12:00.0 Systen peripheral: Intel Intel Corporation JHL7540 Thunderbolt 3 NHI (Titan Hidge 20 2018) (rev 06) 49:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller (Titan Ridge 2C 20181 (rev 06) sh-5.18

[Vadar]

Hi @PartialVolume, Not wanting to hijack this thread. I am experiencing this same issue. Things noted/information:

v2023.08.2_25_x86-64_0.35

• Fails whilst running HMG IS5 Enhanced, Crashes out between 3-30mins
• Succeeds whilst running Single pass PRNG Stream with 0
• Fails whilst running multi pass (3) PRNG Stream with 0

v2021.08.2_23_x86-64_0.34

• Success running HMG IS5 Enhanced

Noticed UHD different version and processor gen to @Trump125532

Hardware information Multiple Dell Latitude 5500 Laptops, Variety of M.2 NVME disks including SK Hynix, WD etc. Temps when displayed are sub 70oc (Ambient Office Temp, Not in sunlight) lspci dump:

Cheers, Cal

[jpatry07]

I am also experiencing this issue on Lenovo X1 Carbon (multiple units, multiple gens),, intel CPU and Toshiba NVME. I ran the program from bootable USB vanilla and am doing a full DoD wipe and it freezes every time. The entire screen freezes and the only "solution" is to do a reboot but I cant get the drives wiped.

Note: Im using the latest version as I need the certificate for compliancy to regulatory authorities

[lizord69]

I was experiencing the same thing but using a tower as my "disk killer". I used to be able to run 6+ drives at a time, when i upgraded to v.35 to use the PDF feature it would crash if i had more than 3 drives. Even disabling the PDF feature it would consistently freeze. I tried using a mixture of just about every setting. I tried just about everything including different motherboard, CPU, RAM, GPU vs Integrated, peripherals, sata cables, power supply, and even different USB drives. As soon as i went back to v.34 it froze once (bad drive i believe) then never again.

Specs: ASUS H270m-plus, i5-7500, 4gb 2400T, 350W PSU

I have had no issues with v.34 since reverting back. I frequently wipe 6 sata drives and 2 nvme drives simultaneously. the case i am using has two fans that i have set to run at full capacity with the drives sitting basically touching the fan. The side pannel is always off while the disk killer is running.

I just thought another input with a different approach may be helpful. :)