Closed carsten-h closed 2 years ago
I've found a bug in the dockerfile, I don't know why it works for me and others. I will release a patch version today. Until then, disable the "update database" check in the configuration.
I think is fixed in version 0.50.1. Can you test it?
Yes, I will do. In the moment I can't see this version in Home Assistant.
@carsten-h go to the add-on store, three points in the up rigth corner, and press reload.
Yes, this worked. But I still get the same error message when selecting to update the database. I am using a HassOS installation on a Pi 4B.
I've reproduced it... delete the contents of the /share/hdd_tools/script folder (using samba or ssh) and press rebuild on the addon page. It will fill this folder again with the right permissions. I will let this issue open by now, others can have the same error. The problem is a copy instruction, it does not copy the "new permissions" of the file and remains with the old one. I'm not too sure why this addon uses this scripts and not the ones that are inside the docker, maybe to make it easier to test new changes.
Yes, when deleting the contents and rebuild, everything is working fine! Thank you!
Seeing the code again, a simple restart will be enough after deleting the files (not rebuild needed) :)
What I don't understand is why I was executing it without problem, because my permissions where wrong too. Every people who installed the version 0.50.0 has the permissions bad.
I can do a fix (maybe a simple -p when copying the file), but I will wait a little to see if more people affected appears here.
Ok, I will wait and can test if there is a new version.
I've pushed the fix, but I will wait to see if more people is affected by this. If more people appear, I will generate a new version. If not, I will postpone it for later.
Same error here on my RPi4 4GB. So I deleted the contents of the /share/hdd_tools/script folder, restarted, and now everything is working fine. Thanks!
Hello!
I found this messages when starting the Addon:
and this can be found in supervisor log: