BetaQuasi

Fantastic timing indeed - I was just adding a new drive to my array and it was failing. Then the update notification popped up. Thanks!

This is a docker network IP used for bridging, and a private IP. It is not expected to be used for connectivity. Your friends should be connecting using your external public IP.

This is an old thread, there will be newer BIOS available now - however I updated the original links for you.

You'll want to use the UEFI method - the DOS method rarely works with Supermicro motherboards. It's not your particular use case, but you can see the same was true on their older boards by following the M1015/X9SCM link in my signature. There is also a Linux flash method, which you can apparently do from within unRAID itself, but I don't have any direct experience with that. From what I can tell, it does require a 32-bit version of unRAID to work successfully though.

Fair enough. I don't tend to bother with a USB stick that exhibits issues since they are so cheap and the new license process is much simpler these days.

Looks to me like your USB stick (sda1) has issues. I'd try replacing it as a first step.

@LondonDragon This docker is on Deluge 2.0 now, which uses Python 3.0. You'll need to bug the plugin authors for updated plugins, or revert to the last 1.3.15 build. linuxserver/deluge:amd64-5b398f77-ls22

To the OP, I've got a couple of different methods documented in the 'M1015/X9SCM Firmware' link in my signature - maybe one of them will work for you?

Probably the most user-friendly way would be to use gparted (https://gparted.org) - I'd grab the live CD/ISO and set that as your boot drive for the VM running unRAID. It should see your existing vmdk and allow you to resize it. From memory (and this is going back quite a few years now so I don't know for sure!) the .vmdk file itself was already 1Gb, so you should be able to extend the partition to fill that. If the .vmdk file itself also needs extending, you can do that from the command line in VMware, using the vmkfstools command. You can see more detail here. You would first extend the .vmdk file to a certain size, and then run gparted to expand the partition to fill the newly-created disk. https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc_50%2FGUID-97FED1EC-35A5-4EF2-80BA-7131F8455702.html There's quite a few other ways to approach this too, but that should specifically address what you need. Lastly, back up the .vmdk first in case something goes wrong!

Yeah I noticed this myself today. Thought it was a browser issue at first, but seems to persist on all browsers and PC's. Not the end of the world, but a bit annoying when you can't check on the progress of a big move/copy job!

The stock fans are actually amazing for airflow, they are just noisy as all hell. If you don't care about noise, I wouldn't bother switching them out.

I would just attach the cache drives directly to the SATA ports on the motherboard if you don't intend on using them for anything else. I can see the Norco 4224's have come a fair way since I bought mine 6 years ago! Those mounting bolts etc look like they are much better quality. That being said, I haven't had a single issue with the case/backplanes etc in 6 years now, so all good!

You should be fine to keep your existing config, just point the appdata path to the same place. Stop the old docker first of course, and perhaps take a backup of the appdata just in case of any weirdness. Have done this a couple times myself with no issues in any case.

Ok, thanks for the quick response!

Hi guys, Apologies if this has already been asked. I did do an in-topic search with this new forum for 'develop' but didn't get any relevant hits. Is there any way of forcing the container to download the 'develop' builds instead of the stables? i.e. via a variable or similar? I'm doing that inside Sonarr itself, but when the docker restarts or updates, it's taking me back to the stable build (to be expected of course!.