xokia

Fair enough I did preference with just a guess. You folks would have the download data. Its a very useful feature. At any point I think I will wait for a future release before trying to upgrade again. At least the role back wasn't too difficult.

I uninstalled and then reinstalled the plugin and seems to be ok. But I also rolled back to 6.12.15. I am guessing that "if installed" maybe save off config uninstall/ reinstall? Or give some indication that an uninstal/reinstalll needs to occur. Honestly mover tuning features should be basic unraid features just my $.02 for what its worth. I would wager 95% of unraid user have it installed but thats just a guess. Once I rolled back mover instanltly started working again. Only issue I had is I had to delete the SSL certificate and reissue certificate.

This is a really useful plugin. It is easy to see where files are accessed from cache or HDD. Do you see any reason to have incompatibility issues with 7.1.x ?

home-server-diagnostics-20250510-1217.zip I have mover tuning installed it tells me its incompatible but to install a version that I already have installed. How do I role back to 6.12.15? This version isn't ready for prime time JMO. app "open files" seems to be incompatible. Which is a really useful app to tell which files are being accessed and from where (cache or HDD).

I take that back. After update if I click "Move" mover fails to execute. It just leaves my files sitting on the cache drive. I can see each time I click mover in the log file but nothing happens

I upgraded to 7.1.1 it appeared to go smoothly. Hopefully everything stays functional and no issues.

I run my own dns server .20 is my dns server. I tried manually adding the dns to the swag container. I also tried --dns 8.8.8.8 --dns 1.1.1.1 made zero difference. There is no option for custom dns server under the docker setting

Now I am confused if I ping the offending address from the swag container it resolves! Maybe there is something wrong with letsencrypt? I know my error log is full of these it appears it tries every 5 min or so. 2025/05/02 18:14:06 [error] 961#961: e6.o.lencr.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: e6.o.lencr.org, certificate: "/config/keys/cert.crt" 2025/05/02 18:19:46 [error] 969#969: e6.o.lencr.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: e6.o.lencr.org, certificate: "/config/keys/cert.crt" 2025/05/02 18:19:58 [error] 970#970: e6.o.lencr.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: e6.o.lencr.org, certificate: "/config/keys/cert.crt" PING e6.o.lencr.org (23.32.152.232): 56 data bytes 64 bytes from 23.32.152.232: seq=0 ttl=45 time=29.889 ms 64 bytes from 23.32.152.232: seq=1 ttl=45 time=30.711 ms 64 bytes from 23.32.152.232: seq=2 ttl=45 time=29.913 ms 64 bytes from 23.32.152.232: seq=3 ttl=45 time=30.170 ms 64 bytes from 23.32.152.232: seq=4 ttl=45 time=29.624 ms 64 bytes from 23.32.152.232: seq=5 ttl=45 time=30.873 ms 64 bytes from 23.32.152.232: seq=6 ttl=45 time=29.585 ms ^C --- e6.o.lencr.org ping statistics --- 7 packets transmitted, 7 packets received, 0% packet loss round-trip min/avg/max = 29.585/30.109/30.873 ms

It would appear that ngnix is unable to resolve dns. /etc/resolv.conf nameserver 127.0.0.11 options ndots:0 This appears to point to the docker dns which should in return point to the host dns. The host dns resolves. I cant seem to change the /etc/resolv.conf file in swag as each time I change it then restart swag it recreates itself. I can't figure out why the docker container is unable to resolve dns if the host can. This is a relatively new occurrence and I haven't changed anything in swag or unraid other then the pushed updates. Any help would be appreciated host dns below root@Server:~# dig A r3.o.lencr.org @1.1.1.1 +short dig A r3.o.lencr.org @1.0.0.1 +short dig A r3.o.lencr.org @8.8.8.8 +short o.lencr.edgesuite.net. a1887.dscq.akamai.net. 104.100.168.73 104.100.168.115 o.lencr.edgesuite.net. a1887.dscq.akamai.net. 104.103.68.73 104.103.68.105 ; <<>> DiG 9.16.42 <<>> A r3.o.lencr.org @8.8.8.8 +short ;; global options: +cmd ;; connection timed out; no servers could be reached

is no one else seeing these issues? Kinda quite in here.

getting a lot of errors in nginx error log lately. I assume its trying to validate the letsencrpt certificate and failing? My sites seem to work ok massive amounts of these errors not sure what changed in swag lately but there really isnt an indication that there is a problem without looking 2025/04/21 17:35:20 [error] 984#984: e6.o.lencr.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: e6.o.lencr.org, certificate: "/config/keys/cert.crt" 2025/04/21 17:43:09 [error] 986#986: e6.o.lencr.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: e6.o.lencr.org, certificate: "/config/keys/cert.crt" server: za.*, request: "POST /api/webhook/18b659ea610297da1687675d589e2c33bbb52f42d654bea0b734f5ba1822b7bd HTTP/1.1", upstream: "http://192.168.1.1:8123/api/webhook/18b659ea610297da1687675d589e2c33bbb52f42d654bea0b734f5ba1822b7bd", host: "mydomain" 2025/04/22 18:11:36 [error] 955#955: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 18.210.179.88, server: za.*, request: "POST /api/webhook/18b659ea610297da1687675d589e2c33bbb52f42d654bea0b734f5ba1822b7bd HTTP/1.1", upstream: "http://192.168.1.1:8123/api/webhook/18b659ea610297da1687675d589e2c33bbb52f42d654bea0b734f5ba1822b7bd", host: "mydomain" 2025/04/22 18:11:39 [error] 959#959: e6.o.lencr.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: e6.o.lencr.org, certificate: "/config/keys/cert.crt" 2025/04/22 18:11:40 [error] 960#960: e6.o.lencr.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: e6.o.lencr.org, certificate: "/config/keys/cert.crt"

I dont have my shares broken up into that granularity. Which under "new permissions" I can't go any deeper then the initial share which would be the entire disk. What does "new permission" do? *edit* it did work Its not part of appdata entirely seperate disk

Trying to delete a file via smb that was created by "nobody" . I wouldn't think "nobody" should have permissions that should prevent me from deleting. What am I missing

Whats the advantage to setting to both vs files? I suppose this prevents someone from encrypting the folder that contains the files?

I run those exos 20TB drives. Parity runs at damn near 280MB/s takes about 1.5 days to build parity. I can't comment on why you are getting 23MB/s something is definitely wrong. What other drives do you have in your system? Its going to get dragged down to the slowest drive.

Good to know I appreciate the feedback. I prefer the stability over jumping to something new. Maybe I will wait a while longer to upgrade.

I have different "shares" but only for very specific things. Its a home server I dont need 20 different user shares. Since a single drive is setup for a particular thing I can "share" the entire drive for a particular service and assign appropriate permissions for that drive. Pool5 happens to be a 20TB drive that contains nothing but movies. I used to use proxmox and lxc containers. The drives were setup under that system before I moved over to unraid. So I left the drives as they were. I think at the time I was also playing around with ZFS and decided it wasn't for me the names stuck everything else changed. I do not split data across drives I haven't found the need to do that. The way I have it setup it isn't spinning up multiple drives unnecessarily. Most of the time the large 20TB drives are actually powered down. Things run from the cache drives and only a single drive spins up if a drive is accessed with data that can't be serviced from the cache drives which are all SSD or NVME. Even if my plex database is accessed it doesnt spin the drive up unless the movie is streamed. Anyway the setup works great for me.

Correct I dont split the data across multiple drives. I use single disk drives. I keep movies for instance only on 1 drive. Games on a second drive ect. I guess technically you call them arrays I call them pools.

Just looking to get folks general experience. Has it been mostly trouble free? i.e. everything worked? Or did you run into issues? What issues to expect? Trying to avoid a long down time. I avoided the 7.0.0 upgrade but starting to question if its now worth upgrading to 7.0.1. I am afraid something will break on a system that works great. I run plex,homeassistant,sftpgo,nextcloud,swag,vaultwarden in docker and multiple windows VMs. I run single drive pools xfs formatted with multiple cache drives. Just looking for user experience info from those that have done it. Will a parity check get toggled on the upgrade? Parity check for me takes 1.5 days.

hard one to answer. I use chrome, brave and safari.

I am using btrfs for cache pools. I think I read somewhere that was what you wanted for SSD and NVME drives.

Your post came after I rebuilt. I didnt wait around for an answer.

This has bit me twice when swapping out a cache pool for a larger cache drive. 1.3 days to rebuild the parity. Hopefully you folks can improve this in the latest update (wether that is improved documentation or a more user friendly GUI IDK). I didn't see anyway to proceed without rebuilding the entire thing. So sucked it up and rebuilt the parity. I couldn't restart the array without agreeing to restart parity. Can I dynamically change the cache pool size? My cache pools are NVME or SSD. I have a bunch of files I leave in the cache pool because they are lots of small files. Seek times on HDD are terrible specially for lots of small files. This has served me well but I may hit my specified size sometime in the near future.

No way to change cache drive without rewriting parity So this is annoying. I want to change a cache drive and I MUST recalculate parity I swapped in a larger cache drive Chose preserve current assignment Then go to start the array For those saying you can swap out the parity drive without a costly parity rebuild IDK know how you folks are accomplishing that. That information does not seem correct.