O/T HELP! Computer Gurus

Allan in NE

Well-known Member
What a heck of a long run........

My mirrored SCSI problem turned out to be a bad controller.

I was able to save all the data and now have one of the single drives up and running via a single controller to the point where it was when it shut down.

BLUE SCREEN STOP ERROR: NON-ACCESSIBLE_BOOT_DEVICE

I've tried all the F8 options, I've ran a separate scan for virus, ran chkdsk/F and scandisk.

Win 2K. How can I repair this boot sector?

Thanks,

Allan
 
Alan, I'm not much of a techie when it comes to these, but have you tried any of the tech type sites/forums, those messages you are getting might ring a bell somewhere, few more eyes from another direction might help, that has to really have you in a bind, hope like heck you get er turned around !
 
I ordered a complete new server from the east coast. They are flying it in here now.

I'm just trying to get this old dog up and going for tonights workload.

Windows was corupted when she went down. Just thought there was a way to correct.

Allan
 

Sounds like a long night. Hope you can pull something out.

When I took my computor to the computor doctor he talked about reinstalling windows, which he didn't have to do. Found out some of my trouble is with the ISP, which I am going to confer with. Doubt if any of this will help you, but good luck anyway. The tractors need you back in the seat.

KEH
 
I have a ghost image of the machine when new.

Don't know how to get from the blue screen to the file in the CD tho. If I did, I'd reload 'er.

Kinda sux when other support folks are on a 5 hour workday and I'm trying to do 24. :>)

Allan
 
if it is raid there has to still be raid.
if not mbr from a dos window with the proper /option will rebuild the master boot record.
http://en.wikipedia.org/wiki/Master_boot_record
 
Have you tried the other drive? If the controller was failing it might not have been writing to both drives.

Have you tried to boot from the restore cd? May have to change boot order in bios (if cd is bootable).

Finally if you have a win2k cd you could try a repair install.

Good Luck
 
I KNOW NOTHING ABOUT COMPUTERS!
Install another "clean" harddisc into D/e/f/ ...
Change machine "Setup" to boot from a CD drive with a Win2K setup disc innit.
Boot. Install Win2K to HDD you just installed whatever letter.
Swap now bootable HDD with the corrupted HDD that's in C. Copy data from corrupted (now DorEorF whatever) back to C drive.
I had to do this once (With the help from a techie) cause it had a virus.
With todays computers this would probably be just enough info for me to get into BIG trouble.
Was hoping this would prompt some techies to get in here and flame me where I'm wrong but at the same time help you.
I KNOW NOTHING ABOUT COMPUTERS!
 
If from F8 you can get to the recovery console you could try the fixmbr command. example here http://pcsupport.about.com/od/termsf/p/fixmbr.htm
fixmbr
 
IF you are using SCSI you have to have the boot drive at the same SCSI ID on the same brand and model SCSI controller. If you had two controlers you have to know which one is the first.


Last chance would be to run Windows setup again and choose the second repair(when you choose the windows partition to install to) not the repair console. This is all from memory so, best of luck
 
IF you are using SCSI you have to have the boot drive at the same SCSI ID on the same brand and model SCSI controller. If you had two controlers you have to know which one is the first.


Last chance would be to run Windows setup again and choose the second repair(when you choose the windows partition to install to) not the repair console. This is all from memory so, best of luck
 
If I recall SCSI controlers are ID'd by the slot they are in on the server.

If the drives are hot swap they need to be in the same position as the original boot drive.

If they are just cabled they have jumpers or switches to determine the SCSI ID directions are on the label.
 
Since you are getting a blue screen error, that tells you that it is (probably) not a problem with the boot sector. The boot sector is being read and the kernel is being started. What it's choking on is that it cannot find the RAID controller in the same place that it was when you installed Windows. This could be because you replaced the RAID controller with a slightly different one (wrong driver) or even something as stupid as it being the same type of card but in a different slot (different IRQ).

Your best bet is probably to do a repair booting off Windows install CD as Steve said. Then you Windows will re-learn everything it needs to about that controller.
 
Allan, I keep a copy of Knoppix on hand just for such situations. Knoppix is a complete Linux operating system on a single bootable CD. On several occasions I've been able to recover data on a Windows drive that had a bad boot sector. There are also some utilities included with Knoppix that may be used (at your own risk) to fix boot sector problems and similar issues.

A working knowledge of UNIX or Linux is useful but not necessarily a requirement to use Knoppix. One advantage of Knoppix versus a Windows CD is that Knoppix mounts your drives read-only (unless you tell it to make them writable). So your data is never touched.
Knoppix
 
A third vote for run a "repair" install. It doesn't have the right drivers for that SCSI controller.

If you're really nervous, disconnect the 2nd hard drive from the mirror array so you can do data recovery from it later on if everything goes horribly wrong.
 
Thanks Guys,

You always get me straightened out. I ordered another Raid controller and will use this machine for a back up when everything gets here.

The original Raid controled the boot and I gotta set up another one for it to be right with these drives. :>(

Allan
 

We sell tractor parts! We have the parts you need to repair your tractor - the right parts. Our low prices and years of research make us your best choice when you need parts. Shop Online Today.

Back
Top