Norton Ghost problem with BE6 ATA-66 HD...

[usbnuts]

Hi, I am having problems with booting up a Quantum 20GB FS ATA66 hard disk containing an exact drive image created by Norton Ghost from my IBM 8.4GB hard disk.

System configuration:
Windows 2000
NTFS
BE6
Only 20GB HD connected during the problem occurred

This is first time I try to use ATA-66 controller on my mobo.

During the boot up, I encountered a bootup drive initialization problem. {error code: INACCESSIBLE BOOTUP DRIVE}

I was able to boot up my new 20GB hard disk using the ATA-33 controller, but not wth the ATA-66 channel.

Could anyone please help?

Best regards,

 

[ZoSo]

A couple things to check:
1-Get the latest BIOS update available.
2-Jumper on HDD set to master or single drive.
3-Make sure you have the correct ribbon cable, 40pin 80wires.
4-Make sure BIOS recognized the drive correctly. Set it to auto detect in BIOS.
5-Check that UDMA is enabled, in BIOS, for the controller on M/B, if available.

 

[CAMS]

Check your BIOS that your ATA 66 controllers is enabled and boot sequence is set to select it first.

 

[usbnuts]

Thanks for your replies. I have set the boot sequence in this order: EXT, A, C. And I have also set the "What EXT means" to UMA66.

The 20GB ATA66 HD seems to work fine with my ATA-33, but it just cannot boot when connected to a ATA-66 controller.



<< 1-Get the latest BIOS update available.
2-Jumper on HDD set to master or single drive.
3-Make sure you have the correct ribbon cable, 40pin 80wires.
4-Make sure BIOS recognized the drive correctly. Set it to auto detect in BIOS.
5-Check that UDMA is enabled, in BIOS, for the controller on M/B, if available. >>



Ans.
1. 7/31/00 I have the latest for sure.
2. The only drive connected to ATA-66 is master, as seen in POST.
3. I have the correct ribbon.
4. Hmm...I will check this...thanx.
5. I have UDMA enabled.

 

[ZoSo]

Double check the jumper on the HDD. Some manufactures have a &quot;no jumper&quot; or &quot;park&quot; setting if drive is a single drive. While using the &quot;master&quot; jumper if your running two drives.

Here's some stuff from Quantums site:


<<
If your disk drive is not being detected (auto-detected) by the system BIOS, try the following steps to try and isolate/troubleshoot the problem.
Verify all the cable connections - This applies to both the data cable and the power supply cable. To test the data cable use a known good cable or try the cable in question on a known working drive. Make sure that the cable is plugged into both the motherboard and the drive correctly. The stripe along one edge of the data cable should be matched up to pin #1 on the drive and pin #1 on the motherboard.


Verify the jumper settings - If the drive is a Master or a stand-alone drive (on a standard data/ribbon cable), the DS jumper needs to be installed. If the drive is a slave drive then the DS jumper must be removed (and stored in the PK position if desired). If you are using an Ultra-ATA data cable (which typically use a Cable Select configuration), then both drives (master and slave) must have their CS jumpers installed.

Ultra-ATA data cables typically have their connectors color-coded to help you identify proper drive placement. On these cables, the master drive is attached to the black (end) connector, the slave is connected to the gray (middle) connector, and the blue connector is attached directly to either your motherboard or your ATA adapter card.


Test the drive as the only hard disk device in the system - Define the drive as a Drive Type-1 (10MB drive) from the drive table in your system BIOS (CMOS setup)and then boot your system from a floppy disk that contains the FDISK.EXE program. If the drive is now detected, the FDISK program should report it as a 10MB drive. Now go back into the CMOS settings for the hard drive and manually enter the correct CHS values (these are listed on a label on the top of the drive). However, if your drive is greater than 8.4GB, then you will need to use the AUTO setting instead. In either case make sure to enable LBA support. Rerun FDISK to make sure the drive is being detected and at the correct capacity.


Test the ATA adapter card - If possible, check it by trying a known working card or use a known working drive. If your ATA adapter is built into your motherboard, you will need to test the drive in another machine or try a known working drive in the same machine in question.


Test the disk drive in a different system - If the drive still isn't being detected, return it for replacement.

Quantum® ATA hard drives have their jumper block located at the back of the drive on the interface connector (see the first diagram below), or for some earlier models it may located directly on the drive's printed circuit board (see the second diagram below). In either case, the most common setting for a master drive is to install the jumper on the DS position, and the most common setting for a slave drive is to simply remove the jumper or store it on the park (PK) position if available

Here's image
The diagram above applies to the following Quantum® hard drives:

Fireball models: lct20, lct15, lct10, lct8, CX, CR, EX, EL, SE, and ST.
Fireball Plus models: AS, LM, KX, and KA.

Note: Some of the newer Fireball lct and Fireball Plus models ship from the factory with a default jumper setting of CS.

>>

 

[Grminalac]

What kind of ATA 66 card do you have?

 

[usbnuts]

My ATA-66 card is built onto the Be6 mobo. I forgot what the name of the controller is.

Anyhow, my ATA66 HD is detected by the BIOS, and it is set to boot sequence. The problem's with Windows 2000 not allowing the drive to boot.

 

[Grminalac]

I am not sure the boot sequence has much to do with the problem. With the 66 add on cards, both onboard and pci, the comp will go through the bootup sequence and if no bootable devices are found, the 66 controller bios will kick in. The reason for the sequence on the motherboard is to tell the comp you would prefer it to boot from the controller card before going to a bootable device on the 33. For some reason the hard drive is not being detected at all when you boot up.
When the computer starts up goto the bios screen and then have the computer auto detect the hard drives. (with your 20 gigger on the controller card) It shouldn't find anything. Restart and see what happens. Hopefully it will search through and find the hard drive on the U66.

 

[usbnuts]

Hi, my ATA-66 HD was being detected, but Windows 2000 detected an error (INACCESSIBLE BOOTUP DRIVE)

So, the problem is beyond the BIOS.

 

[rlism]

I think Windows 2000 is looking for your OS files in the wrong place. The way Windows 2000 works is that the boot.ini points to the right place to find your OS files. For example mine looks like this:

multi(0)disk(0)rdisk(0)partition(1)\WINNT=&quot;Microsoft Windows 2000 Professional&quot;

That means, it's looking for it on the first partition of the first drive on the first controller. I think your drive is now on the second controller so you'll have to change it to read something like this:

multi(1)disk(0)rdisk(0)partition(1)\WINNT=&quot;Microsoft Windows 2000 Professional&quot;

Sorry, I really don't have much practice with this so please remember the changes you've made in case I'm totally off. Better yet, save a copy of the original c:/boot.ini file. You could also just move the drive to the correct location on the first ide channel too.