Solved

After Master/Slave attempt, one hard drive won't boot

Posted on 2003-12-11
9
629 Views
Last Modified: 2010-04-14
I was not present when the following occured, so this is based on what was related to me...  Two identical computers, both with W2K Pro.  Took hard drive (we'll call it HD1) out of one computer, rejumpered for slave (I am told it was properly done, I have no first hand knowledge), and installed on primary controller of second computer.  Booted up, got NTOS kernel error.  Rebooted, got W2K splash screen, went no further.  Couldn't boot into safe mode either.  Took HD1 off primary channel, put it on secondary channel as master in place of CD Rom (again, I wasn't there to be sure of proper jumpering), same result.  Took HD1 out completely, and computer booted normally.  Put HD1 back in its original computer, with original master setting on primary channel, now it won't boot - gets to same place at splash screen.  Tried to repair, but W2K installation not detected.  Can anyone guess the most likely scenario of what happened here?  I'm guessing something with the boot sector, but I'm not positive.  I'm also guessing the jumpering was incorrect at some point in the process.  If anyone can help me figure out what happened so I can figure out if there is a way to fix it, I'd appreciate it!  
0
Comment
Question by:slandise
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
9 Comments
 
LVL 40

Accepted Solution

by:
Fatal_Exception earned 250 total points
ID: 9924738
Have you tried the Recovery Console to fix the boot sector?  (Fixboot - Writes a new partition boot sector onto the specified partition.)  (Or Fixmbr - Repairs the master boot record of the specified disk.)

And I believe you are right, it was jumpered incorrectly.  From what I can see, this is the only explanation.  But, of course, I may be wrong...:)

FE
0
 
LVL 13

Expert Comment

by:Gnart
ID: 9925673
When putting the second drive (jumpered as slave) into the computer, the jumper on the first drive may need to be set (drive can be jumpered as only drive, primary and slave).  The first drive may have been set as only drive.  Also, the second drive may have been jumpered as only drive instead of slave.  The problem with setting drive jumper is some folks don't know which way to hold and read the jumpers.  If you hold it upside down, which is it (right or left) of the middle pin-set.

Also, the BIOS setting should be checked.  The 2nd drive setting may not have been set as auto-detect.  This would result in the problem with the bootstrap and no OS.

cheers
0
 
LVL 1

Expert Comment

by:notch_ur_head
ID: 9927527
HI slandise

Just remove the JUMPER from the JUMPER PINS and the restart the pc..
this will solve ur problem..

-notch_ur_head
0
Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

 
LVL 2

Author Comment

by:slandise
ID: 9928372
I finally got my hands on the computer and ran chkdsk /r on it.  Now it boots fine.  I'm still curious to know what caused the problem - I'm running diagnostics on the hard drive, but don't really think it's a problem with the drive itself.  To Gnart:  this is a Seagate drive, and the master jumper is supposed to be for master OR only drive.  As far as I can tell there is no separate jumpering for "only" drive, but I could be wrong.  That possibility makes sense.  And to Notch_ur_head, no jumpers is the setting on this drive for slave, which is how I'm told it was set when it was on the primary channel of the other computer.  It is currently jumpered for master.  This is probably one of those things I'll never have the exact answer to, but I'd still be interested if anyone has any further ideas.  I'm agreeing with the comments at this point that jumpering had something to do with it.  If I don't hear anything in the next couple days I'll close this question and chalk it up to one of those many unanswered questions....
0
 
LVL 40

Expert Comment

by:Fatal_Exception
ID: 9928497
It could have been as simple as the head bumping a sector as it was moved around, creating non-contiguous errors in the files needed to boot.  Since chkdsk fixed this (as it fixes so many unanswered WHY's), that may be the case.  Mis-jumpering it should have no affect in the disc spin up, at least as I understand it.

But the bottom line here is you got her running again.

Happy Holidays

FE  
0
 
LVL 2

Author Comment

by:slandise
ID: 9929514
Maybe I do have an answer after all.  Upon investigation, it turns out that the computer was shipped from the manufacturer with the Welchia virus.  Fortunately it was not on a network.  I have never heard of Welchia causing failure to boot, and particularly failure to allow a computer to boot even when the drive is installed as a slave, but that's what I will chalk it up to for now.  Thanks for everyone's help!
0
 
LVL 40

Expert Comment

by:Fatal_Exception
ID: 9929557
OMG...  Guess you don't want to tell us the Brand Name, eh?  :)

Again, just glad to see her fixed.

FE
0
 
LVL 2

Author Comment

by:slandise
ID: 9929580
It was a custom built system from a company that installs the OS and their own program from an image...  an image that happened to be infected!  But it's not a brand name, so not to worry!
0
 
LVL 40

Expert Comment

by:Fatal_Exception
ID: 9929596
Figures.  Sloppy, if you ask me.  But since nobody did...:)
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
When the s#!t hits the fan, you don’t have time to look up who’s on call, draft emails, call collaborators, or send text messages. An instant chat window is definitely the way to go, especially one like HipChat. HipChat is a true business app. An…
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question