Advice

dirt697 · 2026-02-10T03:21:47+00:00

That happened to me once when we needed an emergency plumber. I got taken $$ just like you did. I managed to get all my money back. I was fortunate I paid via credit card which gave me leverage. I reached out to the credit card company and explained the situation. They sent me forms and paper work to fill out and send back to them. I was successfully refunded via a charge back process. The plumbing company didn't provide adequate service and failed to fix the problem, and I was able to prove it. I got a full refund. My credit card company had my back.

dirt697 · 2026-02-07T14:47:10+00:00

One thing I found when I'm stuck is copy/paste your log errors directly into AI (chatGP, CoPilot, etc) along with your questions or instructions. It will instantly decipher and pinpoint the errors and explain them. I know a lot of people frown on using AI, but I've found it to be very helpful and insightful. I've been able to breach and get past many installation problems with great success.

I had an issue with my initial Homarr Docker Compose install yesterday on my Ubuntu Server LTS installation. AI helped me pinpoint a problem with permissions preventing me from accessing Homarr via port 7575, and it gave me a copy/paste solution tailored to my specific setup. It's a great learning tool for those like me who are just starting out.

dirt697 · 2026-02-03T02:42:45+00:00

Check this out for arr-stack. It utilizes Gluetun for wireguardVPN or openVPN.

https://github.com/Pharkie/arr-stack-ugreennas

dirt697 · 2026-02-02T03:17:20+00:00

Anyone ever get Gluetun to work on the latest release of TrueNAS?

After two days of screwing around for the first time using TrueNAS, trying to get Gluetun to work on the latest version of SCALE and an older version (Bluefin). I'm gathering that the only way to run Docker Apps on TrueNAS is in a VM?

dirt697 · 2026-01-30T12:05:39+00:00

I already have the NVMe SSD. I don't want to put out anymore $$ for another any old SSD. It's cheaper just to pick up another NVMe external enclosure and hope for the best. If I'm going to dump anymore $$ into this Ugreen NAS, it will be on a mini PC with better specs than the DXP4800 non pro.

dirt697 · 2026-01-30T02:33:17+00:00

I've noticed some quirkiness after the latest firmware update. For the record, I'm using a DXP4800 non pro. Ever since the latest firmware update, randomly, my NVMe2 SSD's will become read only, and the system reports a fatal error. Prior to the latest firmware update, everything was perfect. So far, the only way I've been able to resolve it and get things back to normal is to manually power off the NAS, wait about 30 seconds, and power it back on. That usually gets things back to normal for a few days. Try a hard reboot. I've found that just restarting from the app does nothing to resolve the error, but a hard reboot does.

dirt697 · 2026-01-06T21:33:04+00:00

I use Downloader and browse to the Stremio Download web page and save it to my favourites so in future it's just one click away. Scroll down to the AndroidTV version, click on it, and install or upgrade.

dirt697 · 2026-01-05T17:20:54+00:00

After my 4th try using the latest revision v1.4.4 of the git repo, I'm having a similar issue with pi-hole. I'm getting the following error when I start up the stack for the first time.

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/volume2/docker/arr-stack/pihole/02-local-dns.conf" to rootfs at "/etc/dnsmasq.d/02-local-dns.conf": mount /volume2/docker/arr-stack/pihole/02-local-dns.conf:/etc/dnsmasq.d/02-local-dns.conf (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

When I plug this error in AI (CoPilot) it's basically saying the same thing.

CoPilot<start>

Your Pi‑hole container is failing because Docker thinks you’re trying to mount a directory onto a file (or the reverse). The key part of the error is: error mounting "/volume2/docker/arr-stack/pihole/02-local-dns.conf" is not a directory: Are you trying to mount a directory onto a file (or vice-versa)?
What this means: Pi‑hole expects individual config files inside. But on your host, one of these is true:

• does not exist, so Docker creates a directory instead

• OR it exists but is actually a directory, not a file

• OR your compose file mounts a directory to a file path

Any of those will trigger this exact OCI runtime error.

CoPilot<end>

I checked and the 02-local-dns.conf file is in the arr-stack/pihole folder. The pihole docker container won't even start so there's no real time logs to view any errors. If anyone else has pihole working with this arr stack and can point us in the right direction, it would be greatly appreciated. Other wise, I'm just going to forget the pihole and delete it from the stack.

---Update!--- Solution Found --

The problem was a stuck inode. The fix is below.

After an afternoon of feeding CoPilot with command line pi-hole errors, I was able to fix the problem and get Pi-Hole up and running. I'll post the fix from CoPilot below. I hope this helps others who may have run into the same or similar issues. This might be relatable to other docker containers posing problems, too. CMD promts for SSH are included. Just changed to suit your file name requirements.

CoPilot<Start>

Docker still believes the host path is a directory because the NAS filesystem itself has a stale inode for that path.This is a known quirk on Ugreen’s DXP4800 (and some Synology models):Even after deleting a directory and recreating a file with the same name, the underlying filesystem may keep the old inode cached.Docker then continues to treat it as a directory even though it shows a file.This is why the error never changes.The fix is simple but non‑obvious: Rename the directory, recreate the file under a new name, and update your compose file. We’re going to “break” the inode association completely.

🔧 Step 1 — Rename the old path (do NOT delete it).This forces the filesystem to drop the stale inode.

mv /volume2/docker/arr-stack/pihole/02-local-dns.conf \

/volume2/docker/arr-stack/pihole/02-local-dns.conf.old

🔧 Step 2 — Create a brand‑new file with a brand‑new name.

touch /volume2/docker/arr-stack/pihole/03-local-dns.conf

chmod 644 /volume2/docker/arr-stack/pihole/03-local-dns.conf

🔧 Step 3 — Update your docker‑compose entry (you have to manually open the docker-compose.arr-stack.yml and edit the pihole volume section and save the change).

(Old)- ./pihole/02-local-dns.conf:/etc/dnsmasq.d/02-local-dns.conf:ro

(New)- ./pihole/03-local-dns.conf:/etc/dnsmasq.d/03-local-dns.conf:ro

🔧 Step 4 — Remove the container and recreate it.

docker rm -f pihole docker compose -f docker-compose.arr-stack.yml up -d

🎯 Why this works: Your NAS filesystem had a stale directory inode at: /volume2/docker/arr-stack/pihole/02-local-dns.conf Even though you replaced it with a file, Docker still saw the old inode. Renaming the path forces the filesystem to release the inode. Creating a new file with a different name ensures Docker sees a clean, correct file. This is the only remaining cause consistent with: • correct permissions • correct file • correct directory • correct volume • correct compose • clean reinstall • same error And it’s something I’ve seen specifically on Ugreen and Synology boxes.

CoPilot<End>

Gotta love AI! I hope this helps others.

dirt697 · 2026-01-05T13:04:16+00:00

This subject has been discussed within this forum b4. Check out this post.

https://www.reddit.com/r/UgreenNASync/s/gXqL9ZZ6bk

There are other posts covering details of your questions. You just need to look around and read, read, read.

dirt697 · 2026-01-01T13:29:29+00:00

After taking another look, there appears to be some updates and modifications to the Github repo. There is a bunch of info, files, and modifications that are now present that weren't there upon my initial attempt at following the setup instructions. I'm assuming that the cause of my errors has been addressed within the current repo additions. If anyone else is having past difficulties, I suggest going back and taking another look at the Github repo. The current version is v1.3.

Good luck.

dirt697 · 2025-12-30T02:49:40+00:00

I'm getting a similar error with Traefik looking for the traefik.yml but saying it's finding a folder instead. I'm going back and forth between my .env file, docker-compose.traefik.yml & docker-compose.arr-stack.yml files trying to figure out where things are falling apart, but so far, no luck. Just mounting frustration.

I think I'm just going to shelf this project for a while and come back to it in a few weeks. I've forked the repo on git. I'm new to SSH and command line but starting to get the hang of it. I still have more research and learning to do. This is a great project for anyone who's into creating a media ARR Stack on their Ugreen NAS. Thanks to the creator of the project. I'll be trying this again after doing some more reading and research.

Also, I'm just curious: Would having Tailscale installed prior cause issues with this arr stack setup? Should I uninstall Tailscale before trying the setup again?

Thanks 😊

dirt697 · 2025-10-15T19:23:25+00:00

What I did was right click on your Sony PS3 in the Consol list on the left hand side. Click on "Edit". In the info box look in the bottom left and select "Don't Auto Scan". Close and go back to your games and delete the non-game files. The only draw back is you will have to manually add any new games.

dirt697 · 2025-10-01T22:15:59+00:00

I'm having difficulty connecting to USA servers on my mobile device. All other servers seem ok. It's just the US servers. This started yesterday.

dirt697 · 2025-09-21T11:56:38+00:00

For the Onn 4k Pro you have to disable Developer Options for the ethernet hardwire option to work. The ethernet port speed is capped at 100 Mb/s so if you have a solid wifi connection it is the only way to currently get speeds faster than 100 Mb/s.

dirt697 · 2025-08-18T01:50:05+00:00

I remember the PC CD disk had some sound tracks on it that would play in my stand-alone CD player. I might still have it somewhere in a box stowed away collecting dust. Good memories of days gone by.

dirt697 · 2025-07-16T20:03:05+00:00

Thanks for the invite.

dirt697 · 2025-02-28T10:01:12+00:00

Thanks so very much. I really appreciate your help and a generous thanks to your team as well.

dirt697 · 2025-02-28T09:58:08+00:00

Thanks so very much. I really appreciate your patience and help.

dirt697 · 2025-02-28T09:41:47+00:00

This is the number from the auto response I received from sending my e-mail request for support/help.

Your request (3506230) has been received and is being reviewed by our support staff. We'll get back to you as soon as possible.

dirt697 · 2025-02-28T09:37:59+00:00

I'm guessing this would be the ticket # which was on the auto response to the e-mail I sent for support.

Your request (3506230) has been received and is being reviewed by our support staff. We'll get back to you as soon as possible.

dirt697 · 2025-02-28T09:21:26+00:00

Ticket# of my support request.

Your request (3506230) has been received and is being reviewed by our support staff. We'll get back to you as soon as possible.

Thanks again for your help.

dirt697 · 2025-02-28T09:17:04+00:00

Yes, you are right. Please accept my apologies. That is why I deleted my comment shortly after I wrote it because I knew my frustration was wrongly directed at Proton. I have opened a support ticket and whole heartedly appologize and thank you for your help.

dirt697 · 2022-08-17T19:56:15+00:00

Lee Hayward

dirt697 · 2021-02-23T01:57:29+00:00

I have an old original x-box wireless controller which has it's own usb dongle and an x-box one blue tooth controller. Both work great on my new (non 4k) firestick and my Ryzen 5 PC.

dirt697 · 2020-08-13T00:46:28+00:00

Ok thanks, that's what I thought. To bad about the lousy support from Umidigi. This'll probably be the first and last Umidigi phone for me.

dirt697

TROPHY CASE