pdf guide for newbies on how to setup FreeNAS and not make stupid storage decisions. In the end I would like to setup FreeNAS to serve media files and provide a backup storage location for photos and the like.īefore I got too far into the project I read the great post by on “ how not to lose your data” when running FreeNAS in a virtualized environment along with the complete.
I will also use a VM as an NVR with the intention of FreeNAS providing the storage for video recordings. FreeNAS boots as it should running as a VM. I have successfully deployed a VM’s with data stores located on the SSD along with one for FreeNAS. I have installed ESXi 6.5 on the SSD and it boots and functions as it should. That being said this is my fist go at both vitalization and FreeNAS.Īs I mentioned I have a SuperMicro X8DTU-F Server with the following hardware: ( )Ģ x 4TB Ironwolf HDD (Installed in Server Drive Bays attached to the onboard Intel ICH10 Controller)ġ20 GB Intel SSD Boot Drive (Installed on a separate PCI Card: ) I’m not an IT guy by trade but consider myself an enthusiast with a reasonable bit of experience. I bought an old SuperMicro 1U server to play with intending to setup a small home virtualization lab. Before I go any further I would like to provide a little background on what I have and have done up to this point. I’m having an issue passing through my onboard SATA controlled from ESXi 6.5 to a FreeNAS VM and was hoping I might get a little help.
#Asm1062 serial ata controller driver driver
vmkdevmgr: Found driver vmw_ahci for device bus=pci addr=p0000:07:00.0 id=1b21061218490612010601.Hello all, I’m new here and I’ve run into a roadblock. vmkdevmgr: Error loading driver vmw_ahci: Unable to load module /usr/lib/vmware/vmkmod/vmw_ahci: Failure In the vmkdevmgr-logs, I've found these entries: Module vmw_ahci loaded esxcli system module list |grep ahciĪ reboot results in the same situation, no driver loaded, and therefor storage device not detected and disks not visible. I noticed the vmw_ahci driver is not loaded during boot, even after re-enabling this with the esxcli system module. When logging into via GUI (webinterface), I see the numbers next to 'Virtual Machines' and 'Networking' are correct, however the number next to 'Storage' is 0. ASM1062 Serial ATA Controller esxicli storage filesystem list The Intel sata controller has 2 SSD's connected, containing the ESXI files/system and VM's, where the ASmedia controller has 2 HDD's connected as phyiscal disk to my NAS-VM (by virtualized LUN or something like that -> not a vmware specialist).Īs explained in troubleshooting an issue with one of the HDD's, I decided to disable the vmw_ahci driver which resulted the current esxcli storage core path esxcli storage core device lspci -vvv |grep vmhbaĠ000:07:00.0 Mass storage controller SATA controller: ASMedia Technology Inc. FYI: this server was running fine for 2 years with the following storage config (using the vmw_ahci lspci -vvv |grep hbaĠ000:00:12.0 Mass storage controller SATA controller: Intel Corporation Device 31e3 Ġ000:07:00.0 Mass storage controller SATA controller: ASMedia Technology Inc. Anyhow after disabling the vmw_ahci driver, my esxi-server does not recognize the storage devices anymore, and therefor does not see/mount any of the disks anymore. A potential solution for my issue was disabling the vmw_ahci driver, resulting in the sata_ahci driver being used after a reboot. I've succeeded to 'bring down' my ESXI server when troubleshooting issues with 1 SATA HD.
0 kommentar(er)
