I moved the external drive to a different USB 3.0 port on the computer. I think it is unfair to load too much into one issue. BUT I'll do that in a separate new question. NOTE: Assuming the USB port swap has no effect I will probably open a follow-up question about which brand of drive to get. I do not have a substitute power supply to try. Once a drive starts producing errors in the event log I tend to mistrust it.ĭisassembling the drive does not seem worth it in this situation (no irreplaceable data). Since the drive continues to generate Disk errors in the Windows system event log it seems something is wrong even if the full tests (chkdsk and SeaTools) found nothing. It is about the same cost as a new drive, and my own further use for it is limited. Since it is just the one drive, the cost of HDDRegenerator or a similar utility that works on a USB drive does not seem warranted. If you're interested, my reasoning follows: I will first try a different USB port and if the errors continue then I will replace the drive. There have been no further crashes.Īs for the external hard drive, my conclusions based on all your inputs: That is a mystery for another time, I guess. Any suggestions for what to do next to determine whether the drive is truly having a problem? MY QUESTION: It seems the Event Viewer sees disk problems yet chkdsk and seatools find nothing. Seagate SeaTools for Windows quick test finds no problems. Interspersed are Warnings Event ID 51, Disk sample messages:Īn error was detected on device \Device\Harddisk3\DR9 during a paging operation. The IO operation at logical block address 0x0 for Disk 3 (PDO name: \Device\00000056) failed due to a hardware error. The IO operation at logical block address 0x0 for Disk 3 (PDO name: \Device\00000058) failed due to a hardware error. A couple expanded messages below as samples: Then a couple minutes later a continual string of Disk errors started, all associated with Drive 3, an external Seagate Backup Plus 2TB drive that has three volumes. Reset to device, \Device\RaidPort3, was issued.īUT NOTE: There is no RAID configured on this system. I noticed that on Day 1 things started with an Event ID 129, iaStorA with the message: The BSOD and reboot sent me to the Event Log looking for issues. The system has been operating fine for almost five hours since those two events. I disabled the Solver add-on in Excel, but the three software packages are still installed. I don't know about the second event – it happened while I was away from the computer – I just saw it had rebooted. On the BSOD there was a message CLOCK_WATCHDOG_TIMEOUT message. I experienced one BSOD and one reboot (possibly another BSOD) shortly after those installations. Ubit classic menus for Excel, Word, PowerPoint On Day 2 I temporarily enabled the Excel Solver add-on and installed three new software packages: The Disk errors and the BSOD may be unrelated. This afternoon there were also a Blue Screen of Death (BSOD) and a second reboot that may have been a BSOD within a 20 minute interval. I expect you will see the same dummy serial number.Starting on 2 September (Day 1) and continuing today 3 September (Day 2) I have been experiencing Disk errors / warnings. If you want to prove this for yourself, remove the PCB with a Torx screwdriver and power it up on its own. I suspect that both drives failed to reach the SA at one time, in which case they would have reported the dummy serial number, model number and firmware version in the ROM. When a drive cannot access the firmware area in the reserved section of the platters (System Area = SA), it defaults to identifying itself with a dummy ID stored within the "ROM" on the PCB. XxxxxxAx - Self-Service SeaTools Test Code It appears that the test codes have changed in recent times, but my understanding was (in 2013 ?) that the second last digit identifies the failing test, as follows: It is generated from the drive's serial number and the number of the failing test. This code is an encoded hexadecimal number which is unique to each drive. Can someone help me understand what is going on?Īs part of the RMA process, a user needs to obtain a SeaTools "test code". Here is the log file note the failed tests on two different dates - they are on two different hard drives. This is why the Seatools log file got appended. Here's the bizzarre part: both of these drives are showing up as the same S/N in Seatools - and not what is printed on the label on the hard drives. The replacement drive could be formatted by my Mac, but the Short Generic failed. The first one could not even be formatted (Seatools said cyclic redundancy check failed). But having terrible luck with the quality of the drives being shipped. I found Seagate Ironwolf 4TB drives on Amazon for $15 less than the WD Reds.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |