This is a discussion on LILO guru, anyone??? within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Hi, I am trying setup a fairly automated linux installation procedure that uses a Linux "installation server" where I ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, I am trying setup a fairly automated linux installation procedure that uses a Linux "installation server" where I simply connect a blank IDE disk as /dev/hdc and run a script that partitions, formats, installs the FS, etc. All is working very well except for LILO: Is there a way to install LILO on a harddisk that is currently mounted as /dev/hdc so that it will work when the harddisk is moved to /dev/hda? In other words, the disk is at /dev/hdc during the installation, but after that it will be moved to the new computer and become /dev/hda. I am trying to accomplish this without having to boot from CD or floppy and run lilo manually on the new computer. ------------------------------- # Start LILO global section boot = /dev/hda message = /boot/boot_message.txt #prompt timeout = 100 # Override dangerous defaults that rewrite the partition table: change-rules reset vga = normal # End LILO global section # Linux bootable partition config begins image = /boot/vmlinuz root = /dev/hda2 label = Linux read-only # Linux bootable partition config ends ------------------------------- Any help would be very much appreciated! Thanks, Lars |
| |||
| On Fri, 24 Sep 2004 00:18:18 GMT, Lars wrote: > Hi, > > I am trying setup a fairly automated linux installation procedure > that uses a Linux "installation server" where I simply connect a > blank IDE disk as /dev/hdc and run a script that partitions, > formats, installs the FS, etc. > > All is working very well except for LILO: Is there a way to > install LILO on a harddisk that is currently mounted as /dev/hdc > so that it will work when the harddisk is moved to /dev/hda? Never tried it myself, Create an install.conf which has the hdc mount point then use the -C and -b arguments to lilo. example if hdc mount point was /md101rc1 image=/md101rc1/boot/vmlinuz label="md10_1_rc1" root=/dev/hdc6 initrd=/md101rc1/boot/initrd.img append="devfs=nomount resume=/dev/hdb1 splash=0" vga=788 read-only the try lilo -v -C /etc/install.conf -b /dev/hdc |
| |||
| In alt.os.linux.slackware Lars <noemail@hotmail.com> wrote: > Hi, > > I am trying setup a fairly automated linux installation procedure > that uses a Linux "installation server" where I simply connect a > blank IDE disk as /dev/hdc and run a script that partitions, > formats, installs the FS, etc. > > All is working very well except for LILO: Is there a way to > install LILO on a harddisk that is currently mounted as /dev/hdc > so that it will work when the harddisk is moved to /dev/hda? > > In other words, the disk is at /dev/hdc during the installation, > but after that it will be moved to the new computer and become > /dev/hda. I am trying to accomplish this without having to boot > from CD or floppy and run lilo manually on the new computer. From bash type: rdev /dev/hdc? /dev/hda? where ? is the device number. > ------------------------------- > # Start LILO global section > boot = /dev/hda > message = /boot/boot_message.txt > #prompt > timeout = 100 > # Override dangerous defaults that rewrite the partition table: > change-rules > reset > vga = normal > # End LILO global section > # Linux bootable partition config begins > image = /boot/vmlinuz > root = /dev/hda2 > label = Linux > read-only > # Linux bootable partition config ends > ------------------------------- > > Any help would be very much appreciated! > > Thanks, > > Lars > > |
| |||
| In <comp.os.linux.misc> Lars <noemail@hotmail.com> wrote: > Hi, > > I am trying setup a fairly automated linux installation procedure > that uses a Linux "installation server" where I simply connect a > blank IDE disk as /dev/hdc and run a script that partitions, > formats, installs the FS, etc. > > All is working very well except for LILO: Is there a way to > install LILO on a harddisk that is currently mounted as /dev/hdc > so that it will work when the harddisk is moved to /dev/hda? > > In other words, the disk is at /dev/hdc during the installation, > but after that it will be moved to the new computer and become > /dev/hda. I am trying to accomplish this without having to boot > from CD or floppy and run lilo manually on the new computer. > > ------------------------------- > # Start LILO global section > boot = /dev/hda > message = /boot/boot_message.txt > #prompt > timeout = 100 > # Override dangerous defaults that rewrite the partition table: > change-rules > reset > vga = normal > # End LILO global section > # Linux bootable partition config begins > image = /boot/vmlinuz > root = /dev/hda2 > label = Linux > read-only > # Linux bootable partition config ends > ------------------------------- > > Any help would be very much appreciated! > > Thanks, > > Lars You may be able to piece together something from Google search on <abem73$hqmfj$1@ID-99293.news.dfncis.de> <bop1nb$1fm23u$1@ID-99293.news.uni-berlin.de> -- William Park <opengeometry@yahoo.ca> Open Geometry Consulting, Toronto, Canada |
| |||
| "Realto Margarino" <guymacon@IMAmoron.org> wrote in message news:BOJ4d.27520$pA.1711505@news20.bellglobal.com. .. > In alt.os.linux.slackware Lars <noemail@hotmail.com> wrote: > > Hi, > > > > I am trying setup a fairly automated linux installation procedure > > that uses a Linux "installation server" where I simply connect a > > blank IDE disk as /dev/hdc and run a script that partitions, > > formats, installs the FS, etc. > > > > All is working very well except for LILO: Is there a way to > > install LILO on a harddisk that is currently mounted as /dev/hdc > > so that it will work when the harddisk is moved to /dev/hda? > > > > In other words, the disk is at /dev/hdc during the installation, > > but after that it will be moved to the new computer and become > > /dev/hda. I am trying to accomplish this without having to boot > > from CD or floppy and run lilo manually on the new computer. > > From bash type: > rdev /dev/hdc? /dev/hda? > > where ? is the device number. Thanks for your fast reply! Ok, I tried: "rdev /dev/hdc2 /dev/hda2" and then "lilo -r /mnt -C /etc/lilo.conf" but I get: "Warning: The boot sector and map file are on different disks." When trying to boot, I get: "LILO 22.5.9 Loading Linux......" "LILO 22.5.9 Loading Linux" and then it hangs. What did I do wrong / any suggestions? Thanks, Lars |
| |||
| On Fri, 24 Sep 2004 01:24:03 GMT, Lars wrote: > "rdev /dev/hdc2 /dev/hda2" and then "lilo -r /mnt -C /etc/lilo.conf" > but I get: > "Warning: The boot sector and map file are on different disks." > > When trying to boot, I get: > "LILO 22.5.9 Loading Linux......" > "LILO 22.5.9 Loading Linux" > and then it hangs. > > What did I do wrong / any suggestions? Hmmm, missing map line in lilo.conf? Why no initrd line ? Snippet from my Mandrake 10 Official follows: boot=/dev/hda map=/boot/map install=menu default="md10oe" keytable=/boot/us.klt prompt nowarn timeout=50 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label="md10oe" root=/dev/hdb9 initrd=/boot/initrd.img append="devfs=mount acpi=force resume=/dev/hdb1 splash=0" vga=788 read-only |
| |||
| "Bit Twister" <BitTwister@localhost.localdomain> wrote in message news:slrncl6uul.gtd.BitTwister@wb.home.invalid... > On Fri, 24 Sep 2004 01:24:03 GMT, Lars wrote: > > > "rdev /dev/hdc2 /dev/hda2" and then "lilo -r /mnt -C /etc/lilo.conf" > > but I get: > > "Warning: The boot sector and map file are on different disks." > > > > When trying to boot, I get: > > "LILO 22.5.9 Loading Linux......" > > "LILO 22.5.9 Loading Linux" > > and then it hangs. > > > > What did I do wrong / any suggestions? > > Hmmm, missing map line in lilo.conf? > Why no initrd line ? Thanks for your reply. The map is default to /boot/map and I am not using an initrd. The lilo.conf file I posted works just fine when I run /sbin/lilo with the harddisk on /dev/hda. What I am having a hard time with is installing LILO when the disk is on /dev/hdc in such a way that it can be moved to /dev/hda without having to re-run /sbin/lilo. / Lars |
| |||
| On Thursday 23 September 2004 06:24 pm, Lars did deign to grace us with the following: > "Realto Margarino" <guymacon@IMAmoron.org> wrote in message >> In alt.os.linux.slackware Lars <noemail@hotmail.com> wrote: >> > Hi, .... >> > In other words, the disk is at /dev/hdc during the installation, >> > but after that it will be moved to the new computer and become >> > /dev/hda. I am trying to accomplish this without having to boot >> > from CD or floppy and run lilo manually on the new computer. >> From bash type: >> rdev /dev/hdc? /dev/hda? >> where ? is the device number. > Thanks for your fast reply! > Ok, I tried: > "rdev /dev/hdc2 /dev/hda2" and then "lilo -r /mnt -C /etc/lilo.conf" > but I get: > "Warning: The boot sector and map file are on different disks." > > When trying to boot, I get: > "LILO 22.5.9 Loading Linux......" > "LILO 22.5.9 Loading Linux" > and then it hangs. > > What did I do wrong / any suggestions? > I hope I'm not totally out in left field, but after doing LILO, which incidentally, I get the same message when I put LILO to floppy, then trying to boot, are you trying to boot the drive _as_ hda, I mean, plugged into the other adapter and all? Just a thought. Good Luck! Rich |
| |||
| In alt.os.linux.slackware Lars <noemail@hotmail.com> wrote: > > "Realto Margarino" <guymacon@IMAmoron.org> wrote in message > news:BOJ4d.27520$pA.1711505@news20.bellglobal.com. .. >> In alt.os.linux.slackware Lars <noemail@hotmail.com> wrote: >> > Hi, >> > >> > I am trying setup a fairly automated linux installation procedure >> > that uses a Linux "installation server" where I simply connect a >> > blank IDE disk as /dev/hdc and run a script that partitions, >> > formats, installs the FS, etc. >> > >> > All is working very well except for LILO: Is there a way to >> > install LILO on a harddisk that is currently mounted as /dev/hdc >> > so that it will work when the harddisk is moved to /dev/hda? >> > >> > In other words, the disk is at /dev/hdc during the installation, >> > but after that it will be moved to the new computer and become >> > /dev/hda. I am trying to accomplish this without having to boot >> > from CD or floppy and run lilo manually on the new computer. >> >> From bash type: >> rdev /dev/hdc? /dev/hda? >> >> where ? is the device number. > > Thanks for your fast reply! > > Ok, I tried: > "rdev /dev/hdc2 /dev/hda2" and then "lilo -r /mnt -C /etc/lilo.conf" > but I get: > "Warning: The boot sector and map file are on different disks." > > When trying to boot, I get: > "LILO 22.5.9 Loading Linux......" > "LILO 22.5.9 Loading Linux" > and then it hangs. > > What did I do wrong / any suggestions? > Sorry, my mistake. It should be: rdev /whatever/path/vmlinuz /dev/hda2. That will make the vmlinuz image file bootable on /dev/hda2/ where it was once bootable on /dev/hdc2 Sorry about the misinformation. cordially, as always, rm |
| ||||
| > > Sorry, my mistake. It should be: > > rdev /whatever/path/vmlinuz /dev/hda2. > > That will make the vmlinuz image file bootable on /dev/hda2/ where > it was once bootable on /dev/hdc2 That makes more sense. So with your approach: 1) Run /sbin/lilo with a lilo.conf that has boot=/dev/hdc root=/dev/hdc2 2) rdev (path to kernel) /dev/hda2. 3) Move disk from /dev/hdc to /dev/hda I will try that. Meanwhile, I came up with a similar solution that seems to work: 1) "/sbin/lilo -r /mnt -C /etc/lilo_inst.conf " The file lilo_inst.conf has: boot=/dev/hdc root=/dev/hda2 (The regular /etc/lilo.conf is untouched [boot=/dev/hda, root=hda2]) 2) Move disk from /dev/hdc to /dev/hda I tried my procedure, and it seems to work. The only concern I have is some warnings during boot (the lines below repeats three times): hda: dma_intr: error=0x84 { DriveStatusError BadCRC } hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Also, the first boot it always claims the disk has not been fsck:ed for 49782 days (or something) and forces a check. Odd... I have not yet had time to try with a different disk, but I do not recall having this problem with this disk earlier. Do you (or anyone) see any problem with my procedure above? Thanks, Lars |