reinstall lilo to /boot (/dev/sda2) from dvd after windows install
 

hey,
i have an encrypted slack system on my machine (/dev/sda3), which is booted from /dev/sda2 (mounted as /boot). Now i installed windows and truecrypt on win (/dev/sda1), so i have to reinstall lilo (first it was in mbr) to /boot, for i can still use truecrypt bootloader.

now i am under my slackware 13 installation dvd and mounted /dev/sda2... how do i reinstall lilo to /boot ?

or am i completely wrong? :P

thanks in advance,

lg,
compul

-------edit-------------------------------

when i boot with:

boot: hugesmp.s root=/dev/sda3 initrd=/dev/sda2/initrd.gz

is says:

Loading /kernels/hugesmp.s/bzImage......................................................
Could not find find ramdisk image: /dev/sda2/initrd.gz

the file /dev/sda2/initrd.gz actually exists. maybe it is corrupt? if it is, where do i get a new one from?

btw.: i encrypted slack like this:
http://slackware.osuosl.org/slackwar...ADME_CRYPT.TXT

I use Logical Volumes on top of sda3 (/, /home, swap).

hasnt anyone an idea?

lg!

To boot into your slackware system using the installation CD/DVD, the correct syntax at boot prompt is:

Oh yes, I forgot, to install lilo into /boot, please run liloconfig as root and select expert mode

ok, i made it into my system by using Super Grub Disk, and changing the initrd path from /initrd.img to initrd.gz

But now, when im in my system and run liloconfig nothing happens

# liloconfig
#

why? when i run lilo -v:

bash-3.1# lilo -v
LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 12:43:17 on Nov 29 2008.

Warning: LBA32 addressing assumed
Reading boot sector from /dev/sda2
Warning: '/proc/partitions' does not match '/dev' directory structure.
Name change: '/dev/dm-0' -> '/dev/mapper/root'
Warning: Name change: '/dev/dm-1' -> '/dev/cryptvg/swap'
Warning: Name change: '/dev/dm-2' -> '/dev/cryptvg/root'
Warning: Name change: '/dev/dm-3' -> '/dev/cryptvg/home'
Warning: Partition 2 on /dev/sda is not marked Active.
Fatal: device-mapper: only linear boot device supported

i modified /etc/lilo.conf a little for lilo -v should write to /dev/sda2 (/boot).

vgchange -ay (which exits succesfully - says:
"3 logical volume(s) in volume group "cryptvg" now active"
) does not change anything in "Warning: Partition 2 on /dev/sda is not marked Active."

so how / where should i write lilo?

thanks in advance !

lg :)

that won't work, cuz the system is encrypted ( i think i tried it) so i had to specify the right initrd image.

whatever. i did that. the fact that liloconfig does nothing confuses me x.x

##edit##########

weird.. if course /dev/sda2 hast nothing to do with vgchange -ay cuz its not a LV :P
i did:

bash-3.1# fdisk /dev/sda2
Command (m for help): a
Partition number (1-4): 2
Warning: partition 2 has empty type

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 22: Invalid argument.
The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.
bash-3.1#

so i made a reboot and it tried to boot /dev/sda2 but - of course - there was nothing to boot from yet. So i started from the cd again and did:

bash-3.1# lilo -v
LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 12:43:17 on Nov 29 2008.

Warning: LBA32 addressing assumed
Reading boot sector from /dev/sda2
Warning: '/proc/partitions' does not match '/dev' directory structure.
Name change: '/dev/dm-0' -> '/dev/mapper/root'
Warning: Name change: '/dev/dm-1' -> '/dev/cryptvg/swap'
Warning: Name change: '/dev/dm-2' -> '/dev/cryptvg/root'
Warning: Name change: '/dev/dm-3' -> '/dev/cryptvg/home'
Warning: Partition 2 on /dev/sda is not marked Active.
Fatal: device-mapper: only linear boot device supported

obviously it still doesnt work... i have no idea why !

lg... :-@

compul

okay... i marked /dev/sda2 as active using
# lilo -A /dev/sda 2

lilo -v then said something like the partition would be too small for initrd.gz and it would try to write to /dev/sda1. that didnt work. BUT it crashed my windows bootloader so there is bothing bootable left on my machine :P lucky that the setup was new anyways ... so i think im gonna reinstall win and slackware (with a bigger /boot partition ^^) and then hope that it works... if not... im gonna cry or something :P

so... thanks for everyones help !

not really solved.. :P

lg,

##edit#################

i am using unencrypted windows now, cuz i always get the Fatal message that installing lilo on /dev/sda2 (/boot) would destroy the existing filesystem. using liloconfig i just could install it to root (or is that in the end the same? cuz they are different partitions. in root it would be useless to me cuz / is encrypted, as swap and /home), and i didnt find a choice to install somewhere else. maybe i will try later again :P but so far, im okay with this solution.

lg ;)