Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Wipe finishes instantly (can't wipe) #301

Open
SimpleAdventurer opened this issue Nov 24, 2024 · 5 comments
Open

Wipe finishes instantly (can't wipe) #301

SimpleAdventurer opened this issue Nov 24, 2024 · 5 comments
Assignees
@PartialVolume
Labels
bug Something isn't working

Comments

@SimpleAdventurer
Copy link

I'm trying to wipe my NVMe SSDs and some SATA HDDs.
I made the bootable USB using ventoy and put the nomodeset ISO (other ISOs failed to boot)
When I try to wipe my SSD with the default options, the process finishes almost instantly, and the log looks like this

[2024/11/24 04:51:32] info: ShredOS v2024.02.2_26.0_x86-64_0.37-nomodeset
[2024/11/24 04:51:32] info: Linux version 6.6.22 (nick@nick-optiplex9010) (x
86_64-buildroot-linux-gnu-gcc.br_real (Buildroo
t -g9c929fc958-dirty) 12.3.0, GNU ld (GNU Binut
ils) 2.40) #8 SMP PREEMPT_DYNAMIC Tue Jun 11 20
:55:07 BST 2024
[2024/11/24 04:51:32] notice: Found /dev/sda, ATA ,
[2024/11/24 04:51:32] info: /dev/sda, sector(logical)/block(physical) sizes 512/4096
[2024/11/24 04:51:33] info: HPA: max sectors = 3907029168/3907029168, hpa is disabled
on /dev/sda
[2024/11/24 04:51:33] info: HPA values 3907029168 / 3907029168 on /dev/sda
[2024/11/24 04:51:33] info: hdparm:DCO Real max sectors reported as 1 on /dev/sda
[2024/11/24 04:51:33] info: NWipe: DCO Real max sectors reported as 1 on /dev/sda
[2024/11/24 04:51:33] info: libata: apparent max sectors reported as 3907029168 with sector size as 512/4096 (logical/physical) on /dev/sda
[2024/11/24 04:51:33] info: No hidden sectors on /dev/sda
[2024/11/24 04:51:33] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 0
[2024/11/24 04:51:33] info:
[2024/11/24 04:51:33] warning: Smartctl is unable to provide smart data for /dev/sdb
[2024/11/24 04:51:33] notice: Found /dev/sdb, USB , SanDisk SanDisk 3.2 Gen1, 250 GB, S/N=(S/N: unknown)
[2024/11/24 04:51:33] info: /dev/sdb, sector(logical)/block(physical) sizes 512/512
[2024/11/24 04:51:33] error: SG_IO bad/missing sense data hdparm --verbose -N /dev/sdb 2>&1

[2024/11/24 04:51:33] warning: [UNKNOWN] We can't find the HPA line, has hdparm ouput unknown/changed? /dev/sdb
[2024/11/24 04:51:33] info: hdparm:DCO Real max sectors reported as 1 on /dev/sdb
[2024/11/24 04:51:33] info: NWipe: DCO Real max sectors reported as 1 on /dev/sdb
[2024/11/24 04:51:33] info: libata: apparent max sectors reported as 488914944 with sector size as 512/512 (logical/physical) on /dev/sdb
[2024/11/24 04:51:33] info: func:nwipe_read_dco_real_max_sectors(), DCO real max sectors = 0
[2024/11/24 04:51:33] info:
[2024/11/24 04:51:33] notice: Found /dev/nvme0n1, NVME ,
[2024/11/24 04:51:33] info: /dev/nvme0n1, sector(logical)/block(physical) sizes 512/512
[2024/11/24 04:51:33] info:
[2024/11/24 04:51:33] notice: Found /dev/nvme1n1, NVME ,
[2024/11/24 04:51:33] info: /dev/nvme1n1, sector(logical)/block(physical) sizes 512/512
[2024/11/24 04:51:33] info:
[2024/11/24 04:51:33] info: Automatically enumerated 4 devices.
[2024/11/24 04:51:33] info: bios-version = 9.30
[2024/11/24 04:51:33] info: bios-release-date = 06/16/2021
[2024/11/24 04:51:33] info: system-manufacturer = Micro-Star International Co., Ltd.
[2024/11/24 04:51:33] info: system-product-name = MAG Z490 Codex X5 (MS-B930)
[2024/11/24 04:51:33] info: system-version = 1.1
[2024/11/24 04:51:33] info: system-serial-number = *
[2024/11/24 04:51:33] info: system-uuid = *
[2024/11/24 04:51:33] info: baseboard-manufacturer = Micro-Star International Co., Ltd.
[2024/11/24 04:51:33] info: baseboard-product-name = Z490-S01 (MS-7C98)
[2024/11/24 04:51:33] info: baseboard-version = 1.1
[2024/11/24 04:51:33] info: baseboard-serial-number = *
[2024/11/24 04:51:33] info: baseboard-asset-tag = Default string
[2024/11/24 04:51:33] info: chassis-manufacturer = Micro-Star International Co., Ltd.
[2024/11/24 04:51:33] info: chassis-type = Desktop
[2024/11/24 04:51:33] info: chassis-version = 1.1
[2024/11/24 04:51:33] info: chassis-serial-number = Default string
[2024/11/24 04:51:33] info: chassis-asset-tag = Default string
[2024/11/24 04:51:33] info: processor-family = Core i9
[2024/11/24 04:51:33] info: processor-manufacturer = Intel(R) Corporation
[2024/11/24 04:51:33] info: processor-version = Intel(R) Core(TM) i9-10900KF CPU @ 3.70GHz
[2024/11/24 04:51:33] info: processor-frequency = 3700 MHz
[2024/11/24 04:51:33] notice: Opened entropy source '/dev/urandom'.
[2024/11/24 04:51:33] notice: hwmon: Module drivetemp loaded, drive temperatures available
[2024/11/24 04:51:33] notice: hwmon: sda has temperature monitoring
[2024/11/24 04:51:33] info: Temperature limits for /dev/sda, critical=N/A, max=N/A, highest=N/A, lowest=N/A, min=N/A, low critical=N/A.
[2024/11/24 04:51:33] info: Temperature limits for /dev/sdb, critical=N/A, max=N/A, highest=N/A, lowest=N/A, min=N/A, low critical=N/A.
[2024/11/24 04:51:33] notice: hwmon: nvme0n1 has temperature monitoring
[2024/11/24 04:51:33] info: Temperature limits for /dev/nvme0n1, critical=N/A, max=N/A, highest=N/A, lowest=N/A, min=N/A, low critical=N/A.
[2024/11/24 04:51:33] notice: hwmon: nvme1n1 has temperature monitoring
[2024/11/24 04:51:33] info: Temperature limits for /dev/nvme1n1, critical=N/A, max=N/A, highest=N/A, lowest=N/A, min=N/A, low critical=N/A.
[2024/11/24 04:51:39] info: Nwipe was aborted by the user prior to the wipe starting.

As shown in the final line, Nwipe has been aborted. I tried it with other SSDs, and HDDs, but they all failed to wipe. (Although the GUI says wipe finished).

I disable intel RST, RAIDs, and set connection mode to AHCI.
@PartialVolume
Copy link
Owner

PartialVolume commented Nov 24, 2024 •
edited
Loading 

[2024/11/24 04:51:39] info: Nwipe was aborted by the user prior to the wipe starting.

The log says you never tried to start any wipes.

How did you try to start the wipe? shift s, i.e capital S, after first selecting the drive to be wiped using the spacebar?

@SimpleAdventurer
Copy link
Author 

[2024/11/24 04:51:39] info: Nwipe was aborted by the user prior to the wipe starting.

The log says you never tried to start any wipes.

How did you try to start the wipe? shift s, i.e capital S, after first selecting the drive to be wiped using the spacebar?

I navigated to the drive I planned to erase. Pressed s, and then pressed shift+s (as indicated in the GUI).
As I said, the GUI prompt in the bottom of the screen says wipe finished, and asks to generate a PDF. And I pressed enter to generate the PDF and exit. However, no PDF were generated and the log says I aborted the wipe, which is not the case.

@PartialVolume
Copy link
Owner

PartialVolume commented Nov 25, 2024 •
edited
Loading

I navigated to the drive I planned to erase. Pressed s, and then pressed shift+s (as indicated in the GUI).

Just checking, but did you enable the drive for wiping using the the spacebar?

@SimpleAdventurer
Copy link
Author

Just checking, but did you enable the drive for wiping using the the spacebar?

OMG..I didn't mark the drive to wipe using. Using spacebar to mark -> s -> Shift+s works fine! thank you!!

btw, I was only able to boot using the nomodeset iso. And since the nomodeset version was only provided in ISO, I had to make the boot USB with ventoy (Rufus was unable to flash the USB with the ISO). I see that the nomodeset doesn't use linux direct rendering manager. Is there any way to make a usb with rufus in this case? and my laptop can't boot shredos even with the nomodeset (it only worked with my desktop).

@PartialVolume
Copy link
Owner

PartialVolume commented Nov 30, 2024 •
edited
Loading

I'm marking this as a bug, as I can reproduce the s shift s when no drives are enabled and nwipe then exits. It shouldn't do that, it should be displaying a message saying you haven't selected any drives.

@PartialVolume PartialVolume self-assigned this Nov 30, 2024
@PartialVolume PartialVolume added the bug Something isn't working label Nov 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@PartialVolume PartialVolume

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@PartialVolume @SimpleAdventurer