Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

revisiting non start issue with slave hdd installed

Status
Not open for further replies.

drtom

Technical User
Joined
Feb 26, 2004
Messages
369
Location
CA
I am sorry to revisit this issue (original post - but I made a real dumb mistake when I first went through this process and had to start over again (created a partition that ended up being too small for XPP).
Reprise:
I installed a DeskStar IC35L040AVVA07-0 (Hitachi) HDD as a slave (Device 1) (FRU19K1567) along with a Maxtor 6L040J2 40 GB as the master (Device 0). Jumpers are set to master and slave as per the manufacturer’s specs. Cable is connected correctly.
The computer is set up as a multi boot system:
C: - Fat32 - OS = Win 98
D: - NTFS – OS = Win 2000 Pro
E: - NTFS – OS = Win XPPro
F: - Fat32 – Storage/Work partition
I ran Killdisk on the slave to wipe it before reformatting. I created an extended partition on the slave and created 3 more logical drives:
F:
G:
H:.
Both drives are visible in the BIOS.
When I boot the computer and choose Win98 it starts fine. When I choose to start the computer in either Win2K or XPP I receive a stop error “Innaccessible_Boot_Device”.
I can start the computer in safe mode in either Win2K or XPP and access the slave.
When I disconnect the slave the computer starts normally.
I have tried the system with and without formatting the slave.
I have tried to start the system with the jumper on the slave set to “2 GB clip – slave” and I receive the stop error.
I used the Hitachi Drive Fitness Test (v4.05) which returned no problems on either drive. Hitachi has no suggestions.
Originally I created the partitions on the slave with fdisk and created primary, logical and extended partitions. I thought that this may have been the problem and I repartitioned the slave creating one extended partition across the whole of the drive, with the logical drives within this extended partition. When I start the computer I get the same stop error so I am assuming that the partitioning issue is not the problem.
The points we know for sure are that the master and slave work when the computer is started in Win98 (Fat32), it will start in safe mode in either Win2K or XPP (NTFS) but it will not start in either Win2K or XPP (NTFS) in normal mode.
F: was set to Fat32 to allow access from Win98. There are no issues with the master.
The system information is as follows:
Computer – IBM NetVista 6794-DE4
OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600
System Manufacturer IBM
System Model 6794DE4
System Type X86-based PC
Processor x86 Family 15 Model 2 Stepping 4 GenuineIntel ~2192 Mhz
BIOS Version/Date IBM 20KT46AUS, 6/4/2004
SMBIOS Version 2.31
Windows Directory D:\WINDOWS
System Directory D:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Hardware Abstraction Layer Version = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
Total Physical Memory 768.00 MB
Available Physical Memory 337.29 MB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 1.83 GB

If anyone can give me further insight as to why I cannot start the computer with the 2nd hdd installed I would be very grateful.
Thank you
 
Start it up in SafeMode (XP), go to Drive Management, and see if the Slave is set to ACTIVE?

Use the Drive Management to Kill the Partitions and recreate them there...

mostlikely by using FDISK, has set one of the Partitions to active...

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."
 
Thanks Ben:
I tried your suggestion but found that it wouldn't even start in Safe Mode. I then decided to disconnect the cable and hook it up as a slave to the CD/RW drive. It not only worked in safe mode, it started normally. It must be the IDE cable. Now, before you go rolling your eyes and calling me a dumb twit (which you would have every right to do) I first replaced the original cable last week with one from another machine I have (it worked it that machine) and it got it working in this unit.
i am off to buy a brand new cable this afternoon and prove my point... if only to myself.
Boy, when a computer hits you in the stomach it really hurts...
Thanks, I'll report back on the newe cable.
 
Trust me I wont call you a dumb twit, cuz I been there before aswell... cables are known to fail silently...

and do report back if it really was the cable...

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top