Displaying 2 results from an estimated 2 matches for "y5fpd8g3neei".
2016 Jan 19
2
HDD badblocks
...zvMOlxUWcvKU6O2fSlhRfgF1v2XR+7pL
jf7E332bSml1W0NlA/fzM9HIXTgX3t+BJ9P0F1wjOLGuXuYf5zvdjXff4yjJlgGC
hVc6OEzUZrDM1EAE+Eu8ENqzVg6aTQGm17FkDRuKqVF3XXE4Ok5Pm0+scMjylVRX
V0yXKMzRH+T5IUJK6xnFU84Eadr7dl0EUf6f+EX61wDhhUauK3N5XnVNaOZ3dLom
fuTjk5Qg+BBHVQPG1/Ud4KK8sEZbB55zc7udinhbh45onn3oUGA4LtoA6wqqgHMJ
ue87YC/Y5FPd8G3neei/bVkGrr2EEWgSxJ2PQYxeiXda6trf8nzBNqz7vXK4/mDw
fAl4ie58Zd0vGbRAb2hB
=iezY
-----END PGP SIGNATURE-----
2016 Jan 18
2
HDD badblocks
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Not new: I can remember seeing DEC engineers cleaning up the contacts
on memory boards for a VAX 11/782 with a pencil eraser c.1985. It's
still a pretty standard first fix to reseat a card or connector.
On 18/01/16 15:47, Matt Garman wrote:
> That's strange, I expected the SMART test to show some issues.
> Personally, I'm still