IP-KVM console

Seann Aswell seann at seannaswell.com
Sat Jan 14 21:29:31 PST 2023

Okay, the issue is likely a bit more complicated. Scrolling up in the 
IP-KVM terminal window, I see the following:

(cd8:umass-sim1:1:0:0): got CAM status 0x44
(cd8:umass-sim1:1:0:0): fatal error, failed to attach to device
(cd8:umass-sim1:1:0:0): lost device
(cd8:umass-sim1:1:0:0): removing device entry

I can say that a FreeBSD ISO does boot on this same machine using the 
same IP-KVM/IPMI setup this data center uses. Normally a USB stick using 
an IMG file would be used, which would avoid this altogether...

I could always install some other OS on the second drive and hack 
together a work around, but I have KVM access for 48 hours, so if anyone 
has any other suggestions, please let me know.

On 1/14/23 21:27, Seann Aswell wrote:
> While attempting to setup DragonFly with a dedicated server provider via 
> an IP-KVM, the installer is unable to find the rootvp. They have mounted 
> an ISO and booted the machine, and this is what I see:
> iso_mountroot: can't find rootvp
> Root mount failed: 6
> Mounting root from cd9660:cd8
> no disk named 'cd8'
> Mounting root from cd9660:cd9
> no disc named 'cd9'
> Mounting root from cd9660:/dev/cd0
> no disk named 'cd0'
> Manual root filesystem specification:
> <fstype>:<device> Specify root (e.g. ufs:da0s1a)
> ?     List valid disk boot devices
> When issuing "?" the installer sees the empty hard drives, a few md 
> devices which I believe are the installer (md0, md0s0), vn 0-3 and sg0, 
> sg1 and sg8. None of those appear to be valid.
> I have seen this at some point years ago on a local machine and was able 
> to work around it, but am not sure how to resolve in this case. 
> Obviously the installer saw the boot device to get to this point.
> Any other commands that could shed some light on the situation?

More information about the Users mailing list