Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Asus P2B-S No hard drive found

1 view
Skip to first unread message

Mike Schreiber

unread,
Aug 8, 1999, 3:00:00 AM8/8/99
to
Hi all,

I'm trying to get a P2B-S to recognize _any_ SCSI hard drive.

- The bios is definitely enabled, and support for INT13 devices is
turned on.
- I have tried boot sequence of IDE/SCSI and reversed.
- Onboard AHA bios is Auto
- Have tried AHA bios first Yes and No
- Drives are recognized at boot
- I have tried (2) WD 9100 Enteriprise drives ID0 and ID1 on both U2W
and UW connectors
- I have tried (1) Cheetah ST318203LW on U2W on ID0 (separate from other
devices - this drive was by itself).

- All the above drives identifed correctly; the controller just doesn't
see the drives, even under DOS - FDISK reports No fixed Disks present.
Of course NT proceeds no farther. Note that I CAN verify and/or
lowlevel format drives in the Adaptec bios on bootup. I've also played
with the device settings without luck.

For U2W configuration I have the U2W cable supplied with the board and
termination disabled on whatever drive hooked up (on the WDs - on the
Seagate of coures there are no terminators). For UW configuration I
have a known good UW cable with an active terminator on it, termination
on the drives is disabled.

Adapter termination is currently enabled. I have only one connector in
use.

I just updated to bios 1010; no luck either. I only have a PCI video
card (I've tried two different brands - Diamond and ATI 4MB PCI cards).
Also moved the PCI card to PCI slot 3 so it doesn't share IRQs.

I have made sure no IRQ conflicts exist and have disabled/enabled IDE
channels as well.

The SCSI jumper on the motherboard is also enabled (of course!).

Is there ANYTHING else I can do (other than throw it out the window)?

I would appreciate it if you could CC me a copy of anything you post to
the newsgroup(s).

Thank you very much,
Mike Schreiber


Mike Schreiber

unread,
Aug 8, 1999, 3:00:00 AM8/8/99
to jo...@melbpc.org.aust
Thanks for the response, John.

Well it isn't just NT. It is also DOS FDISK!! I wouldn't worry if only NT didn't
see the drives but even DOS won't. Found out a couple of things since:

- neither 68pin interface on the board works with ANY 68pin drive.
- 50pin interface works fine with a 50pin SCSI drive.

if I disable SCSI Parity checking in the Adaptec BIOS then the board will see
68pin drives, but when I went to FDISK one, it had a stack overflow...

I have replaced the board with a separate board/SCSI controller combination. I
have built a P2B-S before and I really think this one had a problem...

Mike


J Bade wrote:

> Sounds like your controller has found the devices or else you couldn't
> do a low level format.
>
>
>
> Hope this gettting your machine going.
> I have the same m/b with the ATI display card and ASUS wake on lan NIC
> and 2 LVD drives and 50pin Seagate 12/24 DAT tape going perfectly. So
> it does work....and fast.
>
> Cheers
>
> John
>


J Bade

unread,
Aug 9, 1999, 3:00:00 AM8/9/99
to
Sounds like your controller has found the devices or else you couldn't
do a low level format.

The problem maybe getting NT to see them. When installing NT do not
let NT setup auto-detect the 7890chipset. It will not install the
correct device driver. You have to manually select the driver.
When NT is first setting up you have to press F6.

Try this:
Enable boot from CDROM.
Insert the NT server disk.
On restart start pressing F6 and keep going until NT prompts you for
the device drivers > Select "other" disk provided by manufacturer
and insert the floppy disk provided by ASUS with the m/b.
Select and other devices you may need; such as the IDE - ATA CDROM
driver.

Hope this gettting your machine going.
I have the same m/b with the ATI display card and ASUS wake on lan NIC
and 2 LVD drives and 50pin Seagate 12/24 DAT tape going perfectly. So
it does work....and fast.

Cheers

John

On Sun, 08 Aug 1999 01:45:48 -0500, Mike Schreiber <joh...@qni.com>
wrote:

Hi all,


_ ;--:- __---------______________------ ____
c--U---^--''__[__ooo__]---| |_!_||_!_||_!_||_!_||_! [_][++|--|]
_--_ _|------------'_|,[______],|_________________|_|,|____|
/ \__ /__(@)(@)==(@)(@) (o)^(o) (o)(o)--(o)(o) (o)
"/@@@ \~"""~"""~"""~"""~"""~"""~"""~"""~"""~"""~"""~"""~"""~"""

Alt-Ctrl-Del

unread,
Aug 9, 1999, 3:00:00 AM8/9/99
to
Please check the internal setting for termination in the bios. You do
need to disable on board termination as both the 8 and 16 bit scsi
buses need to be terminated at the ends of the cables. The
card/motherboard should not be terminated.

Am assuming the drives are on one cable and that there is a scsi cd or
like on the other cable... ie: the dat drive. Make sure that the dat
is properly terminated and that if it is internal that it is not
supplying power to the scsi terminator.

On Sun, 08 Aug 1999 21:56:35 -0500, Mike Schreiber <joh...@qni.com>
wrote:

>Thanks for the response, John.


>
>Well it isn't just NT. It is also DOS FDISK!! I wouldn't worry if only NT didn't
>see the drives but even DOS won't. Found out a couple of things since:
>
>- neither 68pin interface on the board works with ANY 68pin drive.
>- 50pin interface works fine with a 50pin SCSI drive.
>
>if I disable SCSI Parity checking in the Adaptec BIOS then the board will see
>68pin drives, but when I went to FDISK one, it had a stack overflow...
>
>I have replaced the board with a separate board/SCSI controller combination. I
>have built a P2B-S before and I really think this one had a problem...
>
>Mike
>
>
>J Bade wrote:
>

>> Sounds like your controller has found the devices or else you couldn't
>> do a low level format.
>>
>>
>>

0 new messages