<div dir="auto">I have had exactly that. The only fix was to mount the disk (I luckily had another disk with earlier version) and specify the device correctly in /etc/fstab and more specifically not by UUID.<div dir="auto"><br></div><div dir="auto">During the hang none of the drive options it'd present me with would work.</div><div dir="auto"><br></div><div dir="auto">Harald</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 30, 2020, 01:03 Nelson H. F. Beebe <<a href="mailto:beebe@math.utah.edu">beebe@math.utah.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've been running about 20 different DragonFlyBSD releases from 3.x to<br>
5.6 on VMs (VMware workstation, VMware/ESX, VirtManager QEMU/KVM, and<br>
OVirt) without any serious difficulties.<br>
<br>
Today, I decided to try installation of 5.6.2 on my new workstation, a<br>
Dell Precision 7920 (1 16-core CPU, 32 hyperthreads, 2200MHz Intel<br>
Xeon Platinum 8253, 32GB DDR-4 RAM).<br>
<br>
That system has 8 externally-accessible disk drives, and I'm using it<br>
as a test bed for O/S installations, with recent Fedora, FreeBSD,<br>
Microsoft Windows, NetBSD, OS108, TrueOS, and Ubuntu releases in place<br>
and working normally.<br>
<br>
Solaris 11.4 installs, but then fails at boot time with an infinite<br>
loop that is probing for USB devices. Until today, that was the only<br>
O/S that has failed to produce a working installation on my Dell box.<br>
<br>
This morning, I made a copy of a 4-day old ISO image for DragonFlyBSD<br>
5.6.2 on a new KOOTION 64GB USB-3 drive and attempted to install it.<br>
The boot proceeded normally for some time, but finally reached a point<br>
in text mode on the console that looks like this (typed by hand):<br>
<br>
...<br>
CAM: Configuring 1 busses<br>
CAM: finished configuring all busses<br>
Device Mapper version 4.16.0 loaded<br>
dm_target_error: Successfully initialized<br>
dm_target_zero: Successfully initialized<br>
no disk named 'part-by-label/DragonFly_v5.7.0.1310.g63d3b.a<br>
setrootbyname failed<br>
ffs_mountroot: can't find rootvp<br>
Root mount failed: 6<br>
<br>
Manual root filesystem specification:<br>
<fstype>:<device> Specify root (e.g. ufs:da0s1a)<br>
? List valid disk boot devices<br>
panic Just panic<br>
abort Abort manual input<br>
<br>
At that point, no further keyboard input is possible, and Ctl-Alt-Del<br>
does not reboot the system. A power cycle is necessary.<br>
<br>
I also attempted a boot from the recovery mode menu item: it hangs the<br>
same way. The same hang happens with a "without AHCI" and with a<br>
"without ACPI" menu item boot choice, and with both legacy boot, and<br>
UEFI boot.<br>
<br>
On the Dell system, I've removed all but the USB drive and one disk:<br>
in the disk bay, I've tried an old Hitachi 5K750-500 500GB SSD, and a<br>
brand new never-written-to Crucial MX500 1 TB SSD.<br>
<br>
I then tried a 5.6.2 ISO image from 1-Jan-2020, and copied it onto a<br>
Kingston USB: same behavior.<br>
<br>
Then I tried last night's *.img file, copying it onto a Crucial USB<br>
with a command like this on another box running Ubuntu 19.10:<br>
<br>
% dd bs=4M if=DragonFly-x86_64-LATEST-IMG.img of=/dev/sdc conv=fdatasync status=progress<br>
<br>
Again I got the same behavior on a boot.<br>
<br>
I then tried the three USB drives on an Intel NUC with a M.2 NVMe<br>
drive, and an old Lenovo all-in-one desktop.<br>
<br>
On the NUC, the *.img file reaches the installer/root prompt, but on<br>
login as root, "camcontrol devlist" shows only the USB drive. I<br>
suspected that the M.2 disk might be a problem, and it is.<br>
<br>
On the Lenovo, "camcontrol devlist" shows the USB drive and the normal<br>
disk, so an install might be possible. I did not do so, because it<br>
already has a working O/S on it that I didn't want to destroy.<br>
<br>
The fact that booting from three different USB drives, three different<br>
DragonFly snapshots in two different formats (*.iso and *.img), and<br>
two different target SSDs, all behave the same way suggests that the<br>
failures are NOT due to boot media errors or installation target media<br>
errors.<br>
<br>
Has any list member seen the hang that I describe, and if so, does<br>
anyone have some idea of how I might reach an DragonFlyBSD installer<br>
prompt on my Dell Precision 7920?<br>
<br>
-------------------------------------------------------------------------------<br>
- Nelson H. F. Beebe Tel: +1 801 581 5254 -<br>
- University of Utah FAX: +1 801 581 4148 -<br>
- Department of Mathematics, 110 LCB Internet e-mail: <a href="mailto:beebe@math.utah.edu" target="_blank" rel="noreferrer">beebe@math.utah.edu</a> -<br>
- 155 S 1400 E RM 233 <a href="mailto:beebe@acm.org" target="_blank" rel="noreferrer">beebe@acm.org</a> <a href="mailto:beebe@computer.org" target="_blank" rel="noreferrer">beebe@computer.org</a> -<br>
- Salt Lake City, UT 84112-0090, USA URL: <a href="http://www.math.utah.edu/~beebe/" rel="noreferrer noreferrer" target="_blank">http://www.math.utah.edu/~beebe/</a> -<br>
-------------------------------------------------------------------------------<br>
</blockquote></div>