Unable to wipe a /dev/nume0n1p drive.

I have an HP EliteDesk 800 G3 small form factor. It has a solid state hard drive. I need to wipe the hard drive, so I'm using "SystemRescue CD" (it's a Linux distro). I boot from the CD and then I type:    shred -v /dev/sda.
     I've used this method to successfully wipe a previous PC, but on this PC it won't work. On this PC it says "no such file or directory."
     I tried several variations on this command (shred --v.....     shred -verbose.....     shred --verbose.....) but it still won't work.
     So then I typed:   fdisk -l   and I got the following:
     I've never seen this before. I thought I'd see something like:
     So then I typed:   shred -v /dev/nume0n1p     (as well as the 3 variations of this), but it still won't work.

-Anyone know how I can wipe this PC?
-What is "/nume0n1p"?  Is that the solid state version of "/sda"?
-Are the "v" switch and the "verbose" switch one and the same thing?
-Does it matter if a Linux switch has one dash (-) or two (--)?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

nociSoftware EngineerCommented:
Those are NVMe devices:
More description is here:   https://wiki.gentoo.org/wiki/NVMe
THe basename of a drive will be: /dev/nume0nX
with X starting from 0 should be the drive, the pY  behind it is the partition number (in your case 3 partition.).
(this is commonly used on any device except for the [fhs]dXY, type of devices.)
These devices are called block devices as they process data in block size chunks.
Classic disks that is 512 bytes, some 4K in Flash drives mostly by 1M chunks.

running shred --help  will tell you the options and -v & --verbose are equal.
Now what do you expect from shred, it overwrite files IF files allocation is static. [ not necessarily on btrfs / zfs, and log based filesystem might not help as well ].

NVMe memory (flash memory in general) might not get erased anyway to preserve writability of cells. (Those memory banks often have a lot more storage than shown so wiping it might be troublesome).

The best way is encrypt the drive and have the keys off-drive. And forget about the keys at some point.
Otherwise you need to rewrite the whole drive several times. (And use varying paterns, not to overwrite the neighbour magnetic remnants like on magnetic disks, just to ensure paterns are written to the backing store.)
(paterns like 101010101 , then 01010101, then 1010101 then 010101 ...) and do that several times so the wearleveling backing store is also touched.

Yes - & -- are different. - is short form (mostly allowing single character options, -- is long form using full words, shred --help will show....
there are exceptions (obviously)  openssl uses single - with words.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
can you tell us WHY you want to erase the drive?  for normal operations, you don't need to do that
Duncan RoeSoftware DeveloperCommented:
I think you have the drive name wrong, The second letter should be v-Victor, not u-Uniform. E.g. on my system
08:26:20$ ls -l /dev/nvme*
crw------- 1 root root 240, 0 Feb 23 10:16 /dev/nvme0
brw-rw---- 1 root disk 259, 0 Feb 23 10:16 /dev/nvme0n1
brw-rw---- 1 root disk 259, 1 Feb 23 10:16 /dev/nvme0n1p1
brw-rw---- 1 root disk 259, 2 Feb 23 10:16 /dev/nvme0n1p2
brw-rw---- 1 root disk 259, 3 Feb 23 10:16 /dev/nvme0n1p3
brw-rw---- 1 root disk 259, 4 Feb 23 10:16 /dev/nvme0n1p4
brw-rw---- 1 root disk 259, 5 Feb 23 10:16 /dev/nvme0n1p5
brw-rw---- 1 root disk 259, 6 Feb 23 10:16 /dev/nvme0n1p6
brw-rw---- 1 root disk 259, 7 Feb 23 10:16 /dev/nvme0n1p7

Open in new window

john8217Author Commented:
I thought I needed to wipe this drive because it wouldn't let me image it. It kept giving me some "Task Sequence" error. But now we found out it's not necessary to wipe it.

nobus, it's dawned on me that you're right, manually trying to delete a SSD is kind of strange.

Duncan Roe, you're also right. Those are "v"s and not "u"s (my eyes aren't what they used to be). Thank you for alerting me.

This was my first encounter with SSDs. So far I guess I'm not doing so hot with these. But this was a good learning experience. And noci, thank you for all that information.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.