bmartino1

This is a first after upgrade that a docker disappeared form other beta 4 issues and reports.

GO to WebUI > Docker tab
Then
click add container button
at the top select the template drop down immich.

this should re added the docker from last known setting used and reuse the data already on the system.
 

ok, smart is failing on the drive in question.
runnins stable unraid-6.12.13
 
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.1.106-Unraid] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
Smartctl open device: /dev/sdd failed: INQUIRY failed

dev/sdd is no longer mounit.

I would advise a shutdown of the machine. double check HD cables. But theses are early signs of HD failure.

Potential grab another flash dirve boot to a ubuntu live boot and run diskpart check disk to double check the smart logs on teh disk.
 

copy methods vary.
I personally would use Rsync in this case. I have used mc from terminal in the past.
If the main volumes are ZFS then i would stay ZFS...

 
In Summary:
Use rsync with the proper flags to ensure speed and integrity during transfer.
Format the temporary drives with XFS unless you need ZFS-specific features.
If hard links are important, ensure that all 5 drives are pooled together in a single filesystem.
 
Here's how you can manage your data migration and handle the specifics of your ZFS setup:
Best Way to Move the Files:
CLI with rsync is often the best tool for this kind of large transfer, especially for preserving permissions, timestamps, and hard links. It's also very reliable for resuming transfers in case of interruptions.Example command:

bash Copy code
rsync -aHAXv --progress /source/directory/ /destination/directory/ -a for archive (preserve permissions, symlinks, etc.)
-H for hard links
-A for ACLs
-X for extended attributes
--progress to monitor the transfer speed.
 
Krusader: It’s good for a GUI option but not ideal for large-scale data transfers with complex hard link preservation. Not aware of this on unraid without docker/extra install...
 
Dynamix File Manager/Unassigned Devices: The speeds you're seeing are reasonable for HDDs, but for fine control and reliability, I’d still recommend rsync.
How to Format the 20TB Drive:
 
You don’t necessarily need to format them with ZFS unless you want them to be part of a ZFS pool (for snapshots or other ZFS-specific features). If they are only temporary drives to hold data, XFS is a fine choice as it is widely supported and reliable for general-purpose storage.

If you decide to use ZFS, you’ll be able to take advantage of ZFS’s checksumming, but that’s likely overkill for temporary storage.

Preserving Hard Links:
Hard links refer to the same inode in a filesystem. If you copy files with rsync and use the -H option, it will preserve hard links within the same filesystem.
If you spread these files across multiple filesystems (i.e., if you don’t pool the 5 drives into one filesystem), you’ll break the hard links because hard links can't exist across filesystems. Pooling the 5 drives: If you pool the drives (e.g., using LVM or even ZFS), you’ll ensure that all the files remain within one filesystem and that hard links are preserved.
 
 

Please correct me If I'm misunderstanding you correctly...
 
Your Netowrk Problem Analysis:
Your br2 is associated with VLAN 60, which has a subnet 10.168.60.0/24 with a gateway set at 10.168.60.254. You also have a network br2.80 associated with VLAN 80, with a subnet 10.168.80.0/24 and gateway 10.168.80.254. Containers on br2.80 seem to work correctly, but containers on br2 (VLAN 60) are getting the wrong gateway (10.168.60.1), while you intend them to use 10.168.60.254.

Summary of Key Actions to follow and check:
1 Explicitly Define Gateway in Docker Network.
2 Restart or Recreate Containers to Update Network Settings.
3 Verify Routing Tables on Unraid.
4 Use Docker Options to Set Specific Gateways.

Since your br2 is associated with VLAN 60, which has a subnet 10.168.60.0/24 with a gateway set at 10.168.60.254. You also have a network br2.80 associated with VLAN 80, with a subnet 10.168.80.0/24 and gateway 10.168.80.254. Containers on br2.80 seem to work correctly, but containers on br2 (VLAN 60) are getting the wrong gateway (10.168.60.1), while you intend them to use 10.168.60.254.

1.
Check Docker Network Configuration: The Docker network inspect br2 output doesn't show a defined gateway, which might lead Docker to auto-assign one. This auto-assigned gateway could be 10.168.60.1, which is incorrect.

Action: We Explicitly specify the gateway for the br2 network in Docker....
we will need to recreate br2 and the docker network...
docker network rm br2 docker network create \ -d ipvlan \ --subnet=10.168.60.0/24 \ --gateway=10.168.60.254 \ -o parent=br2 \ br2
2. 
Check Docker Container Configurations: Verify that containers using br2 are configured correctly to use the br2 network. Sometimes, containers may retain old configurations, or they might not automatically update when the network configuration changes.
 
Action: Restart or recreate affected containers using the updated br2 network to apply the changes:

 
docker restart <container_id> # or recreate the container if needed docker rm -f <container_id> docker run --network=br2 <your_container_image> To confirm doecker is using the br2 created above. tempale eidt should see this and be fine...

3.
check ip route
Confirm that the gateway for 10.168.60.0/24 points to 10.168.60.254 and not some other IP. If there’s a misconfigured route, you can add a default gateway for the VLAN 60 subnet:

add additional iprout:
 
ip route add default via 10.168.60.254 dev br2  
Additionally, check if there are any conflicts between VLAN interfaces or IP tables that might be overriding the intended gateway. at router level. trunking needs to be enabled there...

4.
Docker Default Gateway Setting: If you want containers on br2 to use a specific gateway, you may explicitly set a default route for each container using Docker’s --default-gateway option
https://forums.docker.com/t/setting-default-gateway-to-a-container/17420

example docker run command:
 
docker run --network=br2 --default-gateway=10.168.60.254 <your_container_image>
seen in docs:
https://docs.docker.com/engine/network/tutorials/standalone/

https://docs.docker.com/engine/network/

https://stackoverflow.com/questions/45613476/docker-how-to-control-define-default-gateway-settings

can you open unraid web terminal and ping 3 places

ip a
to get current unraid ip info

ping your unraid IP machine
ping your router
ping the public dnd 8.8.8.8
ping google.com

Network setups and to look at:

ping your unraid IP machine
if yes move on if no check your Ethernet cable your have unraid set to a static ip 

ping your router
yes move on,if no... its a dhcp issues from your router and your subnet / cable may be bad.

ping a public dns ip Google is 8.8.8.8
can you ping 8.8.8.8? yes good move on you are making it off internet, if no unraid network settings / router may have an ISP problem and are not talking to the WWW/internet

ping google.com and known web host
if yes no networking issues its something else.. if no, you have internet access but somehow you have lost the ability to resolve dns name.
*this can be caused by improper dhcp setting and/or pihole or other vpn like settings.

Otherwise stop all dockers, turn off autostart, stop all vms, go to settings disable dockers and VM, and lets review your dns / unraid network settings...
 

?This requires a known path that can't be automated due to user intervention... so no...
However, you can install the docker compose plugin and run it via compose..., or make a custom template and add this to unraid.

Since this project is running github python code and then docker run you would need to do follow their instruction on the github.

I would recommend a docker compose method...
Docker Compose: Example Docker Compose file: version: "2.1" services: plex-image-cleanup: image: meisnate12/plex-image-cleanup container_name: plex-image-cleanup environment: - TZ=TIMEZONE #optional volumes: - /path/to/config:/config - /path/to/plex:/plex restart: unless-stopped

so:

mkdir /mnt/appdata/pleximagemain
cd /mnt/appdata/pleximagemain
git https://github.com/Kometa-Team/ImageMaid.git

cd ImageMaid

Unraid: New stack 
Advance past file path:
/mnt/appdata/pleximagemain ? ? ? gits folder....

then add the compose file... map to plex data fodler  and plex config folder of already running docker...

so the volume would need edited in the example compose... I use Linux IO ploex docker


so my config folder is xyz

not sure of the git hubs script and not that interested. I don't want a 3rd paty thing touching my plex system..
As you can see I don't have a /plex and not sure what path its referring to? data media libary? etc daemon? etc...

 
beside, a similar and potential better may already exist with in unraid but may require similar path access to your Plex system:

 

yes, its a good card.

From my experience, AliExpress can be less than eBay in terms of quality of goods. Fujitsu is an established known brand for electronics. There are  known for their storage and electronics (more semiconductors) in the USA. If that card fits your needs 12 GB transfer speeds, 8 disk connection.
Site Tech specs: https://www.fujitsu.com/au/products/computing/servers/primergy/components/pmod-157814.html#specs

Be sure to find one in IT mode.

With alliexpress watch the sellers. I've gotten really good hardware and really bad hardware from alliexpress. Then link i sent is from a known seller who handles there products well.

Welcome back. I will try to rewrite the installation procedures to reproduce. There's a lot and i used this as notes/sound board.

Assumptions:
I assume you already have a data spot in mind and the compose plugin installed.
I chose /mnt/user/appdata

Step 1 
open terminal and go to the installation path of your choosing.


I chose to keep this together with my docker data.
Unraid terminal script setup: run one line at a time (./config is the config folder where your dat path is)
#It is best to use full paths. ./config/ in my case is /mnt/user/appdata/netprobe_lite/config #Download GitHub project and files/scripts cd /mnt/user/appdata git clone https://github.com/plaintextpackets/netprobe_lite.git #enter project to make changes cd netprobe_lite/ #step 1 prepare for unraid UI rename existing compose file cp compose.yml compose.yml.org rm compose.yml #step 2 prepare for better docker Data path to keep between docker updates. #First Grafana: cd ./config/grafana #echo make save location to keep Grafana data mkdir data cd data #echo copy the dashboard to correct spot -- missing data that we changed in compose(I use MC to copy the folder): cp -R ./config/grafana/dashboards ./config/grafana/data/ #echo Recreate the empty folder paths Grafana needed for latter use inside the “./config/grafana/data/” (issue in past with docker not making folder needed Docker should make this at first run): cd data mkdir csv mkdir pdf mkdir plugins mkdir png #echo fixing grafana files and paths(grafana entprise config) docker should make these at first run this should be in “./config/grafana/data/”: mkdir alerting cd alerting mkdir 1 cd 1 touch __default__.tmpl cd .. cd .. touch grafana.db #Next Promethus - The actual data that needs saved to keep between dockers updates and deletion! “./config/prometheus" makin its "/data/” location #Drop back to config folder “./config/”: cd .. cd .. cd prometheus/ mkdir data #Fix permission – set unraid docker safe perms….: #Drop back to config folder: cd .. #setting unraid docker safe permissions to config folder only!: #echo setting correct docker permissions “./config/”: chmod 777 -R * chown nobody:users -R *
Step 2 setup docker compose:
our data exist: at /mnt/user/appdata/netprobe_lite/


 
This will make the compose file we use in unraid and import the .env file used to configure and control netprobe.
Next we want to edit the stack:





Step 3 env file first:
Github default env file: https://github.com/plaintextpackets/netprobe_lite/blob/master/.env
we want to make a few changes:

DOUBLE CHECK YOUR .ENV FILE FOR IP and EDITS YOU WANT. If you start this docker and then edit this Grafana may display weird by picking up the data in the Prometheus database. You will need to delete the contents of the “./config/prometheus/data this will erase all collected data and use the env file config.
 
^Here we enabled speedtest it runs every hour.
I then set a custom dns IP(I run Pihole) if you don't run a in house dns server use opendns 208.67.222.222 it will be labled as My_DNS_Server
*^ Do NOT! Change the name the grafana main and other dashboard file call it weirdly to display correctly.

I run piehole docker, a custom DNS, and it currently set to that IP.

Step 4:
Then edit the docker compose file with the following edits:
 
^Here is my working unraid Compose file that keeps data. Note the Compose items for lables, theses http links and data go in the UI lables when prompted. This adds the docker image to the docker tab.

You can set an admin account at this time by editing the grafana section option of ...
 
environment: - GF_SECURITY_ADMIN_USER=admin - GF_SECURITY_ADMIN_PASSWORD=admin
Default admin/admin

Then set the UI labels (compose no longer fills in the data.)


^In the UI lables copy from the compose file

your 10 TB drive may me a shingled cached drive.
https://en.wikipedia.org/wiki/Shingled_magnetic_recording

Their is nothing wrong with the HD. it just doesn't have a high cache partition via the manufacture which is why a large data transfer that a parity / data rebuild is, is slow.

the blue circle and the one in green is the default grbu boot options. to boot in gui mode open unraid web ui

Main > Flash Drive
Main/Settings/Flash?name=flash



and select the Unraid OS GUI Mode 

click apply at bottom.

Glad that worked: Sometimes we just need to clear the acpi table created by mobo bios...
Correct it mainly debugging acpi:
https://wiki.ubuntu.com/DebuggingACPI

mainly its a kernel bug caused by bios... Make sure the mote board is on the latest bios revision.
some other users reported that keeping a keyboard/mouse pluged in - replug in fixes the issues.
https://forums.unraid.net/topic/116612-692-cpu-cores-stuck-at-100-2-coresthreads/?do=findComment&comment=1076132

 
Other claim fault driver plugins at boot:
https://forums.unraid.net/bug-reports/stable-releases/692-cpu-usage-stuck-at-100-2-corethread-r1279/?do=findComment&comment=13471
 
 

unraid web ui not responding?
Did you change unraid web ui port to 88? or docker?

Have you tried a reboot of the machine via power button
is nginx server running?
rc.nginx status

Option 1: in place upgrade prepare 
Main > Flash > Download backup

stop all vm
stop all dockers
Unraid setting disable vm and dockers!

Compatibility plugins
delete all plugins.
^-Only keep the CA defaults!
Ones you can keep: ZFS(any and all) / FCP / tips n tweaks / drivers plugin if installed...

Then go to unraid web UI and upgrade.Folow the pormpts and what it says!
boot and you may have to turn off machine. Plug flash drive in and delete the network config due to 6.12 changes... to fix networking and boot. Web UI login add previous plugins... enable vms / dockers ... etc..

Option 2: Recommend due to old version installed... restore via recovery option on same usb to not lose license!

Main > Flash > Download backup
plugin flash drive into another computer
copy config folder off flash drive
reformat drive and manual install latest unraid to flash
run make botable
copy config folder to flash drive
(may still have to go into config folder and delete network config...)
boot to unraid

Terminal commands:

ip a

netstat -i

ifconfig

ifconfig bond0 down
any errors?

ifconfig br0 down
any errors?
 
ifconfig eth0 down
any errors?

and then

ifconfig eth0 up
ifconfig br0 up

you most likely have a docker or other application set to auto start and that docker is replacing or claiming port 80 of the host.

ok then what are you docker settings?

what dockers are you running. are any in host mode?
if in host that docker will replace all of unraids ports including port 53 needed for dns.
 

its supposed to be full. problay a bad dhcp server response to generate and get...

go to settings network and set them manual:

smb is the servers service that you would edit for traffic over the interface.
We don't have access to edit the main unraid servers services config like other linux distro...
NFS is a different server config and has its own config type to set interfaces. NFS is harder to manipulate than smb for share settings. OP was not clear in how they were sharing...

In unriad this is not possible without editing the core service config and setting them to the desired interfaces.
Unraids networking is aimed at the end users for a point and click. 

 

yes

install plugin:


 

found my notes for the grub otion.
 
 
pcie_acs_override=downstream,multifunction vfio_iommu_type1.allow_unsafe_interrupts=1

your 
Label GPU passthrough mode
  menu default
  kernel /bzimage
  append initrd=/bzroot video=vesafb:off,efifb:off,simplefb:off,astdrmfb initcall_blacklist=sysfb_init pci=noaer pcie_aspm=off pcie_acs_override=downstream,multifunction options vfio_iommu_type1 allow_unsafe_interrupts=1

so add the vfio_iommu_type1.allow_unsafe_interrupts=1. test adding all three iommu options as well. 

amd_iommu=on iommu=pt intel_iommu=on

so
 
Label GPU passthrough mode   menu default   kernel /bzimage   append initrd=/bzroot video=vesafb:off,efifb:off,simplefb:off,astdrmfb initcall_blacklist=sysfb_init pci=noaer pcie_aspm=off pcie_acs_override=downstream,multifunction options vfio_iommu_type1 allow_unsafe_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 amd_iommu=on iommu=pt intel_iommu=on  

Can you access any other 2.x address such as your router over the tunnel? if yes its your docker 2.208 settings. if no its network/routing issue.
 
Other than the bad route data. as metric should be 1 but that line ipv4 192.168.2.208 wg0 is not a good data rout. that's telling unraid that ip goes to interface wg0 no traffic would be making it across.

I belie you should disable bridging. this may be causing a macvlan trace issue.
Otherwise, set docker setting to ipvlan.
 
You may also need to reboot the device.