Updating Fsys.eide during floppy install.

Hello:

I’m doing my first installation to a system with a hard drive larger
than 8.2GB,
and am having some trouble.

I’m working with the 4.25 diskset, and a 4.25A boot floppy.

The boot floppy seems to have no trouble seeing the full drive (I’m
making
the entire drive one large QNX partition) but after the apparently
successful
installation completes and I reboot, I get a message saying the
partition is
too large for the drive when the system gets to the second loader.

I believe that I’m not getting the verson of Fsys.eide that I need onto
the drive.
The floppy has a version of Fsys.eide that is 68474 bytes in size, is
dated
18-nov-1998 and that “sin ver” reports is v4.24N while the hard drive
winds
up with a version (presumably from the 425 install diskset) that is
68014
bytes in size, is dated 13-may-1998 and seems to be v4.24M. I have seen
other postings that indicated that people installed the patchA s/w but I
am
not sure how I can do this without rebooting the PC.

Can someone tell me how to update the version of Fsys.eide (or install
the
correct patch) from this floppy install before rebooting the first time?

Thanks in advance.
Kevin B.

Following up my own post (after some more noodling with the system
in question) I wrote:

I’m working with the 4.25 diskset, and a 4.25A boot floppy.

The boot floppy seems to have no trouble seeing the full drive (I’m
making the entire drive one large QNX partition) but after the
apparently successful installation completes and I reboot, I get a
message saying the partition is too large for the drive when the
system gets to the second loader.

I believe that I’m not getting the verson of Fsys.eide that I need
onto the drive.

I managed to get the same version of Fsys.eide onto the hard drive.
I doesn’t help: when the system gets to the second loader it still
complains about the partition not fitting on the drive.

A quick rundown of the H/W and S/W I’m working with:

  • ASUS P3V4X motherboard with 64MB RAM.
  • Quantum LM10.2 10.2GB hard drive, with shielded 80-pin ribbon.
  • QNX 4.25 installation diskset with v4.25A boot floppy. (Fsys.eide
    with >8.4GB HD support.)

BIOS settings:

  • HD type: Auto

With the above settings and gear, the installation seems to proceed
normally, with one exception. Early in the install after executing
Fsys.eide, the system pauses and begins to print out the following
message:

Waiting for /dev/hd0 to initialize.

This is repeated nine times, and then the installation continues.

[Note: While this message is not printed, there is also a noticeable
delay if I boot from the install boot floppy and manually run
Fsys.eide before I get a console message indicating that the HD
has been recognized.]

Since this system will be dedicated to QNX, I instruct fdisk to create
a single partition on the drive that uses all of the available space.

[Note: I have seen messages that indicate that the requirement is
that the entire boot file be below the 1024 cyliner range because
of a BIOS limitation. With the size of the 4.25 OS, this should
not be a problem, but does this limitation mean that I cannot
successfully create a single QNX partition larger than 8.2GB?]

The installation seems to complete successfully. Before rebooting I am
able to list and run commands from /hd.

After taking out the last floppy and rebooting, the system restarts
and seems to have no difficulty with the primary loader. It gets to
the secondary loader and prints:

starting QNX…

and then after a delay, it prints the following to the console:

Path=0 - EIDE
target=0 lun=0 Direct-Access(0) - QUANTUM FIREBALL Rev:
mount -p: cannot mount partition 77 (04dh) on /dev/hd0:
error No space left on device
disk /dev/hd0 has 16514064 sectors
partition (63…20065185) does not fit within disk

If I reboot from the installation boot floppy and run fdisk on
/dev/hd0, QNX’s fdisk reports the following:

Start cylinder: 0
End cylinder: 1248
Number of:
cylinders: 1249
blocks: 20065185
Size: 9797MB
Bootable: maybe
255 heads/63 sectors-per-track/1249 heads

Why does the loader report that /dev/hd0 has 16514064 sectors
when fdisk reports 20065185?

I’ve confirmed that the version of /bin/Fsys.eide that appears on
/dev/hd0 is the one from the v4.25A boot floppy. I’ve also tried
changing the drive parameters:

HD Type from “Auto” to “User Defined”
HD Translation to “match partition table”

and I’ve tried disabling UDMA in the BIOS. So far nothing has changed
the behaviour on bootup.

I know that others have had trouble with larger drives. In fact, from
some earlier postings I had saved, the 10GB drives seemed to be more
trouble than drives in the 20 and 30GB range.

Can someone point me in the right direction so that I can get the
system booting (and then try configuring all of the other new
hardware in the system!)?

Thanks in advance.
Kevin B.

Kevin.Beauchamp <Kevin.Beauchamp@ualberta.ca> wrote in message
news:39B02EA0.4C0C6A52@ualberta.ca

Following up my own post (after some more noodling with the system
in question) I wrote:

I’m working with the 4.25 diskset, and a 4.25A boot floppy.

The boot floppy seems to have no trouble seeing the full drive (I’m
making the entire drive one large QNX partition) but after the
apparently successful installation completes and I reboot, I get a
message saying the partition is too large for the drive when the
system gets to the second loader.

I believe that I’m not getting the verson of Fsys.eide that I need
onto the drive.

I managed to get the same version of Fsys.eide onto the hard drive.
I doesn’t help: when the system gets to the second loader it still
complains about the partition not fitting on the drive.

I used an updated driver from Qnx

-rwxrwxr-x 1 root root 69654 May 25 1999 Fsys.eide*

which handles large drives.

I’ve confirmed that the version of /bin/Fsys.eide that appears on
/dev/hd0 is the one from the v4.25A boot floppy. I’ve also tried
changing the drive parameters:
Thanks in advance.
Kevin B.

Glenn Sherman wrote:

Kevin.Beauchamp <> Kevin.Beauchamp@ualberta.ca> > wrote:


I’m working with the 4.25 diskset, and a 4.25A boot floppy.

The boot floppy seems to have no trouble seeing the full drive (I’m
making the entire drive one large QNX partition) but after the
apparently successful installation completes and I reboot, I get a
message saying the partition is too large for the drive when the
system gets to the second loader.

I used an updated driver from Qnx

-rwxrwxr-x 1 root root 69654 May 25 1999 Fsys.eide*

which handles large drives.

I tried the latest version of Fsys.eide that I have around here (a version
from one of the v4.25D updates that has a file date of 09-Feb-2000, and
is 70437 bytes in size). I dumped it onto the v4.25A boot floppy and then,
after the installation was complete, manually copied it into /bin on the
hard
drive.

I hasn’t helped: at boot the system still complains that the defined
partition
is too large for the drive. :frowning:

I wish I could find out why it insists at boot time that the drive only has
16514064
sectors when during the installation is recognizes that it has a capacity
of 20065185.

Kevin B.

Kevin.Beauchamp <Kevin.Beauchamp@ualberta.ca> wrote in message
news:39B64A68.EF8B4724@ualberta.ca

Glenn Sherman wrote:
Kevin.Beauchamp <> Kevin.Beauchamp@ualberta.ca> > wrote:


I’m working with the 4.25 diskset, and a 4.25A boot floppy.

The boot floppy seems to have no trouble seeing the full drive (I’m
making the entire drive one large QNX partition) but after the
apparently successful installation completes and I reboot, I get a
message saying the partition is too large for the drive when the
system gets to the second loader.

I used an updated driver from Qnx

-rwxrwxr-x 1 root root 69654 May 25 1999 Fsys.eide*

which handles large drives.

I tried the latest version of Fsys.eide that I have around here (a version
from one of the v4.25D updates that has a file date of 09-Feb-2000, and
is 70437 bytes in size). I dumped it onto the v4.25A boot floppy and then,
after the installation was complete, manually copied it into /bin on the
hard
drive.

Did you put it into the /bin directory on the boot floppy?
(Is it using the updated Fsys.eide during the install?)

I hasn’t helped: at boot the system still complains that the defined
partition
is too large for the drive. > :frowning:

I wish I could find out why it insists at boot time that the drive only
has
16514064
sectors when during the installation is recognizes that it has a capacity
of 20065185.

Kevin B.

-Glenn Sherman

Glenn Sherman wrote:

Kevin.Beauchamp <> Kevin.Beauchamp@ualberta.ca> > wrote:

I tried the latest version of Fsys.eide that I have around here (a version
from one of the v4.25D updates that has a file date of 09-Feb-2000, and
is 70437 bytes in size). I dumped it onto the v4.25A boot floppy and then,
after the installation was complete, manually copied it into /bin on the
hard drive.

Did you put it into the /bin directory on the boot floppy?
(Is it using the updated Fsys.eide during the install?)

Yes; at least I think so, although the method I’m using feels a little
ham-fisted.

Once the installation is complete, and before I reboot, I try to update
the copy of Fsys.eide on the hard drive. With the installation bootdisk
containing the updated Fsys.eide still in the floppy drive, I type the
following commands:

umount /dev/fd0
mount /dev/fd0 /fd
cp /fd/bin/Fsys.eide /hd/bin/Fsys.eide

It almost seems as if there is either an old copy of Fsys.eide still active,
or that there is some parameter/partition information that is not being
“scrubbed” off the drive when I use fdisk to delete the partitions
created by the earlier installations.

I was going to try an installation with the HD translation set explicitly
to “LBA” and with the installation command invoked with this
condition:

install -p “eide -c 255,1249,63”

but my v4.25 install disk set is now toast. I’m going to have to create
another copy of the first disk (at least) and try again.

Thanks
Kevin B.

Once the installation is complete, and before I reboot, I try to update
the copy of Fsys.eide on the hard drive. With the installation bootdisk
containing the updated Fsys.eide still in the floppy drive, I type the
following commands:

umount /dev/fd0
mount /dev/fd0 /fd
cp /fd/bin/Fsys.eide /hd/bin/Fsys.eide

This is too late, as the Fsys.eide driver is bound into the
boot image.
You must rebuild the boot image in order to use n a new Fsys.eide.
If your system is “live”, rebuild the boot image & copy to /.boot
before rebooting.

Anyhow, I believe if you do “install -v -u”, the script will prompt
you for a Fsys driver at some point during the install.
You can then insert a separate disk with the new driver on it.

Also, you cannot (anyways I have not been able to) access the upgrade
boot
disk or other disks in the normal way. (ie you can’t mount that boot dis
or the other disks).
So copying anything to them is not going be useful.

Try the -v option, I think that will do it for you.

Alex Cellarius <acellarius@systems104.co.za> wrote in message
news:39B6B4AC.CA106ABC@systems104.co.za

Once the installation is complete, and before I reboot, I try to update
the copy of Fsys.eide on the hard drive. With the installation bootdisk
containing the updated Fsys.eide still in the floppy drive, I type the
following commands:

umount /dev/fd0
mount /dev/fd0 /fd
cp /fd/bin/Fsys.eide /hd/bin/Fsys.eide

This is too late, as the Fsys.eide driver is bound into the
boot image.
You must rebuild the boot image in order to use n a new Fsys.eide.
If your system is “live”, rebuild the boot image & copy to /.boot
before rebooting.

I don’t think this is the case. The boot image on the floppy should
have no reference to the Fsys.eide driver. The Fsys.eide driver is
started during the install process.

Anyhow, I believe if you do “install -v -u”, the script will prompt
you for a Fsys driver at some point during the install.
You can then insert a separate disk with the new driver on it.

Don’t use the -u option if you want to do a fresh install.

Also, you cannot (anyways I have not been able to) access the upgrade
boot
disk or other disks in the normal way. (ie you can’t mount that boot dis
or the other disks).
So copying anything to them is not going be useful.

You CAN add or change the boot disk, or you can make your own. You can not
simply copy things to the others disks. You could read them into a tar
file, then
extract them into a directory tree, make changes to that directory tree,
then create
a new tar file and copy that back out to floppies.

You may only what a few things to get loaded on a new system.

Try the -v option, I think that will do it for you.

I am moving my office tomorrow, but after I get settled in to my new space,
I will try setting up a new (large) disk and tell you what I have to do to
get
it to work.


You may want to try deleting all of the partition data and then rebooting
the
machine, and start fresh.

-Glenn Sherman

Alex Cellarius wrote:

Once the installation is complete, and before I reboot, I try to update
the copy of Fsys.eide on the hard drive. With the installation bootdisk
containing the updated Fsys.eide still in the floppy drive, I type the
following commands:

umount /dev/fd0
mount /dev/fd0 /fd
cp /fd/bin/Fsys.eide /hd/bin/Fsys.eide

This is too late, as the Fsys.eide driver is bound into the
boot image.
You must rebuild the boot image in order to use n a new Fsys.eide.
If your system is “live”, rebuild the boot image & copy to /.boot
before rebooting.

Of course! I totally overlooked that step! (Sound of hand slapping forehead).

When your message came in I was (again) half-way through an install. After
updating the version of Fsys.eide on the hard drive, I rebooted and mounted
the disk from the floppy, rebuilt the image and rebooted - successfully!

Anyhow, I believe if you do “install -v -u”, the script will prompt
you for a Fsys driver at some point during the install.
You can then insert a separate disk with the new driver on it.

Also, you cannot (anyways I have not been able to) access the upgrade
boot disk or other disks in the normal way. (ie you can’t mount that
boot disk or the other disks). So copying anything to them is not going
to be useful.

Try the -v option, I think that will do it for you.

I will remember the -v option for next time.

Thanks to both Alex and Glenn for their help.

Kevin B.

I do a considerable amount of new install now and this is how I had to handle
this. I create my own 4.25D boot disk by mounting the boot disk and replacing
the Fsys.eide. I also replaced the SCSI and Net drivers then edited the driver
list to reflect the changes (floppy disk too small for all the drivers so I had
to remove some I will never use). I then make the install BUT before I reboot,
I copy the /fd/bin/Fsys.eide to /hd/bin/ then rebuild the boot image and
re-install it to /hd/.boot (the Net files also if needed such as Net.via). This
gives me the eide driver to bring up the system on the first shot. I then have
the ability to get the machine on our network and download all the rest of the
files I need to install.

The problem is that you may have the latest drivers on your boot disk but the
install uses the drivers from the install disks.

Douglas M. Barker (800) 387-4876 (toll free)
Software Support Engineer (519) 888-9304 (voice)
PC Automation Inc. (519) 888-9085 (fax)
925 Erb St. W., Waterloo email: support@pcauto.com
Ontario, Canada, N2J 3Z4


Alex Cellarius wrote:

Once the installation is complete, and before I reboot, I try to update
the copy of Fsys.eide on the hard drive. With the installation bootdisk
containing the updated Fsys.eide still in the floppy drive, I type the
following commands:

umount /dev/fd0
mount /dev/fd0 /fd
cp /fd/bin/Fsys.eide /hd/bin/Fsys.eide

This is too late, as the Fsys.eide driver is bound into the
boot image.
You must rebuild the boot image in order to use n a new Fsys.eide.
If your system is “live”, rebuild the boot image & copy to /.boot
before rebooting.

Anyhow, I believe if you do “install -v -u”, the script will prompt
you for a Fsys driver at some point during the install.
You can then insert a separate disk with the new driver on it.

Also, you cannot (anyways I have not been able to) access the upgrade
boot
disk or other disks in the normal way. (ie you can’t mount that boot dis
or the other disks).
So copying anything to them is not going be useful.

Try the -v option, I think that will do it for you.