pcss

Thanks, much appreciated!

Hi, original issue recurred today. Diagnostics attached, have not rebooted. Suspected corrupted docker image, deleted it, but now cannot restart docker service. tower-diagnostics-20200903-2111.zip

Will do, thank you. Can I manually flush the cache drive somehow beyond having TRIM enabled on it?

Diagnostics attached. tower-diagnostics-20200825-1840.zip

Hi all, Been having issues with my PiHole docker that escalated to "Docker Service" failed to start errors. I'm not certain if this is limited to the docker image itself or whether it's indicative of something else, hence why I'm posting here first. I've restarted my unRAID box a few times and had things run fine only for things to recur; digging in the logs revealed the following: Aug 25 17:18:14 Tower emhttpd: shcmd (1350): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20 Aug 25 17:18:14 Tower root: truncate: cannot open '/mnt/cache/system/docker/docker.img' for writing: Read-only file system Aug 25 17:18:14 Tower kernel: BTRFS: device fsid a751297c-8ef2-44d2-b96c-1d34e347ff81 devid 1 transid 1598788 /dev/loop3 Aug 25 17:18:15 Tower kernel: BTRFS info (device loop3): disk space caching is enabled Aug 25 17:18:15 Tower kernel: BTRFS info (device loop3): has skinny extents Aug 25 17:18:15 Tower kernel: BTRFS info (device loop3): start tree-log replay Aug 25 17:18:15 Tower kernel: BTRFS warning (device loop3): log replay required on RO media Aug 25 17:18:15 Tower root: mount: /var/lib/docker: can't read superblock on /dev/loop3. Aug 25 17:18:15 Tower kernel: BTRFS error (device loop3): open_ctree failed Aug 25 17:18:15 Tower root: mount error Aug 25 17:18:15 Tower emhttpd: shcmd (1350): exit status: 1 Is this a hardware failure or something else? I'm not seeing any errors at all on any of my drives or the boot flash drive. I'm not certain where to go from here. Appreciate any help, thank you!

Hi all, Not sure what's happened here, successfully updated to 5.2 without issue, went to look at my lists just now and seeing two different issues: 1/ This error in Group Management. Do I need to go through the JSON debugging process or is something else at play here? 2/ This error in settings. Both were not apparent a few days ago and I've not changed anything in my docker or Pi-Hole config that I'm aware of. All help appreciated, thanks! ETA: Tried to restart the docker, got execution error 403 and now cannot start the docker. ETA again: A full restart of my unRAID box has me up and going. I'm glad, but given no changes and no errors on my flash drive or storage drives, I'm thoroughly confused as to what happened and why. Explanation may be helpful for others beyond just myself.

Now in bash for the Pihole container itself but in well over my head. Suspect the script would need changing to work properly within the container context.

Hi all, Apologies if this isn't the right forum, but given it's Pihole related and on unRAID, I thought I'd start here. I want to implement this script https://gitlab.com/grublets/youtube-updater-for-pi-hole/-/tree/master in order to see if I can have better results blocking YouTube ads across my devices. I've followed the readme, edited and saved the file. I am stuck in scheduling it - I've looked at the CA User Scripts plugin but am definitely no cron/linux expert - far from it. Do I need to move this script to the flash drive or is there a way to get it to run as intended so it updates in the background? Thanks!

Thanks! Workaround at the moment is to install the CA Auto Update Applications plugin and then apply it to the docker settings. Now updated correctly and fine.

Hi @spants, forgive the newbie question but will the new template fix the above issue or is this due to something else?

Two things: Also interested in an answer to the above as my Youtube ad blocking is currently broken to the point of not always retaining that I'm signed in. My install currently showing that there's an upgraded docker image available but upon attempting to upgrade, pulls zero data, stops and then restarts the docker. Anyone else seeing the same? Thanks, John

This is now resolved as of the latest update.

No disrespect to AdGuard or those using it but shouldn't discussion about it be in a separate thread?

Other update just now but version numbers haven't changed? Functionality is fine so I'm not 100% sure if I have to go to CLI as the post suggests?

Unexpected update to the docker yesterday - am I on a dev version? Pi-hole Version vDev (HEAD, v4.3-0-g1d43c0a) Web Interface Version vDev (HEAD, v4.3-0-g44aff72) FTL Version v4.3.1

How do I update this docker? I installed using the YouTube video originally referred to. 4.1 is out and it's notifying me of updates. In the docker settings the repo is set to pihole/pihole:latest and I've changed the Docker URL from the diginc to https://hub.docker.com/r/pihole/pihole/ Thanks!

Many thanks Squid, up and going again, very much appreciated!

I pulled the files off the USB manually, no backup via plugin unfortunately.

Failing that, what can I look at from the backup of the old USB to determine what the disk allocations were please?

I managed to get to 6.5.3 using the install tool and transferring my .key file from a backup. I thought transferring disk.cfg would assign disks - this hasn't been the case. I have the files from the existing USB backed up, what should I be doing for the old disks config to be picked up? Thanks!

Sorry to bump this very old topic, but for various reasons I've been unable to attend to this since and *urgently* need any available help in resurrecting my unRAID install. I'm not certain whether using the installer tool on my existing USB will result in loss of licence and/or data. Help greatly appreciated, thank you!

Login prompt reporting 6.3.4, believe the config has been trashed. Using a Sandisk Ultra Fit USB 3.0 on the motherboard header in a HP N40L. I couldn't find a small enough USB 2.0 drive. It's been fine for well over a year. Will try the upgrade files manually.

Hi all, Been stable with no issues for quite a while, previous upgrades OK, saw 6.3.4, downloaded OK, rebooted when prompted, seeing USB read errors in startup. Had this happen once before, USB checked out OK then and (different) USB checks out OK now. Everything plugged into a UPS, no apparent issues during the upgrade. How can I go about recovering this? Thanks, JT

This can be marked as solved now, for some reason the upgrade process trashed the file permissions on the boot USB to the point where logins and other files weren't being read. Rebuilt the USB with config backups and stable on 6.1.4 now.

Definitely FAT32 and perfectly accessible with no errors on two other boxes, no UEFI on boot, yet note the USB device related errors in the attached pics, hence my confusion as this wasn't apparent prior to the upgrade attempt. IMG_0774.jpg.zip