[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Minor install problem



Last night, I installed Debian Linux to a new machine and ran into a fairly
minor problem, but thought I'd mention it to the list.  I'm not sure it's a
bug, undocumented product feature, or BDU (brain-dead user), but,
anyway....  Call this a bug report, request for comment, your choice.

Debian Version - 1.3.0
Boot Disk Version - May 30, 1997
Hardware - P/100, 64MB, AHA2940, 1x1GB SCSI, 1x2GB SCSI

The 1GB drive is /dev/sda1
The 2GB drive is /dev/sdb1, /dev/sdb5, /dev/sdb6

/dev/sda1 is 1GB, mounted to /
/dev/sdb1 is 1GB, mounted to /usr
/dev/sdb5 is 1GB, mounted to /var
/dev/sdb6 is ~60MB swap

The Debian install allowed me to do all of the above flawlessly; however,
when it came time to make the system bootable, the install complained that
it wasn't possible to boot off the second disk (at this time).  I found
this a little strange as /dev/sda1 (drive with ID=0) was where I
wanted/expected to boot from and the install script was "thinking" that I
was wanting to boot from /dev/sdb....  Not sure what the problem was here. 
Was it because I was partitioning and initializing the second drive after
the first and the install script works with the last drive accessed??? 
....

Anyway, I created a boot disk, booted the system, edited /etc/lilo.conf,
ran lilo and I'm now happily booting off /dev/sda.

So, why am I mentioning this?  Well, the install routine didn't behave like
I expected and it wasn't a choice that I made to try to boot from the
second drive - I'm not sure why the install tried to do that.

I had no problem "fixing" the problem; however, someone new to Linux and/or
Debian, etc. would have trouble with this.

My thoughts for the day.

later,

Kevin Traas			Baan Business Systems
Systems Analyst		Langley, BC, Canada
Kevin@Baan-BBS.CA		(604) 882-8169


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .


Reply to: