gigem2

Okay. A reboot brought disk 5 back. Thanks for the assistance.

Sorry for the delay, and thanks for the help. humptower-diagnostics-20180702-1420.zip

I'm new to the troubleshooting unRaid thing. I downloaded the diagnostics. Which portion would you like to see?

So, long story as to the circumstances, but here's the nitty gritty: Stuck away from the server with work. I connected tot he server using FTP and was cleaning out the shares, deleting old stuff, keeping some of it locally, etc. On the device page, the parity drive had a red 'x' and said failed. I wasn't thinking and stopped the array in order to restart it and rebuild parity. I didn't realize it was telling me the drive had failed. After the array was stopped, one of the data drives now says it's not available. Can I regain access to this data without having physical access?

So why does IOMMU show as enabled when I use 6.1.9, but not 6.2?

According to the manual, I have 6 ports on an Intel® ICH10R, and 2 ports each on 2 JMB322 multipliers coming from a Gigabyte SATA2 controller. I also disabled the secondary controller in BIOS and still had no luck.

I'm trying to create a VM on unRAID 6.1.9 with the following hardware: Gigabyte GA-EX58-UD5 using a bios version someone else received from Gigabyte to add a menu to enable VT-d i7-920 6 GB Ram XFX R5-220 in X16_1 Gigabyte GV-R478D5-1GD in X16_2 Intel 530 SSD and a host of other HDDs I've tried creating a VM with Windows 7 and Windows Home Server 2011, both have the same result: VM creation error internal error: early end of file from monitor: possible problem: 2016-03-28T01:32:33.522200Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted 2016-03-28T01:32:33.522231Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 17 2016-03-28T01:32:33.522240Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 17 2016-03-28T01:32:33.522252Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2016-03-28T01:32:33.522264Z qemu-system-x86_64: -device vfio-pci,host=03:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized I can only assume it's a GPU passthrough issue. I'm trying to pass the 4870 through, but I've tried to pass the R5 as well, with the same result.

Trying to set up unRAID 6.2 on the following hardware: Gigabyte GA-EX58-UD5 using a bios version someone else received from Gigabyte to add a menu to enable VT-d i7-920 6 GB Ram XFX R5-220 in X16_1 Gigabyte GV-R478D5-1GD in X16_2 Intel 530 SSD and a host of other HDDs If I leave VT-d disabled, unRAID will load. If I enable VT-d, unRAID stops with this on screen: Unpacking initramfs... Freeing initrd memory: 129500K (ffff880078189000 - FFFF880080000000) DMAR: Host address width 36 DMAR: DRHD base: 0x000000fe711000 flags: 0x0 DMAR: dmar0: reg_base_addr fe711000 ver 1:0 cap c9008010e60262 ecap f0207a DMAR: DRHD base: 0x000000fe710000 flags: 0x1 DMAR: dmar0: reg_base_addr fe710000 ver 1:0 cap c90780106f0462 ecap f020fe DMAR: RMRR base: 0x000000cfef0000 end: 0x000000cfefffff DMAR: No ATSR found DMAR: dmar0: Using Queued invalidation and it stops here. I have been able to run 6.1.9 successfully, but am having issues with VMs, but that's for another post.