Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Jun 1995 10:17:35 -0400 (EDT)
From:      Jeff Aitken <jaitken@cslab.cs.vt.edu>
To:        hackers@freebsd.org
Subject:   2.0.5R install notes
Message-ID:  <199506131417.KAA08546@husky.cslab.vt.edu>

next in thread | raw e-mail | index | archive | help
First, congrats to everyone who made the 2.0.5 release possible.  The
install was especially slick (even more so than the 2.0R one, which I
though was pretty nice).  I did encounter a couple thinsg worth
mentioning:

1.  I had some difficulty getting an MBR written correctly.  I was
previously running 2.0R, and the 2.0.5 install read the disklabel (or
MBR, or whatever, I'm a little hazy on these ideas yet) and found my old
partitions.  Which seemed great at first because I was able to install
2.0.5 and retain my 300MB of stuff in /home without restoring the
backups (just told it not to newfs that FS).  But, after all was
installed, I rebooted and got something like "partition out of reach of
BIOS".  I was able to stick in the boot floppy, then at the prompt tell
it to boot from sd(0,a)/kernel and it worked fine.  Well, I tried
playing with fdisk, and disklabel, but to no avail -- again, I'm still
not 100% sure how all this works.  After a very frustrating hour or so,
I just formatted the entire drive under DOS, then did a clean re-install
of 2.0.5, and it worked like a charm.  

2.  Under 2.0R, the machine would not boot after a clean shutdown.  I
would get messages from the NCR driver (I have the NCR 53c810 SCSI card
and a Micropolis 4110 Fast SCSI-2 drive) about some command failing,
then stuff about inodes or symlinks, and I would have to turn the
machine off.  Whenever I rebooted and it actually had to go and clean
the filesystems, there was no problem (ie, if I just cut the power off,
and didn't 'shutdown -h now', I would get a normal reboot).  I have no
idea what was causing this; I believe there was some chatter in this
mailling list about it awhile back.  (Sanity check: I did try and force
an fsck at boot time by changing /etc/rc, but that didn't help).  Anyway,
the problem has vanished (for me anyway) under 2.0.5R


-- 
Jeff Aitken
jaitken@vt.edu




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506131417.KAA08546>