M.K. (via DragonFly issue tracker) wrote:
M.K. <[email protected]> added the comment:
OS: dfly-2.2.0-REL
Installer quits (at newfs) when you try to install using part of disk (i.e.
using partition no. 2, 3 or 4 for dfly).
Reason: missing device nodes for disk label letters.
Fix: manually add disk label device nodes before running installer.
e.g.:
# ./MAKEDEV ad0s2a
# ./MAKEDEV ad0s3a
# ./MAKEDEV ad0s4a
Note.1: Doing it just for "a" makes all the other letters as well.
Note.2: problem occurs for both hammer and ufs FS selection.
----------
status: unread -> chatting
_____________________________________________________
DragonFly issue tracker <[email protected]>
<http://bugs.dragonflybsd.org/issue1292>
_____________________________________________________
Side note:
This has not been seen here if/as/when the target device has previously
been sliced/labeled by a prior DFLY install, OR with FreeBSD's toolset,
even if the target partition was not previously used by DFLY.
I have installed both/either of 2.3.0 // 2.2.0 to first and second
slices where FreeBSD 7 or 8 or Vector Linux previously lived, and to
where a slackware-based Linux once lived, and to a /dev/ar0 ATACONTROl
RAID1 array previously created with FreeBSD 8-
That holds for both 100%-HAMMER, 100%-UFS, and mixed, UFS-system +
HAMMER-add-on partitions.
Reboot between configuring the slice & partitions and completing the
install, as other OS'en may need, was not required.
All were CLI-mode cd iso installs, none yet tried here with the dvd.
No MAKEDEV yet required, other than whatever is inbuilt to the
installation process.
I suspect a label-reading issue, not a MAKEDEV fail per-se.
I shall now go off and format an external drive with the Mac for a test
of extreme weirdness, label-wise, and see if I can reproduce the
behaviour you report when converting it.
HTH,
Bill Hacker
