[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

3.2 Install doesn't see Seagate HDD



Hi,

Could someone please help me with my unsuccesful 3.2 install?

I have a pentium 1/100 with two nics, that I would like to turn into a 
router/firewall for my home network, using openbsd.

I have reasonable linux experience, but little to no openbsd experience.

Below is all the info I've got and what I've already tried.

- The system is a Pentium 1/100, 16 mb ram, 261 mb harddisk with two nics in 
pci slots.
Motherboard: Abit AB-PT5 with integrated e-ide (from 1999)
Harddisk: Seagate ST3290A (this may be the cause of the problem, see later)

- I have an openbsd 3.2 bootdisk

- When I boot with the boot flop, install starts, but at the point where I 
type "y" to continue with the install, the script quits with "no available 
disks found."

- The bios automatically and correctly recognises a 261 mb ide harddisk as a 
primary master. It says the drive is of type 0, and it correctly recognises 
the geometry parameters:
1001 cylinders/15 heads/34 sectors

- if I boot WITHOUT the boot flop, the system starts Windows 98, which is 
installed on the harddisk.

- If I connect the system to a 880Mb Quantum disk, it fails to boot at all, 
it just passes the memory test and then does nothing.

- If I run the bootdisk on another system, a K6-2/400 with a 6.4Gb Quantum 
disk, it works as it should. The install script continues past the point 
where it hangs on the system on which I intend to run it: it asks if the 
whole harddrive is to be used for openbsd, and fdisk starts in interactive 
mode.

- If I boot the system with the boot flop and go to /dev, I see /dev/wd0a to 
wd0p, /dev/wd1a to wd1p and /dev/wd2a to wd2p.

- If I try to fdisk the disk manually with
fdisk -e wd0
or
fdisk -e wd0a
the system responds:
Device not configured.
The same if I try with /dev/wd0a or any /dev/wd* device for that matter

- fdisk -e /dev/wd0 produces
No such device

- If I start the system, I see a table from the bios with (among other 
things)
Primary master disk: CHS, mode 0, 261Mb

- If the systems starts to boot from the openbsd bootflop, one of the first 
lines on the screen is:
disk: fd0 fd1 hd0*
(those two floppy drives are a 3.5" and a 5.25" clay tablet drive)

- There is only one ide-slot on the motherboard: the one that the 
problematic hard drive is connected to.

- dmesg | grep ide:
 pciide0 at pci0 dev 7 function 1 "Intel 82371FB IDE" rev 0x02: DMA, channel 
0 wired to compatibility, channel 1 wired to compatibility

- If I connect the problematic hard drive to another system (the K6-2/400), 
and fire it up with the openbsd-boot flop, it has the same problem: when I 
confirm that I want to continue with the installation, the install script 
quits with "No available disks found". If I boot the K6 with the 
problematic hard drive, WITHOUT the boot flop, it starts Windows 98 from 
the hard drive.

- I searched with Google to see if the Seageate ST3290A was the problem, and 
yes, other people have had problems with installing openbsd > 2.8 with this 
drive: apparently it doesn't support DMA which confuses openbsd.
So I disabled dma during the floppy-boot process as follows:
boot> boot-c
yadda, yadda
UKC> disable pciide*
pciide* disabled
UKC> quit
yadda, yadda
But then, when I came to the point where I had to confirm I wanted to 
continue with the install, install still said: No available disks found.
fdisk -e wd0 still produced:
Device not configured.
With all the other /dev/wd* devices, it said the same.
With /dev/wdc0 (as I saw someone do on a mailing list), it said "No such 
device"

Can anyone please help?

Kind regards,

Bert de Jong



Visit your host, monkey.org