1 # DragonFly Release 2.4
3 # Possible Upgrade Issues
5 * The kernel is unable to find the root and stops at the mountroot prompt.
6 Due to the upgrade the drive may have changed names.
7 * Hit scroll-lock on the console, scroll up and locate the root drive.
8 * For BOOT+HAMMER try specifying: "hammer:xxxs1d", where xxx is the drive.
9 * For UFS try specifying: "ufs:xxxs1a", where xxx is the drive.
10 * Once you get the system up you may have to remount / read-write, then
11 fix /etc/fstab and adjust /boot/loader.conf as necessary to specify
12 the root mount using vfs.root.mountfrom="hammer:serno/<SERIALNUMBER>.s1d"
13 (for example). We recommend specifying mount points by serial number,
14 using /dev/serno/<SERIALNUMBER>.s1<partition> as necessary.
16 * Your kernel and world are out of sync.
17 * Try booting into single user mode and complete the installation.
18 * Or boot the CD and re-upgrade.
20 * HAMMER-only installation fails with BTX errors or is unable to load
21 the loader, or kernel.
22 * An algorithmic bug in the loader's HAMMER implementation causes the
23 loader to improperly parse file data in some cases.
24 * All we can recommend here is to switch to a BOOT+HAMMER installation,
25 which is fully supported and actually considerably easier to manage.
26 You can steal 256MB from your swap partition to create a UFS boot
27 partition, naming it 'a'. Then copy the HAMMER /boot into it
28 (directly, not as a subdirectory called 'boot').
32 * Occasional panic after burning a CD. This is a known issue
33 which we hope to address in 2.4.1.
34 * Possible issues with kqueue operations getting stuck (w/ postfix).
35 This issue is being investigated.
36 * 64-bit kernel is unable to probe USB mass storage devices. This is a
37 known issue which we hope to address in 2.4.1.