Uh, so get started on those diags. If a drive shows any errors, you can stop the test. At that point, you'll want to copy data off of the bad drive.
Printable View
Uh, so get started on those diags. If a drive shows any errors, you can stop the test. At that point, you'll want to copy data off of the bad drive.
For now, you're done with UBCD5. The bootable/DOS version probably won't be able to see the USB drives. That's why I said to use the Windows version.
You still want to do the short test first, then the long test. If the short test fails, you don't need to run the long test.
Ran the Seam Tools for Windows, and it recognizes all the drives (internal and external) EXCEPT the Seagate one! Yet, I see it in Windows Explorer.
Strange. Anyway, start with the WD drives. Disconnect the drives that you are NOT scanning.
OK first run on the Fantom drive (WD), I get:
Quick Test on Drive 4 did not complete!
Status code = 07 (Failed read test element), Failure checkpoint = 97 (unknown Test)
SMART self-test did not complete on drive 4!
>> I guess this might mean that this is the Drive 4 that was showing so many errors since 2 days in the Event Viewer.
Any point in running the long test?
So that drive is bad for sure. I'd still run diags on the other drives.Quote:
If the short test fails, you don't need to run the long test.
Since the Sea Tool does not seem to see the Seagate drive, can I use the DLG for that? Or what else can I do for that one specific drive?
I tried uninstalling and reinstalling the Sea Tools and I get the same thing.
Interestingly, DLG sees it no problem.
Interestingly, there is NO error since I disconnected that "big" EHD that was problematic.
I still have not scanned the Seagate one.
DLG might be able to see the Seagate drive, but it won't be able to SCAN it. That why I said you needed Seatools.
Did you try plugging the Seagate into a different USB port?
In any case, you'll want to copy the data off of the "bad" hard drive ASAP.
Yeah, that is what i thought.Quote:
DLG might be able to see the Seagate drive, but it won't be able to SCAN it. That why I said you needed Seatools.
I have tried all 4 USB ports I have on the front and the Sea Tool still does not "see" it.Quote:
Did you try plugging the Seagate into a different USB port?
Should I try on a different computer?
Definitely a next step!Quote:
In any case, you'll want to copy the data off of the "bad" hard drive ASAP.
Reading the help for Sea Tool, it reads this:
"SeaTools may not find or access hard disk drives when CMOS is set to "none" for those drives."
I don't know what CMOS is or if it is something that I am experiencing. What is that? Could that be the problem?
What about the BACK USB ports? Otherwise, yes you could take it to another computer and scan it there.Quote:
I have tried all 4 USB ports I have on the front and the Sea Tool still does not "see" it.
The CMOS (BIOS settings) is for INTERNAL drives, not USB.
Tried 3 USB from the back. Same thing.
Could it have something to do with the fact that it WAS an internal hard drive just put in an enclosure and now used as an External?
I set it up on the laptop, and Sea Tools still does not see it.
I doubt it. It's more likely that Seatools doesn't like the hard drive controller in the enclosure. Another option would be to take the Seagate out of the enclosure and connect it to an internal SATA port.Quote:
Could it have something to do with the fact that it WAS an internal hard drive just put in an enclosure and now used as an External?
If you're not seeing more errors in Event Viewer, then the priority should be getting data off of the "bad" drive.