Thanks, that's what I was thinking, but as the drive *seems* to be working properly in all other aspects I was hoping for a way to re-build the drive's firmware. I agree though. Thanks for sharing your thoughts.
Seagate's site says I'm out of warranty, I think I bought it a few months prior to the 5 year warranty's introduction. maybe I can find one to swap PCB's with. :P
Ok, SeaTools shows me that the drive is configured for 48 bit addressing, but the drive is reported as having a capacity of 137 GB I suppose this software just calculates the size using 1000B = 1KB instead of 1024B = 1KB
One interesting find in the SeaTools app, the "Max Native Address" is...
Vacunita -
I have tried seagate's tools, I don't recall what it determined so i'll run through that again to get specifics...
M1ckG -
The BIOS also sees the drive as 128 GB (consistantly on many dissimilar machines ranging from a few years old to less than a month old).
Wolluf -
Yeah, a...
bad block = failed drive, unfortunately there's just not much more to it than that. buy a new drive and transfer your data before you lose more blocks.
check the system and application event logs for any relevant information. You may see specific error messages appear at the same time as you have encountered problems. I have often seen indications of drive failiure in the event log.
Yes, I have done that. Under Disk Management it shows up with the dimensions I listed previously. Recently I bought a MacBook Pro, I tried connecting it to that also out of curiousity but again, the drive shows up as a 128 GB drive. No matter what OS, or update level, the highest drive capacity...
It is possible that the drive is partitioned, but not formatted or initialized and not partitioned, so it would show you a drive, or a part of a drive that is healthy, but cannot be utilized. can you see the file system type of the drive you are trying to access?
I have a 200 GB Seagate hard drive, regardless of what computer I connect it to it shows up as a 137,XXX,XXX,XXX byte (128GB) hard drive. I initially thought this was a matter of my BIOS being out of date or my OS not being fully patched, but as I tried to rectify those issues, the problem...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.