coffeeroasted

Currently running Ryzen 3600 Zen 2 CPU. Upgraded to latest 6.9.0 beta version. When attempting to open a Windows 10 VM, I get an immediate BSOD with KERNEL_SECURITY_CHECK_FAILURE error. Windows tries to fix the error and continuously loops into the same BSOD. After doing some research, it seems that QEMU 5 / kernel above 5.4 does not work well with Zen 2 CPU. In order to bypass this, I had to edit the XML. I changed the cpu mode from host-passthrough to host-model. I also had to change cache mode from passthrough to disable. After I saved my changes, unRaid ended up making some changes to the XML, where the cpu mode then changed to custom. Everything seems to be working now, but I don't know if the changes I made will cause issues down the road. I just wanted to throw out a fix that seems to allow me to keep running Windows 10. If anyone is familiar with LibVirt and cpu/cache modes, could you tell me if doing this will cause any issues?

It should be active immediately. You have to make sure the share is loaded in macOS. It can't just be the server loaded, the individual folder has to be mapped. Actually, now that I'm testing a couple things to answer your questions, I realize that's all that needs to be done. The .cfg file doesn't need to be modified. What has to be done is the folder HAS to be mounted, not just the server. I tested this by creating a new time machine share, mounted it, and was able to see it in Time Machine. I didn't have to change the .cfg file at all.

That's strange. Mine have survived reboots and I didn't change anything from what I posted. I was under the impression that anything listed under /boot should survive reboots unless something changes it once it loads into RAM. Do you have any scripts running that may change your share .cfg files after boot? The only other thing that I could see affect it is if you make changes in the share GUI, as most changes made to the file are overwritten if an update is done in the GUI.

I was just referring to the issues people were mentioning re: Catalina. I don't know if it's specific to it or if the issue is in an unRaid update. I thought people were having able to get it to work on earlier OSs, but looking back in this thread, I don't think that's the case. I think it may just be an issue with unRaid's setup. All I know is that changing 'shareFruit' to yes fixes my issue, at least with backup. I haven't tried restoring at all.

Thanks, again. Everything seems to be working swimmingly now. I've had a couple crashes since making this change, but it had to do with an HDD issue. Is there a way to tag this as solved or do I just edit the title? Or don't worry about it?

This is the link I used to debug my share: Using Linux or Windows as a Time Machine network server. The things he points out that are required to enable Time Machine support were: The fruit module, which provides Apple’s proprietary extensions to SMB, The catia module, which maps the encoding of filenames that macOS expects to a form most native Linux filesystems can support, The streams_xattr module, which maps macOS’s extended attributes to a separate AppleDouble file, Optionally, the spotlight module, which builds a Spotlight search index on the server to speed up discovery of files in the backup, and Avahi, a multicast (aka Bonjour) daemon for Linux, used here to allow Macs on the network to discover the Time Machine share. I assume unRaid enables Avahi when macOS interoperability is enabled and I don't see anything in the config files supporting catia, streams_xattr, or spotlight, but it seems to work great between Avahi and the fruit module.

This is the link I used to debug my share: Using Linux or Windows as a Time Machine network server. The things he points out that are required to enable Time Machine support were: The fruit module, which provides Apple’s proprietary extensions to SMB, The catia module, which maps the encoding of filenames that macOS expects to a form most native Linux filesystems can support, The streams_xattr module, which maps macOS’s extended attributes to a separate AppleDouble file, Optionally, the spotlight module, which builds a Spotlight search index on the server to speed up discovery of files in the backup, and Avahi, a multicast (aka Bonjour) daemon for Linux, used here to allow Macs on the network to discover the Time Machine share. I assume unRaid enables Avahi when macOS interoperability is enabled and I don't see anything in the config files supporting catia, streams_xattr, or spotlight, but it seems to work great between Avahi and the fruit module.

That's why I went ahead and just ordered a 3600. The RAM I ordered was supposed to be 2933 at 1.2V, but what was sent was OC'd at 2933, which caused me issues. I'd like the ability to utilize my system to it's max capacity, plus the 3600 gives me a couple more cores to utilize for VMs.

I'm in just about the same boat as you. I'm running a Zen+ APU and was having the same issue. I've got a 3600 on order that should be here next week. I can report back and let you know. I may be wrong (hopefully not), but I'd expect the 1700x wouldn't have issue with RAM as spec'd, since I suspect the issue is with the increased voltage for overclocking.

Ben, I could be way off track, as I'm fairly new here, but the first thing I'd check is the syslog under /var/log. You'll want to look for the drives to show up during the boot process. If you don't see it, I'd suspect something's not being passed correctly when unRaid is booting. Something you could try is re-flash the HBA but without the ROM. Since you don't need the HBA to manage your devices, you may be able to see them passed through that way. I just flashed a 9217 to HBA and left out the ROM and my devices showed up instantly. The downside is they won't show in UEFI/BIOS, but I have no need to boot from my HDDs so no big deal. Finally, does the mobo have at least one SATA port? I don't know anything about the hardware you mentioned, so I'm just taking a stab in the dark. If you've got a SATA port, I'd ensure that a drive can be recognized that way. Good luck!

Hey, y'all. The issue with creating a Time Machine share with Catalina is due to a misconfigured setting in the share's .cfg file. For an SMB .cfg, Apple expects a setting to be passed called 'shareFruit'. For whatever reason, even when following @SpaceInvaderOne's video setup, the .cfg file passes a 'no' for that setting. Once you change the setting to yes, you'll be able to see it in Time Machine. The file is located at /boot/config/shares/***.cfg (*** being the name of your Time Machine share). I've reported the issue last week. It may be helpful for some people to comment on the bug report stating whether the change worked: https://forums.unraid.net/bug-reports/stable-releases/683-time-machine-share-r930/

Awesome, thanks so much! I've been banging my head against the wall trying to figure this out. I had seen the P-State issue listed, but saw it was only an issue pre-6.8 and also not really a problem with Zen+ or higher. Didn't catch the note about OC. Gonna have to take a look at my setup now. Gigabyte's QVL for this CPU listed my setup as supported up to 2933 MHz, but it seems I was sent DR RAM even though I ordered SR (based on part number). I've returned the RAM speed back to stock @ 1.2v and will report in a couple days.

I'm at my wit's end. I've been running unRaid for approximately 2 weeks now and I can't figure out why my system keeps freezing and/or crashing. I just finished a new build and am using all new parts with the exception of my HDDs and an SSD. For the first few days, I had no issues. Starting off slow, I added a couple plugins, created a Windows 10 VM, and figured out how to pass through a USB device. Then I replaced the 500 GB NVME drive I had available with a WD Black 1 TB NVME drive. From that point, it started freezing up. I'd see two different screens (see images at bottom). I started a syslog server and have scoured the log every time it crashes and I can't see anything that indicates why the system crashes. Whenever it freezes/crashes, the GUI is unavailable, I can't ssh into the computer, and it has to be hard shutdown. There doesn't seem to be any specific task that causes this issue. It's frozen/crashed in the middle of pre-clear, loading a plug-in, accessing an SMB share from my laptop, etc. --EDIT: I'm on my 3rd clean install of unRaid 6.8.3, and my second USB device. Both flash drives were brand new Sandisk Ultra USB 3.1 devices. This issue happens regardless of completely clean install or if I'm running plugins. I've tried different data drives as well. I thought maybe there was something wrong with the NVME drive I used, so I swapped the old one back in. It ran for an entire day, even allowing a full pre-clear (although the drive failed post-read). It's still doing the same thing. I ran a Memtest for 36 hours with 0 faults. At this point, I'm thinking it's MB, CPU, or PSU. I don't see any signs of PSU problems, though. Here's what I'm currently running: AMD Ryzen 5 Pro 3400GE Gigabyte B450 AORUS M mobo (BIOS on most recent update) 32GB HyperX Black DDR4 3200MHz SilverStone Tek 550W 80 Plus Gold PSU Syslog is attached. Something weird to point out: time shifts by 4 hours sometimes in the log - I'll set my BIOS time to the correct time locally, but syslog shows it 4 hours early until ntpd resolves. Then after a while, the time in my BIOS is set to 4 hours later than local time. The sylog is quite long, I've been running it since Sunday. I'm open to any recommendations. Thanks in advance! syslog_2May_0958.log