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"
14 * We recommend specifying mount points by serial number, using
15 /dev/serno/SERIALNUMBER.s1PARTITION as necessary. Also remember
16 you may have a device specification in your /etc/rc.conf (for the dump device),
17 and of course the root mount specification in /boot/loader.conf.
19 * Your kernel and world are out of sync.
20 * tty's and pty's may not work properly in this case, you may have
21 trouble getting a root prompt.
22 * Try booting into single user mode and complete the installation.
23 * Or boot the CD and re-upgrade.
25 * HAMMER-only installation fails with BTX errors or is unable to load
26 the loader, or kernel.
27 * An algorithmic bug in the loader's HAMMER implementation causes the
28 loader to improperly parse file data in some cases.
29 * All we can recommend here is to switch to a BOOT+HAMMER installation,
30 which is fully supported and actually considerably easier to manage.
31 You can steal 256MB from your swap partition to create a UFS boot
32 partition, naming it 'a'. Then copy the HAMMER /boot into it
33 (directly, not as a subdirectory called 'boot').
35 * You have an AHCI SATA controller but the new AHCI driver is having
36 problems detecting your drives.
37 * There is a boot menu option to disable the AHCI driver, which will
38 cause the kernel to fall back to the NATA driver. Setting
39 hint.ahci.disabled=1 in /boot/loader.conf will accomplish the same
42 * The installer errors out while trying to install a disklabel.
43 * Known issue. We blew the partition cleaning dd. Basically the
44 installer wants to install a disklabel64 but there is a standard
45 disklabel already installed. For safety reasons the disklabel
46 program refuses to blow away the old label.
47 * You can blow away the whole disk or the slice from the emergency
48 shell prompt (alt f3? alt f4?) and then start the installation over
50 * dd if=/dev/zero of=/dev/RAWDISK bs=32k count=4 **This will blow
51 away the whole disk**. You can try it on just the slice, aka
52 RAWDISKs1 but it is fairly dangerous to do so be careful.
57 * Occasional panic after burning a CD. This is a known issue
58 which we hope to address in 2.4.1.
59 * Possible issues with kqueue operations getting stuck (w/ postfix).
60 This issue is being investigated.
61 * 64-bit kernel is unable to probe USB mass storage devices. This is a
62 known issue which we hope to address in 2.4.1.