tjb_altf4

I'm still on 6.11.5 on one of my servers (on 535), and I need the 550 driver for a new application. Do I need to upgrade the Unraid OS for this driver? or is the plugin not showing available versions for some other reason? Thanks

an active wifi module will use that power anyway, its a zero sum game.

IP should be none unless you want an unraid UI on that nic. I wouldn't recommend using the same subnet on multiple nics, it tends to not work unless you do some advanced networking. The typical pattern for this is to create separate subnets (vlan + subnets) on your managed switch for each interface to use, you'd ideally also move the things it connects to onto the same vlan, e.g. NVR + cameras onto the same vlan+subnet.

Might need to chmod +x the script file, or possibly investigate some other permission issue.

You mention a few times you prefer a lifetime licence option... Unraid still has a lifetime licence Also, If you don't chose a lifetime licence option, nothing stops working in future when your sub expires, other than availability of Unraid OS updates.

Fresh install can help root out edge case issues if you are having issues, but the best reason is to see what is now part of the OS and with fresh eyes decide whether you actually need all those plugins and mod scripts you might have added over the years.

@ljm42 point 1 still points to the previous 6.12.11 release notes

Looking at your post history, it shows you were asked to share diagnostics in your support thread, and you never responded. Also looks like you bought a cracked version, which probably explains some of the issues.

this is the first sale since the new licencing model came into effect, so no.

tools are already on unraid, it just needs sg_write_buffer You'll have to search, maybe ask around on servethehome forums, the firmware repo I've used in the past has been removed.

I would start by updating the firmware to NA04, these drives had a nasty bug that when they hit a certain power on hours they brick themselves. Serverthehome has resources for this, I've had to do a few of these drives. Not sure about the speed issues, although I've seen one isolated comment mention they don't always handle 6Gbps connections correctly... not sure if there is much weight in that one but worth investigating, maybe an incompatibility with controllers assuming you changed during your tests.

Thanks Jorge. Makes sense that its actually default, I assumed because it wasn't run with the priority flags it wasn't being deprioritised (or there were lower levels available)... I missed the man note. I have revisited my testing, and reducing the amount of pools scrubbing in parallel has improved the situation, so I think I was being over zealous and overloaded the CPU, or possibly the HBA, both of which are avoidable situations

Requesting IO tuning options for btrfs scrub in the UI (scheduler), or some sensible defaults for file system scrubs. Currently my experience is that the disk(s) become unusable for even regular read operations during scrub, pool size of ~100TB means scrubs takes 2-3 days. relevant scrub options for adoption -c <ioprio_class> set IO priority class (see ionice(1) manpage) -n <ioprio_classdata> set IO priority classdata (see ionice(1) manpage) https://man7.org/linux/man-pages/man8/btrfs-scrub.8.html

The original plans, including Pro tier are grandfathered in with lifetime support, so you would see no benefit to "upgrading" to Lifetime. Feature-wise Pro is on par with Lifetime. More info: https://unraid.net/blog/pricing-change

"database disk image is malformed" means your database is corrupted and needs to be replaced with a backup or recreated from scratch. The application will not run until this is resolved. Reason it happened is it possibly corrupted due to out of space at some point, or hardware issue.

Trigger warning

I believe this was one of the original use cases of the Unassigned Devices plugin, where it would remember the ID of an external disk device, for which you can add a custom script to be run upon connection (such as copy contents to a share).

Might be slightly different as I'm on 6.11.5, but should be Settings > UPS Settings > Start APC IPS daemon = No

Just modify the template, you can see latest docker vars here: https://github.com/Chia-Network/chia-docker Unless you plan on running different keys on separate farmers (or some other niche requirement), you are better off running a harvester only service.

Specs in my signature, but in summary its a dell r730 with dual 2697v4 xeons. External storage is connected via LSI 9207-8e HBA. This is all in one Unraid VM, although I run other VMs on this server also.

Moved most of the old setup to a R730 with multiple Netapp DS4246s for disk management. Proxmox is the hypervisor, running Unraid as a VM. root@cloudbreak:~# df -h --total Filesystem Size Used Avail Use% Mounted on ... total 1.4P 1.4P 11T 100% -

Great to hear! Also if you need qemu agent, it is already installed on unraid, but you need to activate it like so:

I did find this interesting thread on Proxmox forums, does this sound applicable to your setup? https://forum.proxmox.com/threads/vm-stop-starts-every-5-minutes.136678/

Apologies you can leave cpu type as "host", but otherwise rules out that being the issue. Most of your settings are the same as mine... only other suggestion is to ensure "Ballooning Device" is unchecked in Proxmox vm memory options, possibly pump this up to 6 or 8GB if you have the spare memory especially if you are running more than pure storage on it e.g. docker. 5 min is not very long, are you actually getting into Unraid at any point? Does the console show the boot process finishing?

Try changing "Processors" to the following