<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 01/25/2011 7:57 AM, Ian Robinson wrote:
<blockquote
cite="mid:AANLkTi=XbAMQ69G-7tR-XGUrUYCXOESUuUBLM+vK=hRm@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">On Mon, Jan 24, 2011 at 10:41 PM, Ian
Robinson <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:fitchkendall@gmail.com">fitchkendall@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">>><br>
>> Tonight, I will try a "fresh install" on machine #2, which I
expect to<br>
> >go well. I will hold off on messing with machine #1 in case
Kris<br>
> wants me to test anything.<br>
>><br>
> >Ian Robinson<br>
> >Salem, Ohio<br>
<br>
>Ian,<br>
><br>
>Well, the firmware update was worth a try. In looking over the
changes<br>
>that went into 8.2 over at the FreeBSD 8.2 TODO page, I don't see<br>
>anything that jumps out at me related to LSI, SCSI, CAM or
otherwise. It<br>
>would suck if some regression got introduced with SCSI support.<br>
><br>
>Arthur<br>
<br>
<br>
</div>
Arthur -- It was a great suggestion. I do not think there is a
regression with SCSI support. A "fresh install" worked flawlessly.
I'm wondering if the problem is related specifically to the upgrade
script. The kernel panic occurs as the upgrade removes the "old"
packages. I wonder what is being triggered? <br>
<br>
I'm trying to look on the DVD and in the archived packages to see if I
can find the upgrade installation script, but so far I have not found
it.<br>
<font color="#888888"><br>
Ian Robinson<br>
Salem, Ohio<br>
<br>
<br>
</font></blockquote>
<div><br>
I did not find the script in the DVD, but the installation script can
be located in a successful installation at:<br>
<br>
/PCBSD/pc-sysinstall<br>
<br>
========== Code Excerpt: ========================<br>
<br>
# Set a variable of files we want to make backups of before doing
upgrade<br>
BKFILES="/etc/rc.conf /boot/loader.conf"<br>
<br>
if [ -e "/dev/${MPART}" ] ; then<br>
rc_nohalt "mount /dev/${MPART} ${FSMNT}"<br>
if [ "$?" != "0" ] ; then<br>
# Check if we have ZFS tank name<br>
rc_halt "mount -t zfs ${MPART} ${FSMNT}"<br>
fi<br>
else<br>
# Check if we have ZFS tank name<br>
rc_halt "mount -t zfs ${MPART} ${FSMNT}"<br>
fi<br>
<br>
# Mount devfs in chroot<br>
mount -t devfs devfs ${FSMNT}/dev<br>
<br>
# Check if we have any ZFS partitions to mount<br>
zfs mount -a<br>
<br>
# Mount all the fstab goodies on disk<br>
chroot ${FSMNT} /sbin/mount -a >>${LOGOUT} 2>>${LOGOUT}<br>
chroot ${FSMNT} umount /proc >/dev/null 2>/dev/null <br>
chroot ${FSMNT} umount /compat/linux/proc >/dev/null
2>/dev/null<br>
<br>
# Now before we start the upgrade, make sure we set our noschg flags<br>
echo_log "Cleaning up old filesystem... Please wait..."<br>
rc_halt "chflags -R noschg ${FSMNT}"<br>
<br>
# Make backup copies of some files<br>
for i in ${BKFILES}<br>
do<br>
cp ${FSMNT}${i} ${FSMNT}${i}.preUpgrade >/dev/null 2>/dev/null<br>
done<br>
<br>
# Remove some old dirs<br>
rm -rf ${FSMNT}/etc/rc.d >/dev/null 2>/dev/null<br>
<br>
# If we are doing PC-BSD install, lets cleanup old pkgs on disk<br>
if [ "$INSTALLTYPE" != "FreeBSD" ]<br>
then<br>
echo_log "Removing old packages, this may take a while... Please
wait..."<br>
echo '#/bin/sh<br>
for i in `pkg_info -E \*`<br>
do<br>
echo "Uninstalling package: ${i}"<br>
pkg_delete -f ${i} >/dev/null 2>/dev/null<br>
done<br>
' >${FSMNT}/.cleanPkgs.sh<br>
chmod 755 ${FSMNT}/.cleanPkgs.sh<br>
chroot ${FSMNT} /.cleanPkgs.sh<br>
rm ${FSMNT}/.cleanPkgs.sh<br>
run_chroot_cmd "pkg_delete -f \*" >/dev/null 2>/dev/null<br>
run_chroot_cmd "rm -rf /usr/PCBSD" >/dev/null 2>/dev/null<br>
run_chroot_cmd "rm -rf /PCBSD" >/dev/null 2>/dev/null<br>
run_chroot_cmd "rm -rf /var/db/pkgs" >/dev/null 2>/dev/null<br>
run_chroot_cmd "rm -rf /usr/local32" >/dev/null 2>/dev/null<br>
run_chroot_cmd "rm -rf /usr/sbin" >/dev/null 2>/dev/null<br>
run_chroot_cmd "rm -rf /usr/lib" >/dev/null 2>/dev/null<br>
run_chroot_cmd "rm -rf /usr/bin" >/dev/null 2>/dev/null<br>
run_chroot_cmd "rm -rf /boot/kernel" >/dev/null 2>/dev/null<br>
run_chroot_cmd "rm -rf /sbin" >/dev/null 2>/dev/null<br>
run_chroot_cmd "rm -rf /bin" >/dev/null 2>/dev/null<br>
run_chroot_cmd "rm -rf /lib" >/dev/null 2>/dev/null<br>
run_chroot_cmd "rm -rf /libexec" >/dev/null 2>/dev/null<br>
fi<br>
</div>
</div>
</blockquote>
<br>
Is there some way through a VM that you could trap the installation
progress and then drop to a terminal to grab progress from a log file?
There's got to be some way to see the failure occur in a debug mode or
something to know exactly where the failure happens.<br>
<br>
Arthur<br>
</body>
</html>