Personal computing discussed
Moderators: renee, morphine, Steel
Igor_Kavinski wrote:You can try a different cloning program. If that also fails, the SSD's internal filesystem may be borked. You can keep the SSD connected to the PC for a few hours to see if the SSD's firmware manages to fix the issue on its own. Failing that, RMA might be the only option.
zEfn wrote:Igor_Kavinski wrote:You can try a different cloning program. If that also fails, the SSD's internal filesystem may be borked. You can keep the SSD connected to the PC for a few hours to see if the SSD's firmware manages to fix the issue on its own. Failing that, RMA might be the only option.
Also does kingston has software for my ssd?
Igor_Kavinski wrote:zEfn wrote:Igor_Kavinski wrote:You can try a different cloning program. If that also fails, the SSD's internal filesystem may be borked. You can keep the SSD connected to the PC for a few hours to see if the SSD's firmware manages to fix the issue on its own. Failing that, RMA might be the only option.
Also does kingston has software for my ssd?
You can try this: https://www.kingston.com/en/support/tec ... ssdmanager
zEfn wrote:Igor_Kavinski wrote:zEfn wrote:Also does kingston has software for my ssd?
You can try this: https://www.kingston.com/en/support/tec ... ssdmanager
How my ssd disk looks like in file explorer : https://prntscr.com/qkt3y1
Also even though my cloning process failed, my ssd has same partitions as my hdd : https://prntscr.com/qkt4bz
Disk 0 is my hdd drive
Disk 1 is my ssd drive
Maybe because my ssd has same partitions, thats why i cant use my ssd?
I dont know i am very lost right now.
zEfn wrote:https://prntscr.com/qkt9aj
Says basically samething when i try to open my ssd disk in file explorer.
Igor_Kavinski wrote:zEfn wrote:https://prntscr.com/qkt9aj
Says basically samething when i try to open my ssd disk in file explorer.
Search for cmd in the start menu and right click it and select "Run as Administrator". Then run the command.
Igor_Kavinski wrote:After disconnecting HDD, you do not need Windows to boot from the CD burned with the secure erase ISO. Your PC/laptop will boot from the CD. Select EMM386 (Max Memory). Then it should stop at a command prompt R:\. Type hdderase and enter Y to proceed. Once it completes, remove the CD, connect your HDD and check if the SSD is accessible in Windows.
Igor_Kavinski wrote:You can't delete the partitions as the firmware has locked the drive. Try the bootcd and see if it lets you erase the drive.
Igor_Kavinski wrote:In disk management, right click drive E and select Delete partition. If that works, delete the other SSD partitions and use the Kingston software to secure erase.
If deleting partition in Disk Management does not work, download this: http://cmrr.ucsd.edu/_files/hdd-erase-web.zip
Extract the contents of this zip file. You will see a file called HDDErase.iso. Double click it. It will ask for CD to burn to. After that, disconnect HDD, put the CD in and boot your PC. Select EMM386 (Max Memory) from the list of options shown. Then it should stop at a command prompt R:\. Type hdderase and enter Y to proceed. Once it completes, remove the CD, connect your HDD and check if the SSD is accessible in Windows.
zEfn wrote:Igor_Kavinski wrote:In disk management, right click drive E and select Delete partition. If that works, delete the other SSD partitions and use the Kingston software to secure erase.
If deleting partition in Disk Management does not work, download this: http://cmrr.ucsd.edu/_files/hdd-erase-web.zip
Extract the contents of this zip file. You will see a file called HDDErase.iso. Double click it. It will ask for CD to burn to. After that, disconnect HDD, put the CD in and boot your PC. Select EMM386 (Max Memory) from the list of options shown. Then it should stop at a command prompt R:\. Type hdderase and enter Y to proceed. Once it completes, remove the CD, connect your HDD and check if the SSD is accessible in Windows.
I can only delete volume in disk management, where are the partitions.
Igor_Kavinski wrote:For disk 1 in Disk Management, delete all volumes and then it should show the full space 447GB as Unallocated. After that, you can secure erase from Kingston SSD software. Otherwise, find a 700MB CD-R to burn the iso.
Igor_Kavinski wrote:For disk 1 in Disk Management, delete all volumes and then it should show the full space 447GB as Unallocated. After that, you can secure erase from Kingston SSD software. Otherwise, find a 700MB CD-R to burn the iso.
Igor_Kavinski wrote:That's good that you were able to delete one partition. Right click the Unallocated space and create new partition and format it as NTFS and see if you can access it and copy some files to it.
I don't think deleting partitions from cmd using diskpart would be any different from Disk Management console. You are welcome to try if you want to, though.
Igor_Kavinski wrote:That's good that you were able to delete one partition. Right click the Unallocated space and create new partition and format it as NTFS and see if you can access it and copy some files to it.
I don't think deleting partitions from cmd using diskpart would be any different from Disk Management console. You are welcome to try if you want to, though.
Igor_Kavinski wrote:Depends on your intended purpose for the SSD. If you want to use the SSD to boot Windows, clean install Windows on the SSD with the HDD removed and WIndows shouldn't be bothered by the existence of these partitions and should install normally. However, if you want to use the SSD just for storage (not sure why you would want Windows working from spinning rust in this case), you are fine and can leave everything as is.
just brew it! wrote:You may have received a defective SSD. If doing a secure erase doesn't fix it, it is time for an RMA.