From 9d3d8d0409c8720f685efc607d1e15d44dbf5701 Mon Sep 17 00:00:00 2001 From: dillon Date: Wed, 16 Sep 2009 20:32:55 -0700 Subject: [PATCH] --- issues24/index.mdwn | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/issues24/index.mdwn b/issues24/index.mdwn index 5d63c346..e8bd736b 100644 --- a/issues24/index.mdwn +++ b/issues24/index.mdwn @@ -1,2 +1,35 @@ # DragonFly Release 2.4 + +# Possible Upgrade Issues + +* The kernel is unable to find the root and stops at the mountroot prompt. + Due to the upgrade the drive may have changed names. + * Hit scroll-lock on the console, scroll up and locate the root drive. + * For BOOT+HAMMER try specifying: "hammer:xxxs1d", where xxx is the drive. + * For UFS try specifying: "ufs:xxxs1a", where xxx is the drive. + * Once you get the system up you may have to remount / read-write, then + fix /etc/fstab and adjust /boot/loader.conf as necessary to specify + the root mount using vfs.root.mountfrom="hammer:serno/.s1d" + (for example). We recommend specifying mount points by serial number, + using /dev/serno/.s1 as necessary. + +* Your kernel and world are out of sync. + * Try booting into single user mode and complete the installation. + * Or boot the CD and re-upgrade. + +* HAMMER-only installation fails with BTX errors or is unable to load + the loader, or kernel. + * An algorithmic bug in the loader's HAMMER implementation causes the + loader to improperly parse file data in some cases. + * All we can recommend here is to switch to a BOOT+HAMMER installation, + which is fully supported and actually considerably easier to manage. + You can steal 256MB from your swap partition to create a UFS boot + partition, naming it 'a'. Then copy the HAMMER /boot into it + (directly, not as a subdirectory called 'boot'). + # Known Issues + +* Occasional panic after burning a CD. +* Possible issues with kqueue operations getting stuck (w/ postfix). + + -- 2.41.0