Install 2.3.1 hangs - UHUB0 usbus0
-
Trying to install the latest 2.3.1 onto an older HP DL360 but it keeps hanging at a line which mentions
UHUB0 root HUB usbus0
Sorry I can't be more specific, it's hard to get the error.
Might anyone have some thoughts? I've tried disabling ACPI but not sure what else to try.
-
same problem here, trying to install on my remote datacenter
on vmware esxi 6.0 and hyper-v 2012 R1 works fine
-
In my case, I've no need for anything special, no serial ports, no USB, nothing but the machine and its two NICs.
-
anyone?
@mprog, how did you disable ACPI ?
-
Disabling ACPI is no longer valid advice unless we're talking about hardware from '90s or very early 2000s. Modern hardware needs ACPI and performs very badly with ACPI disabled.
-
A quick Google search found this:
https://forums.freebsd.org/threads/45026/I have a tip that should allow gathering more info:
-
Boot the system
-
Press ESC while on "Welcome to pfSense" boot screen
-
Type "boot -v" and hit ENTER
– See attached picture --
When it hangs, take a screenshot (if you can) and post it.
Regards,
Jorge M. Oliveira
-
-
I´ve taken a photo from the console
here it is… hangs on this last line (first reboot after a fresh install)
-
Now try booting the system with the following commands:
set hint.ata.0.disabled=1 set hint.ata.1.disabled=1 boot -v
Then add to /boot/device.hints:
hint.ata.0.disabled="1" hint.ata.1.disabled="1"
Hopefully, it does work now.
(In addition to the link on my previous post, also found that at:
https://superuser.com/questions/1055316/why-does-disabling-ata-fixes-run-interrupt-driven-hooks-still-waiting-after-60) -
The server I've been using for the longest time is an HP DL360 dual XEON, 4GB machine. Mainly because I have a stack of them left over from projects long ago. these are era 2008 or so.
Anyhow, I've tried your suggestion but for what ever reason, I can't get to the prompt to enter the commands and had to give up. I'm back to 2.0 release at this point and will install onto a newer server then migrate from the HP to the new one.
Thanks for all the help.
-
Now try booting the system with the following commands:
set hint.ata.0.disabled=1 set hint.ata.1.disabled=1 boot -v
Then add to /boot/device.hints:
hint.ata.0.disabled="1" hint.ata.1.disabled="1"
Hopefully, it does work now.
(In addition to the link on my previous post, also found that at:
https://superuser.com/questions/1055316/why-does-disabling-ata-fixes-run-interrupt-driven-hooks-still-waiting-after-60)didn't work for me… but thanks anyway.
confirmed with my datacenter support, they are running QEMU with IP KVM for managing console through user portal