(no commit message)

diff --git a/issues24/index.mdwn b/issues24/index.mdwn
index 5d63c34..e8bd736 100644 (file)
--- 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/<SERIALNUMBER>.s1d"
+   (for example).  We recommend specifying mount points by serial number,
+   using /dev/serno/<SERIALNUMBER>.s1<partition> 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).
+
+