Hello, I am really new to Manjaro and among other problems I’m facing this one is the biggest thus far.
I am trying to erase/format my spare Samsung SSD so that I can use it in Manjaro, right now it is formatted to work in windows since I was using it in windows before.
I did try using google but all google gives me are results for when someone is actually installing Manjaro for the first time instead someone like me who has Manjaro already and is trying to figure out how to erase/format their SSD within Manjaro.
Any way, I opened up PartitionManager as suggested by a post I found with google but when I go to the SSD in the list using the option “New Partition Table” is grayed out. In fact, on every drive I have this is grayed out. The only drive I have that it’s not grayed out is my USB flash drive.
I have mounted the SSD which didn’t think of at all from the start, created a new partition table and then made the unallocated space allocated. Now I’m stuck again because when I mount or unmount the drive, it doesn’t seem to matter, it still shows up as the old SSD title and the same contents as before with windows.
This looks to me, that you only created pending operations (in KDE Partition Manager, right?) and forget to press apply button after that, take a look at the lower bottom window.
Right except that once it aborts the window freezes and the only way to get it working again seems to be to kill the process of the KDE partition manager.
I’ve tried to do this a few times now, each time with an error / saying it aborted and the window freezing up.
What is the more complicated way through the terminal? Maybe it’s somehow easier or works better.
Substitute sdX and sdX1 for the proper device and partition, such as sdh and sdh1.
BE VERY CAREFUL as your “drive letter” can change between reboots and based on which port it is plugged into, so that sdb can next time be sdf, and so forth.
You can use /dev/disk/by-id/ata-SAMSUNG-blahblahblah if you prefer to use the device name based on its serial number. To use the partition, just append -part1 to the end of the path.
Make sure you have exfatprogs instead of exfat-utils.
Then format the first (and only) partition with exfat.
sudo mkfs.exfat /dev/sdX1
Finally, for good measure…
sudo partprobe -s
UPDATE: I’ll leave the above steps for posterity, but the solution was much simpler. As suspected by @chomsky, the SSD was not unmounted prior to issuing the KDE Partition Manager commands. Hence, @lahpyrcopa could not modify nor reformat the drive.
For me the terminal way looks really advanced/complicated, maybe you can boot with a USB Stick/DVD and format your drive with Windows Partition Manager or maybe it works with KDE Partition Manager under USB Livelinux?
What happends when you only change the Partition Table from your Samsung Drive or only shred without creating a partition?
Btw. on your second screenshot where the error occurred, you missed to click/open Details… that info could also help or is it freezed there already? In this case, maybe you have to click on details very quick… befor it can freeze
Edit: It also could be highly possible that there is a sector damage on your SSD, i know a few tools for Windows that can repair/block this damage sectors, but i have no clue how to fix this issue under Linux, maybe someone can show us a Tool for Linux to scan broken sectors?
This process took entirely way too long to happen, I feel like that any way.
In any case I FINALLY got it to erase into an NTFS drive.
In order for the drive to properly erase/format I had to unmount it which is the error given in the details panel and I couldn’t see the details panel unbeknownst to me because for some reason several windows were opened on my second monitor.
Thanks for all of your help.
KDE Partition Manager: SMART Status Report
KDE Partition Manager: SMART Status Report
Date:
05/10/2021 10:26
Program version:
21.08.1
Backend:
pmsfdiskbackendplugin (1)
KDE Frameworks version:
5.85.0
Machine:
Linux jesse-ms7922 5.13.19-2-MANJARO #1 SMP PREEMPT Sun Sep 19 21:31:53 UTC 2021 x86_64
I marked @chomsky’s post as the solution, since it simplifies the answer for future readers of this thread, and moots the complexities from the latter replies.