Annoying stupid boot issue

Django x2 · 8 Jul 2010 at 10:43

Ok this is weird and it's annoyed me for the last time ever!

My machine has two sata drives in it. The system drive with W7 on is 320Gb. I also have a 500Gb drive which has a load of movies / music on there.

Sometimes I take the 500Gb drive out and move stuff from it, or too it.

When I plug it back in, the machine fails to boot. I think W7 writes sys info to it.

Is there a way to avoid this happening, i.e., the 500Gb drive is like a proper slave drive?

Fanatic · 8 Jul 2010 at 12:08

In the BIOS do you have the drives in the correct order to boot from? The 320GB needs to be first.

Sp00n · 8 Jul 2010 at 12:40

If it failed when you had the drive out then it would point towards system files on the 500 but its not so it sounds like boot order or something similar.

Why don't you put it in a caddy and use it over usb if you are taking it out all the time?

Django x2 · 8 Jul 2010 at 12:58

I think there is a sysvol info directory on that drive. I'm tempted to pull the data from it and format it properly then move it back to the machine.

Thing is, because this has happened before, I even build the machine with just the 320GB drive in there then add the 500GB once its up and running.

Fortunately today, I just did a repair install from the W7 disc