Bug #3336
closed
CAM probe removes boot device
0%
Description
Attempting to install DragonFly from USB mounted ISO, via an IP-KVM provided by a dedicated server provider. After kernel loads, installer fails looking for rootvp:
CAM: Configuring 8 busses
(probe9:umass-sim1:1:0:0): inquiry data fails comparison at DV1 step
CAM: finished configuring all busses
Device Mapper version 4.16.0 loaded
dm_target_error: Successfully initialized
dm_target_zero: Successfully initialized
(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
...
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
The ISO booted via /dev/cd8, but a CAM probe failed for some reason, which then removed cd8, causing the installation to fail.
Finishing the installation using alternate means, filing this report for future reference, in case there is an easy fix...
Updated by daftaupe almost 2 years ago
- Status changed from New to Feedback
Hi,
do you think it's possible to get some hardware info from your provider ?
Also you mention "from USB mounted ISO", if using USB, you should use the .img file if I remember correctly.
Updated by aswell almost 2 years ago
daftaupe wrote in #note-1:
do you think it's possible to get some hardware info from your provider ?
After installing, I will attach hardware info, for reference.
Also you mention "from USB mounted ISO", if using USB, you should use the .img file if I remember correctly.
The support folks initially mounted an IMG file, however the installer exhibited the same behavior. The kernel booted, and CAM removed the boot device, leaving the installer unable to continue as the boot media disappeared.
This may be difficult to troubleshoot, as the issue may be related to the way the IMG/ISO's are mounted. And, the machine is only accessible via HTML5 KVM and requires manual intervention by data center staff for each reboot.
However, will post hardware info once booted into a working OS, in case there is an obvious solution.
Updated by aswell almost 2 years ago
- Status changed from Feedback to Closed
aswell wrote in #note-2:
This may be difficult to troubleshoot, as the issue may be related to the way the IMG/ISO's are mounted...However, will post hardware info once booted into a working OS, in case there is an obvious solution.
After reading thru some archived mail threads about issues with CAM and booting, it appears resolving this issue without access to the KVM device and machine likely won't be possible.
Therefore, I will close this issue to save everyone time.
Thanks for the followup. Good to see people monitoring these reports...