Has anyone experienced hard drive failures once Safeboot/Endpoint has been installed? If so do you believe this is just a case of the hard drive already having a failure on it but because Safeboot encrypts the drive, it rights to every defect so eventually will fail after a few days use or instantly?
So, just so I'm clear, a drive has failures on but can last a while in normal use. As soon as you put encryption on it, it will make the drive fail pretty soon after or instantly due to the way the drive is encrypted. Correct?
So not a fault of Safeboot but essentially Safeboot detects the error or runs into the error and then just crashes the laptop?
the drive is bad, it doesn't know it though. When any kind of encryption addresses those sectors, the drive remaps them to a reserve area.
eventually the drive runs out of "invisible" remap space, and starts reporting errors to the controller itself.
a bad block scan would do the same thing.
We don't detect bad blocks, that's the job of the drive itself. Even the OS doesnt do any bad block detection - the only way to tell if a block is bad, is to write something to it, read it, and see if you got the same result. That's not something the file system does ever, not even if you're using RAID.
OK I think I understand. That was kinda my point but I explained it badly. My point is the fact that the encryption, what ever encryption software is used, addresses every single sector on a drive, thus the issue of a bad drive then becomes apparent, where as before it could take months. I assume Endpoint does encrypt every single sector on a drive.
RE: What Does Chkdsk do to prevent a encryption failure?
chkdsk will just validate the file system - which is kind of pointless since FDE does not care about files at all. chkdsk /r will do exactly the same as encrypting the drive, ie kill it if it's too far gone already.
You're better of just querying the SMART status, that's usually 50% accurate (ie half the time the drive will fail even though SMART thinks it's good). Chkdsk isnt really going to help the root problem, which is bad drives will go terminal.