Hello to creators of this wonderful software, that has become a de-facto standard for testing used hard drives.
I've recently had an issue with my Maxtor DiamondMax 9 drive, from september 2003, Model 6Y080L0, Code YAR41BWO. I burned the original PCB when I accidentally touched it with molex connector in the opposite orientation, and later the drive wouldn't spin. After that I put a different PCB from another Maxtor drive but from 2005, also the one without separate BIOS chip like mine, and my system booted successfully, though just once. Mobo reported "Smart command failed", but it booted and gave access to data. However, the head was making strange seek noise even when not expected to seek as much and was creating small delays in data access, but files could be read (sadly, I had no second drive in system to back them up). The next time I powered the system, though, it wouldn't boot and when put in another machine both partitions showed up in explorer, but were reported as "unformatted", and the next time system wouldn't even show them. Sentinel now sees the drive but can't read it's status. Is there any way to regain access to SMART parameters in Sentinel again, to refresh/recover them, and recover data from partitions (or at least see their filenames once more to know what remained "locked")?
Thanks in advance.
Problem with Maxtor DiamondMax 9, 80GB
- hdsentinel
- Site Admin
- Posts: 3128
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: Problem with Maxtor DiamondMax 9, 80GB
Thanks
Oh....
Yes, the best would be if you could immediately perform a backup when the drive started to working again, as it was not too safe to work in such condition. After the power cycle, the drive may use a different sector translation method - so then the original sectors may not be accessible - or may accessible only by wrong order which result that the partition table is still there and accessible - but all entries pointing to partitions point to wrong sectors.
The result is that the partitions seem "raw" (unformatted) and the files may not be available, even by data recovery tools - as the MFT may broken.
If the SMART commands do not work (and thus no health status could be displayed) it also confirms that the disk drive may not find the proper data self-monitoring data (error counters, data structures etc.) stored on the disk platters, so it may not be able to read/write the proper data sectors.
In Hard Disk Sentinel, you may try to inspect the "raw" sector contents, to verify if at least they can be read and contain data: please select Disk menu -> Surface test and after selecting the drive, click on the View button. Then click on any block of the disk surface map to view the "raw" contents of the sector.
If the sectors could be read and they show data (not all zeroes) then in theory, the data may be retrieved, but I'm afraid this could be done only by a special data recovery company as they can re-calculate the sector addressing and recover the original files.
Oh....
Yes, the best would be if you could immediately perform a backup when the drive started to working again, as it was not too safe to work in such condition. After the power cycle, the drive may use a different sector translation method - so then the original sectors may not be accessible - or may accessible only by wrong order which result that the partition table is still there and accessible - but all entries pointing to partitions point to wrong sectors.
The result is that the partitions seem "raw" (unformatted) and the files may not be available, even by data recovery tools - as the MFT may broken.
If the SMART commands do not work (and thus no health status could be displayed) it also confirms that the disk drive may not find the proper data self-monitoring data (error counters, data structures etc.) stored on the disk platters, so it may not be able to read/write the proper data sectors.
In Hard Disk Sentinel, you may try to inspect the "raw" sector contents, to verify if at least they can be read and contain data: please select Disk menu -> Surface test and after selecting the drive, click on the View button. Then click on any block of the disk surface map to view the "raw" contents of the sector.
If the sectors could be read and they show data (not all zeroes) then in theory, the data may be retrieved, but I'm afraid this could be done only by a special data recovery company as they can re-calculate the sector addressing and recover the original files.
Re: Problem with Maxtor DiamondMax 9, 80GB
That was very helpful.
The thing is that I first put a slightly different PCB, although both had no external BIOS chip and were fairly similar, one just had a few SMD components more. That board gave access to data, but seemingly would not write to disk, as I got some error in Windows when I tried to copy something. Some days after those first attempts to access data with a different PCB, I placed the second one, from a faulty drive I ordered online, and that one is the same as mine, but the disc behavior didn't change (BIOS recognizes it, I get SMART error before booting and no status in Sentinel). My PCB has a white sticker with some code F4FYA on it, the first replacement I put was M6FYA, and the current one is F4FYA again. Is there any point in trying yet another F4FYA board, as this one I ordered first was on a 2005 drive (though it didn't seem original) and the second one I can get is on a drive very similar to mine (same year, type, similar four-letter code (N,M,G,A vs my N,M,G,D)? As much as I'd like to retrieve data, I would also like to revive my 12 year old drive that (to date) has about 3000 days of operation, a little over 600 bad sectors (16% health) at the end of first partition, but partitions were later resized to leave the damaged part out of data area. I remain curious to see how long that impressive piece of technology can last.
I almost forgot - I also tested some partition recovery tools and one saw a lost partition of 86GB on the drive, but found no files on it. And something else - for the last 6-7 months my Maxtor inaccurately reported SMART parameters, like power-on time, power-on count and spin-up time. Power-on time, for instance, kept "resetting" to zero, every several days, but was counting power-on hours normally in the meantime. How was that possible?
The thing is that I first put a slightly different PCB, although both had no external BIOS chip and were fairly similar, one just had a few SMD components more. That board gave access to data, but seemingly would not write to disk, as I got some error in Windows when I tried to copy something. Some days after those first attempts to access data with a different PCB, I placed the second one, from a faulty drive I ordered online, and that one is the same as mine, but the disc behavior didn't change (BIOS recognizes it, I get SMART error before booting and no status in Sentinel). My PCB has a white sticker with some code F4FYA on it, the first replacement I put was M6FYA, and the current one is F4FYA again. Is there any point in trying yet another F4FYA board, as this one I ordered first was on a 2005 drive (though it didn't seem original) and the second one I can get is on a drive very similar to mine (same year, type, similar four-letter code (N,M,G,A vs my N,M,G,D)? As much as I'd like to retrieve data, I would also like to revive my 12 year old drive that (to date) has about 3000 days of operation, a little over 600 bad sectors (16% health) at the end of first partition, but partitions were later resized to leave the damaged part out of data area. I remain curious to see how long that impressive piece of technology can last.
I almost forgot - I also tested some partition recovery tools and one saw a lost partition of 86GB on the drive, but found no files on it. And something else - for the last 6-7 months my Maxtor inaccurately reported SMART parameters, like power-on time, power-on count and spin-up time. Power-on time, for instance, kept "resetting" to zero, every several days, but was counting power-on hours normally in the meantime. How was that possible?
- hdsentinel
- Site Admin
- Posts: 3128
- Joined: 2008.07.27. 17:00
- Location: Hungary
- Contact:
Re: Problem with Maxtor DiamondMax 9, 80GB
I'm sorry, but personally I do not really think that an other, 3rd PCB will make it working again
As the internal sector addressing may corrupted / confused, I suspect no other board (even 100% identical of the original one) would help.
Yes, if the disk surface (the sectors) can be read, it is possible that a recovery software may find the start of the partition(s) but the chance to find the actual files on it is very low.
Wow !!
How good could be to see a developer report (Report menu -> Send test report to developer option) when it was working!
Yes, personally I also try to collect information about older drives, especially if they have higher power on time - and especially if they already reported problems and the health is lower. I'm also always curious to see how long these hard disk drives can run - but I suspect your one really reached the end of its lifetime.
The incorrect values issue sounds really interesting. It would be nice to see some such reports to investigate them with more details as personally I've never saw such with Maxtors.
Generally, the raw "data" of the Power on time attribute on Maxtors reset periodically (it's normal) but the "Value" field also decreases. By using these two together, Hard Disk Sentinel calculates and reports the real power on time.
As the internal sector addressing may corrupted / confused, I suspect no other board (even 100% identical of the original one) would help.
Yes, if the disk surface (the sectors) can be read, it is possible that a recovery software may find the start of the partition(s) but the chance to find the actual files on it is very low.
Wow !!
How good could be to see a developer report (Report menu -> Send test report to developer option) when it was working!
Yes, personally I also try to collect information about older drives, especially if they have higher power on time - and especially if they already reported problems and the health is lower. I'm also always curious to see how long these hard disk drives can run - but I suspect your one really reached the end of its lifetime.
The incorrect values issue sounds really interesting. It would be nice to see some such reports to investigate them with more details as personally I've never saw such with Maxtors.
Generally, the raw "data" of the Power on time attribute on Maxtors reset periodically (it's normal) but the "Value" field also decreases. By using these two together, Hard Disk Sentinel calculates and reports the real power on time.
Re: Problem with Maxtor DiamondMax 9, 80GB
Pity, but thanks.
The recovery software I ran found 3 partitions on my system - two of something like 17GB, and the third of 86GB. The smaller ones contained some files, but I didn't recognize them - they are probably from a 40GB boot-drive I bought second-hand and even repartitioned later. No files were found on the third one - I suspect that's the 80GB Maxtor, only it's size was reported wrong.
Strangely, but, in my view, that Maxtor could run a significant more time to come! It had about 3000 power-on days but with "low-load", since I process many videos on relatively slow machines, and the drive spins for a long time doing little data access. However, the data I burned on about 2500 DVDs for others and myself was once stored on the drive, so at least about 10 TB of data was written and read from it (not counting some more in temporary files along the way), and it also hosted virtual-ram file in Windows for at least 11 years! Since it was the only drive, it often had to move/copy data from one area to another too, quickly moving the heads back and forward for lengths of time. Bad sectors started appearing this summer, at the end of a system partition where windows "hibernate" file was. Health decreased quickly from 96 to about 50-60, stabilizing at 16%. The drive first marked 4-5 sectors as "bad" after one power-failure several years ago (those might have not been "bad" at all, though, as it lost power during intensive write operations), but that increased to 17, than 22, 300 and finally 622 the 4 times it accessed the "hibernate" file recently (I noticed the access to it became unusually slow). It was a relatively small damaged area, but as a quick and safe fix I still "moved" the entire system partition by about 17GB - to the "healthiest" part of the surface, decreasing second partition size. Performance rose from 97-98 to 99 and even 100% shortly after, as RunOutCancel parameter improved. The drive had some areas of slower access, an occasional darker-green block or two on surface-scan, especially near the end of the partitions. The fault was mine - I rarely did backups, so the actively used area became rather small and was accessed often. Spin-up time was slowly increasing, but that SMART parameter was still good (green), there were some yellow exclamation marks on RunOutCancel (values were around 20-30-40), and a few other parameters tracking data access errors. The drive was hot from day one - always at least around 43 and reaching as far as 52 degrees in the summer! I think it's maximum temperature ever recorded was 56.
A few SMART parameters behaved "strangely". Power-on time, power-on count, and the oldest to exhibit the same kind of "weirdness" was spin-up time. Spin up time had a "saw"-like value pattern - increasing for days, than falling to a lower level, then increasing steadily again. Power-on time was often resetting to a value of about 10-15 days, then counted normally until the next sudden reset. Power-on count was the most interesting, as it kept resetting to lower values too, but with each boot of the system it would "add" a few hundred "starts" to the value!
I must admit, as much as I wanted my data back (not too much was there, luckily, as I backed up the drive at the end of August), even more I wanted to use it until it's very end!
Once again, thanks for a wonderful piece of software!
The recovery software I ran found 3 partitions on my system - two of something like 17GB, and the third of 86GB. The smaller ones contained some files, but I didn't recognize them - they are probably from a 40GB boot-drive I bought second-hand and even repartitioned later. No files were found on the third one - I suspect that's the 80GB Maxtor, only it's size was reported wrong.
Strangely, but, in my view, that Maxtor could run a significant more time to come! It had about 3000 power-on days but with "low-load", since I process many videos on relatively slow machines, and the drive spins for a long time doing little data access. However, the data I burned on about 2500 DVDs for others and myself was once stored on the drive, so at least about 10 TB of data was written and read from it (not counting some more in temporary files along the way), and it also hosted virtual-ram file in Windows for at least 11 years! Since it was the only drive, it often had to move/copy data from one area to another too, quickly moving the heads back and forward for lengths of time. Bad sectors started appearing this summer, at the end of a system partition where windows "hibernate" file was. Health decreased quickly from 96 to about 50-60, stabilizing at 16%. The drive first marked 4-5 sectors as "bad" after one power-failure several years ago (those might have not been "bad" at all, though, as it lost power during intensive write operations), but that increased to 17, than 22, 300 and finally 622 the 4 times it accessed the "hibernate" file recently (I noticed the access to it became unusually slow). It was a relatively small damaged area, but as a quick and safe fix I still "moved" the entire system partition by about 17GB - to the "healthiest" part of the surface, decreasing second partition size. Performance rose from 97-98 to 99 and even 100% shortly after, as RunOutCancel parameter improved. The drive had some areas of slower access, an occasional darker-green block or two on surface-scan, especially near the end of the partitions. The fault was mine - I rarely did backups, so the actively used area became rather small and was accessed often. Spin-up time was slowly increasing, but that SMART parameter was still good (green), there were some yellow exclamation marks on RunOutCancel (values were around 20-30-40), and a few other parameters tracking data access errors. The drive was hot from day one - always at least around 43 and reaching as far as 52 degrees in the summer! I think it's maximum temperature ever recorded was 56.
A few SMART parameters behaved "strangely". Power-on time, power-on count, and the oldest to exhibit the same kind of "weirdness" was spin-up time. Spin up time had a "saw"-like value pattern - increasing for days, than falling to a lower level, then increasing steadily again. Power-on time was often resetting to a value of about 10-15 days, then counted normally until the next sudden reset. Power-on count was the most interesting, as it kept resetting to lower values too, but with each boot of the system it would "add" a few hundred "starts" to the value!
I must admit, as much as I wanted my data back (not too much was there, luckily, as I backed up the drive at the end of August), even more I wanted to use it until it's very end!
Once again, thanks for a wonderful piece of software!