JWHIII

I rebooted again and it worked this time. Thanks

Is this correct? It seems to cause a no boot on my server. Thanks

Thanks tower-smart-20231004-0718.zip

Hello, I recently updated my server to 6.12.4 and after the reboot I noticed the one of my array disks was disabled. I looked at SMART test and found no errors. Ran a new SMART test and found no errors. Looked at the Disk Log info and found this. Oct 3 20:28:23 Tower kernel: ata6.00: exception Emask 0x0 SAct 0xc00 SErr 0x0 action 0x0 Oct 3 20:28:23 Tower kernel: ata6.00: irq_stat 0x40000008 Oct 3 20:28:23 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Oct 3 20:28:23 Tower kernel: ata6.00: cmd 60/78:50:88:00:00/00:00:00:00:00/40 tag 10 ncq dma 61440 in Oct 3 20:28:23 Tower kernel: ata6.00: status: { DRDY ERR } Oct 3 20:28:23 Tower kernel: ata6.00: error: { UNC } Oct 3 20:28:23 Tower kernel: ata6.00: configured for UDMA/133 Oct 3 20:28:23 Tower kernel: sd 6:0:0:0: [sdg] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Oct 3 20:28:23 Tower kernel: sd 6:0:0:0: [sdg] tag#10 Sense Key : 0x3 [current] Oct 3 20:28:23 Tower kernel: sd 6:0:0:0: [sdg] tag#10 ASC=0x11 ASCQ=0x4 Oct 3 20:28:23 Tower kernel: sd 6:0:0:0: [sdg] tag#10 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 88 00 00 00 78 00 00 Oct 3 20:28:23 Tower kernel: I/O error, dev sdg, sector 216 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Oct 3 20:28:23 Tower kernel: ata6: EH complete Found the "Repairing a File System" section of the user manual. Disk is mountable. Parity is good. Put the array in maintenance mode and ran XFS check filesystem. Here is the output. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done Finally, here are diagnostic files Thanks for any help tower-diagnostics-20231003-2128.zip

I have two disk shares that are accessed by two devices using NFS. The spamming is so bad I can't see anything else in my logs. Is there still no fix for this?

The bios says it is enabled. My guess is a broken bios...

After some investigating, I have found that if I boot UEFI and no Gui all works. If I boot UEFI and GUI, it will boot and be operating but the GUI never loads, just a blinking cursor. So, I have been able to boot in UEFI and have the settings for VT-x and VT-d enabled in the bios, but still no IOMMU to pass through my 2 NICs. tower-diagnostics-20210412-1355.zip

unRAID 6.9.2 HP H8-1260t, i7-2600, 16GB ram, 1TB nvme ssd, 1x 6TB Ironwolf, 1x 4TB Ironwolf, 1 PNY 32GB USB Flash, 1x PCIe x16 dual NVME adapter, 2x PCIex1 Ethernet NIC, 1x PCIe x1 SATAIII adapter First bootup with unRAID worked, checked the box to allow UEFI boot, updated from 6.9 to 6.9.2, rebooted machine and it froze shortly after I saw "haveged starting up". Froze = blank screen with blinking cursor. If I disable UEFI boot in the BIOS or re-insert the ~ next to the EFI folder on the flash drive, the machine boots and I am able to setup my array. Not sure if I need to be running with a UEFI boot or not. I have set up a VM and am trying to get access to my 2x PCIe NICs from inside the VM with no luck. When setting up the VM, passing the NICs through is not an available option. I have bonding switched off on all 3 NICs and bridging on for each. br0 to eth0, br1 to eth1, and br2 to eth2. I have br1 and br2 set in my VM settings and can see two NICs inside my VM but they seem to be bonded together and to whatever br# is set as default in VM Manager. The VM client is Untangle 16.2 which is Debian based, if that matters. tower-diagnostics-20210410-1533.zip

Thanks for the reply ChewyBeaver. I have been using Untangle for 12+ years, but I have never set it up as a virtual machine. This will also be my first Unraid setup. I expect there will be a steep learning curve. lol.. Did you use the standard install iso from Untangle or the VM image?

I'm wanting to set up a server with Unraid to run an Untangle firewall/router and NAS. The topics that I have found in the forum are all about problems with Untangle setup. My question is, has anyone set a Untangle firewall inside Unraid that has it working?