jj_uk

Is it possible to exclude folders everywhere that have a certain name? I use the recycle bin plugin and I don't want to include .Recycle.Bin folders in my backups. I'd like to globally exclude .DS_Store, *.tmp, .Recycle.Bin

I've just turned on an unraid server that's been off for 3 years. when I go to the IP address of the server, it redirects to https://**removed**.unraid.net But there's an error page: This site can’t be reached Check if there is a typo in **removed**.unraid.net. If spelling is correct, try running windows network Diagnostics. DNS_PROBE_FINISHED_NXDOMAIN It was working ok when the server was shut off a few years ago. Any ideas? I don't have a monitor cable to connect to the server at the moment, so no console.

Hi- I'm trying to fix nextcloud following the instructions here: https://info.linuxserver.io/issues/2023-06-25-nextcloud/ but i'm stuck. I changed the repository back to lscr.io/linuxserver/nextcloud:version-24.0.12 and restarted. I had some warnings about /nextcloud/nginx/nginx.conf and /nextcloud/nginx/site-confs/default.conf being out of date, so i deleted them and restarted the container. They were recreated. The log file now shows only this: When accessing the nextcloud webgui ip address, I get this: When trying to update, I get this: I read my notes from past updates and run the command that I always use: sudo -u abc php /config/www/nextcloud/updater/updater.phar but get the same write permission error as above. Here's my nextcloud appdata, the user/group seems to be nobody/nogroup. I can't remember if this was user/group abc/abc previously? I'm now stuck and don't know what to do to get nextcloud working again? I've tried as much as I can, but this is beyond me. EDIT: I ran chown -R abc:abc /config/www sudo -u abc php /config/www/nextcloud/updater/updater.phar The updater is now running. We'll see what happens. EDIT 2: This is working for me. Nextcloud updated once and I was able to access the GUI.

It's copying from /mnt/disk2/MediaServer to /mnt/disk1/MediaServer So that's disk to disk, right? /mnt/user/MediaServer <-- is that a user share?

So the data is just lost? ok, i'm moving the data off the drive i'd like to remove using the Dynamix File Manager plugin. I'll take a look at unBalance.

The process of changing the parity drive to a 20T drive, and replacing a faulty disk has now completed. I've now replaced another small data disk with a 20T disk. As I now have loads of free space on the server, I'd like to remove a disk. The process to remove a drive is to reset the config, choosing to preserve assignments, changing the disk to be removed to 'unassigned' then starting the array (in maintenance mode, for speed). As a disk has been removed, what happens here? Does Unraid try recreate the removed disk's data onto the remaining disks? In my case, there will definitely be enough space for this to happen, but what happens if there's not enough space? What happens to the share settings if they're set to use, or exclude that disk? This isn't covered in the FAQ. https://wiki.unraid.net/Manual/Storage_Management#Removing_data_disk.28s.29

OK, I'll stop worrying now. Seems to be reading and writing only the new parity drive. Was this fixed in a newer Unraid version (I'm using 6.10.2) ? I'm planning on replacing a data drive with a 20T once this parity check finishes.

I followed the procedure 'exactly' to perform the parity swap. The old parity drive was 8T, the new parity drive is 20T. I have the following drives (image below) : The parity swap process completed successfully. The last part of the instructions states that running a parity check is optional. So I chose to run it. There are literally millions of sync errors being corrected by the parity check! - What's going on ?! The parity check position is past 8T (my largest data drive). Is this simply the parity drive being reset to a known state and nothing to worry about? The new parity drive was precleared before use. Should I be worried?? tower1-diagnostics-20221208-1820.zip

The mention of the cache drive was a mistake, I was supposed to be referring only to the parity and data drives. Yes- Once they've done a few weeks of preclearing on the binhex-preclear docker, i'll pop them out of the usb cases and attach then via sata.

I have a data disk that is showing smart errors. The disk is about 12 months old, and annoyingly a 3-cycle preclear didn't show any errors, but that's life. The drive was ripped from a USB backup box so it has no warranty. Bye bye cash. My server is running low on storage, so I've bought two 20TB drives (usb backup drives, currently connected via usb and preclearing 3x cycles). All data disks and the parity disk are currently 8TB. To insert the 20T disks, I'll also need to replace the cache drive as it must be >= the largest data disk. Would I be OK swapping out the parity drive with a 20T, rebuilding the array then swapping the failing drive with the old parity drive? Or should I do a the parity swap procedure instead ? (https://wiki.unraid.net/The_parity_swap_procedure)

So I do, thanks!!

I've had this problem for a while now. A long time ago, I renamed a share from CamelCase, to lowercase. Ever since doing that, the camel case share comes back at system reboot. For the old camel case share, I've deleted all the share's folders from all disks and the cache drive using MC, and i've deleted the share in the 'shares' tab UI, but upon reboot, the share re-appears - I just can't get rid of it, then fix common problems detects duplicate shares again. Any ideas how to delete the old share, forever?

Changed Status to Closed

Yes, that's what it was. Not sure what to do about it so disabled it.