LILO complains "Invalid partition table"

LILO complains "Invalid partition table"

Post by James R. Van Zan » Fri, 13 Jul 2001 06:17:14



I'm trying to set up a new Gateway Solo 3350 (20 GB disk) to dual boot
WindowsME and Debian Linux.  I used FIPS (latest version, downloaded
from the home site) to split the original FAT32 partition, and the
fdisk on the Debian 2.1 installation disk to delete the second
partition and install two new ones.  I got Linux installed on
/dev/hda3, and can boot it with a floppy.  Putting LILO on the MBR
failed, so I restored it with the DOS fdisk ("fdisk /mbr"). I'm now
trying to install the LILO loader on /dev/hda3.  However, LILO
complains about the partition table:

  Script started on Wed Jul 11 16:30:41 2001
  talon:~# fdisk -lu /dev/hda

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

     Device Boot    Start       End    Blocks   Id  System
  /dev/hda1   *        63  32354909  16177423+   c  Win95 FAT32 (LBA)
  /dev/hda2      32354910  32852924    249007+  82  Linux swap
  /dev/hda3      32852925  39070079   3108577+  83  Linux
  talon:~# lilo -v
  LILO version 21.5-1 beta, Copyright (C) 1992-1998 Werner Almesberger
  'lba32' extensions Copyright (C) 1999,2000 John Coffman

  Reading boot sector from /dev/hda3
  Device 0x0300: Invalid partition table, 3rd entry
    3D address:     63/254/1021 (16418429)
    Linear address: 1/0/2045 (32852925)
  talon:~# exit

  Script done on Wed Jul 11 16:30:57 2001

I remember FIPS mentioning an incorrect entry, but it assured me that
was no problem.  Not so, apparently.  I would appreciate any pointers
on diagnosing and fixing this.

My lilo.conf is attached, but I don't think lilo got far enough to
read it.

                - Jim Van Zandt

lba32
boot=/dev/hda3
root=/dev/hda3
compact
install=/boot/boot.b
map=/boot/map
delay=20
vga=normal
default=Linux
image=/boot/bzImage-2.4.5
        label=Linux
        read-only
image=/vmlinuz
        label=Linux-2.2.17
        read-only
image=/vmlinuz.old
        label=LinuxOLD
        read-only
        optional
other=/dev/hda1
        label=WindowsME
        alias=3

 
 
 

LILO complains "Invalid partition table"

Post by Glen Sanf » Fri, 13 Jul 2001 08:32:01



Quote:

> I'm trying to set up a new Gateway Solo 3350 (20 GB disk) to dual boot
> WindowsME and Debian Linux.  I used FIPS (latest version, downloaded
> from the home site) to split the original FAT32 partition, and the
> fdisk on the Debian 2.1 installation disk to delete the second
> partition and install two new ones.  I got Linux installed on
> /dev/hda3, and can boot it with a floppy.  Putting LILO on the MBR
> failed, so I restored it with the DOS fdisk ("fdisk /mbr"). I'm now
> trying to install the LILO loader on /dev/hda3.  However, LILO
> complains about the partition table:

>   Script started on Wed Jul 11 16:30:41 2001
>   talon:~# fdisk -lu /dev/hda

>   Disk /dev/hda: 255 heads, 63 sectors, 2432 cylinders
>   Units = sectors of 1 * 512 bytes

>      Device Boot    Start       End    Blocks   Id  System
>   /dev/hda1   *        63  32354909  16177423+   c  Win95 FAT32 (LBA)
>   /dev/hda2      32354910  32852924    249007+  82  Linux swap
>   /dev/hda3      32852925  39070079   3108577+  83  Linux
>   talon:~# lilo -v
>   LILO version 21.5-1 beta, Copyright (C) 1992-1998 Werner Almesberger
>   'lba32' extensions Copyright (C) 1999,2000 John Coffman

>   Reading boot sector from /dev/hda3
>   Device 0x0300: Invalid partition table, 3rd entry
>     3D address:     63/254/1021 (16418429)
>     Linear address: 1/0/2045 (32852925)
>   talon:~# exit

>   Script done on Wed Jul 11 16:30:57 2001

> I remember FIPS mentioning an incorrect entry, but it assured me that
> was no problem.  Not so, apparently.  I would appreciate any pointers
> on diagnosing and fixing this.

> My lilo.conf is attached, but I don't think lilo got far enough to
> read it.

>                 - Jim Van Zandt

> lba32
> boot=/dev/hda3
> root=/dev/hda3
> compact
> install=/boot/boot.b
> map=/boot/map
> delay=20
> vga=normal
> default=Linux
> image=/boot/bzImage-2.4.5
>         label=Linux
>         read-only
> image=/vmlinuz
>         label=Linux-2.2.17
>         read-only
> image=/vmlinuz.old
>         label=LinuxOLD
>         read-only
>         optional
> other=/dev/hda1
>         label=WindowsME
>         alias=3

Shouldn't that be "boot=/dev/hda"?

There is a line "table=/dev/hda" in your WindowsME section, isn't there?

What does the (v)erify function in fdisk have to say about it all?

Glen

 
 
 

LILO complains "Invalid partition table"

Post by Dave Uhrin » Fri, 13 Jul 2001 10:23:57




>> I'm trying to set up a new Gateway Solo 3350 (20 GB disk) to dual boot
>> WindowsME and Debian Linux.  I used FIPS (latest version, downloaded
>> from the home site) to split the original FAT32 partition, and the
>> fdisk on the Debian 2.1 installation disk to delete the second
>> partition and install two new ones.  I got Linux installed on
>> /dev/hda3, and can boot it with a floppy.  Putting LILO on the MBR
>> failed, so I restored it with the DOS fdisk ("fdisk /mbr"). I'm now
>> trying to install the LILO loader on /dev/hda3.  However, LILO
>> complains about the partition table:

>>   Script started on Wed Jul 11 16:30:41 2001
>>   talon:~# fdisk -lu /dev/hda

>>   Disk /dev/hda: 255 heads, 63 sectors, 2432 cylinders
>>   Units = sectors of 1 * 512 bytes

>>      Device Boot    Start       End    Blocks   Id  System
>>   /dev/hda1   *        63  32354909  16177423+   c  Win95 FAT32 (LBA)
>>   /dev/hda2      32354910  32852924    249007+  82  Linux swap
>>   /dev/hda3      32852925  39070079   3108577+  83  Linux
>>   talon:~# lilo -v
>>   LILO version 21.5-1 beta, Copyright (C) 1992-1998 Werner Almesberger
>>   'lba32' extensions Copyright (C) 1999,2000 John Coffman

>>   Reading boot sector from /dev/hda3
>>   Device 0x0300: Invalid partition table, 3rd entry
>>     3D address:     63/254/1021 (16418429)
>>     Linear address: 1/0/2045 (32852925)
>>   talon:~# exit

>>   Script done on Wed Jul 11 16:30:57 2001

>> I remember FIPS mentioning an incorrect entry, but it assured me that
>> was no problem.  Not so, apparently.  I would appreciate any pointers
>> on diagnosing and fixing this.

>> My lilo.conf is attached, but I don't think lilo got far enough to
>> read it.

>>                 - Jim Van Zandt

>> lba32
>> boot=/dev/hda3
>> root=/dev/hda3
>> compact
>> install=/boot/boot.b
>> map=/boot/map
>> delay=20
>> vga=normal
>> default=Linux
>> image=/boot/bzImage-2.4.5
>>         label=Linux
>>         read-only
>> image=/vmlinuz
>>         label=Linux-2.2.17
>>         read-only
>> image=/vmlinuz.old
>>         label=LinuxOLD
>>         read-only
>>         optional
>> other=/dev/hda1
>>         label=WindowsME
>>         alias=3

> Shouldn't that be "boot=/dev/hda"?

> There is a line "table=/dev/hda" in your WindowsME section, isn't there?

> What does the (v)erify function in fdisk have to say about it all?

> Glen

He just told us that he was trying to install lilo to /dev/hda3.

Try running fdisk /dev/hda to fix the problem.  It will probably be
necessary to delete partition 3 and then add it in again.  Before
attempting this, run

# fdisk /dev/hda > part.table
p
q
# lpr part.table

Thus you have a hard copy of your existing partition table.

The only tool which I have found to be consistently accurate in
partitioning a hard drive is Linux fdisk.  FIPS may be useful in moving a
DOS partition around but fdisk should be used for actually setting up your
drive.

 
 
 

LILO complains "Invalid partition table"

Post by Eric » Fri, 13 Jul 2001 15:40:39


Quote:> I'm trying to set up a new Gateway Solo 3350 (20 GB disk) to dual boot
> WindowsME and Debian Linux.  I used FIPS (latest version, downloaded
> from the home site) to split the original FAT32 partition, and the
> fdisk on the Debian 2.1 installation disk to delete the second
> partition and install two new ones.  I got Linux installed on
> /dev/hda3, and can boot it with a floppy.  Putting LILO on the MBR
> failed,

Let me guess, you got "LI"
Does your BIOS support the lba32 part?
(Check if "interrupt 0x13 extensions" are available)

Quote:> so I restored it with the DOS fdisk ("fdisk /mbr"). I'm now
> trying to install the LILO loader on /dev/hda3.  However, LILO
> complains about the partition table:

/dev/hda3 starts over cylinder 1024
You cannot boot from there.
Put lilo in the MBR again.

Quote:>   Script started on Wed Jul 11 16:30:41 2001
>   talon:~# fdisk -lu /dev/hda

>   Disk /dev/hda: 255 heads, 63 sectors, 2432 cylinders
>   Units = sectors of 1 * 512 bytes

>      Device Boot    Start       End    Blocks   Id  System
>   /dev/hda1   *        63  32354909  16177423+   c  Win95 FAT32 (LBA)
>   /dev/hda2      32354910  32852924    249007+  82  Linux swap
>   /dev/hda3      32852925  39070079   3108577+  83  Linux

(32852925/(63*255))=2045 (Just as lilo says)
This is indeed over cyl. 1024.
It's pointless to install lilo here.

Quote:>   talon:~# lilo -v
>   LILO version 21.5-1 beta, Copyright (C) 1992-1998 Werner Almesberger
>   'lba32' extensions Copyright (C) 1999,2000 John Coffman

>   Reading boot sector from /dev/hda3
>   Device 0x0300: Invalid partition table, 3rd entry
>     3D address:     63/254/1021 (16418429)

You don't show your table with the CHS values, but if it holds 1021
for the starting cyl. of hda3 it is incorrect. It should hold 1023 instead.
I wouldn't change it though, as I can't tell what the effect of that would
be.

Quote:>     Linear address: 1/0/2045 (32852925)

2045 is over 1024

Quote:>   talon:~# exit

>   Script done on Wed Jul 11 16:30:57 2001

> I remember FIPS mentioning an incorrect entry, but it assured me that
> was no problem.  Not so, apparently.  I would appreciate any pointers
> on diagnosing and fixing this.

There's no fix. Put lilo in the MBR or make a small /boot below
cylinder 1024 to get around this problem.

Quote:> My lilo.conf is attached, but I don't think lilo got far enough to
> read it.

> - Jim Van Zandt

> lba32
> boot=/dev/hda3

change this back to "boot=./dev/hda"

Quote:> root=/dev/hda3
> compact

You don't need compact here.
(I don't think it hurts though)

The rest is okay.

Eric

 
 
 

LILO complains "Invalid partition table"

Post by James R. Van Zan » Fri, 13 Jul 2001 21:01:01




>> I'm trying to set up a new Gateway Solo 3350 (20 GB disk) to dual boot
>> WindowsME and Debian Linux.  ...  Putting LILO on the MBR
>> failed,

>Let me guess, you got "LI"

No.  I think the message was "invalid partition table".

Quote:>Does your BIOS support the lba32 part?
>(Check if "interrupt 0x13 extensions" are available)

It's a brand new machine, so I assumed it would have lba32 support.
It has a PhoenixBIOS 4.0 release 6.0 version 25.04 copyright 1985-1998
(not as new as I would have thought).  I see no mention of lba32 or
0x13 extensions in the BIOS setup menus.  Is there some way of
checking for them, from either Linux or WindowsME?

Quote:>> so I restored it with the DOS fdisk ("fdisk /mbr"). I'm now
>> trying to install the LILO loader on /dev/hda3.  However, LILO
>> complains about the partition table:

>/dev/hda3 starts over cylinder 1024
>You cannot boot from there.
>Put lilo in the MBR again.

I thought that if there was a problem with cylinder 1024, it was the
kernel image had to be below that point (e.g. I could put it in the
Windows partition).  You're saying lilo has to be below that point
too?  Would lba32 support eliminate the 1024 cylinder limit?

Quote:>>   talon:~# lilo -v
>>   LILO version 21.5-1 beta, Copyright (C) 1992-1998 Werner Almesberger
>>   'lba32' extensions Copyright (C) 1999,2000 John Coffman

>>   Reading boot sector from /dev/hda3
>>   Device 0x0300: Invalid partition table, 3rd entry
>>     3D address:     63/254/1021 (16418429)

>You don't show your table with the CHS values, but if it holds 1021
>for the starting cyl. of hda3 it is incorrect. It should hold 1023 instead.

sfdisk is a bit more informative:

Disk /dev/hda: 2432 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls   #blocks   Id  System
/dev/hda1   *      0+   2013    2014- 16177423+   c  Win95 FAT32 (LBA)
                end: (c,h,s) expected (1023,254,63) found (989,254,63)
/dev/hda2       2014    2044      31    249007+  82  Linux swap
/dev/hda3       2045    2431     387   3108577+  83  Linux
                start: (c,h,s) expected (1023,254,63) found (1021,254,63)
                end: (c,h,s) expected (1023,254,63) found (383,254,63)
/dev/hda4          0       -       0         0    0  Empty

Is the combination 1023/254/63 some special code used by lba32 to
signal that the real value is specified a different way?  Otherwise, I
don't know how sfdisk should be expecting the same value in three places.

I guess I'll try using sfdisk to replace the partition information for
partition 3.  But I'll save a copy of its data in the FAT32 partition first.

 
 
 

LILO complains "Invalid partition table"

Post by Eric » Fri, 13 Jul 2001 21:32:15


Quote:> >Does your BIOS support the lba32 part?
> >(Check if "interrupt 0x13 extensions" are available)

> It's a brand new machine, so I assumed it would have lba32 support.
> It has a PhoenixBIOS 4.0 release 6.0 version 25.04 copyright 1985-1998
> (not as new as I would have thought).  I see no mention of lba32 or
> 0x13 extensions in the BIOS setup menus.  Is there some way of
> checking for them, from either Linux or WindowsME?

Perhaps in the documentation?
But don't bother, if it's this new, it'll have support for this.

Quote:> >> so I restored it with the DOS fdisk ("fdisk /mbr"). I'm now
> >> trying to install the LILO loader on /dev/hda3.  However, LILO
> >> complains about the partition table:

> >/dev/hda3 starts over cylinder 1024
> >You cannot boot from there.
> >Put lilo in the MBR again.

> I thought that if there was a problem with cylinder 1024, it was the
> kernel image had to be below that point (e.g. I could put it in the
> Windows partition).  You're saying lilo has to be below that point
> too?

The PC will execute whatever is in the MBR. From that point on, the
bootloader is responsible. Put LILO there, and it will be able to access
beyond cyl. 1024. Your DOS loader can't do this. The bootsector at
cyl. 2045 cannot be reached by it.

Quote:> Would lba32 support eliminate the 1024 cylinder limit?

Yes, but only if the calls are used. Placing LILO itself at an unreachable
position
is for sure not going to work.

Quote:> >>   talon:~# lilo -v
> >>   LILO version 21.5-1 beta, Copyright (C) 1992-1998 Werner Almesberger
> >>   'lba32' extensions Copyright (C) 1999,2000 John Coffman

> >>   Reading boot sector from /dev/hda3
> >>   Device 0x0300: Invalid partition table, 3rd entry
> >>     3D address:     63/254/1021 (16418429)

> >You don't show your table with the CHS values, but if it holds 1021
> >for the starting cyl. of hda3 it is incorrect. It should hold 1023
instead.

> sfdisk is a bit more informative:

> Disk /dev/hda: 2432 cylinders, 255 heads, 63 sectors/track
> Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

>    Device Boot Start     End   #cyls   #blocks   Id  System
> /dev/hda1   *      0+   2013    2014- 16177423+   c  Win95 FAT32 (LBA)
> end: (c,h,s) expected (1023,254,63) found (989,254,63)
> /dev/hda2       2014    2044      31    249007+  82  Linux swap
> /dev/hda3       2045    2431     387   3108577+  83  Linux
> start: (c,h,s) expected (1023,254,63) found (1021,254,63)
> end: (c,h,s) expected (1023,254,63) found (383,254,63)
> /dev/hda4          0       -       0         0    0  Empty

Ough!
How did you create this table?
It wraps the partitions cylinder numbers for hda1 and hda3 (hda2 appears
clean).
You may very well have an incorrect FS at hda1 too.
Did windows/DOS touch this table?

Quote:> Is the combination 1023/254/63 some special code used by lba32 to

Not by lba32. It's the only way to invalidate the CHS values, and thus
indicate
that the LBA values must be used.

Quote:> signal that the real value is specified a different way?  Otherwise, I
> don't know how sfdisk should be expecting the same value in three places.

You were (almost) correct in your assumption that these have a special
meaning.

Quote:> I guess I'll try using sfdisk to replace the partition information for
> partition 3.  But I'll save a copy of its data in the FAT32 partition

first.

You are aware that you can destroy stuff (To the point of inaccesible data)
if you make errors/changes.

Changing it, may have a strange effect on windows.
Make sure to have a linux boot/root floppy at hand.

BTW. You can force lilo to accept the linear addresses it finds.
Use the -P switch (man lilo)

Eric

 
 
 

LILO complains "Invalid partition table"

Post by Glen Sanf » Fri, 13 Jul 2001 21:53:24





> >> I'm trying to set up a new Gateway Solo 3350 (20 GB disk) to dual boot
> >> WindowsME and Debian Linux.  I used FIPS (latest version, downloaded
> >> from the home site) to split the original FAT32 partition, and the
> >> fdisk on the Debian 2.1 installation disk to delete the second
> >> partition and install two new ones.  I got Linux installed on
> >> /dev/hda3, and can boot it with a floppy.  Putting LILO on the MBR
> >> failed, so I restored it with the DOS fdisk ("fdisk /mbr"). I'm now
> >> trying to install the LILO loader on /dev/hda3.  However, LILO
> >> complains about the partition table:

> >>   Script started on Wed Jul 11 16:30:41 2001
> >>   talon:~# fdisk -lu /dev/hda

> >>   Disk /dev/hda: 255 heads, 63 sectors, 2432 cylinders
> >>   Units = sectors of 1 * 512 bytes

> >>      Device Boot    Start       End    Blocks   Id  System
> >>   /dev/hda1   *        63  32354909  16177423+   c  Win95 FAT32 (LBA)
> >>   /dev/hda2      32354910  32852924    249007+  82  Linux swap
> >>   /dev/hda3      32852925  39070079   3108577+  83  Linux
> >>   talon:~# lilo -v
> >>   LILO version 21.5-1 beta, Copyright (C) 1992-1998 Werner Almesberger
> >>   'lba32' extensions Copyright (C) 1999,2000 John Coffman

> >>   Reading boot sector from /dev/hda3
> >>   Device 0x0300: Invalid partition table, 3rd entry
> >>     3D address:     63/254/1021 (16418429)
> >>     Linear address: 1/0/2045 (32852925)
> >>   talon:~# exit

> >>   Script done on Wed Jul 11 16:30:57 2001

> >> I remember FIPS mentioning an incorrect entry, but it assured me that
> >> was no problem.  Not so, apparently.  I would appreciate any pointers
> >> on diagnosing and fixing this.

> >> My lilo.conf is attached, but I don't think lilo got far enough to
> >> read it.

> >>                 - Jim Van Zandt

> >> lba32
> >> boot=/dev/hda3
> >> root=/dev/hda3
> >> compact
> >> install=/boot/boot.b
> >> map=/boot/map
> >> delay=20
> >> vga=normal
> >> default=Linux
> >> image=/boot/bzImage-2.4.5
> >>         label=Linux
> >>         read-only
> >> image=/vmlinuz
> >>         label=Linux-2.2.17
> >>         read-only
> >> image=/vmlinuz.old
> >>         label=LinuxOLD
> >>         read-only
> >>         optional
> >> other=/dev/hda1
> >>         label=WindowsME
> >>         alias=3

> > Shouldn't that be "boot=/dev/hda"?

> > There is a line "table=/dev/hda" in your WindowsME section, isn't there?

> > What does the (v)erify function in fdisk have to say about it all?

> > Glen

> He just told us that he was trying to install lilo to /dev/hda3.

> Try running fdisk /dev/hda to fix the problem.  It will probably be
> necessary to delete partition 3 and then add it in again.  Before
> attempting this, run

> # fdisk /dev/hda > part.table
> p
> q
> # lpr part.table

> Thus you have a hard copy of your existing partition table.

> The only tool which I have found to be consistently accurate in
> partitioning a hard drive is Linux fdisk.  FIPS may be useful in moving a
> DOS partition around but fdisk should be used for actually setting up your
> drive.

He said installing to the MBR failed so he tried the partition.  I doubt
that's what he really wants, and feel the previous failure was due to a
misconfiguration.

I agree with your assessment of the Linux fdisk.

Glen

 
 
 

LILO complains "Invalid partition table"

Post by James R. Van Zan » Sat, 14 Jul 2001 20:57:54




>> I guess I'll try using sfdisk to replace the partition information for
>> partition 3.  But I'll save a copy of its data in the FAT32 partition
>first.

>You are aware that you can destroy stuff (To the point of inaccesible
>data) if you make errors/changes.

>Changing it, may have a strange effect on windows.
>Make sure to have a linux boot/root floppy at hand.

I ran sfdisk -d to get an ASCII partition description, and fed that
back into sfdisk to fix the partition table.  Linux boots off a floppy
fine.  Windows has a problem though.  I get a cycle of

        failed reboot (requires reset)
        boot to "safe mode" (runs scandisk)
        select Start | shutdown
        apparently normal boot  
        select Start | shutdown
        failed reboot (requires reset)

A couple of times I did not notice a failed boot right away, and by
the time I did the CPU area had gotten alarmly hot.  I suspect that
the "normal" operating mode is with the CPU at full clock speed and
the fan off, and that slowing the clock or turning on the fan require
software actions.  Not very "fail safe".

I'd like to clear this up before I try again to put LILO on the MBR.

                - Jim Van Zandt

p.s. I would a lot rather be chasing Linux problems.

 
 
 

LILO complains "Invalid partition table"

Post by Thomas Papendie » Mon, 16 Jul 2001 05:22:19


Hi,

I've a similar problem.

About one year I booted linux out of WinNT's bootloader.
I installed LILO on a floppy and copied it via "dd" to the file
<bootsect.lin> which was uset by the NT-bootloader to start LILO.

Now I installed SuSE 7.1 (and 7.2) wich comes with LILO 26.3.

I also installed kernel 3.4.5

I did not change any thing at the System configuration (2 SCSI-HD's)

Now I can boot Linux from a floppy propperly.

The same LILO fails to start out of the NT-bootloader at "LIL-"
I don't understand, what makes the difference.

Thanks for your time
Thomas

 
 
 

LILO complains "Invalid partition table"

Post by Shaw » Mon, 16 Jul 2001 07:53:21


I am not sure if I got similar problem last year the first time I installed
Linux on my Compaq Armada 7800 laptop and dual boot with WinNT and Win98.  I
didn't aware that the boot partition had to be below 1024 cylinder.  So I
installed Linux after Windows and got boot up failed.  I couldn't even boot
to Windows NT or 98 and finally fixed it with FDISK /MBR.

Finally, I used Partition Magic to move the Win98 and WinNT partitions up
and left several hundred MB space at the lower track for Linux boot
partition.  Now it runs beautifully.  My laptop is rather new as well.

Did you aware of this when you installed your Linux?

Richard





> >> I guess I'll try using sfdisk to replace the partition information for
> >> partition 3.  But I'll save a copy of its data in the FAT32 partition
> >first.

> >You are aware that you can destroy stuff (To the point of inaccesible
> >data) if you make errors/changes.

> >Changing it, may have a strange effect on windows.
> >Make sure to have a linux boot/root floppy at hand.

> I ran sfdisk -d to get an ASCII partition description, and fed that
> back into sfdisk to fix the partition table.  Linux boots off a floppy
> fine.  Windows has a problem though.  I get a cycle of

> failed reboot (requires reset)
> boot to "safe mode" (runs scandisk)
> select Start | shutdown
> apparently normal boot
> select Start | shutdown
> failed reboot (requires reset)

> A couple of times I did not notice a failed boot right away, and by
> the time I did the CPU area had gotten alarmly hot.  I suspect that
> the "normal" operating mode is with the CPU at full clock speed and
> the fan off, and that slowing the clock or turning on the fan require
> software actions.  Not very "fail safe".

> I'd like to clear this up before I try again to put LILO on the MBR.

> - Jim Van Zandt

> p.s. I would a lot rather be chasing Linux problems.

 
 
 

1. LILO says "Invalid partition table"

LILO keeps giving me "Invalid partition table" errors when I try to add
a boot entry for Windows into lilo.conf.  Windows is on a drive
connected to a Promise Ultra66 IDE controller (hde).  I have Mandrake
7.0.2 installed on a 5GB drive on the primary IDE master (hda), with the
kernel and LILO packages updated from the 7.1 release.  This newer
kernel recognizes the Ultra66 during boot just fine and the newer LILO
has no 1024-cylinder limitation so I *thought* this would work.

There's nothing wrong with the partition table on the drive connected to
the Ultra66; every utility I have says it's fine.  It was fdisk'd and
formatted using Win98 commands, so there isn't that known problem caused
by using Partition Magic.

Any ideas what's going wrong?

Thanks,

- Leo

Sent via Deja.com http://www.deja.com/
Before you buy.

2. What video card should i get?

3. Help Me: Dos "Invalid partition table" errot

4. Longshine NIC with Realtek Chip

5. new filesystem problems: "fdisk: can't write fdisk partition table: Invalid argument"

6. Terminal on hacked LGX won't work...

7. What to do about "invalid partition table"?

8. COMMERCIAL: Dr Linux - The Complete Linux Documentation Book.

9. "Invalid Partition Table" after dd command

10. "Invalid partition table" error message

11. RedHat 7.2: "Invalid partition table"

12. * HELP - "Invalid partition table" after installation of Slackware 3.2

13. HELP - "Invalid partition table" after installation of Linux