Re: Help needed: can't boot with LILO on new hdd
From: JohnInSD At san DOT rr dot COM (bitbucket_at_hotmail.com)
Date: 10/01/04
- Next message: John Thompson: "Re: Software to create an E-book?"
- Previous message: A. S. Budden: "Re: accident: "rm core *""
- Maybe in reply to: anc: "Re: Help needed: can't boot with LILO on new hdd"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 01 Oct 2004 14:48:06 GMT
If you are using version 21.5 of LILO, you will have problems (see below).
This version is very out-of-date (3 years or so). The current revision is
22.6.
Reading between the lines, it appears you took your old disk which was
/dev/hda and moved it to /dev/hdb. This makes this disk unbootable with
version 21 of LILO because you have changed the BIOS device code of the disk.
Version 21 can boot this system, but you have to get a lot of things right in
the config file. Version 22.6 is much more forgiving. At first glance, your
config file looks like it is usable.
1. Get the current release of LILO: http://lilo.go.dyndns.org/pub/linux/lilo
Both source and binary are available.
2. Generate a log of your LILO install: "lilo -v5 >log.txt"
This file will be big.
The main difference between Version 21 and Version 22 of LILO is that the
latter determines the BIOS device codes of your disks at boot-time, not
install time. This is much more flexible.
With XP on both disks, you may get a Volume ID conflict. Since you are going
to install XP after the Linux install, it is okay to let LILO resolve the
conflict by changing the VolumeID of the NEW disk. Leave the old disk alone.
--John
On Thu, 30 Sep 2004 20:25:09 +0200, "martines" <martines@REMOVEacn.waw.pl>
wrote:
>Hello all,
>
>I've bought 160 gb samsung hdd. I've already got Gentoo installation on my
>old 40gb hdd so I followed Hard-Disk-Upgrade Howto to transfer linux to my
>new disk Files transfer didn't give any troubles. I edited lilo.conf
>(listing 1) and fstab to make appropriate changes. I executed 'lilo'
>command successfully. However when I reboot I got either DISK BOOT FAILURE
>(before unsuccessful XP installation - thats another story) or simple hang
>(after unsuccessful XP installation).
>
>Listing 1 - /new-disk/etc/lilo.conf
>
>=== begin ===
>
>boot=/dev/hda
>#disk=/dev/hda
># bios=0x80
># sectors=63
># heads=16
># cylinders=310101
>#disk=/dev/hdb bios=0x81
>map=/new-disk/boot/map
>install=/new-disk/boot/boot.b
>prompt
>timeout=30
>vga=791
>lba32
>#linear
>default=linux-hda
>
># new linux
>image=/new-disk/boot/kernel-2.4.20-gentoo-r6
> label=linux-hda
> root=/dev/hda7
> initrd=/new-disk/boot/initrd-2.4.20-gentoo-r6
> append=" root=/dev/hda7 init=/linuxrc acpi=off"
>
># old linux
>image=/boot/kernel-2.4.20-gentoo-r6
> label=linux-hdb
> root=/dev/hdb8
> initrd=/boot/initrd-2.4.20-gentoo-r6
> append=" root=/dev/hdb8 init=/linuxrc acpi=off"
>
>other=/dev/hdb2
> label=win
> table=/dev/hdb
>
>=== end ===
>
>Since Lilo menu doesn't appear at all I can't even boot to linux-hdb which
>is my old linux. What is more confusing I can't even boot to my new linux
>from working Lilo installed on /dev/hdb (old hdd) using lilo.conf as
>follows:
>
>=== begin ===
>
>disk=/dev/hda bios=0x80
>disk=/dev/hdb bios=0x81
>boot=/dev/hdb
>map=/boot/map
>install=/boot/boot.b
>prompt
>timeout=30
>vga=791
>lba32
>default=win
>
># doesn't work
>image=/new-disk/boot/kernel-2.4.20-gentoo-r6
> label=linux-new
> root=/dev/hda7
> initrd=/new-disk/boot/initrd-2.4.20-gentoo-r6
> append=" root=/dev/hda7 init=/linuxrc acpi=off"
>
># works
>image=/boot/kernel-2.4.20-gentoo-r6
> label=linux
> root=/dev/hdb8
> initrd=/boot/initrd-2.4.20-gentoo-r6
> append=" root=/dev/hdb8 init=/linuxrc acpi=off"
>
># works
>other=/dev/hdb2
> label=win
> table=/dev/hdb
>
>=== end ===
>
>When I choose linux-new from Lilo menu couple of dots (showing progress)
>appears and computer hangs.
>
>Here is my partition table on new hdd:
>
>=== begin ===
>
>(parted) print
>Disk geometry for /dev/ide/host0/bus0/target0/lun0/disc: 0.000-152627.835
>megabytes
>Disk label type: msdos
>Minor Start End Type Filesystem Flags
>1 7000.383 152627.835 extended lba
>5 7000.414 7030.898 logical ext2 boot
>6 7030.929 7530.468 logical linux-swap
>7 7530.500 17530.734 logical reiserfs
>8 17530.765 38010.656 logical ntfs
>9 38010.687 70771.148 logical fat32
>10 70771.179 96371.296 logical ntfs
>11 96371.328 152627.835 logical ntfs
>
>=== end ===
>
>I've just learned about parted so I installed it. It prints following
>warning:
>
>Using /dev/ide/host0/bus0/target0/lun0/disc
>Warning: Unable to align partition properly. This probably means that
>another
>partitioning tool generated an incorrect partition table, because it
>didn't have
>the correct BIOS geometry. It is safe to ignore,but ignoring may cause
>(fixable) problems with some boot loaders.
>
>Perhaps this is the reason why I can't boot new partition (but why I can't
>boot old linux using Lilo from /dev/hda). How to fix it?
>
>My computer is an Athlon on NForce2 MSI mobo.
>
>Thank you in advance.
>
>martines
>
>P.S. And here is an output from windows/dos utility 'FINDPART.EXE tables':
>
>Findpart, version 4.45 - for Windows 95/98/ME/NT/2000/XP.
>Copyright Svend Olaf Mikkelsen, 1999-2004.
>
>OS: Windows 5.1.2600 Dodatek Service Pack. 1 Partition tables:
>
>Disk: 1 Cylinders: 310101 Heads: 16 Sectors: 63 MB: 152628
>
>--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
> 0 1 0F 14336784298245024145627 14223# 0 1310100* 15 63 OK
>
> 14223 1*83 63 62433 30 14223# 1 1 14284* 15 63 OK OK
> 14223 2 05 62496 1023120 499 14285# 0 1 15299* 15 63 OK
>
> 14285 1 82 63 1023057 499 14285# 1 1 15299* 15 63 OK
> 14285 2 05 1085616 20480544 10000 15300# 0 1 35617* 15 63 OK
>
> 15300 1 83 63 20480481 10000 15300# 1 1 35617* 15 63 NB OK
> 15300 2 05 21566160 41942880 20479 35618# 0 1 77227* 15 63 OK
>
> 35618 1 07 63 41942817 20479 35618# 1 1 77227* 15 63 OK OK
> 35618 2 05 63509040 67093488 32760 77228# 0 1143788* 15 63 OK
>
> 77228 1 0B 63 67093425 32760 77228# 1 1143788* 15 63 R0 OK
> 77228 2 05130602528 52429104 25600143789# 0 1195801* 15 63 OK
>
>143789 1 07 63 52429041 25600143789# 1 1195801* 15 63 OK OK
>143789 2 05183031632115213392 56256195802# 0 1310100* 15 63 OK
>
>195802 1 07 63115213329 56256195802# 1 1310100* 15 63 OK OK
- Next message: John Thompson: "Re: Software to create an E-book?"
- Previous message: A. S. Budden: "Re: accident: "rm core *""
- Maybe in reply to: anc: "Re: Help needed: can't boot with LILO on new hdd"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
