I still prefer a big hard drive with at least 2TB storage space for most of my files are panorama and landscape photos in Tiff format which can eat up storage space really quick like Homer Simpson in a all-you-can-eat buffet. It is tempting especially given that someone is selling 1TB SanDisk Ultra SSD for only MYR 905, It's a ACER Predator 17 with removable dvd-drive, which I replaced it with the ejectable cooling fa cooling fan, which even though it only lowers the temperature down between 2-3 degree Celsius, still helps a bit to cool down the laptop. When one of the HDD have failed then just replace it without the risk of losing any data. Doing so you does not need to worry about HDD failing ever again. You using Win 10 and have empty SATA port? Why not buy another HDD and make RAID-1 with this HDD. Since it's on RAID-1 then I just keep using it to see when it will fail. But I have a HDD in NAS that have the value but have stuck at 67 value for months. If the value keep increasing everyday then you know better to replace it. The thing is, it does not necessarily means the HDD will fail in short time. This is a serious shortcoming, for if such a drive contains marginal sectors that consistently fail only after some time has passed following a successful write operation, then the drive will never remap these problem sectors. However some drives will not immediately remap such sectors when written instead the drive will first attempt to write to the problem sector and if the write operation is successful then the sector will be marked good (in this case, the "Reallocation Event Count" (0xC4) will not be increased). Read errors on a sector will not remap the sector immediately (since the correct value cannot be read and so the value to remap is not known, and also it might become readable later) instead, the drive firmware remembers that the sector needs to be remapped, and will remap it the next time it's written. If an unstable sector is subsequently read successfully, the sector is remapped and this value is decreased. Count of "unstable" sectors (waiting to be remapped, because of unrecoverable read errors).
0 kommentar(er)
