spants

@JohnSracic the best place for this question is http://discourse.nodered.org but if you can export that part of your flow (just the bit with your timers) and PM it me, I will sort it out for you.

I decided to scrap the DNS323 and use a PI with SSH/SFTP connection with rclone instead. If the connection fails for any reason, it shouldn't then affect my server.

Thanks for the info!

same here - was during an rsync clone to a remote smb mounted connection. I think that the connection dropped but Unassigned devices still accepted the data (maybe caching in ram until it was full?)

Sometimes my unit SMB server (I have an old DNS323 dlink unit with ALT-F firmware that supports larger drives) sleeps (or disconnects) and my rclone beta backup then seems to write to /mnt/disks/xxxxxx (or RAM?) causing my unraid to lock up. Not sure if its Unassigned devices or the external unit causing the problem. Can RClone talk to an SMB share with user/password?

Your unraid DNS should be static and point to a real DNS server. If your router is sending out DNS requests that point to pihole and the docker is down, unraid will not get outside!

Managed to get the disk mounted by running the xfs_repair with -L parameter. Lots of data in lost/found.... Will move the data off the disks and restore the important files from the backup.

So I have noticed a disk problem just before it completely failed. I decided to do a Plan with unBalance (no writing to disks) to see if I could move the files from the emulated disk to real ones..... it started reading then the disk 7 disappeared completely... What is the best way to proceed without losing the data on the emulated disk? This is the log for the disk 7 error. I am now on 6.7.2 Nov 10 23:55:20 Tower kernel: XFS (md7): Mounting V4 Filesystem Nov 10 23:55:20 Tower kernel: XFS (md7): Starting recovery (logdev: internal) Nov 10 23:55:21 Tower kernel: XFS (md7): Internal error XFS_WANT_CORRUPTED_GOTO at line 1862 of file fs/xfs/libxfs/xfs_alloc.c. Caller __xfs_free_extent+0xdf/0x146 [xfs] Nov 10 23:55:21 Tower kernel: CPU: 3 PID: 14896 Comm: mount Not tainted 4.19.56-Unraid #1 Nov 10 23:55:21 Tower kernel: Hardware name: System manufacturer System Product Name/P8Z68-V PRO, BIOS 3603 11/09/2012 Nov 10 23:55:21 Tower kernel: Call Trace: Nov 10 23:55:21 Tower kernel: dump_stack+0x5d/0x79 Nov 10 23:55:21 Tower kernel: xfs_free_ag_extent+0x3d2/0x5ff [xfs] Nov 10 23:55:21 Tower kernel: __xfs_free_extent+0xdf/0x146 [xfs] Nov 10 23:55:21 Tower kernel: xfs_trans_free_extent+0x27/0x5d [xfs] Nov 10 23:55:21 Tower kernel: xfs_efi_recover+0x14b/0x199 [xfs] Nov 10 23:55:21 Tower kernel: xlog_recover_process_efi+0x2d/0x43 [xfs] Nov 10 23:55:21 Tower kernel: xlog_recover_process_intents+0xa6/0x1b0 [xfs] Nov 10 23:55:21 Tower kernel: xlog_recover_finish+0x13/0x80 [xfs] Nov 10 23:55:21 Tower kernel: xfs_log_mount_finish+0x5a/0xc3 [xfs] Nov 10 23:55:21 Tower kernel: xfs_mountfs+0x50d/0x72f [xfs] Nov 10 23:55:21 Tower kernel: ? xfs_mru_cache_create+0x12b/0x151 [xfs] Nov 10 23:55:21 Tower kernel: xfs_fs_fill_super+0x448/0x527 [xfs] Nov 10 23:55:21 Tower kernel: ? xfs_test_remount_options+0x53/0x53 [xfs] Nov 10 23:55:21 Tower kernel: mount_bdev+0x12f/0x17c Nov 10 23:55:21 Tower kernel: mount_fs+0x10/0x6b Nov 10 23:55:21 Tower kernel: vfs_kern_mount+0x62/0xfa Nov 10 23:55:21 Tower kernel: do_mount+0x7b3/0xa2f Nov 10 23:55:21 Tower kernel: ? __kmalloc_track_caller+0x65/0x122 Nov 10 23:55:21 Tower kernel: ? _copy_from_user+0x2f/0x4d Nov 10 23:55:21 Tower kernel: ? memdup_user+0x39/0x55 Nov 10 23:55:21 Tower kernel: ksys_mount+0x6d/0x92 Nov 10 23:55:21 Tower kernel: __x64_sys_mount+0x1c/0x1f Nov 10 23:55:21 Tower kernel: do_syscall_64+0x57/0xf2 Nov 10 23:55:21 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Nov 10 23:55:21 Tower kernel: RIP: 0033:0x14ee3912bfca Nov 10 23:55:21 Tower kernel: Code: 48 8b 0d c9 7e 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 96 7e 0c 00 f7 d8 64 89 01 48 Nov 10 23:55:21 Tower kernel: RSP: 002b:00007ffe41fa7648 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5 Nov 10 23:55:21 Tower kernel: RAX: ffffffffffffffda RBX: 000000000040d2b0 RCX: 000014ee3912bfca Nov 10 23:55:21 Tower kernel: RDX: 000000000040d4c0 RSI: 000000000040d540 RDI: 000000000040d520 Nov 10 23:55:21 Tower kernel: RBP: 000014ee392baf24 R08: 0000000000000000 R09: 0000000000000000 Nov 10 23:55:21 Tower kernel: R10: 0000000000000c00 R11: 0000000000000206 R12: 0000000000000000 Nov 10 23:55:21 Tower kernel: R13: 0000000000000c00 R14: 000000000040d520 R15: 000000000040d4c0 Nov 10 23:55:21 Tower kernel: XFS (md7): Internal error xfs_trans_cancel at line 1041 of file fs/xfs/xfs_trans.c. Caller xfs_efi_recover+0x15e/0x199 [xfs] Nov 10 23:55:21 Tower kernel: CPU: 3 PID: 14896 Comm: mount Not tainted 4.19.56-Unraid #1 Nov 10 23:55:21 Tower kernel: Hardware name: System manufacturer System Product Name/P8Z68-V PRO, BIOS 3603 11/09/2012 Nov 10 23:55:21 Tower kernel: Call Trace: Nov 10 23:55:21 Tower kernel: dump_stack+0x5d/0x79 Nov 10 23:55:21 Tower kernel: xfs_trans_cancel+0x52/0xcd [xfs] Nov 10 23:55:21 Tower kernel: xfs_efi_recover+0x15e/0x199 [xfs] Nov 10 23:55:21 Tower kernel: xlog_recover_process_efi+0x2d/0x43 [xfs] Nov 10 23:55:21 Tower kernel: xlog_recover_process_intents+0xa6/0x1b0 [xfs] Nov 10 23:55:21 Tower kernel: xlog_recover_finish+0x13/0x80 [xfs] Nov 10 23:55:21 Tower kernel: xfs_log_mount_finish+0x5a/0xc3 [xfs] Nov 10 23:55:21 Tower kernel: xfs_mountfs+0x50d/0x72f [xfs] Nov 10 23:55:21 Tower kernel: ? xfs_mru_cache_create+0x12b/0x151 [xfs] Nov 10 23:55:21 Tower kernel: xfs_fs_fill_super+0x448/0x527 [xfs] Nov 10 23:55:21 Tower kernel: ? xfs_test_remount_options+0x53/0x53 [xfs] Nov 10 23:55:21 Tower kernel: mount_bdev+0x12f/0x17c Nov 10 23:55:21 Tower kernel: mount_fs+0x10/0x6b Nov 10 23:55:21 Tower kernel: vfs_kern_mount+0x62/0xfa Nov 10 23:55:21 Tower kernel: do_mount+0x7b3/0xa2f Nov 10 23:55:21 Tower kernel: ? __kmalloc_track_caller+0x65/0x122 Nov 10 23:55:21 Tower kernel: ? _copy_from_user+0x2f/0x4d Nov 10 23:55:21 Tower kernel: ? memdup_user+0x39/0x55 Nov 10 23:55:21 Tower kernel: ksys_mount+0x6d/0x92 Nov 10 23:55:21 Tower kernel: __x64_sys_mount+0x1c/0x1f Nov 10 23:55:21 Tower kernel: do_syscall_64+0x57/0xf2 Nov 10 23:55:21 Tower kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Nov 10 23:55:21 Tower kernel: RIP: 0033:0x14ee3912bfca Nov 10 23:55:21 Tower kernel: Code: 48 8b 0d c9 7e 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 96 7e 0c 00 f7 d8 64 89 01 48 Nov 10 23:55:21 Tower kernel: RSP: 002b:00007ffe41fa7648 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5 Nov 10 23:55:21 Tower kernel: RAX: ffffffffffffffda RBX: 000000000040d2b0 RCX: 000014ee3912bfca Nov 10 23:55:21 Tower kernel: RDX: 000000000040d4c0 RSI: 000000000040d540 RDI: 000000000040d520 Nov 10 23:55:21 Tower kernel: RBP: 000014ee392baf24 R08: 0000000000000000 R09: 0000000000000000 Nov 10 23:55:21 Tower kernel: R10: 0000000000000c00 R11: 0000000000000206 R12: 0000000000000000 Nov 10 23:55:21 Tower kernel: R13: 0000000000000c00 R14: 000000000040d520 R15: 000000000040d4c0 Nov 10 23:55:21 Tower kernel: XFS (md7): xfs_do_force_shutdown(0x8) called from line 1042 of file fs/xfs/xfs_trans.c. Return address = 000000007285336a Nov 10 23:55:21 Tower kernel: XFS (md7): Corruption of in-memory data detected. Shutting down filesystem Nov 10 23:55:21 Tower kernel: XFS (md7): Please umount the filesystem and rectify the problem(s) Nov 10 23:55:21 Tower kernel: XFS (md7): Failed to recover intents Nov 10 23:55:21 Tower kernel: XFS (md7): log mount finish failed Nov 10 23:55:21 Tower root: mount: /mnt/disk7: mount(2) system call failed: Structure needs cleaning. Nov 10 23:55:21 Tower emhttpd: shcmd (71): exit status: 32 Nov 10 23:55:21 Tower emhttpd: /mnt/disk7 mount error: No file system Nov 10 23:55:21 Tower emhttpd: shcmd (72): umount /mnt/disk7 Nov 10 23:55:21 Tower root: umount: /mnt/disk7: not mounted.

could it be related to this:

That's not a pinhole template problem. I've seen it on several apps before and I think an update to unraid fixed it? ( Or was it a patch? )

@BRiTGoogle drive does enforce the 1TB limit - I just hit it.... (using legacy google apps account)

For some reason the github client doesnt update the repository quickly - have deleted pihole-template and changed pihole to use the new settings. Also uploaded a new node red

yes - I will need to create a new template for it (hopefully today) as some of the parameters have changed. Just a note: I have only created the simple template for this - it is the official docker underneath.

Thanks for posting - was just about to!

I think that there is a problem with the unraid tool that checks upgrades.....lots of people seeing it with linuxserver dockers. There were some threads about it. Just boarding flight so cant look! Sent from my SM-N950F using Tapatalk

I must get round to cleaning the instructions, unfortunately I travel alot for work so that becomes difficult. With unraid, if you make changes to the template these are not seen by existing users.... the only way seems to be to create a new pihole app. Just to be clear, my only involvement with pihole is to create the original template for unraid. I dont touch the docker files at all. Hopefully a new template in a week! Sent from my SM-N950F using Tapatalk

Wondering if it is due to this error? I remember someone else having that and solving it.... Unfortunately I am traveling - take a look back through this thread, it might be there,

I know it isn't going to help, but it works for me! (but I do not use a reverse proxy for it)

I had something similar - so I used the userscripts plugin to restart it daily... Content of the script: (hope it helps) #!/bin/bash docker restart ZeroTier

You need to ask here: https://github.com/pi-hole/docker-pi-hole I only did a simple template

What you are seeing is normal. You can instead change the DHCP server in your router to hand out piholes IP as the dns server and then you will see the clients IP. (or just use pihole as the dhcp server)

Yes, the Linux server guys had a look at it. It just needs a template as the docker is already built (like pihole)

yes - it works well in this way... My settings are here (pihole on 192.168.1.24) pihole network settings

apologies - you may be right if you only have one network adaptor..... I have two in my system.

Yes - if you have openvpn installed, you can look at admin panel (I tested it). If you want to block advertisements whilst remote, you will need to look at routing all traffic over vpn and that your dns is pointing to pihole.