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
AMD EPYC 7282 CPU Processor 16 Cores 32 Threads 2.8GHZ up to 3.2GHZ 120W no lock
$75.00
Intel - Core i7-12700K Desktop Processor 12 (8P+4E) Cores up to 5.0 GHz Unloc...
$419.99
Intel - Core i9-12900K Desktop Processor 16 (8P+8E) Cores up to 5.2 GHz Unloc...
$619.99
Intel Xeon E5-2697A V4 2.6GHz CPU Processor 16-Core Socket LGA2011 SR2K1
$39.99
Intel Quad Core i3-12100 3.3GHz 12MB LGA1700 12th Gen. CPU Processor SRL62
$45.96
AMD Ryzen 5 4500 6-Core 3.6GHz Socket AM4 65W CPU Desktop Processor
$79.00
Intel Core i9-13900KF Unlocked Desktop Processor - 24 Cores (8P+16E) & 32 Thread
$539.99
Intel Core i7-3770 3.40GHz Quad-Core CPU Processor QC1W LGA1155 Socket
$33.49
AMD Ryzen 7 7700 Processor (5.3 GHz, 8 Cores, Socket AM5) Boxed -...
$259.99
Intel Core i7-3770 3.40GHz 8MB Quad Core Socket LGA1155 CPU Processor SR0PK
$35.00