Now I am a tiny bit confused re setting up a used SSD for a clean install and I have used the DISKPART clean for this as I really am not that keen on relying on just a format.
Now I am wondering how I find this LBA on drives that I intend cleaning because that thread went on to say that drives can be bricked if the LBA 63 is wiped.
Now I am not an expert by any means and I am also wondering when I buy a brand new drive is this LBA 63 already on the drive? or is it created as a permanent feature of that drive by doing a clean install. To me it doesn't make much sense if that is what happens?
In my simple mind a drive is a drive and apart from the controller the "blocks" are just empty spaces.
My Computer
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Own build (new) Desk1 / Asus ROG Win 7 / Desk2 1st build
OS
Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
One other Desktop (tester) and spare Toshba laptop both with SSD's
Running Kaspersky 2016 ISS on all machines config'd identically
Logitec audio stereo systems on each machine (x3)
Canon MG5250MFC
Router/modem TP-Link running WPA2SK
Hi,
I doubt using the clean does any harm but clean all I doubt that is really needed
Steve and wolfgang have posted the clean operation hundreds of times
My Computer
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom assembled by me :}
OS
Win-7-Pro64bit 7-H-Prem-64bit
CPU
i7-5930K 2nd i9-9940x both water blocked VRM's too
2nd ASUS X299 Apex/Intel i9-9940x with Custom water loop/7H-Prem-x64/Corsair 450D case/Ram Trident-z 3600C16 4x8gb / Samsung970Evo plus 500gb SSD/Dual ssd EZ swap evo/PSU EVGA SuperNova 1200w-P2 80+Platinum/GPU Titan Xp /8-ML-140 on push-pull on 2-280GTX rads
Thanks mate like I have said to quite a few members who have asked I clean SSD's as a matter of course and the member I have been trying to help is adamant about not using DISKPART so I went looking anyway.
That is when I found that old thread and was wondering what they were discussing about in such great detail re that LBA 63. Anyway not to worry I am really just a simple user and really don't understand that jargon stuff.
My Computer
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Own build (new) Desk1 / Asus ROG Win 7 / Desk2 1st build
OS
Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
One other Desktop (tester) and spare Toshba laptop both with SSD's
Running Kaspersky 2016 ISS on all machines config'd identically
Logitec audio stereo systems on each machine (x3)
Canon MG5250MFC
Router/modem TP-Link running WPA2SK
Hi, there is 2 ways to load Win7 (I refer to Legacy install not UEFI).
If you take the used SSD and remove all partitions including the 100 Mb system reserved (MBR) and in effect make the whole disk Raw.
Then when you install Windows the system will set up a new 100Mb (MBR) and load a new "C" drive with the OS.
If you format the whole drive first in NTFS then install Windows you will not see a new 100Mb (MBR) you will only see a new "C" drive as the whole partition and the MBR will be incorporated within it.
It is not necessary to wipe the SSD clean this will only give it extra read and writes that is just extra work for no real reward.
I feel the second method has merit because when taking an Image of the OS the MBR can not be mistakenly omitted.
I often see people that have restored their system from an Image and then they can't Boot and I think it is because in the process of making the Image they have not incorporated the 100Mb MBR I.E. they did not Image the whole disk only the "C" drive sector.
Wayne
My Computer
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Owner Builder
OS
Windows 7 Ultimate x64 SP1 OEM
CPU
Intel i7 3930K
Motherboard
Asus X79 Deluxe
Memory
Kingston Genesis KHX2133C11D3K4/32G
Graphics Card(s)
Asus RTX 2070 Ti Turbo fan series
Sound Card
Creative Sound Blaster ZXR
Monitor(s) Displays
Samsung U32J39 UHD
Screen Resolution
3840 x 2160
Hard Drives
Samsung 860 Pro 256 GB
OCZ Vertex 4 512GB
Western Digital Black 4TB
PSU
Corsair AX850
Case
Gigabyte
Cooling
Push - Pull 120 mm Noctua PWM, Scythe Big Shuriken 2 Rev. B
Keyboard
Logitech K800 Backlit
Mouse
Logitech MX2 Master
Internet Speed
NBN 25 Mbps
Antivirus
Kaspersky Internet Security
Browser
Mozilla FireFox
Other Info
TP-Link Archer VR600v
Sennheiser TR220 WiFi Head Phones.
Hi,
This is the only jargon I bother to remember compliments of Wolfgang and Steve
Diskpart
List disk
Select disk n (where n is the letter that was given for your SSD in List disk)
Clean
Create partition primary align=1024
Format fs=ntfs quick
Active (assuming you want to install an OS)
Exit
My Computer
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom assembled by me :}
OS
Win-7-Pro64bit 7-H-Prem-64bit
CPU
i7-5930K 2nd i9-9940x both water blocked VRM's too
2nd ASUS X299 Apex/Intel i9-9940x with Custom water loop/7H-Prem-x64/Corsair 450D case/Ram Trident-z 3600C16 4x8gb / Samsung970Evo plus 500gb SSD/Dual ssd EZ swap evo/PSU EVGA SuperNova 1200w-P2 80+Platinum/GPU Titan Xp /8-ML-140 on push-pull on 2-280GTX rads
I often see people that have restored their system from an Image and then they can't Boot and I think it is because in the process of making the Image they have not incorporated the 100Mb MBR I.E. they did not Image the whole disk only the "C" drive sector.
Yep I agree Wayne and I used to use what Mike has posted too way back but now I just do it up to clean and format it seems to work for me without any nasty little surprises.
My Computer
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Own build (new) Desk1 / Asus ROG Win 7 / Desk2 1st build
OS
Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
One other Desktop (tester) and spare Toshba laptop both with SSD's
Running Kaspersky 2016 ISS on all machines config'd identically
Logitec audio stereo systems on each machine (x3)
Canon MG5250MFC
Router/modem TP-Link running WPA2SK