Hi All,
Sort of a newbie question - just upgraded (by NFS! what a pleasure!
Patrick Volkerding is a god!) to the latest slackware version and am trying
to get LILO to work correctly.
Everything installed OK and the system is useable, but it WILL NOT
boot from the HD. I have an adaptec aha1540c (floppy-less) scsi
controller,
Maxtor 3.5" HH LXT 340 MB drive (as well as an older IMPRIMIS 5.25" FH
600MB drive with which I am having similar problems). I also have one
of the infamous 486SLC2/66 Blue Lightning/Alaris motherboards w/ AMI
BIOS (yes, I read about the problem with the BIOS setting for
disk type 47 0:300 vs DOS 1K - tried it both ways)
The fdisk setup is: (note the comment after the "/dev/sda1" line - is
this significant?)
Disk /dev/sda: 64 heads, 32 sectors, 324 cylinders
Units = cylinders of 2048 * 512 bytes
Device Boot Begin Start End Blocks Id System
/dev/sda1 * 1 1 24 24575+ 83 Linux native
Partition 1 does not start on cylinder boundary:
phys=(0, 0, 2) should be (0, 1, 1)
/dev/sda2 25 25 41 17408 82 Linux swap
/dev/sda3 42 42 324 289792 83 Linux native
My lilo.conf (generated by the install program) looks like:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
#compact # faster, but won't work on all systems.
delay = 50
vga = normal # force sane state
ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /vmlinuz
root = /dev/sda1
label = Linux
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/sdc1
label = DOS
loader = any_d.b
table = /dev/sdc
# DOS bootable partition config ends
(I plan to install 2 other disks, hence the '/dev/sdc' entry.
The problem is 2 fold. First, after the installation and making
the boot floppy, I can use the boot floppy to boot up the machine just
fine.
However, after installing LILO with the above lilo.conf file to a
test floppy, it will star to boot correctly, but give the following
error
midway thru the boot process:
.
.
Partition check:
sda: sda1 sda2 sda3
MINIX-fs: unable to read superblock
EXT2-fs: unable to read superblock
XIA-FS: read super_block failed (inode.c 74)
MSDOS bread failed
isofs_read_super: bread failed, dev 0x341 iso_blknum 16
Weird - unlocked, clean and not uptodate buffer on list 0
Weird - unlocked, clean and not uptodate buffer on list 0
Weird - unlocked, clean and not uptodate buffer on list 0
Weird - unlocked, clean and not uptodate buffer on list 0
Weird - unlocked, clean and not uptodate buffer on list 0
Weird - unlocked, clean and not uptodate buffer on list 0
harddisk I/O error
dev 0341, sector 0
HPFS: map_sector: read error
Kernel Panic: VFS: Unable to mount root
and then hang.
Rebooting with the original (non-LILO) boot floppy will bring the system
up
normally and in fact the fsck that takes place in the course of normal
bootup finds nothing wrong (as implied by the error messages above).
The one time I did fsck the root fs, it did find a few
inconsistancies, but correcting them did nothing to change this
behavior.
The other problem is thatI've never been able to get either of my HDs to
boot with LILO, despite setting (and resetting the MBR with the DOS "fdisk
/mbr" command, using the linux fdisk, reformatting (high and low level),
etc. Haven't even been able to get a part of the 'LILO' trace to show.
After going thru the normal power-on procedures (memory check, check of the
Adaptec BIOS, detecting the HD, checking the floppy), it just sits there
like a dead dog with the line "Missing operating system" glaring at me.
Any ideas, suggestions, pointers, FMs to read, HOWTOS welcomed. Responses
will be summarised and posted, with results.
Thanks
Harry
--
Harry Mangalam, VCO/Micro+Mol Genetics, Irvine Hall, College of Medicine,
UC Irvine, Irvine, CA, 92717, Vox:(714) 856-4824, Fax:(714) 725-2118,
There's no better glory, when it all gets harried, to be laughing in the
midst of it all. --- Doug and the Slugs ---