Unable to install on Proxmox VE VirtIO SCSI drive

[markshank]

Getting Started documentation page specifies VirtIO SCSI controller. A drive attached to SCSI will appear in the FreeBSD Installer drive selection list, but that drive cannot be selected.

Workaround by attaching virtual disk to SATA instead of SCSI.

[probonopd]

We disabled installing to /dev/da* disks due to https://github.com/helloSystem/ISO/issues/200:

https://github.com/helloSystem/Utilities/blob/dc94c2fc45c785e691e2ea1fb82cb450b5f7d229/Utilities/Install%20FreeBSD.app/Resources/freebsd-install.py#L741-L744

Any hints on why https://github.com/helloSystem/ISO/issues/200 happens and how it can be resolved properly would be highly welcome.

For the meantime, I have changed the documentation. Thanks!

[markshank]

Any hints on why helloSystem/ISO#200 happens and how it can be resolved properly would be highly welcome.

I did read through that entire issue and I don't have anything I can contribute other than I did experience an issue with Airyx that seems to have been mentioned in your issue. There was a umount issue when using OVMF.

[probonopd]

@mszoek do you think the umount issue when using OVMF is related to the message 'kern.geom.part.mbr.enforce_chs: 0 -> 0'?

[mszoek]

I assumed it might be related to my unionfs changes but I haven't had time to look into it yet.

[ragazenta]

Weird, somehow I could install 0.5.0 on Virtio SCSI by editing the installer https://github.com/helloSystem/ISO/issues/260.

~But now, I can't install 0.6.0.~

Edit: I can install 0.6.0. I need to recreate new empty SCSI disk. If I install on previous existing disk, the installer stalls.

[probonopd]

With kern.geom.part.mbr.enforce_chs: 0 -> 0 in the Installer Log?

[ragazenta]

With kern.geom.part.mbr.enforce_chs: 0 -> 0 in the Installer Log?

Yes.

[probonopd]

We need to find out what produces this error. I have no clue honestly.