jordan

Thanks. I had this drive fail yesterday, so DB is currently not running and I'm rebuilding; then I'll be moving the entire array to a new (better cooled) system. Christmas break is coming up, so I'll have a couple days to dive into it for real. If I do find the problem I'll post a solution back.

Quick followup - is anyone else getting tornado warnings in their log? From older threads it seems to be a connection error with the Dropbox backend but isn't critical. Still if there's an easy fix to remove them it would make my logs a bit cleaner.

I should add that all of my really important stuff is backed up to a cloud service and all but the last couple of days is on a portable drive in my fire safe (because as much as I love cloud backup, a multi-TB download on my internet connection would be painful). edit: by "important stuff" I pretty much mean all of my personal content. My commercial media...well, others have already uploaded that to the cloud, mostly in better quality than my own rips. I:-)

Everything - photos of the kids, home video, all my college coursework, my business files, everything. Poof - it's just locked inside a dead hard drive. So I just want to say a little thanks to the community and unraid because, of course, the server emailed me the drive suddenly failed, the server is running perfectly fine serving my files from the cache, and I only needed a few minutes to power down the server, and swap in a spare drive which is now being rebuilt. It's been pretty good for a "bad Monday."

I'm in the middle of switching from an old generic case with an icy-dock 5-in-3 (awful cooling - can't recommend)) to a DS380 from Silverstone with an ASRock Z390M-ITX/ac MB (6 SATA onboard + PCIe x4 M.2, one PCIe x16, 2x Intel 1000bt + wifi). One advantage I just found out about is that the HD trays are powered by a 4 pin Molex and I just confirmed that there is no 3.3v on the power bus for the rack. That means no messing with the pin-bypass hack on shucked drives - it's not powered in this system. I'm not sure about the cooling as I've not run it full of disks (SoonTM), but the placement of fans is good. The only issue I can see is that, while one side of the 8x bay is covered with two large fans, the opposite side is the sliding case is flush, so the drive fans pressurize the case and the rear fan draws that air from the drives, over the CPU cooler, then out. I'm running an i5-9400 with the stock cooler and it's about 4x the CPU I need, so I don't expect it to be an issue. The unit is reasonably quiet with the three fans running. The PS (300W Silverstone Bronze/80) hasn't fired up the fan yet (it's fanless at idle), but I'm just working through a memory test with no drives.

Sorry to dig up an old thread, but I've had piss-poor luck choosing MBs for unraid in the past. Did you ever get quick sync working on your i5-9 series on the asrock ITX board? I'm looking to move to a nicer box and this board seems like a winner if I can get hardware transcoding on the iGPU.

If you have a reference/tutorial you have seen for creating this, would you drop me a link in the reply? If not I can go through the google, but there are some exceptionally common terms in my likely query so any help or shortcut to resources would be appreciated. :-)

Okay, thanks. That's definitely going to take some reading.

That got it running. One last question (I hope) - After linking I'm greeted with the ominous [ALERT]: So your files continue to sync, sign in to your Dropbox account and move Dropbox to a supported file system. I just paged back through this thread, and I see where it came up last year when DB kicked everything but ext4 to the curb, but I can't tell whether there was a workaround built in, or everyone just bailed on the protected array and using external USB formatted to ext4? Or are those using it installing a trick like https://www.linuxuprising.com/2018/11/how-to-use-dropbox-on-non-ext4.html ?

Ah - makes sense. I didn't think to go back and scrub the old directories out manually. I'll try that.

I've clearly done something wrong, but I'm at a loss as to what. I initially tried updating the container and came up with an error so I deleted the container and reinstalled from Community Applications. I got (effectively) the same error: Did I miss some dependency or other pre-installation setup requirement?

No need for apologies; volunteer support when you're moving away from a platform is a tough spot. Thanks for checking, though! If it doesn't update, I'll try a different method. Thanks, again!

(warning: Docker newbie) I just installed it and am getting the error. I saw a post from back in 2017 that this was an issue, but am not clear on how it was resolved. The docker interface in unRaid claims that the application is up to date (and have already executed a check for updates). Apologies if I'm leaving out any critical information, this is my first experience with docker containers.

Thanks for the answers!

Hi, just upgraded to v6; went for a clean install so I could start my "new" build with just the parity-protected array intact. [edit: upgrade from 5.0.6] I see that the default setup is to set every top level directory as a Share. Convenient, except that I only need/want three of the forty shared. I also see that the default is to not share any of the Disk mounts as accessible, which is what I would prefer. I have two(-ish) questions: 1. How do I share the disks? (i.e. if I go into a Windows browser and type \\tower\disk1, the location doesn't exist, nor is it in the \\tower directory list) [edit] found this one in an old thread - enabling sharing for Disks is under Settings|Global Share Settings instead of in the Share tab 2. Can I mass-delete all of the existing Shares (not the folders/files, just the shares), or do I have to manually go into all 37 shares I don't want and set them to Export = no? 2a - if I set the shares to export=no and access the files from the /diskn share, does unRaid ignore the split, or must I also set allocation to fill-up and split level to manual? Thanks!