![]() SMART values give you a glimpse into the drive’s internal health, but they don’t tell you for sure that it’s going to fail or that it’s fine. So, Is Instant Karma gonna get me or is it reasonable for me to continue with my cautious approach? I’m hoping that some hardware gals/guys can weigh-in with their expertise. ![]() Instant Conundrum! BTW, Image 1 gives the drive’s specs. Well, Speccy says the “real” count is 121 and the drive’s Health Status is “Good” (see attached image 2). The count has not changed.Īnd then my subconscious smacked me in the head and said “Why not see what Speccy has to say”. However, the count of reallocated sectors didn’t seem very high to me (see attached image 1) so I ruminated about whether to soon but a new drive or just keep an eye on the count once a week. I did some research and found some opinions that catastrophic failure could be imminent. Recently, CrystalDiskInfo has been warning me that my “Reallocated Sectors Count” on the Data Drive is too high. Periodically I run CrystalDiskInfo in order to view the S.M.A.R.T. The System is on the primary and I use the other one as a Data drive. Since then, another pending sector has turned up.My desktop has 2 spinning platter disk drives. (C7) Ultra DMA CRC Error Count 200 200 0 0 ok (C6) Offline Uncorrectable 100 253 0 0 ok (C5) Current Pending Sector 200 200 0 10 warning (C4) Reallocated Event Count 200 200 0 0 ok (C0) Unsafe Shutdown Count 200 200 0 148 ok (0B) Calibration Retry Count 100 100 0 0 ok ![]() (09) Power On Hours Count 94 94 0 4860 ok (05) Reallocated Sector Count 200 200 140 0 ok I am facing a similar issue, and didn’t want to start a new thread. But if you want to mess with this more, then try killing the partition, and long-formatting and see what happens. If I was telling this to like a user/customer or photographer for example I’d say RMA the drive and call it a night. But I’d be watching it like a hawk and be sure that whatever is on the disk that there’s a backup copy of it. Once the firmware deals with it it and no more show up, then, I might trust it. You either need pro tools to do it, or you can keep trying stuff to trigger writes to them to get the firmware to handle it. Right this moment I wouldn’t trust the disk till they are mapped out by the disk & firmware itself. And these “diagnostics” and digging around are first now exposing them. I think they were there before, from day one. These 561 bad sectors may have been here before, or they may have developed in the past day or two. We need to make the disk’s firmware put these in the G-list (grown defect list) by itself. We will need to kill the partition and long-format it. So they will sit in limbo until we call enough attention to them, NTFS is aware of these and will not make use of them. But checkdisk has now remapped them on a high level. There needs to be write activity to those sectors. The disk’s firmware has yet to even start dealing with these. In “doing stuff” chkdsk found more bad sectors and is telling the o/s, via the metafiles, to not use those. Then the reallocated count will go up and the pending count will go down.Ĭhkdsk remapped sectors on the logical partition level, not the disk low-level. Where did they come from and why? The disk has not re-mapped them yet, and probably won’t until some write operations are done on them. Ohh dear… according to that, you’ve got 561 unstable sectors. They kinda popped up “just like that” but not all at once. And I’ve personally got a disk with 3 reallocated sectors that I fully trust. It’s when the smart values keep increasing rapidly on their own over a short time that’s when you’ve got a bad disk.Ī few bad sectors doesn’t mean the drive is toast. I would say this disk is still quite healthy otherwise. So you have to give it a swift kick in the - from time to time. Normally all this happens behind the scenes, sometimes it doesn’t. You can also wait and see if the internal “data lifeguard” background scans get around to remapping this faulted sector, all by itself. It would then flag the disk as good again. You can “null” out or set CrystalDisk’s Reallocated sector count to allow for the 1 bad sector. Then CrystalDisk will consider the Reallocated sector count to be bad and *STILL* flag your disk as bad. Of course, zeroing means you will need to backup your data. Doing CHKDSK with scan for bad sectors might also “encourage” the disk to remap the failed sector. And then your Reallocated Sectors Count will go up by 1. Sometimes a zero-write to the whole disk will force that 1 sector to be re-mapped. Looks like there is a problem with 1 sector that hasn’t been reallocated yet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |