Devices > PC's and Other Hardware

Problems reading hard disk from a WHS

<< < (2/12) > >>

audioriver:

--- Quote from: Theogenes on May 31, 2012, 01:22:05 pm ---Sounds reasonable enough. Silly question-- how would I go about checking it?
--- End quote ---

Go to the hard disks' manufacture website. They usually offer a tool you can download, that performs these tests.

Theogenes:
Okay, tried to copy over one album that was not playing in MC onto another drive to see if that fixed it. The file wouldn't even copy-- I got the following error message:

"An unexpected error is preventing the operation. Make a note of this error code, w hich might be useful if you get additional help to resolve this problem: Error 0x80070780: The file cannot be accessed by the system."

A quick Google search for 'Error 0x80070780' returns several WHS-based forums, including this link: http://homeservershow.com/forums/index.php?/topic/846-help-with-file-recovery/, which talks about 'pointers' and 'tombstones.' Is it possible that these files are somehow links or shortcuts to the actual files, which are stored elsewhere? Or am I way off base here?

Thanks again!!

Theogenes:

--- Quote from: audioriver on May 31, 2012, 01:31:01 pm ---Go to the hard disks' manufacture website. They usually offer a tool you can download, that performs these tests.

--- End quote ---

Gotcha, I'll pop the drive out now, look it up, and give it a shot!! Thank you!!

Theogenes:

--- Quote from: audioriver on May 31, 2012, 01:31:01 pm ---Go to the hard disks' manufacture website. They usually offer a tool you can download, that performs these tests.

--- End quote ---

Okay, tried that, and now it gets curiouser and curiouser...

Downloaded SeaTools for Windows from here: https://apps1.seagate.com/downloads/request.html

Ran it, popup says "SCSI: Scanning for supported drives. Please wait...", and everything looks normal. After a few moments, I get this:

"Fatal Error: Device Discovery
Argument 'Length' must be greater or equal to zero. System.String
Mid(System.String, Int32, Int32)"

I did see a note while digging for the SeaTools app that said something about a firmware bug keeping one from being able to access files on the drive... Maybe we're onto something here?

Any ideas what the gibberish in that fatal error message means?

EDIT: I also went back and found another Seagate application that is supposed to make sure you've got the right model number for your drive called Drive Detect (here: http://support.seagate.com/firmware/drive_config.html). However, when I run it, it just sits there with no drives found.

EDIT 2: Okay, so there's ANOTHER application for Seagate drives in non-Seagate external enclosures here (http://knowledge.seagate.com/articles/en_US/FAQ/213111en), which DOES detect the drive, and then proceeds to tell me things I already know (S/N, model number, firmware version), and then when I select "Check new firmware," it merely opens up the same window for me to enter in the drive info, which takes me back to the same download page, and the download again gives me the Fatal Error message above.

I feel like I've pissed off Lawnmower Man or something here... I'm guessing the problems with running the firmware update on the drive are related to it being in an external enclosure, but I don't have any space left in my machine to add it on directly (or I would've done that first). Is this my next step, or am I missing something?

Thanks as always!!

JimH:
I don't know what that is, but if you have any other drives installed, unplug them.  Even thumb drives, etc.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version