cybrnook

What is AutoBackupVM? I use my own script to backup VM's. Seems the script is exiting with status 2, so something is not happy. When you run it by hand, after it completes what does "echo $?" return

I have a cron I run in Ubuntu that is for the first Saturday of every month. My syntax is: 0 0 * * 6 [ $(date +\%d) -le 07 ] && /script/path/follows/here.sh

New BIOS (1.70) posted as of today: https://www.asrockrack.com/general/productdetail.asp?Model=X399D8A-2T#Download @deadmeatgames sounds like memory would be my first spot to check.

@ich777 Hope all is well! Noticing a small wrinkle on boot with the latest version from today. On boot, I am watching the boot log, and just prior to SMB starting and all at the very end of the boot process, when the system is installing all the addon packages, I am noticing that this new version is showing some error/warnings: /bin/bash: line 285: check_package: command not found /bin/bash: line 286: install_package: command not found Then the system goes on to say that it's subbing /bin/bash with /bin/sh Took me a little while to figure it out, but I rolled back the Nvidia plugin to the previous version and rebooted, and these messages went away.

https://1drv.ms/u/s!AlHg8pmWgJJ_gr9mLid6muLTIMOddA?e=KbfHe2

They are grouped, yes, but options other than "Auto" let you specify what each slot is at. For example, for PCIE2/3 here I can set it to x8 x8 or x8 and then x4x4, or x4x4 and x8, for example. Before you could only choose x8x8 or x4x4x4x4 and that would be assigned to both slots. I hope that makes sense. Anyways, looks fine and good luck, enjoy the board.

Bifurcation was supported in BIOSes already prior to 1.37. What 1.37 gave me, and is what I asked for, is PER SLOT bifurcation options. Prior to 1.37 bifurcation worked in groupings.

https://1drv.ms/u/s!AlHg8pmWgJJ_gr9mLid6muLTIMOddA?e=KbfHe2

You right you right 🙂

Wouldn't your cron schedule go like this? : 0 4 * * 3

I see, so you're going folder by folder based on the old package and then copying the "new" files and replacing, then re-tarring?

Thanks for this, I followed on a Ubuntu VM, but can't seem to find where the output *.txz package is written to?

There are a few things you may need to consider (nothing really specific to the board itself, but overall). Not sure what your current USB drive is, but you would want to make sure it's formatted for UEFI boot vs Legacy boot (that also means renaming the -EFI file to EFI on the unraid USB). Then in the BIOS of the board, you will need to make sure your boot options are setup correctly. My server is in the middle of it's monthly parity check, so I am not going to reboot it now, but if you want, I can send you a screenshot of my boot options the next time I reboot so you can see what I am using. High level I disabled all boot options for things I didn't need, like PCIe boot, booting from network etc. Now that I think about it, the AsRock rack boards come with a lot of virtual devices enabled in the BMC, you will have to disable that for your USB drive to be listed as a bootable device. If you don't, then the boot options menu in the bios are just flooded with virtual devices. Disable in General: Set all devices to 0 in VMedia Instance: EDIT: Also, you said Make sure that you are NOT using the same IP for BMC as you are for your UnRaid server, they need to be different IP's. On top of that, the board has a dedicated NIC for BMC, I assume that's what you have plugged in. You will need to use one of (or both) of the 10Gb nic's for your UnRaid server. So that means you will need to make sure the MAC address and NIC device are set accordingly in your existing unraid install, since that's likely setup for your old system. An easy way to get around that is to rename your existing network.cfg file and replace it with a stock one from the vanilla unraid install media and then boot. Once it's up and running with DHCP, you can log in and reconfigure your network.

Just want to add to this thread, that I also am getting this warning. However, it's basically by design for me at the moment since I am having to keep my Dockers on eth0 while my vm's are on eth1 to avoid the floating issue within unraid of call traces. Setting network type of virtio-net is not a sure fire fix as I already have that and still get them. Setting dockers on one nic and VM's on the other seems to bring some stability until this issue truly gets fixed.

"The advantage of using this setup is that you benefit from Cloudflare fast DNS resolution and add an extra layer of security by hiding your server identity while ensuring that all the connections pass through Cloudflare. This prevents any malicious requests from reaching the server." https://support.cloudways.com/configure-cloudflare-origin-certificate-with-your-application/ In a nutshell it let's CF field all the nasties on the web for you, while hiding your server and it's point of origin behind it's WAF. Good way to mitigate attempts against your port forwarded server sitting on the web.