Help - Sata boot "no device"

[docevi1]

This is a nightmare of the highest order! I have an Asus A8v and a SATA Seagate barracuda harddrive which this morning simply stopping working. I'm fairly certain I know what the problem is - the mbr has been wiped, but that goes beyond the realms of my knowing how to fix.

In really typical fashion it's happened two weeks before my first dissertation deadline and as every Computer Science student knows to do but never does - I have no backups what so ever.

I will probably be able to get the machine working with an old harddrive (IDE) therefore can probably boot into Windows with the SATA drive connected (but not seen), is there any way I can rebuild the mbr or get the data back from there???

All I need is a folder < 10mb recovered, but all the places local are going to charge a small fortune (>£100) and don't suggest they can do it today (earliest was a week). I really, really, really that data!

Help, I don't think I've been this worried for a very long time!

[Plotloss]

If you put the disk in another machine it should be able to be read, MBR or no MBR

Thats going to be a LOT easier than attempting to rebuild the MBR.

[docevi1]

I'm just trying that now.

would a mbr show that there is "no device" connected in the SATA device manager on boot?

[Plotloss]

It should still show as a device whether it has an MBR or not I think.

All the MBR does is point to the location of one or many operating systems...

[docevi1]

bugger, is there anyway to force interogate a SATA connection to see if there is a device there at all?

[Plotloss]

Does the BIOS see it?

[docevi1]

no, the SATA Bios doesn't see it at all. Therein lies my main problem.

[Plotloss]

Its definately got power?

[docevi1]

90% sure, I had it outside of the case sitting on an antistatic bag but connected up and you can feel/hear it whirring and clicking.

[Plotloss]

Curious.

This disk was working perfectly up until recently I take it?

[docevi1]

absolutely fine. It's been in the case working for nigh on 8 months now, jthere have been a few times when it has said "no device" before, but that has been resolved with a restart.

I took it out of the case this morning to check the model number and when I put it back in it decided not to show up in the BIOS. The only thing that concerns me about the procedure was that the PC tried to boot once or twice and was shut down by me holding the power switch down for the required 10secs or so. I can't see that doing any damage but it's the only thing that I had done differently or thinking back would have me mildly concerned.

I'm just installing WinXP onto another harddisk...

[malman]

If the SATA BIOS doesn't see the device then you're looking at 1 of these probably

1) the SATA controller is bust
2) the connections to the device are bust (power / data)
3) the device controller board is bust

1) try it on another controller (know anyone with sata PC). Ive just built one for my sister if you're desperate I can arrange to get it fired up on that. Typically I went for the MB without SATA. Otherwise ...

2) new cable set (if its spinning up then just the data cable)

3) if you really want the work back this gets expensive


Just remembered I've got a SATA based PC at the office too

>> Edited by malman on Friday 1st April 12:54

[docevi1]

Neil,

is there any chance you could test it for me? The main problem I have is that no-one I know has a SATA mobo or device hence I don't know what is wrong.

I've tried to two cables that came with the hdd, and both ports on the mobo, neither want to work...

[malman]

If I mail your profile will it get to you

YHM - anyway


>> Edited by malman on Friday 1st April 13:02

[Plotloss]

Well thats ruled out the cable.

So now its either the controller in the board or the one in the disk.

Someone somewhere must have a SATA board you can borrow for 5 mins...

[docevi1]

cheers Matt, off to see Neil now.

hopefully come back with some good news.

[docevi1]

Well thank the lord for that one - Neil chucked the drive into his machine and it was seen, although one partion was damaged he managed to get my Uni work backed up.

Thanks again Neil, total diaster averted!

[docevi1]

I have two Sata controllers on my motherboard, one appears to be shot, the other works fine. I had completely forgot about the other slots as they are black and hidden.

Thanks again Neil and Matt, but I feel a little bit of a dufus today!

[docevi1]

that wasn't the end of the story

Windows got corrupted

What a bloody day!

[roop]

What I would say is this. Be VERY careful about using the drive. I have seen on numerous occasions a duff drive actually blow up and take the MoBo controller with it and even a PSU, so don't blame your MoBo just yet. If you can, chuck in a spare old drive in the meantime and get the one you have replaced under warranty.

Obviously, if you can, you might wanna get the MoBo swapped out as well if it's a warranty job / you are feeling flush.

Roop