John_M

No errors so far, which is good. I'd let it run for 24 hours or more.

The LSI SAS card is on its own in group 15.

That's a symptom of UEFI booting. You need to legacy boot to be able to select MemTest86+ from the boot menu.

Is it a vdisk? You can increase the size of a vdisk simply by stopping the VM and increasing the allocation to the vdisk in the template editor. You'll need to use the Storage Manager in Windows to make use of the newly available space. Or are you talking about adjusting the boundaries of the three partitions in the original post? That will need a partition editor and it's a dangerous process as it's very easy to lose data or make a bootable partition unbootable. The safest approach is to backup the contents of all active partitions, repartition from scratch and then restore the contents. Even that approach isn't foolproof.

A PFSense configuration issue was responsible for causing @Rhysee's problem with updating the OS. The Array Stopped * Starting services message is cosmetic but seems to be caused by a plugin incompatibility and is unrelated to PFSense.

Have you tried using NFS instead of SMB with Linux clients?

The safest thing to do is set the share to Cache:Prefer and then run the mover. That will move any files belonging to that share onto the cache. You can then set it back to Cache:Only if you want.

Did you actually run the MemTest, as suggested?

Make a backup copy of the config folder on the flash device. Re-install Unraid, then replace the config folder with the one you backed up. The diagnostics you posted cover a period of less than ten minutes since you booted the system. In Settings -> Syslog Server try turning on the option "Mirror syslog to flash" so that the next time it crashes the log won't be lost.

Yes, you would. Make a USB key and sign up for a month's free trial and see if one of them will boot - you'll need to set up the USB for UEFI boot mode. The trouble with old Mac Pros is that they only officially support four hard disks, though you could probably fit two more in the optical drive bays. So they are rather bulky for the storage capacity they offer. Incidentally, Unraid boots from a USB flash device and runs entirely in RAM so all drive bays are available for storage. Give it a try and see how you get on. I'm in a similar position with my MacBook Pro that can't be updated beyond High Sierra. To be honest, Mojave and Catalina don't offer anything I need - the changes are superficial and simply make macOS even more like iOS. I'm OK with High Sierra while Apple keeps supplying security updates - so, maybe another year to go? Trouble is Apple doesn't make anything that would even come close to replacing what I've been using for almost 10 years. I've got 2 TB (HDD) + 250 GB (SSD) of internal storage configured as a fusion drive, a battery I can replace (I'm on my third, and my second cooling fan) and RAM I can upgrade (done that too), with a real gigabit Ethernet port and a MagSafe charging port. There's no Retina display or USB 3 but I have a mini Display Port and FireWire 800!

OK. That would not have been apparent from the diagnostics. It might help someone else in a similar situation though. That seems to be an issue that a number of people have reported. It might be an unwanted interaction with a plugin. I haven't seen it myself. There's a discussion about -rc5 here, if you want to follow it:

Why do you suppose this is specifically an -rc5 issue? If you messed up and want help a better place would be in the general help forum.

It's never wise to overclock a server.

I don't see anything wrong. You could upgrade manually. Get the zip file from https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.8.0-rc5-x86_64.zip and unzip it. You'll need to shut down your server can transfer the USB flash to a PC. I'd check the device for filesystem errors first (their presence could explain the failure to update via the GUI), then copy all the newly unzipped files that begin with "bz" into the root of your USB flash, replacing the existing files of the same name. Wait for it to finish, then eject the flash. Then use it to boot your server.

The first step is to determine which container is the culprit. That's simply a process of elimination.

The most recent diagnostics don't have the "conflicting memory types" errors but it has segfaults. A Segmentation Fault is an access violation, i.e. an attempt to access an area of memory in an illegal way, such as trying to write to read-only memory or trying to read memory that belongs to another process. It could be a programming bug or I suppose some table of pointers could be getting corrupted, or a hardware problem. Since your other errors are memory related I'd ask about your RAM. Have you run a MemTest on it? Are you operating it within spec?

There are several call traces early on in the start-up sequence: Nov 4 17:05:28 Genie kernel: Your BIOS is broken; DMA routed to ISOCH DMAR unit but no TLB space. Nov 4 17:05:28 Genie kernel: BIOS vendor: American Megatrends Inc.; Ver: 0603 ; Product Version: System Version Nov 4 17:05:28 Genie kernel: WARNING: CPU: 3 PID: 1 at drivers/iommu/intel-iommu.c:5491 intel_iommu_init+0xa8b/0x10d8 Nov 4 17:05:28 Genie kernel: Modules linked in: Nov 4 17:05:28 Genie kernel: CPU: 3 PID: 1 Comm: swapper/0 Tainted: G I 4.19.56-Unraid #1 Nov 4 17:05:28 Genie kernel: Hardware name: System manufacturer System Product Name/P6T, BIOS 0603 05/19/2009 You're running a 10 year old BIOS, which is broken. Is there anything newer available?

Is the server's system clock reasonably accurately set? Your diagnostics might shed some light.

Doesn't the Private share type fit your needs? Set up three users, Alice, Bob and Carol. Set up three shares Share_A, Share_B, Share_C. Make them all Private and add access as required. So for your stated purpose only give Alice read/write access to Share_A, only give Bob read/write access to Share_B, etc. I don't understand the purpose of the Windows file server VM since Unraid it itself a file server.

FWIW, your latest syslog doesn't have any of this Nov 4 14:32:07 9900K kernel: x86/PAT: CPU 3/KVM:5062 conflicting memory types a2000000-a3000000 uncached-minus<->write-combining Nov 4 14:32:07 9900K kernel: x86/PAT: reserve_memtype failed [mem 0xa2000000-0xa2ffffff], track uncached-minus, req uncached-minus Nov 4 14:32:07 9900K kernel: ioremap reserve_memtype failed -16 which flooded your previous one, but it still conatins segfaults: Nov 4 14:51:02 9900K kernel: ffdetect[25520]: segfault at 38 ip 00000000004042af sp 00007ffdde2eeda0 error 4 in ffdetect[403000+c000] Nov 4 14:51:02 9900K kernel: Code: 0f b6 6d 00 40 84 ed 75 b7 48 8b 14 24 48 8d 35 ce ad 00 00 bf 01 00 00 00 31 c0 ff 15 92 59 01 00 48 89 df ff 15 c1 5a 01 00 <41> 0f b6 2c 24 40 84 ed 0f 84 9a 00 00 00 4c 8d 35 2c b1 00 00 eb Did you ever boot into safe mode?

Tools -> Diagnostics. Post the resulting zip file.

Not according to your diagnostics. Bonding is not enabled and only eth0 has a working cable plugged in. It has a static IP address of 192.168.1.3/25. [BONDING] => no ... [BRIDGING] => yes [BRNAME] => br0 [BRNICS] => eth0 ... [PROTOCOL:0] => ipv4 [USE_DHCP:0] => no [IPADDR:0] => 192.168.1.3 [NETMASK:0] => 255.255.255.128 [GATEWAY:0] => 192.168.1.1 Settings for eth0: ... Link detected: yes Settings for eth1: ... Link detected: no From your description this doesn't seem to be how you expect it to be configured. From your syslog there's clearly a discrepancy with the netmask (/24 vs /25): Nov 3 12:54:19 Thanos-Server rc.inet1: ip -4 addr add 192.168.1.3/255.255.255.0 dev br0 Nov 3 13:00:41 Thanos-Server rc.inet1: ip -4 addr add 192.168.1.3/255.255.255.128 dev br0 So take a close look at your Network configuration (Settings -> Network Settings) and check your router's configuration too, to resolve the discrepancy. Personally, I'd let the DHCP server take charge of allocating IP addresses, reserving fixed addresses for given MAC addresses, as required.

The best place to start would be to post your diagnostics. In the Web GUI go to Tools -> Diagnostics and attach the resulting zip file to your next post.

Where did it break? It would be interesting to see a photo. Can you grab a part of it with needle nose pliers or strong tweezers?