Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Droog13

Posted 11 October 2005 - 07:47 PM

Droog13

Member

Topic Starter

Member

38 posts

Well theres no OS installed on the slave. But if I boot just the slave (as master) im pretty sure it is recognized. As I said it is recognized when hooked up as primary slave. By recognized I assume you mean by bios. It still cant be read and just asks for reformat.

Fenor

Posted 11 October 2005 - 07:54 PM

Fenor

Trusted Tech

Retired Staff

5,236 posts

Okay I'm a little confused here. You just said it is recognized when you have it set up as primary slave, but isn't that what you have been trying to do all alogn? Forgive me if I'm off here, long day at work.

Droog13

Posted 12 October 2005 - 03:16 PM

Droog13

Member

Topic Starter

Member

38 posts

If I hook it up as primary slave, BIOS sees it and recognizes it. However once windows starts up then it doesnt see the drive as formarted, only saying local disk (g:) When hooked up as the secondary master bios didnt recognize it, but again it said local disk (g:) in my computer.

Billre1967

Posted 12 October 2005 - 08:09 PM

Droog13

Posted 12 October 2005 - 09:37 PM

Droog13

Member

Topic Starter

Member

38 posts

I dont know exactly what caused my master to fail. It was concluded that is had a corrupt boot sector. I think it was just from getting run to much (hot) but I am not positive on that. I dont know how the first crash could cause the 2nd one to crash. I mailed western digital support but they havent helped yet.

Edited by Droog13, 12 October 2005 - 09:38 PM.

0

Advertisements

Fenor

Posted 12 October 2005 - 09:54 PM

Fenor

Trusted Tech

Retired Staff

5,236 posts

Well if the first hard drive died from heat and the other hard drive was very near it, then it is possible that the heat from the one hard drive could cause the other hard drive to be damaged. Not likely but possible.