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

Error adding an IDE drive to a SCSI boot disk

82 views
Skip to first unread message

willme...@consys.de

unread,
Sep 30, 1997, 3:00:00 AM9/30/97
to

We installed a SCO Open Server 5.0.4 with a SCSI-drive.
All is ok, but now we tested to append a IDE-drive as a second drive.
The Motherboard-BIOS allows to change the boot drive from IDE to SCSI. We
switched this
flag to SCSI and booted our system. We installed the IDE drive by "mkdev
hd".
The kernel was relinked but now:
After showing the different hardware components we see following output:

%disk 0x01f0-0x01f7 14 - type=W0 unit=0 clys=1018 hs=33 secs=63
H iinit
PANIC: srmountfun - Error 22 mounting rootdev hd (1/42)
Cannot dump .. to dumpdev hd (1/41): Space for only 0 pages

Dump not completed

It seems that the system tries to boot from the IDE-drive, which is not
what we want.
When booting from unix.old, the system runs well
there is also another line for the disk-entry, it shows:
%disk - - type=S ha=0 id=0 lun=0 bus=0 ht=slha

We do not need the additional IDE disk, how can we change back to the old
configuration.


Walter Willmertinger

CONSYS Gesellschaft für Softwaretechnologie und Systementwicklung mbH
Dr. Walter Willmertinger
Landsberger Strasse 402 EMail: willme...@consys.de
81241 Muenchen Phone: +49 89 580 81 81
Germany Fax: +49 89 588 77 6
WWW-Homepage: http://www.consys.de

-------------------==== Posted via Deja News ====-----------------------
http://www.dejanews.com/ Search, Read, Post to Usenet

Bela Lubkin

unread,
Sep 30, 1997, 3:00:00 AM9/30/97
to

Walter Willmertinger wrote:

> We installed a SCO Open Server 5.0.4 with a SCSI-drive.
> All is ok, but now we tested to append a IDE-drive as a second drive.
> The Motherboard-BIOS allows to change the boot drive from IDE to SCSI. We
> switched this
> flag to SCSI and booted our system. We installed the IDE drive by "mkdev
> hd".
> The kernel was relinked but now:
> After showing the different hardware components we see following output:
>
> %disk 0x01f0-0x01f7 14 - type=W0 unit=0 clys=1018 hs=33 secs=63
> H iinit
> PANIC: srmountfun - Error 22 mounting rootdev hd (1/42)
> Cannot dump .. to dumpdev hd (1/41): Space for only 0 pages
>
> Dump not completed
>
> It seems that the system tries to boot from the IDE-drive, which is not
> what we want.
> When booting from unix.old, the system runs well
> there is also another line for the disk-entry, it shows:
> %disk - - type=S ha=0 id=0 lun=0 bus=0 ht=slha
>
> We do not need the additional IDE disk, how can we change back to the old
> configuration.

An article in the SCO Technical Articles database describes how to
remove hard disk configuration information from the kernel. Search
http://www5.sco.com/Support/ssl.html.

Instead, however, see what happens if you boot the new kernel with:

Boot
: defbootstr hd=Sdsk

This should make the kernel see the SCSI disk as the root drive. I
would be interested in knowing whether, having done that, you can also
access the IDE drive from Unix (as non-primary drive).

>Bela<

willme...@consys.de

unread,
Oct 1, 1997, 3:00:00 AM10/1/97
to

In article <970930195...@vagabond.armory.com>,

Bela Lubkin <be...@sco.com> wrote:
>
> Walter Willmertinger wrote:
>
> > We installed a SCO Open Server 5.0.4 with a SCSI-drive.
> > All is ok, but now we tested to append a IDE-drive as a second drive.
>
> Instead, however, see what happens if you boot the new kernel with:
>
> Boot
> : defbootstr hd=Sdsk
>
> This should make the kernel see the SCSI disk as the root drive. I
> would be interested in knowing whether, having done that, you can also
> access the IDE drive from Unix (as non-primary drive).
>
> >Bela<

Thank you, Bela Lubkin, for the tip (defbootstr hd=Sdsk). This really
works.

But now I tried to use the IDE disk as a second disk in our system. I
called "mkdev hd" and it recognizes the disk, but with completely wrong
disk parameters. Do you know what it uses? It uses the disk parameter of
the first SCSI disk, not the parameters of the IDE disk. But it seems to
access the IDE disk, because I saw an installed NTFS file system on the
disk, when configuring the partition (by the way, it recognized an OS/2
disk, not an Windows NT NTFS file system). Now I tried another
configuration. We switched the IDE disk to Slave. I read in the "mkdev hd
-u", to try "mkdev hd 1 IDE-0". Then we get the error message "Can't add
an IDE controller to ESDI or SCSI system". Now tried "mkdev hd 1 0" .
This wants to include a SCSI disk. I tried to use "wd" as SCSI adapter.
But this did not work, also not after relinking the kernel.

But as I wrote, we do not need the additional IDE disk, so we change back
to the old configuration by using the defbootstr mentioned above.

Bela Lubkin

unread,
Oct 1, 1997, 3:00:00 AM10/1/97
to

Walter Willmertinger wrote:

> > > We installed a SCO Open Server 5.0.4 with a SCSI-drive.
> > > All is ok, but now we tested to append a IDE-drive as a second drive.
> >
> > Instead, however, see what happens if you boot the new kernel with:
> >
> > Boot
> > : defbootstr hd=Sdsk
> >
> > This should make the kernel see the SCSI disk as the root drive. I
> > would be interested in knowing whether, having done that, you can also
> > access the IDE drive from Unix (as non-primary drive).

> Thank you, Bela Lubkin, for the tip (defbootstr hd=Sdsk). This really
> works.

Good.

> But now I tried to use the IDE disk as a second disk in our system. I
> called "mkdev hd" and it recognizes the disk, but with completely wrong
> disk parameters. Do you know what it uses? It uses the disk parameter of
> the first SCSI disk, not the parameters of the IDE disk. But it seems to
> access the IDE disk, because I saw an installed NTFS file system on the
> disk, when configuring the partition (by the way, it recognized an OS/2
> disk, not an Windows NT NTFS file system). Now I tried another
> configuration. We switched the IDE disk to Slave. I read in the "mkdev hd
> -u", to try "mkdev hd 1 IDE-0". Then we get the error message "Can't add
> an IDE controller to ESDI or SCSI system". Now tried "mkdev hd 1 0" .
> This wants to include a SCSI disk. I tried to use "wd" as SCSI adapter.
> But this did not work, also not after relinking the kernel.

Ah -- I should have explained a bit more.

For OpenServer, booting from a SCSI drive and also accessing an IDE
drive is a completely unexpected configuration. The operating system
"knows" that if an IDE drive exists, it must be the boot drive. It is a
fairly recent development in BIOSes, to allow booting from a SCSI drive
while an IDE drive is present.

So, for instance, the `mkdev hd` script "knows" that if you have a SCSI
root drive, you can't add an IDE drive. I'm not sure how you got it to
agree to do that at all. The message you got when you ran `mkdev hd 1
IDE-0` is what I would have expected. `mkdev hd 1 0` "knows" that you
can't be adding an IDE drive since the root is SCSI.

What I don't understand is what you did in the first place, to get to
the situation where you need to use "hd=Sdsk". What `mkdev hd` command
did you run?

> But as I wrote, we do not need the additional IDE disk, so we change back
> to the old configuration by using the defbootstr mentioned above.

That's probably the best plan for now. The scripts need some work to
deal with this situation.

>Bela<

willme...@consys.de

unread,
Oct 2, 1997, 3:00:00 AM10/2/97
to

In article <971001213...@vagabond.armory.com>,

Bela Lubkin <be...@sco.com> wrote:
>
> Walter Willmertinger wrote:
>
> > > > We installed a SCO Open Server 5.0.4 with a SCSI-drive.
> > > > All is ok, but now we tested to append a IDE-drive as a second drive.
...

> Ah -- I should have explained a bit more.
>
> For OpenServer, booting from a SCSI drive and also accessing an IDE
> drive is a completely unexpected configuration.
> What I don't understand is what you did in the first place, to get to
> the situation where you need to use "hd=Sdsk". What `mkdev hd` command
> did you run?

Very simple, just a normal "mkdev hd" with SCSI and IDE drive attached
and BIOS set to "Boot from SCSI drive"

>
...
> >Bela<

Bela Lubkin

unread,
Oct 3, 1997, 3:00:00 AM10/3/97
to

Walter Willmertinger wrote:

> > > > > We installed a SCO Open Server 5.0.4 with a SCSI-drive.
> > > > > All is ok, but now we tested to append a IDE-drive as a second drive.
> ...
> > Ah -- I should have explained a bit more.
> >
> > For OpenServer, booting from a SCSI drive and also accessing an IDE
> > drive is a completely unexpected configuration.
> > What I don't understand is what you did in the first place, to get to
> > the situation where you need to use "hd=Sdsk". What `mkdev hd` command
> > did you run?
>
> Very simple, just a normal "mkdev hd" with SCSI and IDE drive attached
> and BIOS set to "Boot from SCSI drive"

Ok, then I guess the scripts so little expect this that they don't even
protect against it. They simply "know" that the situation is impossible
because the IDE drive "always" boots first. :-(

>Bela<

--
Sandy & Bela Lubkin are traveling around the world for a year! Currently
posting from Moscow, Russia. Next: St. Petersburg; then Europe. Stories
and pictures are at http://www.armory.com/~alexia/trip/trip.html

0 new messages