Skip to main content

Free Shipping on Domestic Orders $75+

Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds

What you need

  1. Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, USB-C>USB-A adapter note: step 1, image 1 of 2 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, USB-C>USB-A adapter note: step 1, image 2 of 2
    • If you don't have a spare USB-C to USB-A adapter (such as from a broken Poly headset), you can easily find them online or at retailers like Best Buy by searching for "USB-C to USB-A adapter". This adapter lets you connect modern USB-C UASP devices to legacy PCs, saving you from searching for an elusive native USB-A UASP adapter.

    • They can be purchased here if you cannot salvage one: UGREEN USB to USB C Adapter & USB C to USB Adapter Combo 4-Pack.

    Ask FixBot

    Add Comment

  2. Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Mounting the hard drive for testing: step 2, image 1 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Mounting the hard drive for testing: step 2, image 2 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Mounting the hard drive for testing: step 2, image 3 of 3
    • IF YOUR MACHINE HAS USB-C, FAVOR TYPE-C TO AVOID THE HASSLE. USB-A enclosures are a mixed bag, though genuine USB 3.x ones do support UASP. If you lack USB-C, ensure you get a USB-A enclosure with true USB 3.0/3.1 and UASP support or pair it with a USB-C>USB-A adapter.

    • IMPORTANT: Adapters with a blue interface but only 4 pins are "fake" USB3 and won't support UASP—if your enclosure has this, it's a liar and should be returned. True USB-A 3.x connectors must have 9 pins. Using a USB-C to USB-A adapter with a USB-C enclosure bypasses all of this compatibility guesswork.

    • If you are testing an M.2 SSD (AHCI or NVMe) outside of the computer (i.e: not on a desktop board or inside a laptop), you will need an enclosure specially built for this. It must support NVMe with NVMe drives, or AHCI for older M.2 SSDs.

    • This guide assumes you have already created your boot drive. If you need instructions on how to make a bootable USB, please refer to this guide (Rufus) or this guide (Etcher).

    • Connect the drive using a USB adapter, or plug it directly into a free internal slot (SATA or M.2) on your motherboard.

    Ask FixBot

    Add Comment

  3. Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Linux - locating the device ID: step 3, image 1 of 1
    • These steps will work on ANY Debian based Linux distro with Debian packages. However, you must be online temporarily for installation purposes. This is not needed for systems with a permanent installation that is in active use.

    • This can be located in Terminal with sudo nvme list (NVMe only) or lsblk -o NAME,MODEL,SERIAL,SIZE,TYPE,ROTA (SATA). However, Disks will show it without terminal knowledge.

    Ask FixBot

    Add Comment

  4. Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Linux - NVMe: step 4, image 1 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Linux - NVMe: step 4, image 2 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Linux - NVMe: step 4, image 3 of 3
    • These steps will work on ANY Debian based Linux distro with Debian packages. However, you must be online temporarily for installation purposes. This is not needed for systems with a permanent installation that is in active use.

    • These steps are unique to NVMe SSDs. They do not apply to SATA SSDs.

    • Start Ubuntu and run sudo apt-get install nvme-cli on the live image.

    • -H can be replaced with -B but this data will need to be converted from binary to hex to be human readable.

    • NOTE: The device dev ID can be found in Disks, each machine will be different. After installing nvme-cli, run the following command: sudo nvme smart-log -H /dev/nvmeX (change X for the SSD ID). External SSDs may use /dev/sdbX, but same rule for probing it in CLI applies - just double check with externals.

    • Check the following data first: Percentage used, Data Written, Power on hours, Unsafe shutdown (less critical, but check!), Media errors.

    Ask FixBot

    Add Comment

  5. Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Linux, SATA SSDs - SMART data check: step 5, image 1 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Linux, SATA SSDs - SMART data check: step 5, image 2 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Linux, SATA SSDs - SMART data check: step 5, image 3 of 3
    • These steps will work on ANY Debian based Linux distro with Debian packages. However, you must be online temporarily for installation purposes. This is not needed for systems with a permanent installation that is in active use.

    • Some SSDs (example shown: PNY CS900) do not properly relay SMART data. Nothing can be done about this, as the vendor chose to encrypt the data unnecessarily.

    • GSmartControl can be used in Ubuntu if you cannot read the output from Disks.

    • Boot your system into a live Linux session. Locate the Disks application and select the SSD you want to test.

    • From the drop-down menu, select SMART Data and Self Tests. This will pull up the SMART data.

    • Locate the following SMART attributes: Power On Hours, Power Cycle Count, Reallocated sector count and wear leveling count.

    • Example of a unnessacarily overencrypted SSD's SMART data.

    Ask FixBot

    Add Comment

  6. Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Linux - SMART testing: step 6, image 1 of 1
    • If the Percentage used is near 100% (name might be different per SSD vendor), the drive must be replaced; it will likely keep working, but is at high risk of failing and it will be sudden. High usage isn't an issue, but the lifespan will be very limited. For testing, while SMART Extended is better, a quick test may be sufficient.

    • Ubuntu is not required for this step as long as the distro supports the ATA SMART access commands out of the box, such as distros like Debian.

    • eMMC devices do not present SMART data. This is normal on these eMMC Non-UFS devices. UFS devices might present SMART data if it is implemented on your machine.

    • To run a SMART Extended Self-Test, left click Start Self-Test. Select Extended from the drop-down menu.

    Ask FixBot

    Add Comment

  7. Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - NVMe: step 7, image 1 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - NVMe: step 7, image 2 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - NVMe: step 7, image 3 of 3
    • NVMe drives give different data than SATA SSDs - different metrics are used compared to SATA SSDs.

    • In the Attributes tab, locate the following SMART attributes: Available Spare (and Spare Threshold), Percentage used, Data Units (Written), Power Cycles, Power on hours, and Unsafe shutdown (less critical, but check!).

    • To access the NVMe logs, click on NVMe Errors.

    • To test the drive, select Perform Tests. Click Test type: and select Extended Self-Test.

    Ask FixBot

    Add Comment

  8. Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - If no data shows: step 8, image 1 of 2 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - If no data shows: step 8, image 2 of 2
    • If this occurs, read on - you MIGHT be able to salvage the situation.

    • In the event your drive adapter DOES NOT populate the data and shows this, you have to find a different adapter. However, the need for this can be verified in Terminal to make sure it is NOT a GUI issue with the following command: smartctl - H /dev/X (replace X with sdbX, X being the drive number if present).

    • If Terminal just says SMART Health Status: OK, the adapter you picked has issues in Parted Magic (likely due to a chipset blacklist). Pick another adapter as you're flying blind.

    Ask FixBot

    Add Comment

  9. Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - SATA: step 9, image 1 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - SATA: step 9, image 2 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - SATA: step 9, image 3 of 3
    • While high hours are not an indication of failure, the odds of a failure are much higher.

    • Select Disks from the desktop to open GSmartControl.

    • Select the hard disk you want to test. Click Attributes to read the SMART data.

    • Locate the following attributes: Reallocated Sector Count, Power On Time, Power Cycle Count and Wear Leveling Count.

    • In order to check the error logs, click Error Log. Any errors will be stored here. Some drives offer additional data, which can be accessed under Advanced.

    Ask FixBot

    Add Comment

  10. Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - Erasing SSDs - post 3/2026 builds: step 10, image 1 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - Erasing SSDs - post 3/2026 builds: step 10, image 2 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - Erasing SSDs - post 3/2026 builds: step 10, image 3 of 3
    • These steps apply to both NVMe and SATA SSDs - the relevant command is selected automatically now.

    • Everything about these builds is significantly changed. The 2025 build steps will not apply to these. However, I am leaving them in for users of old builds who either have lapsed subscriptions or did a one time purchase.

    • Select the SSD needing to be erased (Verification is optional but recommended) and click Continue.

    • Click Continue and then the "I understand this is permanent" box, then Continue again. The erase will proceed.

    Ask FixBot

    Add Comment

  11. Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - Erasing SSDs - post 3/2026 builds, NIST Purge: step 11, image 1 of 2 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - Erasing SSDs - post 3/2026 builds, NIST Purge: step 11, image 2 of 2
    • Before erasing the machine, you must fill this out in it's entirety:

    Ask FixBot

    Add Comment

  12. Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - Erasing SSDs - post 3/2026 builds, NIST Purge: step 12, image 1 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - Erasing SSDs - post 3/2026 builds, NIST Purge: step 12, image 2 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, Parted Magic - Erasing SSDs - post 3/2026 builds, NIST Purge: step 12, image 3 of 3
    • Newer Parted Magic builds support NIST Purge verification for regulated devices (HIPAA, FINRA, GLBA, SOC 2). Unless your shop has a certified secure environment, avoid retaining these drives due to liability; wipe and return them immediately to maintain chain of custody.

    • When needing to do a NIST Purge, you must toggle NIST Purge - select 100% to be safe (legally mandated for regulated clients). Add the drive S/N as the "asset tag" rather then the machine's serial# as the drive is the critical part that needs to be tracked.

    • Toggle NIST Purge ON (100% verification required for NIST certified erasures), select your SSD, and open Cert Info to ensure the form is complete. In the "asset tag" box, enter the drive S/N and client-assigned asset tag—or use the motherboard S/N and SSD S/N as a fallback if DMI auto-detection fails.

    • Once all certificate info is filled out, click Continue, check "I understand this is permanent", and hit Start Erase.

    • When finished, download and save the erase logs and compliance certificate—which serves as your client's official Certificate of Sanitization/Destruction—and ensure they read SUCCESS to be compliant. Print and deliver these to the client with your intake form, and store the wiped drive in a labeled, dated, and sealed ESD bag.

    • If the client demands destruction of the drive, you must generate a Certficate of Destruction (CoD). Only do this after erasing the drive. Process not shown due to iFixit platform photo limits.

    Ask FixBot

    Add Comment

  13. Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, *Legacy* Parted Magic - Erasing hard drives - pre 3/2026 builds: step 13, image 1 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, *Legacy* Parted Magic - Erasing hard drives - pre 3/2026 builds: step 13, image 2 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, *Legacy* Parted Magic - Erasing hard drives - pre 3/2026 builds: step 13, image 3 of 3
    • As of the 3/2026 builds, these steps only apply to 2025 and early 2026 builds. I am keeping them for legacy ISO users who still need them.

    • eMMC Note for Legacy Builds: If you are using an archived 2025 build to wipe a budget eMMC laptop (without UFS), standard SSD secure commands will not work. Instead of dd in the terminal, select Disk or Shred in the GUI to run a block-level erase. If you ever upgrade to 3/2026+, refer to the dedicated eMMC guide for the automated GUI process

    • The options available here that will work will vary based on what is supported by the firmware on the drive.

    • CAUTION: SATA SSDs with known firmware issues could be bricked with the ATA Secure Erase command set if the bug is severe. If you are easing a drive with known bad firmware with a high chance of bricking the SSD, select EXTERNAL and use Disk or Shred - do not use Nwipe as this puts unnecessary wear on SSDs, especially older 75TBW drives.

    • IF the drive does not support ATA Secure Erase (primarily older drives, extremely rare with SSDs), select External and use Shred or Disk to erase the drive. DO NOT USE Nwipe - THIS PUTS UNECESSARY WEAR ON SSDs

    • AHCI drives (M.2 SATA/2.5" drives/3.5" drives) When possible for security (and in the case of SSDs, reduced or mitigated drive wear), try to use the ATA Secure Erase option when possible, unless the drive has known bugs (see warning above).

    • If you can tolerate a little less security, Disk and Shred are faster then Nwipe, but at the expense of wipe security being compromised. It is fine for personal reuse but should not be used on a drive you are disposing of.

    • NVMe SSD Recomendation: When possible, use NVMe secure erase. This is instant because it destroys the encryption key on these drives so the data can no longer be read and does not need to zero out the entire drive.

    Ask FixBot

    Add Comment

  14. Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, *Legacy* Parted Magic - Erasing non-UFS eMMC - pre 3/2026 builds: step 14, image 1 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, *Legacy* Parted Magic - Erasing non-UFS eMMC - pre 3/2026 builds: step 14, image 2 of 3 Diagnosing and Erasing SSDs and eMMC - Parted magic Legacy and 3/26+ builds, *Legacy* Parted Magic - Erasing non-UFS eMMC - pre 3/2026 builds: step 14, image 3 of 3
    • Note: These steps only apply to older builds (pre-March 2026). If you are using a 3/26+ build, refer to the updated guide.

    • Non-UFS eMMC lacks SMART, fails without warning, and lacks hardware-level erase. Block-erasing limits them to NIST Clear. Avoid multi-pass overwrites (DoD/Gutmann) due to extreme wear, unless legally mandated. These steps are included for end users and non-regulated erases on budget eMMC devices (e.g., Celeron+eMMC HP 14/HP Stream).

    • Older Parted Magic builds do not support NIST Erase. Note that eMMC NIST Purge is legally dubious anyway, as hidden OP space and mmcblkboot partitions cannot be reliably erased by software. High-security compliance requires physical destruction.

    • Open Erase Disk and select Block Wiping (called External on very old builds). Choose either Disk or Shred (both do the same thing).

    • Select all "mmcblk" drives.

    • Note: Drives that cannot be wiped will throw an access error and close—this is a harmless nuisance error expected on older builds attempting to write to hardware-locked boot partitions—dismiss the error and let the main eMMC partition format.

    • Start the erase. This typically takes 20 to 25 minutes, though slow eMMC controllers may take up to 40 minutes.

    Ask FixBot

    Add Comment

Finish Line

Cancel: I did not complete this guide.

One other person completed this guide.

Nick

Member since: 11/10/09

104,395 Reputation

71 Guides authored

0 Guide Comments

Add Comment

View Statistics:

Past 24 Hours: 15

Past 7 Days: 187

Past 30 Days: 341

All Time: 1,060