ikosa

That fixed on my situation too. I'm on 2.9.0 and afraid to click on apply update 😐

Thanks it is enough for me. I can connect my 1.5 and 2tb disks

i found a good deal of this card and planing to replace my SASLP with this one buy i'm not sure if it is comatible with unraid or not? Does anybody have a clue? cant find this version on https://wiki.unraid.net/Hardware_Compatibility#PCI_SATA_Controllers

Two days ago my cache disk was "unmountable no file system" i mount it readonly, copy files in it and formatting resolved that issue. May 17 21:24:24 Tower root: mount: /mnt/cache: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error. May 17 21:24:24 Tower kernel: BTRFS error (device sdc1): parent transid verify failed on 997179392 wanted 2695658 found 2690518 May 17 21:24:24 Tower kernel: BTRFS warning (device sdc1): failed to read tree root May 17 21:24:24 Tower kernel: BTRFS error (device sdc1): open_ctree failed May 17 21:24:24 Tower emhttpd: shcmd (59): exit status: 32 May 17 21:24:24 Tower emhttpd: /mnt/cache mount error: No file system Today it is faulty again, now it is mounted but seems read only. May 18 19:52:26 Tower kernel: ata4.00: exception Emask 0x50 SAct 0x10000000 SErr 0x90a02 action 0xe frozen May 18 19:52:26 Tower kernel: ata4.00: irq_stat 0x00400000, PHY RDY changed May 18 19:52:26 Tower kernel: ata4: SError: { RecovComm Persist HostInt PHYRdyChg 10B8B } May 18 19:52:26 Tower kernel: ata4.00: failed command: WRITE FPDMA QUEUED May 18 19:52:26 Tower kernel: ata4.00: cmd 61/a0:e0:60:3c:00/00:00:00:00:00/40 tag 28 ncq dma 81920 out May 18 19:52:26 Tower kernel: res 40/00:e0:60:3c:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error) May 18 19:52:26 Tower kernel: ata4.00: status: { DRDY } May 18 19:52:26 Tower kernel: ata4: hard resetting link May 18 19:52:27 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) May 18 19:52:27 Tower kernel: ata4.00: configured for UDMA/133 May 18 19:52:27 Tower kernel: ata4: EH complete May 19 03:46:01 Tower kernel: ata4.00: exception Emask 0x50 SAct 0x3ffc SErr 0x90a02 action 0xe frozen May 19 03:46:01 Tower kernel: ata4.00: irq_stat 0x08000000, interface fatal error May 19 03:46:01 Tower kernel: ata4: SError: { RecovComm Persist HostInt PHYRdyChg 10B8B } May 19 03:46:01 Tower kernel: ata4.00: failed command: WRITE FPDMA QUEUED May 19 03:46:01 Tower kernel: ata4.00: cmd 61/80:10:40:fd:79/00:00:04:00:00/40 tag 2 ncq dma 65536 out May 19 03:46:01 Tower kernel: res 40/00:18:20:fe:79/00:00:04:00:00/40 Emask 0x50 (ATA bus error) May 19 03:46:01 Tower kernel: ata4.00: status: { DRDY } May 19 03:46:01 Tower kernel: ata4.00: failed command: WRITE FPDMA QUEUED May 19 03:49:02 Tower kernel: BTRFS error (device sdc1): parent transid verify failed on 7798784 wanted 4229 found 4214 May 19 03:49:02 Tower kernel: BTRFS: error (device sdc1) in btrfs_run_delayed_refs:2935: errno=-5 IO failure May 19 03:49:02 Tower kernel: BTRFS info (device sdc1): forced readonly May 19 03:49:28 Tower kernel: loop: Write error at byte offset 5484916736, length 4096. May 19 03:49:28 Tower kernel: print_req_error: I/O error, dev loop2, sector 10712728 May 19 03:49:28 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 May 19 03:49:28 Tower kernel: loop: Write error at byte offset 5484924928, length 4096. May 19 03:49:28 Tower kernel: print_req_error: I/O error, dev loop2, sector 10712744 May 19 03:49:28 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 May 19 03:50:43 Tower kernel: loop: Write error at byte offset 5484916736, length 4096. May 19 03:50:43 Tower kernel: print_req_error: I/O error, dev loop2, sector 10712728 May 19 03:50:43 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 May 19 03:50:43 Tower kernel: loop: Write error at byte offset 5500923904, length 4096. May 19 03:50:43 Tower kernel: print_req_error: I/O error, dev loop2, sector 10743992 May 19 03:50:43 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0 Is it the time to replace the disk or is there anything i can do? tower-diagnostics-20200519-1232.zip

Thanks it is resolved. 👍 First pass with option -nv Phase 1 - find and verify superblock... - block cache size set to 165392 entries Phase 2 - using internal log - zero log... zero_log: head block 980866 tail block 980866 - scan filesystem freespace and inode maps... agf_freeblks 1328622, counted 1328640 in ag 3 agf_freeblks 15116666, counted 15116714 in ag 0 agf_freeblks 4442773, counted 4442839 in ag 1 agi_freecount 1, counted 0 in ag 3 agi_freecount 1, counted 0 in ag 3 finobt agi_freecount 71, counted 73 in ag 0 agi_freecount 71, counted 73 in ag 0 finobt agi_freecount 2, counted 0 in ag 1 agi_freecount 2, counted 0 in ag 1 finobt sb_ifree 107, counted 110 sb_fdblocks 27229260, counted 27229419 - 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 data fork in ino 1088966556 claims free block 136122249 - agno = 2 - agno = 3 data fork in ino 3240758078 claims free block 419362511 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 entry "5fc9d9c3ca4743f3bcfd3feec3d1aeaf.jpg" (ino 3240758083) in dir 1843271725 is a duplicate name, would junk entry entry "ee209d279d6e44b89a3e06e65d3360f7.jpg" (ino 3240758084) in dir 1843271725 is a duplicate name, would junk entry bad hash table for directory inode 1843271725 (no leaf entry): would rebuild entry "IMG-20200501-WA0001.jpg" (ino 3240758080) in dir 1843271727 is a duplicate name, would junk entry - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 3240758080, would move to lost+found disconnected inode 3240758083, would move to lost+found disconnected inode 3240758084, would move to lost+found Phase 7 - verify link counts... would have reset inode 1088966558 nlinks from 1 to 2 No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Mon May 11 13:53:56 2020 Phase Start End Duration Phase 1: 05/11 13:53:43 05/11 13:53:43 Phase 2: 05/11 13:53:43 05/11 13:53:43 Phase 3: 05/11 13:53:43 05/11 13:53:52 9 seconds Phase 4: 05/11 13:53:52 05/11 13:53:52 Phase 5: Skipped Phase 6: 05/11 13:53:52 05/11 13:53:56 4 seconds Phase 7: 05/11 13:53:56 05/11 13:53:56 Total run time: 13 seconds Second pass with no option Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... agf_freeblks 1328622, counted 1328640 in ag 3 agf_freeblks 15116666, counted 15116714 in ag 0 agf_freeblks 4442773, counted 4442839 in ag 1 agi_freecount 1, counted 0 in ag 3 agi_freecount 1, counted 0 in ag 3 finobt agi_freecount 71, counted 73 in ag 0 agi_freecount 71, counted 73 in ag 0 finobt agi_freecount 2, counted 0 in ag 1 agi_freecount 2, counted 0 in ag 1 finobt sb_ifree 107, counted 110 sb_fdblocks 27229260, counted 27229419 - 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 data fork in ino 1088966556 claims free block 136122249 - agno = 2 - agno = 3 data fork in ino 3240758078 claims free block 419362511 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... entry "5fc9d9c3ca4743f3bcfd3feec3d1aeaf.jpg" (ino 3240758083) in dir 1843271725 is a duplicate name entry "ee209d279d6e44b89a3e06e65d3360f7.jpg" (ino 3240758084) in dir 1843271725 is a duplicate name bad hash table for directory inode 1843271725 (no leaf entry): rebuilding rebuilding directory inode 1843271725 entry "IMG-20200501-WA0001.jpg" (ino 3240758080) in dir 1843271727 is a duplicate name rebuilding directory inode 1843271727 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 3240758080, moving to lost+found disconnected inode 3240758083, moving to lost+found disconnected inode 3240758084, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 1088966558 nlinks from 1 to 2 done Third pass to verify with option -nv Phase 1 - find and verify superblock... - block cache size set to 165392 entries Phase 2 - using internal log - zero log... zero_log: head block 980866 tail block 980866 - scan filesystem freespace and inode maps... - 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 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Mon May 11 14:02:16 2020 Phase Start End Duration Phase 1: 05/11 14:01:56 05/11 14:01:56 Phase 2: 05/11 14:01:56 05/11 14:01:56 Phase 3: 05/11 14:01:56 05/11 14:02:08 12 seconds Phase 4: 05/11 14:02:08 05/11 14:02:09 1 second Phase 5: Skipped Phase 6: 05/11 14:02:09 05/11 14:02:16 7 seconds Phase 7: 05/11 14:02:16 05/11 14:02:16 Total run time: 20 seconds

May 11 11:09:03 Tower kernel: XFS (md5): Internal error XFS_WANT_CORRUPTED_GOTO at line 1438 of file fs/xfs/libxfs/xfs_ialloc.c. Caller xfs_dialloc_ag+0xf3/0x26a [xfs] May 11 11:09:03 Tower kernel: CPU: 0 PID: 12743 Comm: shfs Not tainted 4.19.107-Unraid #1 May 11 11:09:03 Tower kernel: Hardware name: System manufacturer System Product Name/M5A78L-M LX, BIOS 1603 11/05/2013 May 11 11:09:03 Tower kernel: Call Trace: May 11 11:09:03 Tower kernel: dump_stack+0x67/0x83 May 11 11:09:03 Tower kernel: xfs_dialloc_ag_finobt_near+0x15b/0x1dd [xfs] May 11 11:09:03 Tower kernel: xfs_dialloc_ag+0xf3/0x26a [xfs] May 11 11:09:03 Tower kernel: xfs_dialloc+0x206/0x23d [xfs] May 11 11:09:03 Tower kernel: ? _cond_resched+0x1b/0x1e May 11 11:09:03 Tower kernel: xfs_ialloc+0x67/0x4f5 [xfs] May 11 11:09:03 Tower kernel: xfs_dir_ialloc+0x76/0x1cd [xfs] May 11 11:09:03 Tower kernel: xfs_create+0x21d/0x3d2 [xfs] May 11 11:09:03 Tower kernel: xfs_generic_create+0xc9/0x29f [xfs] May 11 11:09:03 Tower kernel: path_openat+0x6a4/0xc8f May 11 11:09:03 Tower kernel: ? flock_lock_inode+0x1e2/0x206 May 11 11:09:03 Tower kernel: do_filp_open+0x4c/0xa9 May 11 11:09:03 Tower kernel: do_sys_open+0x135/0x1d9 May 11 11:09:03 Tower kernel: do_syscall_64+0x57/0xf2 May 11 11:09:03 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 May 11 11:09:03 Tower kernel: RIP: 0033:0x14885943ccf4 May 11 11:09:03 Tower kernel: Code: 84 00 00 00 00 00 44 89 54 24 0c e8 e6 f4 ff ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 18 f5 ff ff 8b 44 May 11 11:09:03 Tower kernel: RSP: 002b:000014884b775b10 EFLAGS: 00000297 ORIG_RAX: 0000000000000101 May 11 11:09:03 Tower kernel: RAX: ffffffffffffffda RBX: 000000000045a3d0 RCX: 000014885943ccf4 May 11 11:09:03 Tower kernel: RDX: 0000000000048242 RSI: 000014884001e340 RDI: 00000000ffffff9c May 11 11:09:03 Tower kernel: RBP: 000014884001e340 R08: 0000000000000001 R09: ffffffffffff0000 May 11 11:09:03 Tower kernel: R10: 00000000000081b6 R11: 0000000000000297 R12: 0000000000048242 May 11 11:09:03 Tower kernel: R13: 0000148840000c50 R14: 000014884b552048 R15: 00000000000081b6 This part is looping in syslog. I try to restart but no help. Can anyone help me with this? tower-diagnostics-20200511-0946.zip

I have updated from 6.8.0 to 6.8.1 after update fail2ban cant start. root@Tower:/custom/fail2ban-0.11.1# /etc/rc.d/rc.fail2ban start Starting fail2ban: ERROR:root:code for hash md5 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 139, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 91, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type md5 ERROR:root:code for hash sha1 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 139, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 91, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha1 ERROR:root:code for hash sha224 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 139, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 91, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha224 ERROR:root:code for hash sha256 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 139, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 91, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha256 ERROR:root:code for hash sha384 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 139, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 91, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha384 ERROR:root:code for hash sha512 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 139, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 91, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha512 ERROR:root:code for hash md5 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 139, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 91, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type md5 ERROR:root:code for hash sha1 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 139, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 91, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha1 ERROR:root:code for hash sha224 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 139, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 91, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha224 ERROR:root:code for hash sha256 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 139, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 91, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha256 ERROR:root:code for hash sha384 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 139, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 91, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha384 ERROR:root:code for hash sha512 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 139, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 91, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha512 2020-01-12 17:11:54,549 fail2ban [15981]: ERROR 'module' object has no attribute 'sha1' ERROR:fail2ban:'module' object has no attribute 'sha1' 2020-01-12 17:12:24,895 fail2ban [15980]: ERROR Could not start server. Maybe an old socket file is still present. Try to remove /var/run/fail2 ban/fail2ban.sock. If you used fail2ban-client to start the server, adding the - x option will do it ERROR:fail2ban:Could not start server. Maybe an old socket file is still present . Try to remove /var/run/fail2ban/fail2ban.sock. If you used fail2ban-client to start the server, adding the -x option will do it

Thanks for your help. At first it make sense but arter i remember that the test i send at the above post was in the cache disk and cache only share. So i check again but now I am confused :s more than before with the result below:

root@Tower:/mnt/user/No_move# mkdir test root@Tower:/mnt/user/No_move# cd test root@Tower:/mnt/user/No_move/test# touch a root@Tower:/mnt/user/No_move/test# ln a b root@Tower:/mnt/user/No_move/test# ls -i 7288342 a 7288343 b Why in unraid hardlinked files does not share the same inode? I'm not a linux expert but i guess this means they are not hardlinks am i right? But when you check second column in ls -l seems like they are linked root@Tower:/mnt/user/No_move/test# ls -l total 0 -rw-rw-rw- 2 root root 0 Sep 5 14:34 a -rw-rw-rw- 2 root root 0 Sep 5 14:34 b When i make the same test in a docker container they share the same inode: root@66f7cacf879c:/root/test# touch a root@66f7cacf879c:/root/test# ln a b root@66f7cacf879c:/root/test# ls -i 8846 a 8846 b My real purpose is to find a files hardlinked copy or check its existance, but i cant do that because of the changed inode.

I attached the diags arter restart. tower-diagnostics-20190301-2225.zip

Suddenly i wake up with 2 disk read errors (1 is disabled) and parity check errors. Can anyone help with the prosedure what is the right thing to do? tower-diagnostics-20190301-1202.zip

Hi all, I was using Picasa and syncing starred photos to google photos but unfortunately google shuts that down and i am searching for a replacement. I sync/copy/backup my all photos to unraid. Some key features that i need: import folders as albums, search or browse by date, year... , tags, stars, exif info etc standart photo management features video support will be good Sync to google photos will be awesome but i dont think that it is possible, maybe a semi automatic way webapp will be better because it is usually faster and better looking than desktop apps&vnc A dockerized app will be perfect too Lychee seems a good candidate but it has 2 major cons: It duplicates every photo or you have to lose your folder structure and filenames. (This issue has a solution with an addon called lycheesync but not supported out of the box) doesnt support videos Can anybody recommend an app like this?

+1 for lycheesync or a way/a fork to use lycheesync with this docker image etc. i dont want to duplicate my all photos or lose folder structure.

Thanks again for this great docker. Yesterday i realize that there is a problem with existing turkish characters on files and folders. I can type turkish chars without problem. But cant see and cant work with files and folders that have turkish chars in it. I think this problem poped up after a update because i use this docker since the beginnig. Can your last update cause this?

Thanks that really helped. But if you can add bash and curl to the container i will be appriciated. Or is there any proper and easy way to add bash and curl to my container that can survive container update?

this requires lots of editing on my scripts.

Container is running and i can log in from webui but i cant login from terminal? root@Tower:/# docker inspect --format="{{ .State.Running }}" MKVToolNix true root@Tower:/# docker exec -ti MKVToolNix /bin/bash rpc error: code = 2 desc = containerd: container not started

after 6.2.1 update (from 6.1.9) i migrate to the limstech sync container (from hurricane's) because for a reason that i dont know this time i cant update it from command line to the latest version which is resilio sync. The problem is my disks wont spindown when sync docker is running, and if i manually spindown my disks they will spinup in a few minutes. When i stop the sync container all disks spindown normally. Can anybody help me about this issue?

I found that sync from limetechs repo causing this. I migrate from another repo to limetech repo after the update. Time to search why. Thanks for your help jonp.

I just have 3 plugins, ca, cache dirs and unassigned devices. I guess some of my dockers causing this. I now stop them all and starting one by one. GM 5 Plus cihaz?mdan Tapatalk kullan?larak gönderildi

After upgrading from 6.1.9 to 6.2.1 automatic spindown is working just on disk2. Manual spindown is working ok. I am aware of the known issue that scsii disks on sas controlers cant be spinneddown but my all disks are sata and most of my disks are on motherboards controller. Edit: After spiningdown manually a few minutes later something is spiningup my drives. Syslog shows some wierd (i guess irrelevant) errors. Just downloaded some subtitles to my cache disk. Oct 11 19:31:57 Tower kernel: mdcmd (82): spindown 0 Oct 11 19:31:57 Tower kernel: mdcmd (83): spindown 1 Oct 11 19:31:58 Tower kernel: mdcmd (84): spindown 2 Oct 11 19:31:59 Tower kernel: mdcmd (85): spindown 3 Oct 11 19:32:00 Tower kernel: mdcmd (86): spindown 4 Oct 11 19:32:00 Tower kernel: mdcmd (87): spindown 6 Oct 11 19:32:01 Tower emhttp: shcmd (41332): /usr/sbin/hdparm -y /dev/sdh &> /dev/null Oct 11 19:34:22 Tower shfs/user: err: shfs_setxattr: lsetxattr: system.posix_acl_access /mnt/cache/No_move/downloaded/sr/Fear.The.Walking.Dead.S02E02.720p.HDTV.x264-AVS[rarbg]/(395028)Fear_the_Walking_Dead_23.976fps_1CD_Turkce_SubRip_DiVXPlanet.rar (22) Invalid argument Oct 11 19:36:35 Tower shfs/user: err: shfs_setxattr: lsetxattr: system.posix_acl_access /mnt/cache/No_move/downloaded/sr/Fear.the.Walking.Dead.S02E03.720p.HDTV.x264-SVA[rarbg]/(395808)Fear_the_Walking_Dead_23.976fps_1CD_Turkce_SubRip_DiVXPlanet.rar (22) Invalid argument Oct 11 19:37:26 Tower shfs/user: err: shfs_setxattr: lsetxattr: system.posix_acl_access /mnt/cache/No_move/downloaded/sr/Fear.the.Walking.Dead.S02E04.PROPER.720p.HDTV.x264-KILLERS[rarbg]/(396651)Fear_the_Walking_Dead_23.976fps_1CD_Turkce_SubRip_DiVXPlanet.rar (22) Invalid argument Oct 11 19:38:41 Tower shfs/user: err: shfs_setxattr: lsetxattr: system.posix_acl_access /mnt/cache/No_move/downloaded/sr/Fear.the.Walking.Dead.S02E05.720p.HDTV.x264-AVS[rarbg]/(411383)Fear_the_Walking_Dead_23.976fps_1CD_Turkce_SubRip_DiVXPlanet.rar (22) Invalid argument Oct 11 19:39:01 Tower shfs/user: err: shfs_setxattr: lsetxattr: system.posix_acl_access /mnt/cache/No_move/downloaded/sr/Fear.the.Walking.Dead.S02E06.720p.HDTV.x264-AVS[rarbg]/(398243)Fear_the_Walking_Dead_23.976fps_1CD_Turkce_Di?er_DiVXPlanet.rar (22) Invalid argument Oct 11 19:39:16 Tower shfs/user: err: shfs_setxattr: lsetxattr: system.posix_acl_access /mnt/cache/No_move/downloaded/sr/Fear.the.Walking.Dead.S02E07.720p.HDTV.x264-AVS[rarbg]/(399204)Fear_the_Walking_Dead_23.976fps_1CD_Turkce_Di?er_DiVXPlanet.rar (22) Invalid argument Oct 11 19:40:40 Tower shfs/user: err: shfs_setxattr: lsetxattr: system.posix_acl_access /mnt/cache/No_move/downloaded/sr/Fear.the.Walking.Dead.S02E08.720p.HDTV.x264-AVS[rarbg]/(407169)Fear_the_Walking_Dead_23.976fps_1CD_Turkce_SubRip_DiVXPlanet.rar (22) Invalid argument Oct 11 19:46:26 Tower shfs/user: err: shfs_setxattr: lsetxattr: system.posix_acl_access /mnt/cache/No_move/downloaded/sr/Fear.the.Walking.Dead.S02E09.720p.HDTV.x264-AVS[rarbg]/(407714)Fear_the_Walking_Dead_23.976fps_1CD_Turkce_SubRip_DiVXPlanet.rar (22) Invalid argument Oct 11 19:46:49 Tower shfs/user: err: shfs_setxattr: lsetxattr: system.posix_acl_access /mnt/cache/No_move/downloaded/sr/Fear.the.Walking.Dead.S02E10.720p.HDTV.x264-AVS[rarbg]/(408372)Fear_the_Walking_Dead_23.976fps_1CD_Turkce_SubRip_DiVXPlanet.rar (22) Invalid argument tower-diagnostics-20161011-1744.zip

Instead of the syslog, we now prefer the diagnostics instead, tells us more (Need help? Read me first!). In particular, I'm wondering what you may be installing from the /boot/plugins folder. Syslog looks mostly OK. Anyone upgrading from 6.1 to any 6.2 should read the first 2 posts of the 6.2 announcement thread, in particular the networking section and Docker section of the Additional Upgrade Advice. I believe you are going to see significant performance issues, due to your tunables and the new tunable, so take note of that section too. i remove the powerdown plugin and manually unmount drives (cant unmount cache) stop array and restart that solves my webgui problem but i guess my docker.img corupted. I recreate it. Now everything seems ok. Thanks for tunables hint, i will keep that in mind if there is any performance issues. BTW there is nothing in /boot/plugins but i m installing CA, cache dirs, dynamix and Unassigned Devices from /boot/config/plugins

i upgrade from 6.1.9 to 6.2.1 from webgui and restart the server. Now i cant reach any webgui neither unraid nor my dockers. But telnet and file sharig seems ok. Syslog is a little odd, no entries after fail2ban. USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.2 0.0 4372 1400 ? Ss 12:35 0:08 init root 2 0.0 0.0 0 0 ? S 12:35 0:00 [kthreadd] root 3 0.0 0.0 0 0 ? S 12:35 0:00 [ksoftirqd/0] root 5 0.0 0.0 0 0 ? S< 12:35 0:00 [kworker/0:0H] root 7 0.0 0.0 0 0 ? S 12:35 0:02 [rcu_preempt] root 8 0.0 0.0 0 0 ? S 12:35 0:00 [rcu_sched] root 9 0.0 0.0 0 0 ? S 12:35 0:00 [rcu_bh] root 10 0.0 0.0 0 0 ? S 12:35 0:00 [migration/0] root 11 0.0 0.0 0 0 ? S 12:35 0:00 [kdevtmpfs] root 12 0.0 0.0 0 0 ? S< 12:35 0:00 [netns] root 14 0.0 0.0 0 0 ? S< 12:35 0:00 [perf] root 255 0.0 0.0 0 0 ? S< 12:35 0:00 [writeback] root 257 0.0 0.0 0 0 ? SN 12:35 0:00 [ksmd] root 258 0.0 0.0 0 0 ? SN 12:35 0:00 [khugepaged] root 259 0.0 0.0 0 0 ? S< 12:35 0:00 [crypto] root 260 0.0 0.0 0 0 ? S< 12:35 0:00 [kintegrityd] root 261 0.0 0.0 0 0 ? S< 12:35 0:00 [bioset] root 263 0.0 0.0 0 0 ? S< 12:35 0:00 [kblockd] root 382 0.0 0.0 0 0 ? S< 12:35 0:00 [ata_sff] root 400 0.0 0.0 0 0 ? S< 12:35 0:00 [devfreq_wq] root 500 0.0 0.0 0 0 ? S< 12:35 0:00 [rpciod] root 529 0.0 0.0 0 0 ? S 12:36 0:00 [kswapd0] root 530 0.0 0.0 0 0 ? S< 12:36 0:00 [vmstat] root 604 0.0 0.0 0 0 ? S 12:36 0:00 [fsnotify_mark] root 621 0.0 0.0 0 0 ? S< 12:36 0:00 [nfsiod] root 624 0.0 0.0 0 0 ? S< 12:36 0:00 [cifsiod] root 636 0.0 0.0 0 0 ? S< 12:36 0:00 [xfsalloc] root 637 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs_mru_cache] root 675 0.0 0.0 0 0 ? S< 12:36 0:00 [acpi_thermal_p root 730 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 735 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 737 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 743 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 746 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 750 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 756 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 759 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 763 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 765 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 766 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 767 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 768 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 769 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 770 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 771 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 772 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 773 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 774 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 775 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 776 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 777 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 778 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 779 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 822 0.0 0.0 0 0 ? S< 12:36 0:00 [vfio-irqfd-cle root 853 0.0 0.0 0 0 ? S< 12:36 0:00 [kpsmoused] root 923 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 929 0.0 0.0 0 0 ? S< 12:36 0:00 [deferwq] root 934 0.0 0.0 0 0 ? S 12:36 0:00 [scsi_eh_0] root 935 0.0 0.0 0 0 ? S< 12:36 0:00 [scsi_tmf_0] root 936 0.0 0.0 0 0 ? S 12:36 0:00 [usb-storage] root 945 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 1082 0.0 0.0 26752 2748 ? Ss 12:36 0:00 /sbin/udevd --d root 1097 0.0 0.0 0 0 ? S 12:36 0:00 [scsi_eh_1] root 1098 0.0 0.0 0 0 ? S 12:36 0:00 [scsi_eh_2] root 1099 0.0 0.0 0 0 ? S< 12:36 0:00 [scsi_tmf_1] root 1100 0.0 0.0 0 0 ? S< 12:36 0:00 [scsi_tmf_2] root 1101 0.0 0.0 0 0 ? S 12:36 0:00 [scsi_eh_3] root 1102 0.0 0.0 0 0 ? S< 12:36 0:00 [scsi_tmf_3] root 1103 0.0 0.0 0 0 ? S 12:36 0:00 [scsi_eh_4] root 1104 0.0 0.0 0 0 ? S< 12:36 0:00 [scsi_tmf_4] root 1105 0.0 0.0 0 0 ? S< 12:36 0:00 [kvm-irqfd-clea root 1106 0.0 0.0 0 0 ? S 12:36 0:00 [scsi_eh_5] root 1108 0.0 0.0 0 0 ? S< 12:36 0:00 [scsi_tmf_5] root 1109 0.0 0.0 0 0 ? S 12:36 0:00 [scsi_eh_6] root 1110 0.0 0.0 0 0 ? S< 12:36 0:00 [scsi_tmf_6] root 1111 0.0 0.0 0 0 ? S 12:36 0:00 [scsi_eh_7] root 1113 0.0 0.0 0 0 ? S< 12:36 0:00 [scsi_tmf_7] root 1115 0.0 0.0 0 0 ? S 12:36 0:00 [scsi_eh_8] root 1117 0.0 0.0 0 0 ? S< 12:36 0:00 [scsi_tmf_8] root 1119 0.0 0.0 0 0 ? S 12:36 0:00 [scsi_eh_9] root 1121 0.0 0.0 0 0 ? S< 12:36 0:00 [scsi_tmf_9] root 1133 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 1134 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 1135 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 1136 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 1137 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 1143 0.0 0.0 0 0 ? S< 12:36 0:00 [scsi_wq_1] root 1144 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 1145 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 1146 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 1148 0.0 0.0 0 0 ? S< 12:36 0:01 [kworker/0:1H] root 1149 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 1150 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 1260 0.0 0.0 233636 2316 ? Ssl 12:36 0:00 /usr/sbin/rsysl message+ 1374 0.0 0.0 19612 236 ? Ss 12:36 0:00 /usr/bin/dbus-d bin 1382 0.0 0.0 13380 176 ? Ss 12:36 0:00 /sbin/rpcbind - rpc 1387 0.0 0.1 21416 5820 ? Ss 12:36 0:00 /sbin/rpc.statd root 1397 0.0 0.0 6484 1664 ? Ss 12:36 0:00 /usr/sbin/inetd root 1406 0.0 0.0 24504 2572 ? Ss 12:36 0:00 /usr/sbin/sshd root 1420 0.0 0.1 98180 4588 ? Ss 12:36 0:00 /usr/sbin/ntpd root 1427 0.0 0.0 4388 112 ? Ss 12:36 0:00 /usr/sbin/acpid root 1436 0.0 0.0 6492 1572 ? Ss 12:36 0:00 /usr/sbin/crond daemon 1438 0.0 0.0 6480 104 ? Ss 12:36 0:00 /usr/sbin/atd - root 1444 0.0 0.1 220176 5520 ? Ss 12:36 0:00 /usr/sbin/nmbd root 1446 0.0 0.3 297204 15444 ? Ss 12:36 0:00 /usr/sbin/smbd root 1448 0.0 0.1 290888 4556 ? S 12:36 0:00 /usr/sbin/smbd root 1449 0.0 0.0 290880 2324 ? S 12:36 0:00 /usr/sbin/smbd root 1453 0.0 0.1 271668 6852 ? Ss 12:36 0:00 /usr/sbin/winbi root 1456 0.0 0.3 273356 12224 ? S 12:36 0:00 /usr/sbin/winbi root 1465 0.1 0.0 9552 2376 ? S 12:36 0:06 /bin/bash /usr/ root 3334 0.0 0.0 19940 3472 ? S 12:36 0:00 /usr/local/sbin root 3350 0.0 0.0 0 0 ? S< 12:36 0:00 [md] root 3351 0.0 0.0 0 0 ? S 12:36 0:00 [mdrecoveryd] root 3359 0.0 0.0 0 0 ? S 12:36 0:00 [spinupd] root 3360 0.0 0.0 0 0 ? S 12:36 0:00 [spinupd] root 3361 0.0 0.0 0 0 ? S 12:36 0:00 [spinupd] root 3362 0.0 0.0 0 0 ? S 12:36 0:00 [spinupd] root 3363 0.0 0.0 0 0 ? S 12:36 0:00 [spinupd] root 3364 0.0 0.0 0 0 ? S 12:36 0:00 [spinupd] root 3388 0.1 0.0 113700 324 ? Ssl 12:36 0:05 /sbin/apcupsd avahi 3408 0.0 0.0 34368 2412 ? S 12:36 0:00 avahi-daemon: r avahi 3409 0.0 0.0 34236 256 ? S 12:36 0:00 avahi-daemon: c root 3417 0.0 0.0 12748 104 ? S 12:36 0:00 /usr/sbin/avahi root 3461 0.0 0.0 0 0 ? S 12:36 0:00 [unraidd] root 3462 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 3463 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 3464 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 3465 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 3466 0.0 0.0 0 0 ? S< 12:36 0:00 [bioset] root 3478 0.0 0.0 0 0 ? S< 12:36 0:00 [reiserfs/md1] root 3488 0.0 0.0 0 0 ? S< 12:36 0:00 [reiserfs/md2] root 3502 0.0 0.0 0 0 ? S< 12:36 0:00 [reiserfs/md3] root 3512 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs-buf/md4] root 3513 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs-data/md4] root 3514 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs-conv/md4] root 3515 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs-cil/md4] root 3516 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs-reclaim/md root 3517 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs-log/md4] root 3518 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs-eofblocks/ root 3519 0.0 0.0 0 0 ? S 12:36 0:00 [xfsaild/md4] root 3530 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs-buf/md6] root 3531 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs-data/md6] root 3532 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs-conv/md6] root 3533 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs-cil/md6] root 3534 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs-reclaim/md root 3535 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs-log/md6] root 3536 0.0 0.0 0 0 ? S< 12:36 0:00 [xfs-eofblocks/ root 3537 0.0 0.0 0 0 ? S 12:36 0:00 [xfsaild/md6] root 3547 0.0 0.0 0 0 ? S< 12:36 0:00 [reiserfs/sdh1] root 3563 0.0 0.0 87740 468 ? Ssl 12:36 0:00 /usr/local/sbin root 3573 0.0 0.0 571488 3872 ? Ssl 12:36 0:00 /usr/local/sbin root 3624 2.0 0.0 0 0 ? D< 12:36 1:20 [loop0] root 3626 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-worker] root 3627 0.0 0.0 0 0 ? S< 12:36 0:00 [kworker/u17:0] root 3628 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-worker-h root 3629 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-delalloc root 3630 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-flush_de root 3631 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-cache] root 3632 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-submit] root 3633 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-fixup] root 3634 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-endio] root 3635 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-endio-me root 3636 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-endio-me root 3637 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-endio-ra root 3638 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-endio-re root 3639 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-rmw] root 3640 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-endio-wr root 3641 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-freespac root 3642 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-delayed- root 3643 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-readahea root 3644 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-qgroup-r root 3645 0.0 0.0 0 0 ? S< 12:36 0:00 [btrfs-extent-r root 3650 0.0 0.0 0 0 ? S 12:36 0:00 [btrfs-cleaner] root 3651 0.0 0.0 0 0 ? S 12:36 0:00 [btrfs-transact root 3655 0.0 0.0 9396 2392 ? S 12:36 0:00 sh -c /etc/rc.d root 3656 0.0 0.0 9524 2492 ? S 12:36 0:00 /bin/sh /etc/rc root 3657 0.0 0.0 6484 1664 ? S 12:36 0:00 logger root 3662 5.5 2.0 269872 78520 ? Sl 12:36 3:41 /usr/bin/docker root 3793 0.0 0.2 200848 9724 ? Sl 12:36 0:00 /usr/bin/python root 3794 0.0 0.0 9524 1856 ? S 12:36 0:00 /bin/sh /etc/rc root 3795 0.0 0.7 195104 27664 ? Sl 12:36 0:00 docker info root 3806 0.0 0.0 6500 1592 tty1 Ss+ 12:36 0:00 /sbin/agetty -- root 3807 0.0 0.0 6500 1588 tty2 Ss+ 12:36 0:00 /sbin/agetty 38 root 3808 0.0 0.0 6500 1608 tty3 Ss+ 12:36 0:00 /sbin/agetty 38 root 3809 0.0 0.0 6500 1516 tty4 Ss+ 12:36 0:00 /sbin/agetty 38 root 3810 0.0 0.0 6500 1656 tty5 Ss+ 12:36 0:00 /sbin/agetty 38 root 3811 0.0 0.0 6500 1560 tty6 Ss+ 12:36 0:00 /sbin/agetty 38 root 3924 0.0 0.0 9396 868 ? S 12:37 0:00 /bin/sh -c /usr root 3925 0.0 0.5 167608 20152 ? S 12:37 0:00 /usr/bin/php -q root 3927 0.0 0.0 25068 3376 ? S 12:37 0:00 wget -qO /dev/n root 3947 0.4 0.0 0 0 ? S< 12:37 0:16 [kworker/u17:1] root 7063 0.0 0.0 0 0 ? S 12:49 0:01 [kworker/u16:2] root 14736 0.0 0.0 0 0 ? S 13:21 0:00 [kworker/0:2] root 15086 0.0 0.4 432804 17776 ? S 13:23 0:01 /usr/sbin/smbd root 15088 0.0 0.1 271668 5948 ? S 13:23 0:00 /usr/sbin/winbi root 15987 0.0 0.1 27064 4372 ? Ss 13:26 0:00 sshd: root@pts/ root 16063 0.0 0.0 13464 3380 pts/0 Ss 13:26 0:00 -bash root 17650 0.0 0.0 0 0 ? S 13:33 0:00 [kworker/u16:1] root 18687 0.0 0.0 0 0 ? S 13:37 0:00 [kworker/0:1] root 19154 0.0 0.0 0 0 ? S 13:39 0:00 [kworker/u16:0] root 19972 0.0 0.0 4368 668 ? S 13:42 0:00 sleep 0.9968907 root 19973 0.0 0.0 11824 2072 pts/0 R+ 13:42 0:00 ps aux syslog.zip

I've already tried this, but Crashplan's logs aren't particularly large. And as I said in my post there don't seem to be any logs internal to crashplan that I can clear or limit the size of. That solves my issue with btsync and couchpotato. SM-N9000Q cihaz?mdan Tapatalk kullan?larak gönderildi