Recent content by GalacticSpines

I tried both and neither worked, but I actually came across this post and thought I would give it a try. mkfs.ext4 /dev/sdj wipefs -a /dev/sdj It worked on the first try and I was able to create a new zfs pool without any errors.

I need some help with the following issue. I'm running FreeNAS VM on my Proxmox setup and used this command to pass-through two hdd's to the FreeNAS VM: qm set 100 -scsi3 /dev/disk/by-id/ata-ST3000DM007-1WY10G_xxxxxx qm set 100 -scsi4 /dev/disk/by-id/ata-ST3000DM007-1WY10G_xxxxxx Long...

Sorted, the issue was setting the boot order on the HBA SAS controller itself to OS.

I have a new Proxmox bare metal server running and installed FreeNAS on it. It works 100%, but when I do pci passthrough of my HBA I get a boot error from FreeNAS. It almost seems that it wants to boot from another drive and not the initial one it was installed on. I've attached two...

Got it sorted. Thanks!

Hope someone might have a solution to this. I'm trying to install Freenas on a brand new baremetal Proxmox 6.2-4 server. Freenas version FreeNAS-11.3-U3.1. So I have no issues setting up vm and running the installation of Freenas, it's when the installation is finished and reboots it just...

I've found the problem, I didn't change my initial DNS from the installation to pfSense (10.10.0.1). Don't know why I missed such a simple thing...

Did anyone come up with a solution? I have the same issue. pfSense VM running everything 100% on lan and wan side, but Proxmox has no internet connectivity though gateway and ip setup correctly.