Bad:
image=/mnt/hda5/boot/vmlinuz-2.4.22-xfs
Good:
image=/hda5/boot/vmlinuz-2.4.22-xfs
Get rid of all those entries that start w/ /mnt.
Hi all,
this is surely a LILO problem, but I cannot figure out myself, what the
heck I am doing wrong.
I have installed the CD to /dev/hda10, a reasonably big partition.
Now there are several smaller partitions like>
/ ==> /dev/hda5
/usr ==> /dev/hda6
/var ==> /dev/hda8
/home ==> /dev/hda9 ...
which I want to use.
I have copied the files with cp -ax to their respective target partitions
and I think this should be allright.
Running lilo doesnt show any mistakes to me, so I am really struggling
why it always boots with /dev/hda10 as root device,despite the lilo.conf.hda5 that I have edited:
Important parts of lilo.conf.hda5:
---snip---
boot=/dev/hda
root=/dev/hda5
install=/mnt/hda5/boot/boot-menu.b
map=/mnt/hda5/boot/map
default=Linux-hda5
image=/mnt/hda5/boot/vmlinuz-2.4.22-xfs
label=Linux-hda5
initrd=/mnt/hda5/boot/initrd.gz
read-only
root=/dev/hda5
image=/boot/vmlinuz-2.4.22-xfs
label=Linux
initrd=/boot/initrd.gz
read-only
root=/dev/hda10
---snap---
lilo -C /mnt/hda5/etc/lilo.conf.hda5
produces the following output:
---snip---
...
Added Linux-hda5 *
<dev=0xe0,hd=20,cyl=66,sct=197>
"ro root=305 hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce"
...
Added Linux
Device 0x030a: BIOS drive 0x80, 255 heads, 4864 cylinders,
63 sectors. Partition offset: 55135143 sectors.
---snap---
After reboot, it will always boot into /dev/hda10.
What is wrong?
Tnx Thomas
Bad:
image=/mnt/hda5/boot/vmlinuz-2.4.22-xfs
Good:
image=/hda5/boot/vmlinuz-2.4.22-xfs
Get rid of all those entries that start w/ /mnt.
But /hda5 does not exist.Originally Posted by rickenbacherus
If I specify an image, ..., it should exist when lilo runs.
This does not make sense to me.
I get the impression it is the initrd which is voiding my attempts
to use a different root partition.
http://www.knoppix.net/forum/viewtopic.php?t=3053#14435
So I would need to change that in linuxrc.in the linuxrc script in the initrd image mount /dev/hda6 is HARDCODED
Any ideas how to do that?
Thomas
the image and initrd references should be relative to your root definition so:image=/mnt/hda5/boot/vmlinuz-2.4.22-xfs
initrd=/mnt/hda5/boot/initrd.gz
image=/boot/vmlinuz-2.4.22-xfs
and
initrd=/boot/initrd.gz
should work,
if not you should use the devices not the mount points like this:
image=/dev/hda5/boot/vmlinuz-2.4.22-xfs
and
initrd=/dev/hda5/boot/initrd.gz
~rock
A-Tech 8GB DDR3 1600 PC3-12800 Laptop SODIMM 204-Pin Memory RAM PC3L DDR3L 1x 8G
$13.99
HyperX FURY DDR3 8GB 16GB 32GB 1600 MHz PC3-12800 Desktop RAM Memory DIMM 240pin
$12.90
A-Tech 8GB PC3-12800 Desktop DDR3 1600 MHz Non ECC 240-Pin DIMM Memory RAM 1x 8G
$13.99
HyperX FURY RAM DDR4 16GB 8GB 32GB 4GB 3200 2666 2400 2133 Desktop Memory DIMM
$9.64
Samsung 128GB (4x 32GB) M86B4G70DM0-CMA3 PC3-14900L 4Rx4 DDR3 ECC Reg Server Mem
$39.99
Samsung 16GB 2Rx4 PC4-2400 RDIMM DDR4-19200 ECC REG Registered Server Memory RAM
$20.99
Lot of 2 32GB DDR4 2666 PC4-21300 SODIMM RAM Modules Mixed Brand
$60.00
Kingston HyperX FURY DDR3 8GB 16GB 32G 1600 1866 1333 Desktop Memory RAM DIMM
$13.25
A-Tech 256GB 4x 64GB 4Rx4 PC4-19200 ECC Load Reduced LRDIMM Server Memory RAM
$287.96
A-Tech 128GB 2x 64GB 4Rx4 PC4-19200 ECC Load Reduced LRDIMM Server Memory RAM
$143.98