unRAID OS version 6.5.0-rc1 available


97 posts in this topic Last Reply

Recommended Posts

  • Replies 96
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Thanks, yes that is a bug. Corrected.

On 6.5.0-rc1, when I run update-smart-drivedb, it returns an error: root@TowerVM:~# update-smart-drivedb /usr/sbin/update-smart-drivedb: gpg: not found ('--no-verify' to ignore) Turns out that

An extra check is now added during system start up and network initialization, this error should be fixed in the next version.

Posted Images

8 hours ago, dlandon said:

Doing that would save a lot of support requests.

Hiding the initial warning about disk UDMA ECC errors would also save a lot of support requests.

Link to post
32 minutes ago, pwm said:

Hiding the initial warning about disk UDMA ECC errors would also save a lot of support requests.

 

True, but it requires a big rewrite of the underlying SMART detection and reporting system, while removing the superfluous metric value in the network config file is just a one-liner.

Link to post
9 minutes ago, bonienl said:

 

True, but it requires a big rewrite of the underlying SMART detection and reporting system, while removing the superfluous metric value in the network config file is just a one-liner.

Does it really?

 

The current code obviously has to make a comparison whenever it sees smart data to see if the ECC count has changed.

 

Wouldn't it be enough to have lack of state in the state data (or possibly a -1 value) mean that you can directly auto-freeze (auto-acknowledge) the first SMART ECC value you get access to. So you don't do any big rewrites but handles it as a "lazy acknowledge" when you notice you don't have any valid watermark value for that specific disk.

Link to post
4 minutes ago, dlandon said:

I just updated my main server and now I can't specify br0 on dockers to set the IP address.  How do I do that now?

 

Can you post a screenshot of the Docker settings page (with Docker stopped and advanced on)

Link to post
3 minutes ago, bonienl said:

 

Can you post a screenshot of the Docker settings page (with Docker stopped and advanced on)

Here you go:

5a9926a5c8b12_DockerNetwork.thumb.png.1ca899e179183c9be4bc36046f63e5f2.png

br0 never shows up in the docker network choices.

Link to post
3 minutes ago, pwm said:

Does it really?

 

Yes, it does.

 

The current implementation reports a SMART issue for any of the monitored SMART values the first time system is started. That is desired because users need to be warned the first time when there are potential issues. "UDMA CRC errors" follow the same logic, but you are asking for an exception here.

Link to post
1 minute ago, bonienl said:

 

Yes, it does.

 

The current implementation reports a SMART issue for any of the monitored SMART values the first time system is started. That is desired because users need to be warned the first time when there are potential issues. "UDMA CRC errors" follow the same logic, but you are asking for an exception here.

It only occurs once when updating and is not that big a deal.  I don't think creating an exception is a good idea.

Link to post
1 minute ago, bonienl said:

 

Yes, it does.

 

The current implementation reports a SMART issue for any of the monitored SMART values the first time system is started. That is desired because users need to be warned the first time when there are potential issues. "UDMA CRC errors" follow the same logic, but you are asking for an exception here.

But after the user acknowledges it, the system remembers the watermark value. Isn't that watermark value saved so it survives the next reboot?

 

Link to post
6 minutes ago, dlandon said:

br0 never shows up in the docker network choices.

 

Looks like it failed to create 'br0' under Docker. A quick workaround is:

rm /var/lib/docker/network/files/local-kv.db
/etc/rc.d/rc.docker restart

For my understanding: did you make any setting modifications or it failed right away after upgrading?

 

Link to post
2 minutes ago, bonienl said:

 

Looks like it failed to create 'br0' under Docker. A quick workaround is:


rm /var/lib/docker/network/files/local-kv.db
/etc/rc.d/rc.docker restart

For my understanding: did you make any setting modifications or it failed right away after upgrading?

 

local-kv.db does not exist.

 

I updated with the array not starting on reboot, made some changes to the network gateway address, then started the array.

Link to post
3 minutes ago, pwm said:

But after the user acknowledges it, the system remembers the watermark value. Isn't that watermark value saved so it survives the next reboot?

 

 

Yes, it is stored on the flash device. Any new notification is only generated if the SMART value changes as compared to the last known (=stored) value.

Link to post
1 minute ago, bonienl said:

 

Yes, it is stored on the flash device. Any new notification is only generated if the SMART value changes as compared to the last known (=stored) value.

 

find-watermark-for-drive;

if no-persistant-ecc-for-drive {

    save-as-current-watermark

}

if ecc != saved-value {

    emit-event

    save-as-current-watermark

}

Edited by pwm
Link to post
5 minutes ago, dlandon said:

local-kv.db does not exist.

 

That's weird. Docker creates this file immediately after it is started (if not present). It holds all docker network assignments.

 

If you do a "rc.docker restart" from CLI, still this db file isn't there?

 

Link to post
1 minute ago, bonienl said:

 

That's weird. Docker creates this file immediately after it is started (if not present). It holds all docker network assignments.

 

If you do a "rc.docker restart" from CLI, still this db file isn't there?

 

Sorry, I did it with the docker stopped.  If the docker is started it is there.

 

I rolled back and now 6.4.1 has the same problem.  What do I need to do to get out of this problem on either version?

Link to post
10 minutes ago, dlandon said:

I updated with the array not starting on reboot, made some changes to the network gateway address, then started the array.

 

Can you post your docker.cfg file, it is under /config on your flash device.

Link to post
4 minutes ago, dlandon said:

I rolled back and now 6.4.1 has the same problem.  What do I need to do to get out of this problem on either version?

 

With docker started :)

rm /var/lib/docker/network/files/local-kv.db
/etc/rc.d/rc.docker restart

 

Link to post
13 minutes ago, bonienl said:

 

Can you post your docker.cfg file, it is under /config on your flash device.

I decided to stay on 6.5.0 and sort through this issue.

10 minutes ago, bonienl said:

rm /var/lib/docker/network/files/local-kv.db /etc/rc.d/rc.docker restart

This did not resolve the problem.

 

docker.cfg:

DOCKER_ENABLED="yes"
DOCKER_IMAGE_FILE="/mnt/cache/system/docker/docker.img"
DOCKER_IMAGE_SIZE="15"
DOCKER_APP_CONFIG_PATH="/mnt/cache/appdata/"
DOCKER_APP_UNRAID_PATH=""
DOCKER_AUTHORING_MODE="no"
DOCKER_LOG_ROTATION="yes"
DOCKER_LOG_SIZE="10m"
DOCKER_LOG_FILES="1"
DOCKER_CUSTOM_NETWORKS="eth1"
DOCKER_USER_NETWORKS="remove"

Appreciate the help.  I need to get my ownCloud working.

Link to post
4 minutes ago, bonienl said:

Try to add br0 manually


docker network create -d macvlan --subnet=192.168.1.0/24 --gateway=192.168.1.1 -o parent=br0 br0

 

That did it.  Is this a bug, or is it my setup?

Link to post
2 minutes ago, dlandon said:

That did it.  Is this a bug, or is it my setup?

 

I am not sure what went wrong for you. For me it is working and can't reproduce this error.

image.png.1ffcc06f3eaec089b865b9fe96a95f00.png

 

root@vesta:~# docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
24d7006fca22        br0                 macvlan             local
a55a2930f25f        br0.5               macvlan             local
09e57f65a472        bridge              bridge              local
2e0d5b0ce86b        host                host                local
5b5cd0378f3a        none                null                local

 

Link to post
9 minutes ago, bonienl said:

 

I am not sure what went wrong for you. For me it is working and can't reproduce this error.

image.png.1ffcc06f3eaec089b865b9fe96a95f00.png

 


root@vesta:~# docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
24d7006fca22        br0                 macvlan             local
a55a2930f25f        br0.5               macvlan             local
09e57f65a472        bridge              bridge              local
2e0d5b0ce86b        host                host                local
5b5cd0378f3a        none                null                local

 

On my test server.

docker.cfg:

DOCKER_ENABLED="yes"
DOCKER_IMAGE_FILE="/mnt/cache/system/docker/docker.img"
DOCKER_IMAGE_SIZE="15"
DOCKER_APP_CONFIG_PATH="/mnt/cache/appdata/"
DOCKER_APP_UNRAID_PATH=""
DOCKER_AUTHORING_MODE="no"
DOCKER_LOG_ROTATION="yes"
DOCKER_LOG_SIZE="10m"
DOCKER_LOG_FILES="1"
DOCKER_CUSTOM_NETWORKS="eth1"
DOCKER_USER_NETWORKS="remove"

docker network ls:

NETWORK ID          NAME                DRIVER              SCOPE
98c2722408d7        bridge              bridge              local
469c4c9736b7        host                host                local
0772cc6efdc5        none                null                local

Should the DOCKER_CUSTOM_NETWORKS be br0 and not eth1?

Link to post
  • limetech unpinned and locked this topic
Guest
This topic is now closed to further replies.