slackware 13.1 will not boot after install from USB

jd5n0vv · 07-05-2010, 08:51 PM

I am installing slackware 13.1 from USB. This will NOT be a dual-boot system.

The install appears to work correctly installing to /dev/sda2 (/dev/sda1 is my swap)

However I get an error when installing to the LILO to the MBR, root, or even to a floppy drive (I tried all 3 multiple times with no luck)

My issues comes when LILO is installing.

After a couple of video warnings I get the following:
Warning: Device 0x0010 inconsistent partition table
CHS address in PT: 15:12:12 --> LBA(230465)
LBA address in PT: 8064 --> CHS(0:130:5)
Fatal: Either Fix-Table or Ignore-Table must be specified. If not sure, first try Ignore-Table (-P ignore)

It appears to me I have an issue with LILO, but what I am not sure. I looked in the /etc/ dir for lilo.conf but it did not exist.

Thanks in advance for help with this.

zordrak · 07-06-2010, 02:55 AM

You would probably have several responses by now if you posted in the Slackware forum rather than the Newbie forum.

It would seem that you have a problem with your partition table. You need to either fix the partition table yourself, tell lilo to fix it, or tell lilo to ignore it (my preference would be to fix it manually).

During install, the lilo.conf will be in /mnt/etc/lilo.conf as per these instructions for manually re-installing lilo in an unbootable system:
http://blog.tpa.me.uk/2009/09/29/re-...kware-boot-cd/

zordrak · 07-06-2010, 02:56 AM

.....................

saikee · 07-06-2010, 03:10 AM

You could write your own lilo.conf or use Grub instead.

Grub1 is possibly the easiest. Just get hold of a Linux (anything other than Ubuntu 10.04 or distros based on it as they use Grub2 now) and do the following

(1) Boot up the Live CD, mount your sda2 containing the Slackware. Make a /boot/grub directory.

(2) Copy 2 files stage1 and stage2 from the boot up Linux and put these 2 files in Slackware's /boot/grub directory. The stage1 and stage2 are normally available in the /boot/grub of the boot up Linux. You can also find them in other dirctories by "find / -name stage1"

(3) Invoke a Grub shell from the boot up Linux and set up Grub by commands

Code:

grub
root (hd0,1)
setup (hd0)
quit

(4) If reboot now your PC will boot to a Grub prompt with which you can boot Slackware manually by commands

Code:

root (hd0,1)
kernel /boot/vmlinuz ro root=/dev/sda2
boot

(5) If you are happy with the result you can make the arrangement permanent by adding menu.lst to /boot/grub directory with the following entries

Code:

title My Slackware 13.1 booted by Grub
root (hd0,1)
kernel /boot/vmlinuz ro root=/dev/sda2

Slackware is great but its Lilo is crap. Absolute also based on Slackware but has a much better Lilo (or a better installer configuring Lilo properly).

The above is the minimal install of Grub. Same thing can be done with Grub2 if you want it instead of Grub1.

Grub is easier because you can boot every system "manually" if you have a need to. If you "dd" stage1 and stage2 into a floppy it can boot any installed system ever invented on a PC. Lilo is rigid that it only boots whatever you put inside /etc/lilo.conf.

Haven't used one for a long time but you can use Slackware installation CD or DVD to install Lilo again or run program "liloconfig" (I think) at a Slackware terminal to try Lilo again.

onebuck · 07-06-2010, 07:17 AM

Hi,

'saikee' it seems to me the OP doesn't have another system installed. The OP can get 'grub' from '/extra'. But it would be easier to repair the partition table and re-install lilo or run 'liloconfig'. Or run 'lilo' with {fix|ignore|<global-option>} options;

Quote:

excerpt from 'man lilo';

-P {fix|ignore|<global-option>}
Fix or ignore `corrupt' partition tables, i.e., partition tables with linear and cylin-
der/head/sector addresses that do not correspond. Always try -P ignore first, as -P fix
will re-write the partition table, possibly destroying all partitions on the disk.

-P ignore is also used to bypass the partition table check for partition types within
the partition table which might not allow the installation of a LILO boot sector. Com-
pare with the "-F" flag, which overrides the check of the actual boot sector.

-P <global-option> allows the passing of any global option which may appear in the
global section (top) of the configuration file (/etc/lilo.conf). For instance, -P
nowarn will pass the "nowarn" option, just as though "nowarn" appeared in the configura-
tion file (same as the "-w" switch). Similarly, -P timeout=50 will add or override the
"timeout=" line in the configuration file. Note that the general -P switch actually
duplicates a number of command line option switches. However, it is not strictly the
same as some switches whick cause an override of other options; e.g., "-g" (-P geomet-
ric), "-L" (-P lba32).

@OP If you decide to use the '-P' option please read the 'man lilo' above as bad things can still occur. Be sure to check the '-F' option.

I would use the 'Ignore-Table (-P ignore)' option first, then 'fix' if that doesn't work.

saikee · 07-06-2010, 07:40 AM

I use Lilo whnever possible but for some reasons the Lilo installations in Slackware were rarely successfuly in my case. Thus possibly 9 out of 10 cases I cut my loss and put Grub in. I do put Linux beyond the 15th partition frequently and that doesn't help either.

My suggestion is to get Grub sourced from a Live CD. Unless Slackware boots the OP can't get anything from it.

I did suggest using Slackware installation CD to try Lilo installation again. The current situation is Lilo has no lilo.conf in /etc directory of OP that seems rather serious. In such a case no repair can be done except installing Slackware again or just Lilo itself.

jd5n0vv · 07-06-2010, 05:20 PM

Thanks to everyone for your replies.

I have not used slackware since v8.1 so it may take me a while to get thru all of the items to try.

I will try the LILO suggestions first, but probably end up installing grub.

Well - I have lots of reading to do, but this is for my own personal webserver and am enjoying every minute of this process. (OK maybe not every minute, but I have fun doing it.)

Thanks again everyone.