PDF problem with version v2024.11_27_x86-64_0.38

[Detron2017]

Hello all,

Unfortunately, I have the problem that I get an error message if I overwrite the hard disk more than once, regardless of which method I use.

I have the boot image of ShredOS version v2024.11_27_x86-64_0.38
-> ShredOS .img x86_64bit for USB Vanilla

and made it bootable on a USB stick using Rufus. I can successfully start Shredos on a workstation.
My goal is to use the Gutmann method. As soon as the first round is over, I get the error in the image.
If I select a different method that only runs 1x, then it works with the PDF. It is then successfully saved on the stick.

Is this a known problem? What can be done about it?

[PartialVolume]

Unfortunately, I have the problem that I get an error message if I overwrite the hard disk more than once, regardless of which method I use.

I'm not sure what you mean, using a method with more than one pass or more than one round or restarting nwipe and wiping a second time?

From that screen shot it looks like nwipe crashed at 3% into the wipe. What's the history of the system it's running on? For instance is it your day to day reliable workhorse or is it's condition unknown?

[PartialVolume]

Can you run a ones method with verification and let me know if the same problem occurs. Thanks.

(Ruling out a memory bit stuck low)

[Detron2017]

Method: Fill with Ones
PRNG: ISAAC-64
Verify: ### Last Pass
Rounds: 1
Blanking: ### Do not perform a final blanking pass
PDF Report - Enable/Disable: Enabled
PDF Report - Preview at Start: Disable

Result: SUCCESS

Method: Fill with Zeros
PRNG: ISAAC-64
Verify: ### All Passes
Rounds: 1
Blanking:### Do not perform a final blanking pass
PDF Report - Enable/Disable: Enabled
PDF Report - Preview at Start: Disable

Result: SUCCESS

Method: Fill with Zeros
PRNG: ISAAC-64
Verify: ### All Passes
Rounds: 1
Blanking: ### PLUS blanking pass
PDF Report - Enable/Disable: Enabled
PDF Report - Preview at Start: Disable

Result: FAILED

[PartialVolume]

Have you added or changed either of the default grub.cfg files, located in /EFI or /boot on the USB stick?

If you have can you post a snapshot. Thanks.

[Detron2017]

I have not changed anything because I use the graphical interface and not the commands.

Here is the entry from \EFI\BOOT\grub.cfg

[PartialVolume]

Can you repeat the wipe that generates a crash but before you start plug a ethernet lead into the computer to connect it to a router that provides DHCP. This is so the logs don't fill up with network related messages. Start the wipe and straight after it crashes can you ALT F2 to switch to the virtual terminal, and type more /var/log/messages and post a snapshot of the screen. I want to see if the kernel reports any problems

[Detron2017]

No ideas from anyone? :)

[IanSnell56]

I appear to be having the same issue.

[IanSnell56]

and filling with 1s and no-blanking pass worked.

[PartialVolume]

Is that 100% repeatable for both working and non working methods/blanking?

[IanSnell56]

Not sure what you mean? I've had around 6 failures before I tried "filling with 1 and no blanking pass". Tried disabling PDF, but that didn't work. I've only tried once on the temporary solution - am currently doing the same to a larger disk. So I should know later today.

[IanSnell56]

This one also failed. I used altF2 and more /var/log/messages. The only messge I could see, having scanned the lot is failure of port type messages.

[IanSnell56]

What can I do to assist?

[IanSnell56]

Is there anything I can do to assist?

[IanSnell56]

sorry can't wait any longer. WIll find another way to wipe disk.

[PartialVolume]

Sorry, just trying to catch up with things. If it works for a method of ones and no blanking pass this suggests you have a hardware fault that only shows when you try to write ones to every bit and location. When a zero gets written a memory fault could occur, this could crash nwipe, maybe the driver. Also nwipe will utilise as much memory as possible so a system that isn't 100% defect free can cause problems. If you weren't happy with just a one's wipe, I'd probably take the SSD out and put it another system or using a USB adapter wipe it on another system. And you could of course try using a different program that only utilizes a small part of memory using direct I/O. Personally, even if it worked I wouldn't be happy with the hardware.