LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 11-07-2010, 12:24 AM   #1
hedron
Member
 
Registered: Jul 2009
Location: NYC
Distribution: Slackware, Bluewhite
Posts: 225

Rep: Reputation: 23
Can't install lilo --> Inconsistent partition table


I get the following error when installing lilo:
Code:
device 0x0800 Inconsistent partition table
CHS address in pt: 2:0:33 --> LBA (32162)
LBA address in pt: 2048 --> CHS (0:32:33)
Some have suggested that I issue lilo -P ignore, but that only destroys my MBR and therefor is not an option.

My lilo.conf is pretty much default.

fdisk -l /dev/sda says that some partitions do not end on the cylinder boundary. I can only assume that this is an important hint.

I have never had this problem when dual booting with XP only now that I've installed Windows 7.
 
Old 11-07-2010, 02:58 AM   #2
seanaustin
LQ Newbie
 
Registered: Feb 2010
Posts: 16

Rep: Reputation: 1
how exactly are you booting back into slackware after the win7 install? are you able to load windows? Is it safe to assume that you simply re-used the winXP partition(s) for win7?

Last edited by seanaustin; 11-07-2010 at 03:00 AM.
 
Old 11-07-2010, 10:22 AM   #3
nutronix
Member
 
Registered: Jan 2003
Location: montreal
Distribution: Slackware and XUbuntu
Posts: 110
Blog Entries: 1

Rep: Reputation: 17
Maybe install Grub?
 
1 members found this post helpful.
Old 11-07-2010, 11:21 AM   #4
MannyNix
Member
 
Registered: Dec 2005
Location: ~
Distribution: Slackware -current, OpenBSD
Posts: 449

Rep: Reputation: 41
Quote:
Originally Posted by hedron View Post
...Some have suggested that I issue lilo -P ignore, but that only destroys my MBR and therefor is not an option.

I have never had this problem when dual booting with XP only now that I've installed Windows 7.
I started to get this problem when I installed FreeBSD aisde my OpenBSD, XP and -current partitions. I've been using lilo -P ignore for months without any problems as I haven't had the time to format and install everything again, now that I don't need the BSD partitions anymore I formated them as ext4. Hopefully a new and clean install will fix evertything.
 
Old 11-07-2010, 11:33 AM   #5
hedron
Member
 
Registered: Jul 2009
Location: NYC
Distribution: Slackware, Bluewhite
Posts: 225

Original Poster
Rep: Reputation: 23
Quote:
Originally Posted by seanaustin View Post
how exactly are you booting back into slackware after the win7 install? are you able to load windows? Is it safe to assume that you simply re-used the winXP partition(s) for win7?
I've booted into Win7 without installing lilo. So, slack is installed but I can't boot to it. I guess I'll try grub.
 
Old 11-07-2010, 11:40 AM   #6
w1k0
Senior Member
 
Registered: May 2008
Location: Poland
Distribution: Slackware, Mint
Posts: 1,241

Rep: Reputation: 196Reputation: 196
The long story short: I encountered such a problem using one of the last versions of Slackware – prior to 13.0. I coped with that running Slackware CD-ROM, mounting Slackware partition in /mnt directory, chrooting to /mnt directory and running lilo command.

The whole story is here.

By the way: according to fdisk manual “fdisk is a buggy program that does fuzzy things”. The same manual advise to “try them in the order cfdisk, fdisk, sfdisk”. So if you’d like to avoid complains about partitions not ending on the cylinder boundary backup your data and recreate partitions using cfdisk.
 
2 members found this post helpful.
Old 11-07-2010, 03:18 PM   #7
nutronix
Member
 
Registered: Jan 2003
Location: montreal
Distribution: Slackware and XUbuntu
Posts: 110
Blog Entries: 1

Rep: Reputation: 17
Thanks for the info ,w1k0 , i had never read the whole man page....hummmm...maybe explains why i did have such a problem with Lilo years back in 10.1 slack release....also hosed my hardrive by the way...thanks again
 
Old 11-07-2010, 03:24 PM   #8
Amdx2_x64
Member
 
Registered: Jun 2008
Distribution: Left LQ. Mods are too Rude!
Posts: 598

Rep: Reputation: 50
I know you are trying to trouble shoot lilo. For awhile I was duel or triple+ booting and at times the bootloaders (Windows, Lilo, GRUB (Legacy and 2,) wouldn't work together. So I started using G.A.G Bootloader. I am not sure if this would be an option for you if things don't go right. I also believe that lilo would have to be installed on the root partition.
 
Old 11-07-2010, 04:54 PM   #9
w1k0
Senior Member
 
Registered: May 2008
Location: Poland
Distribution: Slackware, Mint
Posts: 1,241

Rep: Reputation: 196Reputation: 196
Quote:
Originally Posted by nutronix View Post
i had never read the whole man page....hummmm...
I suspect the only people reading the entire manuals are the authors. It'd be nice to read all Unix manuals but there's a lot of more inspiring activities. In fact reading them isn't sufficient. One have to read them, remember them and be able to use them. I wrote a few manuals for programs I invented. I read each of them a few times when I wrote them. Now I use the basic set of switches allowed by my own programs. When I need any rare used option I have to read my own manuals anew.
 
Old 11-07-2010, 06:26 PM   #10
trxdraxon
Member
 
Registered: Jan 2006
Location: Command Line
Distribution: Slackware
Posts: 68
Blog Entries: 1

Rep: Reputation: 7
This seems to come up a lot with windows 7, with the way it partitions itself. The one time I tried to setup a dual boot I had to install slack then windows 7(using cfdisk to create the partitions). Then go back and reinstall lilo from the slackware dvd.

I am not really sure what the root cause of the issue is as I am not much of a windows user anymore so I haven't looked to much into it. It doesn't seem to use the standard sector zoning format. Normally you will have a few megabytes of space left after creating partitions but with win7 you don't anymore.
 
Old 11-13-2010, 11:11 PM   #11
hedron
Member
 
Registered: Jul 2009
Location: NYC
Distribution: Slackware, Bluewhite
Posts: 225

Original Poster
Rep: Reputation: 23
I'm not sure what happened exactly, but after failing to be able to install grub I reinstalled slackware using cfdisk instead of fdisk but that didn't seem to work and gave me the 99 99 99 etc error. But then I booted with my usb drive and then rebooted and now it appears it works fine.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
"No partition table or unknown signature on partition table" 10.1 install madcow007 Slackware 4 02-09-2009 12:04 PM
Inconsistent partition table w1k0 Slackware 12 01-07-2009 07:44 PM
lilo: Inconsistent partition table picobyte Linux - Hardware 3 10-26-2005 07:45 PM
Partition table unreadable on RedHat 9 install Sanity Linux - Newbie 1 10-28-2003 03:00 PM
'partition table unreadable' on redhat 7.2 install wayne0h Linux - Newbie 2 02-12-2002 10:47 AM


All times are GMT -5. The time now is 12:09 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration