![]() ![]() I'd suggest to please use Report -> Send test report to developer option, then I can check the complete status. This is normal - and you do not need to worry about it now, as only 1% of the total lifetime used. This is completely independent from software, OS, restarts and so: as the amount of written data increases, the health slowly but surely decreases. If you want, you may check how that attribute changes with time on the S.M.A.R.T. This is what you can see in the text description area: there are no problems found, but the 173 Erase Count attribute determines the overall health of the device. If there are no further problems found, Hard Disk Sentinel reads these attributes which determine the complete health of the solid state device. The "wear-leveling" feature of the SSD tries to hide/minimise this effect but generally the SSD device reports the overall health of the memory cells by various attributes. Yes, the health is not 100%, "only" 99% - but it is still "EXCELLENT" see next to the health % bar.Īs you may know, the memory cells in solid state devices experience wear during each write operations and each cells tolerate only a limited number of overwrite passes. No, I can confirm that you do not need to worry.Īs the software displays the status is PERFECT, there are no problems with the SSD. (see the bottom of the page about SSD health) Not sure why you did not find the answer, as it is already discussed on the forum: I can confirm that it is completely normal and expected, nothing "can be done about this" (and nothing needs to be done). SMART perfect.Thanks for the information and sorry for the confusion. The drive gets an A+ rating in AData's test utilities. So I turned the power button off for a second, then turned it back on, and then the Secure Erase utility would run to completion. The XPC does not support hot swapping, but the AData drive was in an external ESATA drive cradle. It said to try hot swapping the drive and running Secure Erase again. It would start the Secure Erase utility, but it would fail because the drive was locked. I loaded Win7 on an old Shuttle XPC that is working as a doorstop in my office and installed AData's SSD tool box. It would very quickly hang at about 6% completion. One of my PCs has a Secure Erase utility in its BIOS. At least I couldn't find it in the menus. It said that the GParted boot disk included a Secure Erase feature for SSDs. I found an HP KB article on Secure Erase for SSDs. This only became apparent after downloading and installing. I tried a variety of third party utilities that said on their free trial download pages that they did SSD secure erase, but they did not state that this feature was only enabled by purchasing a license. Even if you are not concerned about your data security, the reset is probably a good start in troubleshooting. In addition to wiping data, manufacturers' Secure Erase utilities generally reset SSDs to factory parameters. Unfortunately, re-partitioning and formatting does not remove data. I would expect a format the clean OS install to be good, but if you need to do more see this post: I will run the Adata drive through Adata’s utilities on a Windows system and see what it says about itself. I have seen this sort of weird random behaviour on mechanical drives before but never on an SSD. Data transfer speed on the restoration was almost three times as fast. I replaced the hard drive with another SSD drive, reloaded the system, and then restored everything from the network location. I backed everything up to a network location. Curiously I could not do this via USB or Esata because of file splice errors on larger files. Sometimes Gparted would show two partitions where there should only be one.Įventually I was able to backup all data and various application folders from my profile using the Live Disk. ![]() Sometimes booting to the Live Disk would show the system partition properly, sometimes not. ![]() When it did boot properly, the system did not seem entirely stable. Sometimes it would boot from the boot menu, sometimes not. Sometimes I would get to the boot menu before failure, sometimes not. I would shut it down and it wouldn’t reboot next time. And sometimes it would boot properly again. It might wander on to a variety of different things. It might go into a loop coming back to the same message again. Suddenly at boot a message started to come up saying that read/writes were being attempted outside hd0. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |