RE: Problem booting my system

2001-10-19 Thread Kris Huber
Thanks Robert,

I've got my system up now, and I didn't have to resort to putting the boot
partition on the IDE drive.  I think the main problem was in the lilo.conf
file being incorrect.  When I used the default file it (mostly) worked.  I
made an entry in the fstab file instructing it to mount read-write.  Upon
boot-up fsck was always giving an error about the root partition, but yet
when I ran fsck it always reported 'clean' for me.

I'm not sure what the most important difference was, but this lilo.conf
worked:
lba32
boot=/dev/sda
root=/dev/sda2
install=/boot/boot.b
map=/boot/map
delay=50
vga=normal
default=Linux
image=/vmlinuz
label=Linux
read-only
image=/vmlinuz.old
label=LinuxOLD
read-only
optional
where /vmlinuz was a symbolic link to /boot/vmlinuz-2.2.19pre17-compact. 

This lilo.conf seemed to not work for me (although it had worked earlier,
extended with various kernel options, etc.):
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
#prompt
lba32
#vga=ask
timeout=50
default=linux
image=/boot/vmlinuz-2.2.19pre17-compact
label=linux
root=/dev/sda2
read-only
append = 
I noticed that under Linux the IDE drive is found whether or not it is
enabled in BIOS.  I disconnected power from it for awhile to make sure the
system only saw the SCSI drive, but I don't think that was the problem after
all.

-Kris

-Original Message-
From: Robert Waldner [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 18, 2001 6:18 PM
To: debian-user@lists.debian.org
Subject: Re: Problem booting my system 



On Thu, 18 Oct 2001 18:10:09 MDT, Kris Huber writes:
With the boot sequence having scsi first, a program (the kernel, I assume)
runs and prints 001  in an endless loop, filling the screen until I
cntlaltdel.  I have an IDE drive in the system (ext2 file system),
but
I've disabled it in BIOS in addition to not selecting it as a boot drive.

Have you looked at
 http://lists.debian.org/debian-user/2001/debian-user-200109/msg03337.html
?

cheers,
rw
-- 
-- OS/X: Because making Unix user-friendly
-- was easier than debugging Windows.




Problem booting my system

2001-10-18 Thread Kris Huber
Hello Debian enthusiasts,

I'm having difficulty getting my system to boot off my SCSI hard disk.  It
boots off the rescue diskette, and I've rerun lilo after checking over the
lilo.conf file.  I got the following when I ran lilo:

Reading boot sector from /dev/sda
Warning: /dev/sda is not on the first disk
Merging with /boot/boot.b
Boot image: /boot/vmlinuz-2.2.19pre17-compact
Added linux *

The warning concerned me, but I figured it was because I had BIOS set to
boot off the floppy first, if possible.  With boot sequence floppy, scsi,
cd, the system hangs after printing LI (without floppy in the drive).  I
can get the system up if I put a rescue floppy in and do
boot:  rescue root=/dev/sd2.

With the boot sequence having scsi first, a program (the kernel, I assume)
runs and prints 001  in an endless loop, filling the screen until I
cntlaltdel.  I have an IDE drive in the system (ext2 file system), but
I've disabled it in BIOS in addition to not selecting it as a boot drive.
The motherboard is an EPoX K7XA with 800 MHz Athlon processor.

Any ideas of where to go from here?  This first happened when rebooting
after an 'apt-get upgrade' on my packages from the testing distribution of
the 2.4 kernel.  But obviously the problem was something else, because I've
now installed the potato release and the problem hasn't gone away.

Thanks for any clues,
Kris



Re: Problem booting my system

2001-10-18 Thread Robert Waldner

On Thu, 18 Oct 2001 18:10:09 MDT, Kris Huber writes:
With the boot sequence having scsi first, a program (the kernel, I assume)
runs and prints 001  in an endless loop, filling the screen until I
cntlaltdel.  I have an IDE drive in the system (ext2 file system), but
I've disabled it in BIOS in addition to not selecting it as a boot drive.

Have you looked at
 http://lists.debian.org/debian-user/2001/debian-user-200109/msg03337.html
?

cheers,
rw
-- 
-- OS/X: Because making Unix user-friendly
-- was easier than debugging Windows.




pgpwLrZ2TqgVi.pgp
Description: PGP signature