Birdie wrote:
Lenovo T500 Win XP Pro.
Installed Samsung SSD and used for a year. Had fast boot and no problems.
Then Samsung SSD would not boot.
Started boot but not finish. Tried Safe Mode etc. No Go.
See multiple things loading then quits.
Put in original HDD and used it for a week. No problems.
Bought a new SSD Samsung 860 Pro 256G.
Used Samsung app to clone new SSD.
This SSD fails immediately at boot.
Just says used Ctrl Alt Del to reboot.
Booted from my Macrium Rescue CD that I created from this laptop.
Booted ok.
Tried to use the Boot Fix in the Macrium Rescue CD.
Then tried to boot the new SSD again and it immediately failed.
Just says used Ctrl Alt Del to reboot.
Reinstalled original HDD and it booted just fine and I am now on the
laptop with this HDD.
Suggestions please to fix or whatever please ?
So, "Fern", in your other thread, you didn't tell us
the drive was an SSD.
You don't defragment SSDs, for the most part. The only exception,
is something to do with slow "Copy On Write" or COW, which happens
when VSS shadows are used. WinXP shadows don't persist across reboots
(unlike other OSes), so such a usage pattern is less likely to happen.
You can "just use" an SSD, as it appears you've been doing.
However, you can make life for the SSD a bit better, with
some preparation.
1) Place one partition on the SSD.
2) Align the partition to 1MB boundaries. That's so "clusters" in
NTFS, align with "pages" in the SSD flash chips. This results
in no need for residual (fractional) writes at the end of a file
copy or a file save.
3) Disable "Last Accessed". NTFS has several time stamps. One of the
stamps keeps track of the last time the file was read (rather than
written). This means the directory entry for the file gets updated
every time you "touch" the file. and that's extra flash cycles.
The more modern OSes, when they sniff "SSD", they disable that
feature automatically. In WinXP, you use a manual recipe for that.
4) WinXP might not have TRIM in the driver - see if the Samsung
Toolbox offers its own TRIM function. What TRIM does, is uses
an interface, telling the drive "where all the white space is
on the drive". The white space can then be used for the next
write, effectively making the spares pool larger and allowing
the disk to do better management of the Flash. A tradeoff of
using it might be, that immediately afterwards, using an "undelete"
program might not work right. If you're an inveterate file eraser
who needs undelete, you'll need to Google for the tradeoffs of
using TRIM, before using TRIM.
I doubt I can find the OCZ article from long ago, with the list of
things to do, so this will have to suffice. Not everything on the
following article is absolutely necessary, but at least it gives
you a list to look at. For example, the necessary "fsutil" command
is there for you to use (to set the NTFS policy).
https://www.prime-expert.com/article...ased-netbooks/
You can Repair Install using a WinXP installer CD, but then you
have to install all the Windows Update stuff again. Which is a
lot of work. A Repair Install will keep your personal files,
programs and settings, and allow the broken SSD to boot again
(by putting back whatever is missing).
You could compare the System32 files from the working HDD and
the (partially broken) SSD. But again, that's a lot of work.
The SSD can be evaluated with the Samsung Toolbox, to see whether
there is a serious issue in S.M.A.R.T, such as wear life exhausted.
You can clone the "working" HDD to the "new" SSD if you want,
but if using Macrium, you'd probably want to use their alignment
dialog to get the 1MB alignment while copying the HDD. That involves
clicking "Next", then "Back", then highlighting the partition needing
alignment, bringing up the dialog by using a link below the disk
display.
http://reflect.macrium.com/help/v5/p..._alignment.htm
Around frame 6 here, you can see me using the alignment/resize dialog.
By pressing Next, then Back, then selecting the partition, then
accessing the dialog box.
https://s22.postimg.cc/487zw4g1d/Clone_Disk.gif
Paul