problem with hdd and ssd/formating system restore
I don't know if this question belongs here or in the w8 section but here goes. 2 days ago my relatively new awesome self built gaming pc froze so i reset it and when it came back on it said that windows was damaged and needed repair. Now i tried this and it didnt do anything just said "preparing repair " and after a while went into black. so i thought that the best way to go around the problem would be to just format both drives (ssd and the hdd) and start from scratch seeing as i didnt have anything irreplacable on storage. Now i cant get acess to the ssd at all it seems, if i boot the pc with the sata connected to it the pc will just boot from the damaged ssd drive irregardless if i sett the boot prio or force it from the optical drive. If i unplug the ssd im able to format and install windows on my hdd, BUT its not really formatted because all the old stuff is still on it and takes upp space and causes clutter. anyone have any tips on how to just wipe them both clean? as stated i have nothing on them that i cant stand to loose. I just want to start with a blank pc again just as when i buildt it. Thanks for any insight or help.
RealBeast said:What model SSD? Does you motherboard bios have the ability to secure erase your SSD?
Will the machine currently boot from the HDD if the SSD is detached?
the ssd is a 120 gb kingston ssd its modelnr is v300 SSDnow.
the HDD I have is a seagate baracude 7200 rpm 1 tb disk. Yes the pc boots fine if I detach the sata cable from the SSD so its only the hdd. but as mentioned the hdd is not completly formated even though i tried, it has about 70 gb of unacounted missing space. thanks for your reply
also forgot to answer your bios question. I have no idea if my bios has the abilety to erase the ssd or hdd, my mobo is a republic of gamers fromula vi z87 haswell compatible mobo, had the newest bios from asus's site before the disks went crazy. dunno if the bios remains the updated one when i try to do system restores. also can mention that if i have both discs connected i only get the hdd up in boot prio on ez bios. i can still force a boot (a failed one) from the kingston SSD but it doesnt show up in the boot prio, only in the "boot from menu"
I would download Parted Magic from HERE and burn it to a CD -- you can then startup from the CD and secure erase your SSD. Then check your SSD integrity with Crystaldiskinfo from HERE to determine if the drive is good.
After that, you can disconnect the SSD and boot from the Windows installer disk, use a command prompt and then use diskpart commands to erase your HDD. In the command prompt box type:
select disk n (where n is the HDD)
The disk will then be unallocated. I would then install Windows to the SSD (with the HDD not attached) assuming the drive is okay from the above check. Then after the install, attach the HDD and format it.
(Some of the newer bios have a utility built in to do a secure erase usually on the last bios page, so you might check your motherboard manual, if that is available you would not need Parted Magic.)
mrpotato said:okay i will try this, any ideas on why the HDD wont completly format though? even when it is the only drive attached?
To clean a drive at the point of an install one thing that you can do is a custom install, and as the first step delete all partitions on the target HDD.
mrpotato said:that is the problem though, i do use an optical version of w8 (dvd) and it still wont let me clean it... even though i delete entire partitions also checked if bios has ssd erase and it does, but my SSD doesnt show up in the erase page so i cant nuke it from there
You really should be able to get to a command prompt window with the W8 installer disk in the preinstall environment,where another awesome tool -- diskpart -- is available. Diskpart is old school, but quite powerful with loads of option. HERE is a syntax summary that will give you an idea of some of things that you can do.
mrpotato said:Ok thanks man will try this out. Apriciate you taking the time to help out a newbie like me.
We were all newbs in the beginning, which sadly for me was when DOS was the newest thing and memory was measured in small numbers of kilobytes.