MowMdown

Unless you are manually running parity checks, that setting doesn't affect scheduled parity checks. As to why it's not persistent, couldn't' tell you.

Ok so Disk1 just finished, after emptying it and before I ran a format it was showing a FS overhead of 136GB which seems quite low for a 12TB disk. After doing a format, it's now reporting 230GB FS overhead. That only accounts for about 94GB of the ~156GB difference. After Rsync was finished After Disk1 was emptied Disk1 formatted

Post diagnostics please

I have an odd question, related to migrating data between two XFS disks. Both were/are on V5. Background. I have been converting my XFS disks from unencrypted to xfs-encrypted. Here's where it gets weird all my disks are either Seagate IronWolf 12TB (non-pro) or WD Red Plus 12TB drives. I threw in an empty disk, formatted it as xfs-encrypted and ran rsync -aHAXx --numeric-ids /mnt/diskX /mnt/diskY then rinse and repeat up the drive order, fomat the now emtpy disk as xfs-encrupted, and re-run the rsync command for the next two disks Disk4 -> DIsk5, Disk3 -> Disk4, etc.. However when I got to disk2 which was 96% full, after the rsync to disk3, disk3 is now reporting 97% full with fewer remining free space than what disk2 previous was showing. Both disks contained identical copies as I didnt delete the source data. Disk2 was showing 411GB Free where as DIsk3 was now showing 257GB free. Does this make sense? Does LUKS add several GBs of extra overhead on top of the overhead XFS already adds? I knew in my case XFS adds about 230GB of used space for the filesystem metadata/reflinks etc... but how do I "lose" an extra 150GB on top of that? Here is the image when it was nearly finished and I was already showing less free space than disk2 (you can see it is transferring 11,511,081,008,711 bytes) Im currently in the process of moving disk1 now to disk2, here is the before You can see disk2 has nothing on it before I started so I know 230GB is how much the FS takes up. The question I have is does the 512 sector vs 4096 sector change how data is stored and reported? ~# xfs_info md2p1 meta-data=/dev/mapper/md2p1 isize=512 agcount=11, agsize=268435455 blks = sectsz=4096 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=1 = reflink=1 bigtime=1 inobtcount=1 nrext64=1 = exchange=1 metadir=0 data = bsize=4096 blocks=2929717235, imaxpct=5 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1, parent=1 log =internal log bsize=4096 blocks=521728, version=2 = sectsz=4096 sunit=1 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 = rgcount=0 rgsize=0 extents = zoned=0 start=0 reserved=0 ~# xfs_info /dev/md1p1 meta-data=/dev/md1p1 isize=512 agcount=11, agsize=268435455 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=0 = reflink=1 bigtime=1 inobtcount=1 nrext64=0 = exchange=0 metadir=0 data = bsize=4096 blocks=2929721331, imaxpct=5 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1, parent=0 log =internal log bsize=4096 blocks=521728, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 = rgcount=0 rgsize=0 extents = zoned=0 start=0 reserved=0

Do you have the bios setting enabled to turn the system on when power is connected. This should be enough to trigger your system to power back on once the UPS switches back to main power. Or are you saying the UPS itself is turning off but not back on when booted?

Please post diagnostics in a reply to this comment

log into the webgui and pull the diagnostics please

Please post diagnostics

I cannot comment on duplicati as I’ve only used backrest.

I use the backrest docker container to backup stuff to b2 daily. Backrest is a GUI wrapper for restic and restic is included. https://www.linuxserver.io/blog/backup-your-data-to-b2-with-restic-and-backrest

GitHubGitHub - qdm12/gluetun-wiki: Home to the Markdown Wiki pa...Home to the Markdown Wiki page for Gluetun. Contribute to qdm12/gluetun-wiki development by creating an account on GitHub.

If you want https to paperless, paperless itself would need to have its own SSL certificate installed and that’s almost always never the case. Tailscale is secure it’s just wireguard with a fancy interface to seamlessly connect your tailnet devices. That connection is encrypted. But if it really bothers you, you would want to setup a reverse proxy to get https in your browser. Technically the connection between the reverse proxy container and the paperless container would still be using the http port of paperless. I don’t know anybody who installs certs for each container as it would have to be done manually and every time the cert expires. (It’s why everyone uses a reverse proxy) Refer to my Tailscale dns guide I linked and it walks you through how to set it up.

As I said it can take up to 24 hours and in some extreme cases 72 hours to find faulty memory. It’s why I strongly recommend at least 24 hours. 3 passes is nowhere near enough in my opinion especially considering the corruption warnings which is almost always memory related. Just don’t be surprised if these errors keep popping up.

Then yeah if you were doing that, that would explain the container restarts in the log. As far as the memtest goes, you will want to run that for at least 24 hours or unless you get a FAIL message. If you get a FAIL, you can stop the test and either retest each stick individually or replace the entire kit. Do not run the server on failed RAM. It can take several passes to find faulty RAM

Only thing I see is you appear to have a docker container restarting/crashing constantly. You will want to check the uptime for each container on the docker container page to see if any are showing as recently restarted.

Your USB may not be writable and for some reason is missing the share.cfg file. Not sure what's up with that. Someone else may have to answer that. But right now running a Memtest should be a #1 priority. I mean, it's what I would consider an emergency. Everything runs thorough RAM and if RAM is bad, your data can be compromised.

Youre going to want to likely run a memtest, you can do so from the unraid boot screen (blue screen with menu options) Look for Memtest86

your K-9 server has an issue with your NVME drive BTRFS info (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 9, gen 0 and is having further checksum errors Mar 20 00:46:44 K-9 kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 147958 off 53248 csum 0xb0c0e1ae expected csum 0xb0c0e9ae mirror 1 Mar 20 00:46:44 K-9 kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 17, gen 0Since you are not running the devices in a mirror a btrfs scrub will not repair the corrupted data.

Have you ran a Memtest with the replacement RAM? I would start with that. Then if that can pass 24 hours, run unraid in safe mode with no plugins or conatiners. If you can run it as a basic NAS for a day or two, I would start enabling services up one at a time and see if you can survive from any crashes then continue. Either youre running faulty RAM or you may be running out of memory.

No rush, I am working out the kinks with Vlad over in the filerun fourms to make sure that fresh install works just as seamless as doing an in place upgrade on this new exp branch tag. I ran into a few small snags regarding permissions. So far though it's been pretty smooth.

I have a question: I bought a new key but only have an activation code, when I boot my server without my existing pro.key file, when it takes me to account.unraid.net it does not let me activate the new key on the TPM, it only gives me the option to blacklist the USB and do a USB -> TMP transfer which I do not want to do. Essentially I am trying to keep my USB key on the USB and simply activate the new license on the TPM so I can re-use the USB license in a different machine. Is this not possible? Edit: For clarity Updated from 7.2.4 with existing licensed USB On-boarding wizard to move boot to internal drive. Once booted back up, I then shutdown the entire system Removed the USB with the existing pro.key file and booted unraid back up off of the now internal boot disk Unraid complained about a "missing key" so I clicked on the link in the upper right which took me to the urnaid account page I was prompted to migrate from USB to TPM and to acknowledged that my USB will be blacklisted. To which I stopped. There was no option to activate my new license solely on the TMP.

@ImSkully Not sure if youve been following along in the filerun forums but there is going to be a newer conatiner which fixes the apache permission stuff, it's no longer needed You can remove the apache permission vars (all 4) and then just add --user 99:100 to the extra parameters

The process can be stopped by using the terminal and killing the background rsync or move process. You can manage file transfers in any flavor you like, it's linux afterall. I prefer using tmux session and rsync. you can also use mc as well You can use the unbalanced plugin as well which also is just a gui wrapper for rsync. Like it or not, the terminal is simply the best, most robust, option you have and you should not be afraid of using it. Many people also use the Krusader docker container but I have opinions on that.

The zfs master plugin refreshes the dashboard which wakes up all zfs disks/pools. You just need to set the plugin snapshot refresh to disabled.

Setting up the more basic nextclould doesn't require an external DB unless you choose to set one up. It does give you the option of using the built in sqlite db if I recall correctly. However setting up mariadb is quite simple. And now you're finding out that self-hosting has it's pitfalls. You become the network engineer. setting up and maintaining your own infra. However once you do get it working, you can feel satisfied and accomplished.