Hi everyone, 

 

I have a long running unraid box and was hoping to get help with cleaning up some issues found after running the "Fix Common Problems" plugin . The configuration has been running since 2015 and I can't even remember what OS version I started with at this point.

 

Along with the errors reported by "Fix Common Problems", I have observed the following issues:

- the system sometimes has to be force restarted using the power button due to it not responding. 

- Transmission docker instance seems to be saving downloads using permissions that do not allow me to open the files after download. I have to use chmod 777 to be able to move or rename the downloaded directories.

- Pihole docker instance does not save password reset if rebooted after changing it.

 

Recent changes:

- migrated my build to new HDDs while keeping the original USB drive and other components.

- added a 10 Gbit for testing and had it assigned to an iperf instance.

 

The errors I'm getting in my report are:

 

Any help or direction would be greatly appreciated. 

Edited January 11, 20251 yr by adamthepolak

some of that can be ignored. I would look into the Marvel Drive Controler. I think there a driver plugin...

SO, lets start with the ones in red. You can click more info and it will driect you to a post on the forum that Squid worte for the FCP

It appears you madea share name called flash

flash is not reserved for the unraid USB Drive.

the zfs pool name can't be named flash, a share named can't be named this. You will need to make a new share call it something else and the data off flash and into the new share.
*UNLESS! you enabled the flash drive public share. Regardless for each error there is a more information tab that will link to the forum and how to resolve. If its is non UNriad Breaking. You can ignore it. Things like jumbo frames. or addition plugin support Unassigned drives plus. However the FCP is a decent best practice standard for unraid.

what unraid version are you runnign as I run FCP and don't have it complanning about Macvlan or similar....

 

 

fixing the flash storage adn marvle driver may fix your restart and power opptions.

transmission may require adition varbiles.
0- root

99 - nobody

100 - users

 

add puig and pgid:

potential a umask....

 

as seen here:

 

whciih pihole docker are you running?
if you click console and run the pihole 

 

 

you need to run the password command to set a new password. stop the docker then start the docker as the confg didn't save nor update configuration. Otherwise, your pihole folder appdata pathing is bad and the /etc pihole folder is not geting saved across docker starts...

I've taken care of most of the finding:

• Share flash is identically named to a disk share AND
• Reserved user share flash
  • Confirmed my flash drive was not set to Export
  • Confirmed directory was empty
  • Renamed directory, rebooted, no issues and confirmed error no longer reported in FCP
• Macvlan and Bridging found
  • followed https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces
  • changed "Docker custom network type" from macvlan to ipvlan
  • confirmed error no longer reported in FCP
• Share Docker /set to not use the cache, but files / folders exist on the cache drive
  • enabled cache drive use for Docker share
• Jumbo Frames detected on eth1
  • changed MTU to 1500
  • disabled eth1 since I'll be taking this card out soon
• Marvel Hard Drive Controller Installed
  • I'm going to leave this for now. I haven't experienced random drive droppings offline.
• Unassigned Device Plus not installed
  • I do have an unassigned device but it's not being used. Marking IGNORE.
• Transmission Permissions

  • Quote

    21 hours ago, bmartino1 said:

    fixing the flash storage adn marvle driver may fix your restart and power opptions.
    
    transmission may require adition varbiles.
    0- root

    99 - nobody

    100 - users

     

    add puig and pgid:

    

    

    potential a umask....

     

    as seen here:

     

     

     

  • I followed your recommendation and added the variables, it seems to be working now.
• pihole

  • Quote

    21 hours ago, bmartino1 said:

    whciih pihole docker are you running?
    if you click console and run the pihole 

     

     

    you need to run the password command to set a new password. stop the docker then start the docker as the confg didn't save nor update configuration. Otherwise, your pihole folder appdata pathing is bad and the /etc pihole folder is not geting saved across docker starts...

     

     

  • left this for last. I completed the password reset once more, confirmed I could log in, restarted the docker instance and the credentials didn't work again.
  • Version info
    • # pihole -v
        Pi-hole version is v5.18.3 (Latest: v5.18.4)
        web version is v5.21 (Latest: v5.21)
        FTL version is v5.25.2 (Latest: v5.25.2)
  • Could this be related to the my Share Settings? 

Awesome, looks like FCP helped and you were able to go through write a bit. What docker version of piehole are you running?

 

this may also be set in the docker template.

I personally would recommend making a piehole backup deleting your current docker. reinstall this docker sets password with docker template. and teleport to restore your previous pihole settings.

 

you may need to add the varible. 

 

I would recomend moving to a dot/DOH version due to changed within DNS an age of the orgianl pihole system. as this is more a evolution.