![]() ![]() If the device is valid and it really contains an ext2/ext3/ext4įilesystem (and not swap or ufs or something else), then the superblock The superblock could not be read or does not describe a valid ext2/ext3/ext4įilesystem. Sadly fsck doesn’t seem to work either, it will return this if i run it with /dev/sda (running e2fsck with the superblock will return same error): fsck from util-linux 2.37įsck.ext2: Bad magic number in super-block while trying to open /dev/sda I cannot use dd or similar tools to shred the data of the hard drive either, they seem get stuck on the operation and i have to kill their tasks. Input/Output error during write on /dev/sda I cannot in any shape or form do any writing operations to the drive, if i try to reformat, resize or delete a partition in gparted, it returns this error: Recover files with gpart, but only in read mode Identify partitions (gparted can see the filetype and size of the partitions) With the live iso, i tried to diagnose and repair the partitions but it was no much help. After 20% completion, the pc crashed and i cannot boot from the ssd. However i was very stupid that night, and decided to run wipe in the same hard drive it was running from. ![]() #KINGSTON SSD MANAGER CANT SECURE ERASE INSTALL#I was trying to destroy my own data using the tool “wipe” for then securely replace it with a fresh install of Manjaro. So i am writing this in a live iso of manjaro on the same computer the ssd got corrupted. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |