Sco 5.0.7 with IDE drives

[Kristopher Lalletti]

Surprisingly enough, who would ever think that IDE hard drive configuration
would actually fail?

I have an old copy of SCO OpenServer 5.0.4 that I booted-up and it saw my 2
IDE drives without any hesitation.

I have my new copy of SCO OpenServer 5.0.7 that I booted-up and gave me the
following error in the init process.


G hd_config

PANIC: wdsetparam: no device info for ctrl 1 drive 0

Is ctrl 0, drive 0 not an ATA disk ?



Basically, on the primary controller, I have my CD-Rom as master. On my
secondary controller, I have my 2 IDE hard drives occupying both Master and
Slave positions. Unfortunately, putting the IDE drives on the primary
controller is not feasible, and the hardware was designed like this (a dell
PowerEdge 1650).



Is it possible to manual define the Primary and Secondary controller from
the boot string? If so, what would necessarily be the syntax?



Thanks

Kris

[Bela Lubkin]

Kristopher Lalletti wrote:

> Surprisingly enough, who would ever think that IDE hard drive configuration
> would actually fail?
>
> I have an old copy of SCO OpenServer 5.0.4 that I booted-up and it saw my 2
> IDE drives without any hesitation.
>
> I have my new copy of SCO OpenServer 5.0.7 that I booted-up and gave me the
> following error in the init process.
>
> G hd_config
>
> PANIC: wdsetparam: no device info for ctrl 1 drive 0
> Is ctrl 0, drive 0 not an ATA disk ?
>
> Basically, on the primary controller, I have my CD-Rom as master. On my
> secondary controller, I have my 2 IDE hard drives occupying both Master and
> Slave positions. Unfortunately, putting the IDE drives on the primary
> controller is not feasible, and the hardware was designed like this (a dell
> PowerEdge 1650).
>
> Is it possible to manual define the Primary and Secondary controller from
> the boot string? If so, what would necessarily be the syntax?

There is probably a way around this problem. We'll have to start with
some debugging.

When it panics, you should have ended up at a kernel debugger (scodb)
prompt. At that prompt, type "d &wdDriveinfo". You'll get a hexdump
showing 4 longwords. From the message above, I know that the 3rd
longword is 00000000. What are the values of the other 3? (Best if you
just post the entire line.)

Hit 'q' to get back to scodb prompt. Actually, you'll just want to
power cycle or hit reset at that point, or if you want to be slightly
more graceful, tell scodb:

scodb> reboot()

>Bela<