inc0gnit0

Okay, I think that from searching as to what "ahci_device_limit" does, it limits the number of devices per controller. So I guess this is what I would need to do - get this parameter set somehow to 1, and there will be 3 controllers, 1 for each drive apparently.

@pocopico Thank you for replying and thank you for building TCRP! With the way it's set up in TrueNAS, I don't see how in the bhyve environment I can designate the boot drive img to be on a different SATA controller from a virtual perspective. The only way I could think about would be to install the boot drive img on a physical USB and do a passthrough to the VM, that would likely put the boot image on a different controller. I will give that a try, but that isn't an ideal long-term solution. There is a guide - https://xpenology.com/forum/topic/69420-tutorial-install-dsm-72-on-vm-bhyve-freebsd/ - where it appears that the author is successful. However I don't see how he's designated the boot image to be on a separate controller, even though he's editing the configuration files directly and I'm attempting this through the TrueNAS GUI. ahci_device_limit="1" disk0_type="ahci-hd" disk0_name="tinycore-redpill-uefi.v0.9.4.9.img" disk1_type="ahci-hd" disk1_name="disk0.img" disk1_opts="sectorsize=4096/4096" disk1_size="10T" Wondering if anyone else has any documented successes with this setup.

Hi guys, i'm trying to install tcrp on TrueNas Core 13.0-U5.3 (bhyve). I'm able to get the installation through with this configuration : TCRP Image (RAW) (sda) Storage #1 (DISK) (sdb) Storage #2 (DISK) (sdc) However, this is how it's presented when trying to set up the satamap : tc@box: $ ./rploader.sh satamap now Machine is VIRTUAL Hypervisor= Found "00:02.0 Intel Corporation 82801HR/HO/HH (ICH8R/DO/DH) 6 port SATA Controller [AHCI mode]" Detected 6 ports/0 drives. Bad ports: -5 -4 -3 -2 -1 0. Override # of ports or ENTER to accept <6> ◊ Found "00:03.0 Intel Corporation 82801HR/HO/HH (ICHBR/DO/DH) 6 port SATA Controller [AHCI mode]" Detected 32 ports/3 drives. Bad ports: 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32. Mapping SATABOOT drive after maxdisks WARNING: Other drives are connected that will not be accessible! Computed settings: SataPortMap=11 DiskIdxMap=0010 WARNING: Bad ports are mapped. The DSM installation will fail! Should i update the user_config.json with these values ? [Yy/Nn] So it appears that two SATA Controllers are detected, with the first not holding any drives, and second holding the three drives (TCRP, Storage #1, Storage #2). The "SATABOOT drive after maxdisks" issue seems to be the pain point, and the other drives indeed are unaccessible (synology loader indicates no drives are found). What should I change with the setup or how should I configure the SataPortMap/DiskIdxMap in this configuration? Do I need to find a way to blacklist/unload the SATA Controller at 00:02.0? Any pointers would be much appreciated!