John_M

won't work. It would need to be replaced with mkfs.xfs /dev/nvme0n1p3

Your server ran out of memory. How much do you have installed? At what point does it fail? Have you changed anything recently (software or hardware)? Since the root file system resides in memory, maybe something is writing files to the wrong place and filling it up or maybe you have less memory installed or working than you think. Diagnostics would help understand your configuration or, failing that, the full syslog would be better than nothing. I'd start by reseating the DIMMs and running MemTest - check the amount it reports is correct and let it run for 24 hours to see if there are any errors. If the memory passes then try booting into safe mode, which doesn't load any plugins.

It looks like the Dynamix System Temperature plugin (current version is dated 2019-01-12) is replacing the stock version of sensors-detect with its own: Oct 21 19:32:09 Lapulapu root: Verifying package dynamix.system.temp.txz. Oct 21 19:32:09 Lapulapu root: Installing package dynamix.system.temp.txz: Oct 21 19:32:09 Lapulapu root: PACKAGE DESCRIPTION: Oct 21 19:32:09 Lapulapu root: Package dynamix.system.temp.txz installed. Oct 21 19:32:09 Lapulapu root: plugin: skipping: /boot/config/plugins/dynamix.system.temp/sensors-detect already exists Oct 21 19:32:09 Lapulapu root: plugin: creating: /usr/sbin/sensors-detect - copying LOCAL file /boot/config/plugins/dynamix.system.temp/sensors-detect Oct 21 19:32:09 Lapulapu root: plugin: setting: /usr/sbin/sensors-detect - mode to 0755 Oct 21 19:32:09 Lapulapu root: plugin: running: anonymous Oct 21 19:32:09 Lapulapu kernel: it87: Found IT8603E chip at 0x290, revision 1 I'll try safe mode. EDIT: Without the plugin I see a different output from sensors-detect root@Lapulapu:~# sensors-detect # sensors-detect revision $Revision$

There's a file open on Disk1. That's all I can tell from that syslog snippet. Stop all containers and VMs, close terminal sessions, etc, and try again.

Try again later? [Errno -3] Temporary failure in name resolution',)': /simple/requests/

How does one set the serial number of the virtual Macintosh to be one of the invalid ones so there can be no chance of a clash with a real registered Mac?

Is that the first reboot after the installation or have you got past the point where you choose your language, region and set up a user account? If the latter then what customisation have you done to the EFI partition? It might be worth waiting for SpaceInvaderOne to upload his tutorial before proceeding.

Yes.

It will stay there until the Mover moves it. By default the Mover runs once a day, sometime during the night, though you can customise it to whenever and how often you want. If you have only a single cache disk, files stored there don't have the benefit of mirrored protection before being moved to the parity protected array - a slight risk but one you should bear in mind. Some people don't use the cache for its original purpose of caching writes to the server now that "turbo write" is an option. Instead they use the cache exclusively for storing docker containers and VMs. Turbo write is an alternative write method to the parity protected array. The traditional write method is known as "read-modify-write" and its advantage is that only the active data disk and the parity disk(s) need to be spinning - the rest can be spun down. It's disavantage is that it's comparatively slow because it spends a lot of time waiting for the disk platters to complete a full rotation between reading and writing (the modification part is very quick). Turbo write, or "reconstruct write" as it's more correctly known, is faster but its disadvantage is that it needs all array disks to be spinning.

If you have only one cache drive the default is XFS but you can choose BTRFS if you want. If you intend adding one or more drives to you cache pool in the future you might want to choose BTRFS now. At one time, single-disk BTRFS was considered to be less reliable in the event of an unexpected power outage but I don't think that's an issue any more. The checksums allow the Web GUI to offer a scrub option for BTRFS volumes. Advanced users also make use of BTRFS's snapshot facility but at the moment it's only available via the command line. After much experimenting and changing I've settled on using XFS on magnetic disks and BTRFS on SSDs.

As far as containers are concerned it's a shared resource. It isn't the same as passing it through to a VM, where you have to jump through a hoop or two when it's your only GPU.

To be honest, I wouldn't bother trying to upgrade from, say Mojave to Catalina. I'd just create a new clean Catalina VM and transfer my applications to it. FWIW I was able to apply the latest security update to High Sierra. I was dubious that it would work since on my real Macs it involved an update to the firmware too so I took a backup of my vdisk first.

You'll need a Linux driver for the card. There's a special plugin that can provide that by replacing the main Unraid system files on your boot flash. I'm not sure the GTX 1050 does what you want though. I think, though I could be wrong, that at least a 1050Ti is needed by Plex. If I find out more, I'll update. EDIT: According to this, it seems your 1050 is ok: https://developer.nvidia.com/video-encode-decode-gpu-support-matrix EDIT: You'll want to read this thread:

You have ECC RAM, according to your sig. It corrects single errors and the system halts if it detects multiple errors. Have you checked the BIOS event log?

XFS is simpler and more mature. It suits most people's needs. BTRFS is newer and more sophisticated, offering advanced features, like checksums and RAID. The RAID feature is why it's used for cache pools of more than one disk. ReiserFS is obsolete and no longer maintained. As a simple rule of thumb, if you need to ask then your best option is to accept the defaults.

If you want a safe way of accessing your server from outside, scroll to the top of this page and read the section entitled WireGuard support, then follow the link to the guide.

Personally, I'd use something like cp --sparse=always /path/to/original.vdisk /path/to/backup.vdisk which would keep it as small as possible.

Try it and report back with your findings. I'm sure a lot of people will be interested. But back up your vdisk first.

There's still an offending post by @rorton on page 1 that needs redacting. You've already asked him to deal with it but I don't think he was listening.

There's Apple Screen Sharing that's built into macOS. It works well between Macs but I don't know if there's a Windows client.

I'd recommend a Dell PERC H310 from ebay. There are several companies offering them used, pulled from redundant servers for around £25, at which price they are a steal. You'll need to cross-flash it with LSI IT firmware but there are guides and tools for doing that on this site. I also replace the thermal compound under the heatsink as it tends to have dried out.

Looks like file system corruption to me.

Since upgrading to Unraid 6.8-rc series I'm seeing the weekly scheduled integrity check abort with exit status 126: Oct 27 06:00:01 Mandaue crond[1772]: exit status 126 from user root /boot/config/plugins/dynamix.file.integrity/integrity-check.sh &> /dev/null @bonienl Likely a consequence of the permissions change on the boot flash device that now prevents scripts from being executed directly from the flash?

Cool. Thank you so much. That's good to know.

Different driver version.