You are not logged in.
Pages: 1
Hi!
I bought OCZ Vector 128 GB about 5 months ago.
It served me well until yesterday.
I decided to shrink a EXT4 partition (sda3) and extend a NTFS partition (sda1).
Ofcourse I used Gparted.
During data moving process I encountered an error.
The only option here was to reboot my PC and then the problems started.
Now I can't access ANY of 3 partitions on my SSD. Every time I try to communicate with OCZ Vector I get I/O error.
The funny thing is that I can actually boot grub installed on it however I can't boot any OS.
But it is nothing strange compared to this: After I try to communicate with the SSD (mount/format/wipe/boot OS) my PC freezes and I need to reboot. After that the BIOS can not recognize the SSD until I pull the plug for like 5 seconds.
Does anybody know what could happen during the repartitioning process?
SOLVED by:
1. Clearing the memory cells:
$hdparm --user-master u --security-set-pass TEST /dev/sda
$hdparm --user-master u --security-erase TEST /dev/sda
2. Creating a new partition table (in this case it will be a GPT):
$gdisk /dev/sda
$o
$w
Last edited by Skitter (2013-12-19 00:01:26)
Offline
Do you have gparted's log?
If not, boot a liveCD and show us parted's list output for the drive.
Does anybody know what could happen during the repartitioning process?
Partitions could overlap, extend beyond the boundries, have been destroyed, the partition table could've been corrupted, goblins could've stolen your 0s, but left the 1s, etc. Wild speculation is pretty pointless without any evidence to base it on.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Do you have gparted's log?
If not, boot a liveCD and show us parted's list output for the drive.
Does anybody know what could happen during the repartitioning process?
Partitions could overlap, extend beyond the boundries, have been destroyed, the partition table could've been corrupted, goblins could've stolen your 0s, but left the 1s, etc. Wild speculation is pretty pointless without any evidence to base it on.
Thank you for your quick response.
Well, right now I'm working on Arch Linux which is booted from my USB stick (it is a copy of my SSD). Unfortunately I can not provide the logs because it was GParted live CD.
I managed to boot ArchLinux (USB stick) without even touching the SSD and it's still plugged.
Here you can see Gparted's list output for the SSD.
As you can see the partition table looks fine but I'm still afraid of mounting any of them because my PC will freeze and I will have to pull the plug again... It happens every time.
Last edited by Skitter (2013-12-19 00:01:18)
Offline
Don't resize partitions, copy data, delete, repartition, copy data. The I/O errors after the reboot might have a solution. Have you tried clearing the memory cells on the SSD (https://wiki.archlinux.org/index.php/SS … l_Clearing)? Note that doing so will erase all data on the device... hope you have backups.
Last edited by graysky (2013-12-18 22:55:30)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Don't resize partitions, copy data, delete, repartition, copy data. The I/O errors after the reboot might have a solution. Have you tried clearing the memory cells on the SSD (https://wiki.archlinux.org/index.php/SS … l_Clearing)? Note that doing so will erase all data on the device... hope you have backups.
Thank you for your valuable advice.
After cleaning the memory cells Gparted showed 119.24 GiB of unallocated space.
I tried to create a new partition table but it freezed for 5 minutes so I killed the process.
Now I can't even see the identification info of the drive.
skitter ~/$ sudo hdparm -I /dev/sda
/dev/sda:
HDIO_DRIVE_CMD(identify) failed: Input/output error
@Update
After reboot I can clear the memory cells again:
sudo hdparm --user-master u --security-erase TEST /dev/sda
security_password="TEST"
/dev/sda:
Issuing SECURITY_ERASE command, password="TEST", user=user
I will try to create the partition table again by using Gdisk.
Last edited by Skitter (2013-12-18 23:41:27)
Offline
...stop using gparted. Reclear the memory cells and partition from the cli using gdisk for gtp or fdisk for mbr.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
...stop using gparted. Reclear the memory cells and partition from the cli using gdisk for gtp or fdisk for mbr.
Finally! You saved my day guys.
I'm really greatful for your help.
Every day I learn something new and today you gave me another lesson.
My question is: What is wrong with GParted? Until now it worked just fine.
Offline
Dunno. It works fine until it doesn't
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Pages: 1