thostr

@Woosah did you manage to solve the issue? I have the same problem.

I've recently build a new home server, and now i've noticed my USB boot drive became read only. Could anyone please help me solve this? I have added diagnostics for reference. Thank you unraid-server-diagnostics-20250422-0749.zip

Edit: Found a simular theat ths solves it. I'm not exactly sure when, but sometimes after 7.0.0 I can't seem to activate Mover. Even when trying to activate it manually nothing seems to happen? qnap-diagnostics-20250228-0729.zip

D'oh! I could have figured out my self.. Thanks for pointing that out

I get a warning from the array, but can't find where it comes from. Could anyone please help me? I have attached diagnostics for reference.

The following output was presented. I will try to start the array again. Thank you Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_fdblocks 1153375700, counted 1155815273 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 Metadata corruption detected at 0x438a03, xfs_inode block 0x801de878/0x4000 bad CRC for inode 2149443728 bad magic number 0x5c17 on inode 2149443728 bad version number 0x20 on inode 2149443728 inode identifier 6214144509367642759 mismatch on inode 2149443728 bad CRC for inode 2149443729 bad magic number 0x5563 on inode 2149443729 bad version number 0xffffffa6 on inode 2149443729 inode identifier 7647094400151348661 mismatch on inode 2149443729 bad CRC for inode 2149443730 bad magic number 0x9ee9 on inode 2149443730 bad version number 0xffffffc0 on inode 2149443730 inode identifier 3497855744551762425 mismatch on inode 2149443730 bad CRC for inode 2149443731 bad magic number 0xab3 on inode 2149443731 bad version number 0x37 on inode 2149443731 inode identifier 15075787301166573095 mismatch on inode 2149443731 bad CRC for inode 2149443732 bad magic number 0x3b18 on inode 2149443732 bad version number 0x78 on inode 2149443732 bad next_unlinked 0x909ceaee on inode 2149443732 inode identifier 11962776114996555825 mismatch on inode 2149443732 bad CRC for inode 2149443733 bad magic number 0x7826 on inode 2149443733 bad version number 0x38 on inode 2149443733 bad next_unlinked 0x9503193b on inode 2149443733 inode identifier 3144906608139301979 mismatch on inode 2149443733 bad CRC for inode 2149443734 bad magic number 0x7154 on inode 2149443734 bad version number 0xffffffa8 on inode 2149443734 inode identifier 3799095130428576282 mismatch on inode 2149443734 bad CRC for inode 2149443735 bad magic number 0x84b5 on inode 2149443735 bad version number 0x2a on inode 2149443735 bad next_unlinked 0xf19bfbce on inode 2149443735 inode identifier 2101998495035798647 mismatch on inode 2149443735 bad CRC for inode 2149443728, will rewrite bad magic number 0x5c17 on inode 2149443728, resetting magic number bad version number 0x20 on inode 2149443728, resetting version number inode identifier 6214144509367642759 mismatch on inode 2149443728 cleared inode 2149443728 bad CRC for inode 2149443729, will rewrite bad magic number 0x5563 on inode 2149443729, resetting magic number bad version number 0xffffffa6 on inode 2149443729, resetting version number inode identifier 7647094400151348661 mismatch on inode 2149443729 cleared inode 2149443729 bad CRC for inode 2149443730, will rewrite bad magic number 0x9ee9 on inode 2149443730, resetting magic number bad version number 0xffffffc0 on inode 2149443730, resetting version number inode identifier 3497855744551762425 mismatch on inode 2149443730 cleared inode 2149443730 bad CRC for inode 2149443731, will rewrite bad magic number 0xab3 on inode 2149443731, resetting magic number bad version number 0x37 on inode 2149443731, resetting version number inode identifier 15075787301166573095 mismatch on inode 2149443731 cleared inode 2149443731 bad CRC for inode 2149443732, will rewrite bad magic number 0x3b18 on inode 2149443732, resetting magic number bad version number 0x78 on inode 2149443732, resetting version number bad next_unlinked 0x909ceaee on inode 2149443732, resetting next_unlinked inode identifier 11962776114996555825 mismatch on inode 2149443732 cleared inode 2149443732 bad CRC for inode 2149443733, will rewrite bad magic number 0x7826 on inode 2149443733, resetting magic number bad version number 0x38 on inode 2149443733, resetting version number bad next_unlinked 0x9503193b on inode 2149443733, resetting next_unlinked inode identifier 3144906608139301979 mismatch on inode 2149443733 cleared inode 2149443733 bad CRC for inode 2149443734, will rewrite bad magic number 0x7154 on inode 2149443734, resetting magic number bad version number 0xffffffa8 on inode 2149443734, resetting version number inode identifier 3799095130428576282 mismatch on inode 2149443734 cleared inode 2149443734 bad CRC for inode 2149443735, will rewrite bad magic number 0x84b5 on inode 2149443735, resetting magic number bad version number 0x2a on inode 2149443735, resetting version number bad next_unlinked 0xf19bfbce on inode 2149443735, resetting next_unlinked inode identifier 2101998495035798647 mismatch on inode 2149443735 cleared inode 2149443735 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 4 - agno = 2 - agno = 3 - agno = 1 - agno = 6 - agno = 7 - agno = 5 - agno = 8 - agno = 9 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (2:2575356) is ahead of log (1:2). Format log to cycle 5. done

I get this result Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.

Hello, I have some issues with disk acting up. After a fresh reboot, I have no issues, but after a while one of my disks stops responding root@QNAP:/mnt# ls -l /bin/ls: cannot access 'disk3': Input/output error total 16 drwxrwxrwt 2 nobody users 40 Jul 27 15:17 addons/ drwxrwxrwx 1 nobody users 44 Jul 27 15:27 cache/ drwxrwxrwx 4 nobody users 40 Jul 27 15:27 disk1/ drwxrwxrwx 8 nobody users 120 Jul 27 15:27 disk2/ d????????? ? ? ? ? ? disk3/ drwxrwxrwx 3 nobody users 18 Jul 27 15:27 disk4/ drwxrwxrwx 3 nobody users 18 Jul 27 15:27 disk5/ drwxrwxrwx 3 nobody users 26 Jul 27 15:27 disk6/ drwxrwxrwt 2 nobody users 40 Jul 27 15:17 disks/ drwxrwxrwt 2 nobody users 40 Jul 27 15:17 remotes/ drwxrwxrwt 2 nobody users 40 Jul 27 15:17 rootshare/ drwxrwxrwx 1 nobody users 40 Jul 27 15:27 user/ drwxrwxrwx 1 nobody users 40 Jul 27 15:27 user0/ root@QNAP:/mnt# It's driving me crazy! Could anyone please help me resolve this? I will attach diagnostics qnap-diagnostics-20240727-1554.zip

Hello I am trying to set up zigbee2mqtt but having issues connecting to Web frondend. Both mosquitto broker and zigbee2mqtt has verified the connection. Frontend have started on 0.0.0.0:8080 and I have forwarded port in docker configuration. I just can't figure out what I am missing.... What to do? EDIT: uploaded screenshots

In the glances container, how can I make it so it can save the glances.conf to appdata so I can make some custom edits?

Just a follow up. I deleted the content of the Codec folder witch seemed to have fixed the issue.

Hi binhex, I have an issue with transcoding EAC codecs, and I get the following error in the logs: It have been working in the past, but not sure when the the error started. Any suggestions how to fix this? I use PMS 1.20.4.3517 and unRAID 6.8.3

True. The files are named correct but Im not using usenet only torrents. Does it make a difference? Is there any way to correct this?

Please, Anyone have inputs how to resolve hvis? Is this related to unRAID filestructrure, How Radarr renames the movies or a missing setting in this docker build?

I have an issue with Radarr renaming and how it looks in a windows share. I have set up Radarr to use following "{Movie TitleThe} ({Release Year}){ [IMDb Id]} - {[EDITION TAGS]}" to name the movie folders, and the folder names looks correct when I browse unRAID folders. But somehow when I connect to the serverfrom Windows I get wierd loooking names (see screenshot). How can I avoid this whitout disabling renaming in Radarr? Thank you.

Thank you for clarifying. I have removed the limit. Hopefully it will clear things out

I looks like its this container I have limited the container, so how can it use all memory on server? Or does the error indicate the container maxes out my limit on 512MB?

This morning at 4:40 my server has run out of memory, and I have no idea why. The server is not active in that period, and does not use ressources. I have looked through the logs, and the only enrty at the time was: Aug 13 03:03:02 Thor Plugin Auto Update: Checking for available plugin updates Aug 13 03:03:07 Thor Plugin Auto Update: community.applications.plg version 2019.08.11b does not meet age requirements to update Aug 13 03:03:08 Thor Plugin Auto Update: Community Applications Plugin Auto Update finished Aug 13 03:03:42 Thor kernel: mdcmd (58): spindown 0 Aug 13 04:40:02 Thor root: Fix Common Problems Version 2019.06.30a Aug 13 04:40:02 Thor root: Fix Common Problems: Warning: Docker Application binhex-jackett has an update available for it Aug 13 04:40:02 Thor root: Fix Common Problems: Warning: Docker Application binhex-nzbhydra2 has an update available for it Aug 13 04:40:02 Thor root: Fix Common Problems: Warning: Docker Application EmbyServer has an update available for it Aug 13 04:40:02 Thor root: Fix Common Problems: Warning: Docker Application PuTTY has an update available for it Aug 13 04:40:12 Thor root: Fix Common Problems: Error: Out Of Memory errors detected on your server Aug 13 05:24:16 Thor autofan: Highest disk temp is 35C, adjusting fan speed from: 42 (16% @ 0rpm) to: 50 (19% @ 385rpm) Aug 13 05:55:01 Thor Docker Auto Update: Community Applications Docker Autoupdate running Aug 13 05:55:01 Thor Docker Auto Update: Checking for available updates Please help. I cant figure out what goes wrong. I have attached zip file for diagnostics. thor-diagnostics-20190813-0650.zip

I didnt get it to work on this container, so I switched to Embys official one. Here I have no issues at all

Sorry for asksing. But did you setup your local DNS to redirect all request your set up URL to the internal server to keep the traffic local or did you just let the internet handle the route back to your router? If handling locally. how?

+1 This is greatly needed. Instead of browinsing through several pages looking for an answer, it could save a amount of time!

After upgrade to unRAID 6.7 I get an error when starting OpenVPN service. When I log on OpenVPN AS the service is stoppen, and when I try to start it again I get following error: service failed to start due to unresolved dependencies: set(['user']) service failed to start due to unresolved dependencies: set(['iptables_openvpn']) Service deferred error: IPTablesServiceBase: failed to run iptables-restore [status=2]: ['iptables-restore v1.6.0: Bad IP address ""', '', 'Error occurred at line: 153', "Try `iptables-restore -h' or 'iptables-restore --help' for more information."]: internet/defer:653,sagent/ipts:133,sagent/ipts:50,util/daemon:28,util/daemon:69,application/app:384,scripts/_twistd_unix:258,application/app:396,application/app:311,internet/base:1243,internet/base:1255,internet/epollreactor:235,python/log:103,python/log:86,python/context:122,python/context:85,internet/posixbase:627,internet/posixbase:252,internet/abstract:313,internet/process:312,internet/process:973,internet/process:985,internet/process:350,internet/_baseprocess:52,internet/process:987,internet/_baseprocess:64,svc/pp:142,svc/svcnotify:32,internet/defer:459,internet/defer:567,internet/defer:653,sagent/ipts:133,sagent/ipts:50,util/error:66,util/error:47 service failed to start due to unresolved dependencies: set(['user', 'iptables_live', 'iptables_openvpn']) service failed to start due to unresolved dependencies: set(['iptables_live', 'iptables_openvpn'])

Exactly what I was looking for! I'll try create a new install image

@binhexI now tried to install Emby's own docker container, and here I get the expected results (see screenshot). Only extra variable I added was GIDLIST=18 by referencing this post. (it didnt work by adding it to your docker) So somehow your docker isn't working as expected.