System is not able to mount the disk

QNX Newsgroups (Archives) qdn.public.qnx4
1

Hi to everyone,

I am trying to install QNX 4.25 on my PC in order to use an application to
read logfiles. First of all, I used a Rescue CD with SYSLinux 1.76 to
create a QNX partition with FDISK on my harddisk with the following
specifications:

Device Boot Start End Blocks Id System
/dev/hda1 1 1024 8225248 4d Qnx4.x

Then, I used my bootfloppy in combination with my CD. It boots Qnx from
the floppy however it displays the following message:

  1. Starting QNX
  2. Creating QNX harddisk partition
  3. Making QNX harddisk partition bootable
  4. Mounting /dev/hd0
    Mount -p: skipping mount of duplicate partition type 77 on /dev/hd0
  5. Initializing /dev/hd0t77. /dev/hd0t77 is not a floppy or a ramdisk.
  6. Disk /dev/hd0t77 contains 16450497 blocks etc.
  7. Mounting /dev/hd0t77 as /hd
    :sunglasses: Loading operating system
  8. Copying QNX kernel
  9. Copying QNX license files to /hd/etc/licences

From now on, if I reboot my system it says: mount -p: open() on /dev/hd0
failed: No such file or directory

What I understand is, that my FDISK program creates a partition with a
name or volume(/dev/hda1) that is different from that what my Qnx
installation program expects(dev/hd0)? Is this true, and if so, how can I
solve this.

Can somebody help me to solve this problem?

Thanks in advance,

Johan Ditzel, Netherlands

2

“Johan Ditzel” <johan.ditzel@siemens.com> wrote in message
news:bbr3np$q4b$1@tiger.openqnx.com…

Hi to everyone,

I am trying to install QNX 4.25 on my PC in order to use an application to
read logfiles. First of all, I used a Rescue CD with SYSLinux 1.76 to
create a QNX partition with FDISK on my harddisk with the following
specifications:

Device Boot Start End Blocks Id System
/dev/hda1 1 1024 8225248 4d Qnx4.x

Then, I used my bootfloppy in combination with my CD. It boots Qnx from
the floppy however it displays the following message:

  1. Starting QNX
  2. Creating QNX harddisk partition
  3. Making QNX harddisk partition bootable
  4. Mounting /dev/hd0
    Mount -p: skipping mount of duplicate partition type 77 on /dev/hd0
  5. Initializing /dev/hd0t77. /dev/hd0t77 is not a floppy or a ramdisk.
  6. Disk /dev/hd0t77 contains 16450497 blocks etc.
  7. Mounting /dev/hd0t77 as /hd
    :sunglasses: > Loading operating system
  8. Copying QNX kernel
  9. Copying QNX license files to /hd/etc/licences

From now on, if I reboot my system it says: mount -p: open() on /dev/hd0
failed: No such file or directory

What I understand is, that my FDISK program creates a partition with a
name or volume(/dev/hda1) that is different from that what my Qnx
installation program expects(dev/hd0)? Is this true, and if so, how can I
solve this.

Name is totaly irrelavant. In fact I don’t beleive it’s stored in the
partition table at all. Under QNX you could start the Fsys driver and get
the partition to appear under a total different name.

Can somebody help me to solve this problem?

First you don’t need to use Linux to create the partition. Installation
procedure from CD allows you to create partition. This must be an old
install CD because the lastest CD will map the drive as /dev/hd0.0. Could
you give more info as what version of CD and floppy you are using?

Thanks in advance,

Johan Ditzel, Netherlands

3

Johan Ditzel wrote:

Hi to everyone,

I am trying to install QNX 4.25 on my PC in order to use an application to
read logfiles. First of all, I used a Rescue CD with SYSLinux 1.76 to
create a QNX partition with FDISK on my harddisk with the following
specifications:

Device Boot Start End Blocks Id System
/dev/hda1 1 1024 8225248 4d Qnx4.x

Then, I used my bootfloppy in combination with my CD. It boots Qnx from
the floppy however it displays the following message:

  1. Starting QNX
  2. Creating QNX harddisk partition
  3. Making QNX harddisk partition bootable
  4. Mounting /dev/hd0
    Mount -p: skipping mount of duplicate partition type 77 on /dev/hd0
  5. Initializing /dev/hd0t77. /dev/hd0t77 is not a floppy or a ramdisk.
  6. Disk /dev/hd0t77 contains 16450497 blocks etc.
  7. Mounting /dev/hd0t77 as /hd
    :sunglasses: > Loading operating system
  8. Copying QNX kernel
  9. Copying QNX license files to /hd/etc/licences

From now on, if I reboot my system it says: mount -p: open() on /dev/hd0
failed: No such file or directory

What I understand is, that my FDISK program creates a partition with a
name or volume(/dev/hda1) that is different from that what my Qnx
installation program expects(dev/hd0)? Is this true, and if so, how can I
solve this.

Can somebody help me to solve this problem?

Thanks in advance,

Johan Ditzel, Netherlands

Mario,

Thanks for your reply, the CD and floppy are not the orriginial cd and
floppy of qnx, I have two floppies, an initial install boot disk and an
upgrade install boot disk and a cd. Yesterday, I used Fdisk on the upgrade
install disk to initialize my disk as /dev/hd0, and did the installation
again. Now, the installation was completed without errors. But if I reboot
my computer the same errormessage is reported. So, I am able to do the
installation but after restarting my computer the following messages
appears:

Verifying DMI pool data
QNX loader
Boot partition 1
Press Esc for alternate OS
No adapters found
Mount -p: open() on /dev/hd0 failed: No such file or directory

Any idea why?

Thanks,

Johan

4

Mario,

Thanks for your reply, the CD and floppy are not the orriginial cd and
floppy of qnx, I have two floppies, an initial install boot disk and an
upgrade install boot disk and a cd. Yesterday, I used Fdisk on the upgrade
install disk to initialize my disk as /dev/hd0, and did the installation
again. Now, the installation was completed without errors. But if I reboot
my computer the same errormessage is reported. So, I am able to do the
installation but after restarting my computer the following messages
appears:

Verifying DMI pool data
QNX loader
Boot partition 1
Press Esc for alternate OS
No adapters found

No adapters found tell you the driver that is in the .boot file didnt find matching hardware. I dont understand why it would do that.

AFter the install, run sin args and check what driver is started and find
the argument to the Fsys driver. Then compare to what the install CD use to
create the image file.

Mount -p: open() on /dev/hd0 failed: No such file or directory

Any idea why?

Thanks,

Johan

\