I'm in the process of building a new PC to replace my aging PII-400 box.
The trick is that I want to copy over the data from the old to the new.
I've got a nice 30GB IDE drive in the new box, and i've successfully
copied all the data with the following partition table:
Disk /dev/hdd: 240 heads, 63 sectors, 3877 cylinders
Units = cylinders of 15120 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdd1 1 677 5118088+ b Win95 FAT32 Win98
/dev/hdd2 678 680 22680 83 Linux /boot
/dev/hdd3 * 681 1521 6357960 83 Linux /
/dev/hdd4 1522 3877 17811360 5 Extended
/dev/hdd5 1522 1566 340168+ 82 Linux swap
/dev/hdd6 1567 2599 7809448+ 83 Linux /usr
/dev/hdd7 2600 3877 9661648+ 83 Linux /opt
Note, that everything will be /dev/hda in the new box, this is just how
its connected to the old box while i'm copying the data. The data has
copied over without any problems (i've verified by mounting each
partition). The problem at hand is the damn bootloader, LILO.
I'm trying to write LILO to the third partition (hdd3), as i use a
different bootloader in the MBR. Here's what lilo.conf looks like:
==============
boot=/dev/hdd3
read-only
prompt
timeout=20
vga=normal
linear
default=linux-2.4.5
image=/boot/vmlinuz-2.2.19
root=/dev/hda3
label=linux
append="hdb=ide-scsi"
image=/boot/vmlinuz-2.4.5
root=/dev/hda3
label=linux-2.4.5
append="hdb=ide-scsi"
image=/boot/vmlinuz-2.4.7
root=/dev/hda3
label=linux-2.4.7
append="hdb=ide-scsi"
==============
Here's where it all goes to hell:
[root@hal /etc]# /sbin/lilo
Warning: /dev/hdd3 is not on the first disk
Warning: BIOS drive 0x82 may not be accessible
Device 0x1640: Invalid partition table, 3rd entry
3D address: 3/0/128 (1935362)
Linear address: 1/0/680 (10281600)
So i tried to fix the partition table:
[root@hal /etc]# /sbin/lilo -P fix
Warning: /dev/hdd3 is not on the first disk
Warning: BIOS drive 0x82 may not be accessible
Device 0x1640: Invalid partition table, 3rd entry
3D address: 3/0/128 (1935362)
Linear address: 1/0/680 (10281600)
Writing modified partition table to device 0x1640
Warning: BIOS drive 0x82 may not be accessible
Warning: BIOS drive 0x82 may not be accessible
Warning: BIOS drive 0x82 may not be accessible
Added linux
Warning: BIOS drive 0x82 may not be accessible
Added linux-2.4.5 *
Warning: BIOS drive 0x82 may not be accessible
Added linux-2.4.7
Attempts to boot into Linux result in the dreaded "010101010101010110"
series of errors filling the screen. FWIW, i can boot into Windoze just
fine, so this is purely a LILO problem.
Normally, i'd assume that this is that dreaded 1024 cylinder issue, but
as the fdisk output above indicates, /boot is well below the 1024th
cylinder. I'm really not sure what else could be the problem here.
I've been fighting this since Friday night with virtually no progress,
so i'd appreciate the wisdom of any of your LILO gurus. I'm really
eager to get this new box up & running, since its a significant hardware
improvement over the older one.
-Lonni
=====
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lonni J. Friedman [EMAIL PROTECTED]
Linux FAQ & Step-by-step help: http://netllama.ipfox.com
.
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
_______________________________________________
http://linux.nf -- [EMAIL PROTECTED]
Archives, Subscribe, Unsubscribe, Digest, Etc
->http://linux.nf/mailman/listinfo/linux-users
