> I don't think that would be the case. The old drive is a WD Raptor.
> It's working once more after I did the USB enclosure and wiping
> partition trick. The new drive is a Crucial SSD. A SSD should draw even
> less power than a regular drive as far as I know?
Given the BIOS problem, the lower-level the problem, the more likely.
So, a file-system corruption seems like an extremely unlikely explanation.
A partition corruption seems less unlikely.
Yet a hardware problem seems out of the question since you can
reproduce it.
OTOH if it happens on two identical drives, it could be an
incompatibility between the drives and the motherboard's BIOS.
I've heard of various cases of such incompatibilities for SSD disks.
I'm not sure why that is, but my understanding is that part of the reason
can be that while SSD disks are fast in general (e.g. they can boot your
machine very fast), they can be really slow at "initialization" time
(the underlying reason being that to provide good wear-leveling, no part
of the drive can be "special", so at initialization time, the drive's
firmware often needs to look "all over the SSD" in order to find the
"start" of the drive, which can take a very long time).
And indeed, such "slow initialization" can depend on the state of the
drive, so after a clean install, the initialization may be faster than
after installing gigabytes of data on it, which could explain why it
boots fine at first and later hangs after copying your backup.
Just a wild guess.
Stefan
_______________________________________________
mlug mailing list
[email protected]
https://bureau.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
