New
#11
Current Pending Sectors: How bad is it? How to stop it getting worse?
-
-
-
New #13
That's good to hear!
Sorry for the late reply, this isn't the only hardware issue I'm currently dealing with.
One quick question (sorry if this was already said in your own forum topic, I did read it but it's been a while), did you need to reformat the drive, or did SeaTools Bootable fix the issue without any significant data loss?
Copying 5 - 6 TB away and back again would admittedly be rather tedious, and probably also bad for the drive's health.
-
New #14
It was a while ago but I don't think I reformatted. Had my whole Steam library on there so I'd have remembered.That's good to hear!
Sorry for the late reply, this isn't the only hardware issue I'm currently dealing with.
One quick question (sorry if this was already said in your own forum topic, I did read it but it's been a while), did you need to reformat the drive, or did SeaTools Bootable fix the issue without any significant data loss?
Copying 5 - 6 TB away and back again would admittedly be rather tedious, and probably also bad for the drive's health.
-
New #15
Neat! Thanks.
__________________________________________________________________________________________________
Hey,
quick question about the check disk command.
The drive is 8TB (= 7.2 TB), with 5.7 TB filled. So a full chkdsk will probably take a very long time.
So before I end up with an unstoppable process taking a week to complete, I'd like to try a "quick" run of chkdisk first and see if that already fixes it.
I actually suspect now that this isn't really a pending sector count issue, more likely a generic "error code" Seagate uses (see bottom for explanation).
I've actually managed to backup the entire 8TB drive in question at this point, and it didn't give me any read-errors when doing so - unlike my old 1TB drive (which has ~16 pending sectors) where a single (thankfully unimportant) file was damaged and couldn't be accessed for backup.
Are these the right command line parameters if I want to do a "quick chkdisk"?
chkdsk U: /f /i /c
And would /perf tie up my entire PC and make it difficult to do anything else, or just use "some" extra resources as are available to speed up the checkdisk?
chkdsk U: /f /i /c /perf
And wouldn't /forceofflinefix make it safer to abort in case I mess it up somehow? 'Cause, if the drive stays "online/accessible" until the last step, doesn't this mean I have more time to just abort chkdisk safely?
chkdsk U: /f /i /c /perf /forceofflinefix
And this would be the "long" run in case the "quick run" doesn't work, "hunt down bad sectors by scrutinizing everything", I presume?
chkdsk U: /R /perf /forceofflinefix
__________________________________________________________________________________________________
This next bit is only relevant for any passers-by who have the same problem with their Seagate drive and are curious about my conclusion:
As I said, I suspect this isn't a real pending sector issue, probably just a generic error code Seagate uses.
I've seen "8 Pending Sectors, 8 Uncorrectable Sectors" for three different Seagate drives - those EXACT numbers. Two of mine, and @Billy Ball 's.
One is the 8TB drive described in this thread.
The other was a brandnew, less-than-1-month-old-at-the-time 12TB Seagate drive ... which fixed the error on its own the next time I turned it on. Even more interestingly, I still happened to have Crystal Disk Info running the day BEFORE the error occured WHILE I TURNED IT OFF, and then it didn't report that error - but right after turning it on 1 day later, it did. And then the day after that it was gone again when powering the drive back up. Haven't had any problems with that drive. False alarm. No reallocated sectors, either.
Quote
Related Discussions
