Bios sees and does not see HD (enigma)

[Jimmy Neutron]

I just put a new computer together.

The probles is that Bios (Phoenix Awardbios v. 6.00 PC) does not recognise the
IDE HD. I've restored bios defaults (as described in the mb manual).

The HD is a fully working (I took it from another computer) IBM Deskstar IDE hd
(not SATA). The motherboard is Abit AB9 Pro.

Here's what happens at bios load time:

- a short message "Jmicron Technology PCIE to raid ... blah blah" and below is
"HDD0: IBM DTL 307045 press Ctrl-J to enter Raid set up"
If I enter raid set up the HD is fully recognised there with all info on cylinder
etc.

- then Award bios boots up. It reports in "Standard CMOS features" all IDE
channels as "None".

but in another section "Hard disk priority" is lists "1: SCSI-0: IBM DTLA ..."

The HD is connected to the first and only IDE connector and the HD hums as it
should.


What gives? I'm baffled. The computer has just the hd and VGA card + keyboard and
mouse so there should be no conflicts.

 

[philo]

I just put a new computer together.

The probles is that Bios (Phoenix Awardbios v. 6.00 PC) does not recognise the
IDE HD. I've restored bios defaults (as described in the mb manual).

The HD is a fully working (I took it from another computer) IBM Deskstar IDE hd
(not SATA). The motherboard is Abit AB9 Pro.

Here's what happens at bios load time:

- a short message "Jmicron Technology PCIE to raid ... blah blah" and below is
"HDD0: IBM DTL 307045 press Ctrl-J to enter Raid set up"
If I enter raid set up the HD is fully recognised there with all info on cylinder
etc.

Be sure your IDE channel is set to "autodetect" in the bios

 

[kony]

I just put a new computer together.

The probles is that Bios (Phoenix Awardbios v. 6.00 PC) does not recognise the
IDE HD. I've restored bios defaults (as described in the mb manual).

The HD is a fully working (I took it from another computer) IBM Deskstar IDE hd
(not SATA). The motherboard is Abit AB9 Pro.

Here's what happens at bios load time:

- a short message "Jmicron Technology PCIE to raid ... blah blah" and below is
"HDD0: IBM DTL 307045 press Ctrl-J to enter Raid set up"
If I enter raid set up the HD is fully recognised there with all info on cylinder
etc.

- then Award bios boots up. It reports in "Standard CMOS features" all IDE
channels as "None".

That's what it's supposed to show, the bios enumeration is
of non-add-on controllers, and handles and 3rd party
controllers separately, which is essentially why there is a
separate bios routine for the 3rd party controller.

but in another section "Hard disk priority" is lists "1: SCSI-0: IBM DTLA ..."

The HD is connected to the first and only IDE connector and the HD hums as it
should.

So what is the problem? This is what we'd expect when
everything is as it should be.

What gives? I'm baffled. The computer has just the hd and VGA card + keyboard and
mouse so there should be no conflicts.

There's nothing wrong based on what you report.
Have you tried to use the drive and found you couldn't?

If you are trying to boot it, that would be set in the RAID
bios and/or boot order in the main (motherboard)) bios.

 

[Dave]

I just put a new computer together.

The probles is that Bios (Phoenix Awardbios v. 6.00 PC) does not recognise
the
IDE HD. I've restored bios defaults (as described in the mb manual).

The HD is a fully working (I took it from another computer) IBM Deskstar
IDE hd
(not SATA). The motherboard is Abit AB9 Pro.

Here's what happens at bios load time:

- a short message "Jmicron Technology PCIE to raid ... blah blah" and
below is
"HDD0: IBM DTL 307045 press Ctrl-J to enter Raid set up"
If I enter raid set up the HD is fully recognised there with all info on
cylinder
etc.

- then Award bios boots up. It reports in "Standard CMOS features" all IDE
channels as "None".

but in another section "Hard disk priority" is lists "1: SCSI-0: IBM DTLA
..."

The HD is connected to the first and only IDE connector and the HD hums as
it
should.


What gives? I'm baffled. The computer has just the hd and VGA card +
keyboard and
mouse so there should be no conflicts.

You should seperate the issues of a) whether the drive is detected and b)
whether the bios is set up right to boot from it. Boot from a floppy or
livecd and see if the drive is present.

 

[Jimmy Neutron]

That's what it's supposed to show, the bios enumeration is
of non-add-on controllers, and handles and 3rd party
controllers separately, which is essentially why there is a
separate bios routine for the 3rd party controller.

How do I format the ide HD? I put in an USB cdrom and booted Windows 2000 from
it. Unfortunately it can't format the hd and install OS since it's not detected.

The hd was taken from a Win 2000 systems where it was working as a boot drive C:
with windows installed and ready.

So what is the problem? This is what we'd expect when
everything is as it should be.

How would I go about installing OS on it? Windows 2000 setup bluescreens with a
message saying something about missing boot drive or something.

 

[Jimmy Neutron]

Be sure your IDE channel is set to "autodetect" in the bios

They are set as auto[detect] to no avail.

 

[Paul]

I just put a new computer together.

The probles is that Bios (Phoenix Awardbios v. 6.00 PC) does not recognise the
IDE HD. I've restored bios defaults (as described in the mb manual).

The HD is a fully working (I took it from another computer) IBM Deskstar IDE hd
(not SATA). The motherboard is Abit AB9 Pro.

Here's what happens at bios load time:

- a short message "Jmicron Technology PCIE to raid ... blah blah" and below is
"HDD0: IBM DTL 307045 press Ctrl-J to enter Raid set up"
If I enter raid set up the HD is fully recognised there with all info on cylinder
etc.

- then Award bios boots up. It reports in "Standard CMOS features" all IDE
channels as "None".

but in another section "Hard disk priority" is lists "1: SCSI-0: IBM DTLA ..."

The HD is connected to the first and only IDE connector and the HD hums as it
should.

What gives? I'm baffled. The computer has just the hd and VGA card + keyboard and
mouse so there should be no conflicts.

Only Southbridge hosted drives show in the main BIOS screen.
The newer Intel chipsets only have SATA and have no IDE port.
Thus the motherboard maker includes a Jmicron part, a separate
controller chip. That is for the convenience of customers who
still own PATA (ribbon cable) drives - in particular there
are still a lot of CD/DVD drives that need the ribbon cable.

Separate controller chips have their own BIOS module. Frequently,
this is a RAID BIOS, as the controller supports some flavor of
soft RAID. When you use the appropriate key combination to open
whatever BIOS the Jmicron chip has, you may see info on the drive
there. Also, there can be a detection phase where the separate
BIOS module for the separate controller, lists the detected drives.
The detection phase doesn't need a key pressed, to display a little
info about the connected drives.

All you need to do, is:

1) Figure out how to set the boot order.
2) Find a CDROM/DVD drive that you can boot the machine with.
Then you'll be able to boot the Windows install CD. Your CD/DVD
may end up sharing the ribbon cable with your IDE drive.
3) At the appropriate time, press "F6" during the install,
and install whatever driver is included for the Jmicron
controller. That would allow you to install the OS on
the Jmicron hosted IDE drive.

Having the boot drive or your CD/DVD on the separate controller
is not going to be nearly as seamless as if it was plugged to
the Intel Southbridge. But that is the way Intel wants it.

If you are attempting to "transplant" the boot drive from
another computer, you'll need to do a "repair install".
The "repair install" will have all the same issues as a normal
install, in terms of pressing F6 and installing a driver.
There is no way your boot drive is going to be able to boot
from the Jmicron controller, even if you happened to have the
Microsoft driver for IDE installed on the transplanted boot
drive. At minimum you'll need to do the repair install, press
F6, and install a driver of some sort for the Jmicron chip.

One issue with add-in controllers, is whether they support
ATAPI devices (packet interface devices like optical drives).
There have been controllers in the past, like the ITE PATA
controllers, that have the odd issue with supporting boot.
I hope the Jmicron people have done a better job of supporting
any ATAPI devices you are using.

ATAPI is mentioned here, but not in any detail. Notice that
the supported operating systems don't include Win9X/ME and
Win2K/WinXP or newer would be needed.

http://www.jmicron.com/JMB363.html

Paul

 

[Jimmy Neutron]

Only Southbridge hosted drives show in the main BIOS screen.
The newer Intel chipsets only have SATA and have no IDE port.
Thus the motherboard maker includes a Jmicron part, a separate
controller chip. That is for the convenience of customers who
still own PATA (ribbon cable) drives - in particular there
are still a lot of CD/DVD drives that need the ribbon cable.

Separate controller chips have their own BIOS module. Frequently,
this is a RAID BIOS, as the controller supports some flavor of
soft RAID. When you use the appropriate key combination to open
whatever BIOS the Jmicron chip has, you may see info on the drive
there. Also, there can be a detection phase where the separate
BIOS module for the separate controller, lists the detected drives.
The detection phase doesn't need a key pressed, to display a little
info about the connected drives.

All you need to do, is:

1) Figure out how to set the boot order.
2) Find a CDROM/DVD drive that you can boot the machine with.
Then you'll be able to boot the Windows install CD. Your CD/DVD
may end up sharing the ribbon cable with your IDE drive.
3) At the appropriate time, press "F6" during the install,
and install whatever driver is included for the Jmicron
controller. That would allow you to install the OS on
the Jmicron hosted IDE drive.

Having the boot drive or your CD/DVD on the separate controller
is not going to be nearly as seamless as if it was plugged to
the Intel Southbridge. But that is the way Intel wants it.

If you are attempting to "transplant" the boot drive from
another computer, you'll need to do a "repair install".
The "repair install" will have all the same issues as a normal
install, in terms of pressing F6 and installing a driver.
There is no way your boot drive is going to be able to boot
from the Jmicron controller, even if you happened to have the
Microsoft driver for IDE installed on the transplanted boot
drive. At minimum you'll need to do the repair install, press
F6, and install a driver of some sort for the Jmicron chip.

One issue with add-in controllers, is whether they support
ATAPI devices (packet interface devices like optical drives).
There have been controllers in the past, like the ITE PATA
controllers, that have the odd issue with supporting boot.
I hope the Jmicron people have done a better job of supporting
any ATAPI devices you are using.

ATAPI is mentioned here, but not in any detail. Notice that
the supported operating systems don't include Win9X/ME and
Win2K/WinXP or newer would be needed.

http://www.jmicron.com/JMB363.html

Paul

Thanks! Haven't tried it yet but sounds right.

 

[Jimmy Neutron]

It's booting OK from an USB DVD/CD-rom.

Windows 2000 setup disk works OK.

Did that - Windows setup load the diskette OK and continue ..

A couple of minutes later a message "IN_ACCESSIBLE BOOT DRIVE" blue screen
appears and everything halts.


Looks like I have to buy a SATA disk. Bummer.

Thanks for your help though!

 

[Paul]

Looks like I have to buy a SATA disk. Bummer.

Thanks for your help though!

I don't know which motherboard you've got, but here is a
folder with some JMB363 info:

ftp://usa.asus.com/pub/ASUS/misc/sata/JMicron/

JMB363_Manual.zip contains a crappy manual.

There is no mention of any special config for a
non-RAID boot drive on the JMB363. It could be
that you create a "striped array of one disk",
in order to make the disk acceptable to the
RAID software. Another setting that was popular
was "JBOD". That is an old-fashioned solution
to a problem like this, but perhaps Jmicron
didn't figure out how to do it like other
manufacturers.

Also, your BIOS may have a setting for the
Jmicron chip. "Jmicron Controller Mode" may
offer settings like [Basic, RAID, AHCI]. Try
the Basic mode and repeat the beginning of
setup again.

It may take some trial and error, but I bet you
can get it to run.

Paul