PetterH

So i have seen lately that some torrents get errors days after download is complete. Some are ok and doesen't change status from seeding but alot of them are changed to pausing. In the download folder the correct files are there but the sizes say 0kb. For now i have stopped the torrent then started it again and this works for the most part but not always. Anyone have any clue as to what i can do to fix this?

So i updated and couldent get to the web gui. Read some recent posts here and figured i had to get a new rtorrent.rc file. Deleted it but still no joy. For fun i disabled my vpn (pia) and then i got in. Looked through the log and all i see is no errors only two warnings 2021-02-13 12:46:46 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning. 2021-02-13 12:46:46 WARNING: file 'credentials.conf' is group or others accessible (text with yellow background is a warning not error right?) Got new ovpn file form pia and still same problem (tried a custom config and a couple premade by pia) So tried some more and figured out that using port 9443 it works... So seems its the same problem as other are having. Didn't realize i had to use https as when just clicking on the web gui uses http... But like i said earlier it works fine without my vpn on port 9080 if that helps others. Latest update fixed it for me @binhex Its now working on the usual 9080 port!

okey so apperantly i only had to stop the array to exit maintinance mode and start it again to normal and now its good thanks @itimpi

So i ran it again without the -n option and it told me to run it with an -L option. Now what? This is after running it with the -L option 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... agi unlinked bucket 28 is 156 in ag 5 (inode=10737418396) sb_ifree 365, counted 458 sb_fdblocks 1299601301, counted 1315296881 - 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 - agno = 2 - agno = 3 - agno = 4 Metadata CRC error detected at 0x44d70d, xfs_bmbt block 0x280768818/0x1000 - agno = 5 Metadata CRC error detected at 0x44d70d, xfs_bmbt block 0x280768818/0x1000 btree block 5/971016 is suspect, error -74 bad magic # 0x241a9c92 in inode 10737418396 (data fork) bmbt block 1343148296 bad data fork in inode 10737418396 cleared inode 10737418396 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 5 - agno = 0 - agno = 2 - agno = 3 - agno = 6 - agno = 7 - agno = 4 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... Metadata corruption detected at 0x44d608, xfs_bmbt block 0x280768818/0x1000 libxfs_writebufr: write verifier failed on xfs_bmbt bno 0x280768818/0x1000 Maximum metadata LSN (1984442613:-916355275) is ahead of log (1:2). Format log to cycle 1984442616. releasing dirty buffer (bulk) to free list! done

@itimpi I ran the xfs repair tool and got the following: 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 ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... agi unlinked bucket 28 is 156 in ag 5 (inode=10737418396) sb_ifree 365, counted 458 sb_fdblocks 1299601301, counted 1315296881 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 Metadata CRC error detected at 0x44d70d, xfs_bmbt block 0x280768818/0x1000 - agno = 5 Metadata CRC error detected at 0x44d70d, xfs_bmbt block 0x280768818/0x1000 btree block 5/971016 is suspect, error -74 bad magic # 0x241a9c92 in inode 10737418396 (data fork) bmbt block 1343148296 bad data fork in inode 10737418396 would have cleared inode 10737418396 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 5 - agno = 6 - agno = 4 - agno = 1 - agno = 7 - agno = 2 bad magic # 0x241a9c92 in inode 10737418396 (data fork) bmbt block 1343148296 bad data fork in inode 10737418396 would have cleared inode 10737418396 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... Maximum metadata LSN (1984442613:-916355275) is ahead of log (3:1668473). Would format log to cycle 1984442616. No modify flag set, skipping filesystem flush and exiting. Do i remove the -n option and run again or?

I have had problems with one of my disks in my array since i installed it... A couple of days ago i found it with "Unmountable: No file system" error. I assume it failed without doing much of any testing. I have now preformed a parity sync / data rebuild on the replacement disk but that one also has the same error. In the array operation tab i get the option to format the disk. In the guide i found on how to replace a failed disk it says nothing about having to format it after data rebuild The guide i found: https://wiki.unraid.net/Replacing_a_Data_Drive

Hope for the best then, thanks

Before

So yesterday i got these notifications and disk 3 is now only displaying this in the attributes tab Also ran an extended smart test with new diagnostics attached tower-diagnostics-20200324-1736.zip

The error with the parity drive startet pretty soon after i put them in. Before that i diden't have any parity drives. But the last drive in the array happen a while after Haven't done anything other then running the self test as said in original post tower-diagnostics-20200322-1300.zip

One of my disks got two warnings: Warning [TOWER] - current pending sector is 8 Warning [TOWER] - offline uncorrectable is 8 Don't know what it means but ran a short smart self test and it completed without errors Is this anything i need to worry about or should i just close the warning and forget about it? Also my parity drive (i bought these at the same time) has a diffrent warning: This one i did an extended self test but completed without error. Do i need to worry or is there anything i can do?

okei so i reinstalled the docker, deleted appdata folder and restarted unraid and now it magiclally works... i love server problems... maybe it just needed a restart but hey

Im having a weird problem... rtTorrent i showing it is downloading my torrents but when i go to the folder it is supposed to download to nothing is there. It says it is downloading to the correct place in the gui and it even uploads when done...

Thank you, had to prepare the flash as new.

After i updated to latest stable version this error appears when i have a monitor connected to my server... failed to load com32 file menu.c32 The usb stick shows in bios but i have no clue how to fix the error