ikosa

Members
  • Posts

    292
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

ikosa's Achievements

Contributor

Contributor (5/14)

0

Reputation

  1. That fixed on my situation too. I'm on 2.9.0 and afraid to click on apply update 😐
  2. Thanks it is enough for me. I can connect my 1.5 and 2tb disks
  3. 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
  4. 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
  5. 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
  6. 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
  7. after 6.8.1 update fail2ban failed to 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 A quick search shows that is related to python installation: https://stackoverflow.com/questions/59269208/errorrootcode-for-hash-md5-was-not-found-not-able-to-use-any-hg-mercurial-co https://stackoverflow.com/questions/59068580/cqlsh-errorrootcode-for-hash-md5-was-not-found https://stackoverflow.com/questions/20399331/error-importing-hashlib-with-python-2-7-but-not-with-2-6 ... Solution: i download and install python-2.7.17-x86_64-2.txz and fail2ban starts without problem. I download and install python-2.7.5-x86_64-1.txz to double check and fail2ban failed to start again. I'm not sure if there is a python update in 6.8.1 but seems like something broken in it.
  8. 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
  9. 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:
  10. 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.
  11. I attached the diags arter restart. tower-diagnostics-20190301-2225.zip
  12. 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
  13. 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?
  14. +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.
  15. 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?