LILO problem or DOS fault ?

LILO problem or DOS fault ?

Post by Nicola Fabian » Mon, 20 Oct 1997 04:00:00



Hello all. I have a strange problem with (perhaps?) LILO.
I have two disks, and I had to reinstall on the first because the
old disk died. The new unit is a Quantum 4.3 G.
Linux, of course, works perfectly. The problem is DOS 6.2 . It won't
boot; every time I receive the message (translated from italian)

non system disk or disk problem, replace and strike any key

Needless to say that the partition is OK, with its COMMAND.COM and
io.sys and msdos.sys . If I boot from a diskette, all is fine.
Needless to say that Dosemu and Wine work perfectly.

I have tried everything, I have tried also making again the partition
with DOS fdisk and format (because of the DOS 6.x caveat) to no avail.

Here is fdisk's output of /dev/hda:

Disk /dev/hda: 255 heads, 63 sectors, 524 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot   Begin    Start      End   Blocks   Id  System
/dev/hda1   *      422      422      476   441787+   6  DOS 16-bit >=32M
/dev/hda2            1        1      421  3381651   83  Linux native
/dev/hda3          477      477      523   377527+   5  Extended
/dev/hda5          477      477      523   377496    6  DOS 16-bit >=32M

The only doubt I have is that the DOS partition is not the first on a disk
larger than 2.1 G, but in this case I should have a problem when
formatting
also becasue of FAT. Moreover, the fact that the DOS partition is not the
first
should be OK because I had a similar setup on the previous disk without
trouble
(except for the fact that it was a 1.6 G disk).

Have ad excerpt of lilo.config for LILO v1.9 also:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="aha152x=0x340,11,7"
boot = /dev/hda
#compact        # faster, but won't work on all systems.
delay = 50
vga = normal    # force sane state
ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /vmlinuz
  root = /dev/hda2
  label = linux
  read-only # Non-UMSDOS filesystems should be mounted read-only for
checking
...
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda1
  label = dos
  table = /dev/hda
# DOS bootable partition config ends

I am out of ideas. If anyone could help me, I would appreciate it.

System list:

Slakware 96, kernel 2.0.30, X3.3.1, 64 megs ram, K6-200,
hda: Quantum 4.3 G
hdb: Quantum 3.2 G
hdc: CD Pioneer 12x

Thank you in advance.

 
 
 

LILO problem or DOS fault ?

Post by Chris Pet » Mon, 20 Oct 1997 04:00:00




Quote:

> Hello all. I have a strange problem with (perhaps?) LILO.
> I have two disks, and I had to reinstall on the first because the
> old disk died. The new unit is a Quantum 4.3 G.
> Linux, of course, works perfectly. The problem is DOS 6.2 . It won't
> boot; every time I receive the message (translated from italian)

> non system disk or disk problem, replace and strike any key

> Needless to say that the partition is OK, with its COMMAND.COM and
> io.sys and msdos.sys . If I boot from a diskette, all is fine.
> Needless to say that Dosemu and Wine work perfectly.

        That means the partition is not bootable on its own.

        To correct this, copy SYS.COM to the floppy you use to DOS boot.

        Then, boot with the floppy and type "sys c:"

        That should fix it.

-------------------------------------------------------
"The world will never suffer from a lack of stupidity."

 
 
 

LILO problem or DOS fault ?

Post by Reinhard Karch » Tue, 21 Oct 1997 04:00:00



> Subject: LILO problem or DOS fault ?
> Hello all. I have a strange problem with (perhaps?) LILO.
> I have two disks, and I had to reinstall on the first because the
> old disk died. The new unit is a Quantum 4.3 G.
> Linux, of course, works perfectly. The problem is DOS 6.2 . It won't
> boot; every time I receive the message (translated from italian)
> non system disk or disk problem, replace and strike any key
> Here is fdisk's output of /dev/hda:
> Disk /dev/hda: 255 heads, 63 sectors, 524 cylinders
> Units = cylinders of 16065 * 512 bytes
>    Device Boot   Begin    Start      End   Blocks   Id  System
> /dev/hda1   *      422      422      476   441787+   6  DOS 16-bit >=32M
> /dev/hda2            1        1      421  3381651   83  Linux native
> /dev/hda3          477      477      523   377527+   5  Extended
> /dev/hda5          477      477      523   377496    6  DOS 16-bit >=32M
> The only doubt I have is that the DOS partition is not the first on a disk
> larger than 2.1 G, but in this case I should have a problem when
> formatting
> also becasue of FAT. Moreover, the fact that the DOS partition is not the
> first
> should be OK because I had a similar setup on the previous disk without
> trouble
> (except for the fact that it was a 1.6 G disk).

Hello Nicola,
may be the last point is exactly your problem. If your bios does not
operate in the LBA-Mode on your disk, it can only boot the 1st 512MB of
the disk (because of addressing problems).
Your DOS-Partition is clearly beyond that level ( 3,381,651 blocks are
nearly 1700 MB).
On your 1.6 G disk, there was not so much space.

Reinhard

 
 
 

LILO problem or DOS fault ?

Post by Eric Ladne » Tue, 21 Oct 1997 04:00:00



> Hello all. I have a strange problem with (perhaps?) LILO.
> I have two disks, and I had to reinstall on the first because the
> old disk died. The new unit is a Quantum 4.3 G.
> Linux, of course, works perfectly. The problem is DOS 6.2 . It won't
> boot; every time I receive the message (translated from italian)

> non system disk or disk problem, replace and strike any key

I am having the exact same problem (though through different means).  If
you find a solution to this, please shoot me a copy of the answer.  I'll
keep an eye out as well.

Eric

--
-------------------------------------------------------------
Eric Ladner                    Oracle 7.X DBA and SysAdmin on    

#include <disclamer.h>      favorite, Linux: It works for me.
-------------------------------------------------------------

 
 
 

LILO problem or DOS fault ?

Post by Eric Ladne » Wed, 22 Oct 1997 04:00:00


If your dos partition is not on the first disk, (/dev/hdb1 for example)
the lilo stanza for it will look like this:

other=/dev/hdb1
        table=/dev/hdb
        loader=/boot/any_d.b
        label=dos

This assumes you are using a 2.0 kernel...
--
-------------------------------------------------------------
Eric Ladner                    Oracle 7.X DBA and SysAdmin on    

#include <disclamer.h>      favorite, Linux: It works for me.
-------------------------------------------------------------

 
 
 

1. LILO trouble or DOS fault ?

Hello all. I have a strange problem with (perhaps?) LILO.
I have two disks, and I had to reinstall on the first because the
old disk died. The new unit is a Quantum 4.3 G.
Linux, of course, works perfectly. The problem is DOS 6.2 . It won't
boot; every time I receive the message (translated from italian)

non system disk or disk problem, replace and strike any key

Needless to say that the partition is OK, with its COMMAND.COM and
io.sys and msdos.sys . If I boot from a diskette, all is fine.
Needless to say that Dosemu and Wine work perfectly.

I have tried everything, I have tried also making again the partition
with DOS fdisk and format (because of the DOS 6.x caveat) to no avail.

Here is fdisk's output of /dev/hda:

Disk /dev/hda: 255 heads, 63 sectors, 524 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot   Begin    Start      End   Blocks   Id  System
/dev/hda1   *      422      422      476   441787+   6  DOS 16-bit >=32M
/dev/hda2            1        1      421  3381651   83  Linux native
/dev/hda3          477      477      523   377527+   5  Extended
/dev/hda5          477      477      523   377496    6  DOS 16-bit >=32M

The only doubt I have is that the DOS partition is not the first on a disk
larger than 2.1 G, but in this case I should have a problem when
formatting
also becasue of FAT. Moreover, the fact that the DOS partition is not the
first
should be OK because I had a similar setup on the previous disk without
trouble
(except for the fact that it was a 1.6 G disk).

Have ad excerpt of lilo.config for LILO v1.9 also:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="aha152x=0x340,11,7"
boot = /dev/hda
#compact        # faster, but won't work on all systems.
delay = 50
vga = normal    # force sane state
ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /vmlinuz
  root = /dev/hda2
  label = linux
  read-only # Non-UMSDOS filesystems should be mounted read-only for
checking
...
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda1
  label = dos
  table = /dev/hda
# DOS bootable partition config ends

I am out of ideas. If anyone could help me, I would appreciate it.

System list:

Slakware 96, kernel 2.0.30, X3.3.1, 64 megs ram, K6-200,
hda: Quantum 4.3 G
hdb: Quantum 3.2 G
hdc: CD Pioneer 12x

Thank you in advance.

2. Long delay detecting HD and CDROM

3. LILO: Linux + DOS-W311 + DOS/W95-Upgrade

4. mountd/nfsd 1.2.9 problems....

5. How to Uninstall LILO -o How to boot DOS once LILO is installed?

6. dtterm keymap

7. Lilo Help: How do I default Lilo to Dos Partition?

8. Communicator "Check for mail" not working with UnixWare popper

9. LILO error: Can only boot from floppy, LILO will only start dos not linux

10. LILO problem, Linux load ok, DOS = hang

11. LILO problem: Cannot boot into Dos?

12. Red Hat 5 Partition LILO/DOS/NTFS problem newbie needshelp.urgent

13. Problem booting DOS from Lilo