[BUG] smartctl returned an error on QNAP #560
Comments
|
Maybe you can run (replace |
|
Here you go: |
|
The issue is on If you succeed, then have a look at |
|
I found the missing parameter (--device=sat) and can run this successfully from the command line in the container. When I update the config though, it's not running the command with the addition of --device. I'm setting it according to below: Error from the logs below: I'm running the latest container version etc. Is there anything I am missing? |
Many thanks for your comment :) I got the same error in my all of SSD(SATA) on and i went to I tired different args of the until to so i split the collector.yaml | path to remove files or folder to clean the cache:
re-build your scrutiny object and open your config/collector.log file, you should be see the now everything is normal 👯 I made a lot of efforts to search for the section on |
|
@chrisuhg Thanks for the info. Although, I'm not sure why you need to rebuild the container when my config files are stored outside of it and the container reads the config upon every start/restart? |
I knew the container will reads config when every start option, but the Container Manager of the Synology NAS app can not following after i edited the compose.yaml file. so I though the Start/Stop of the GUI button is equal 
Maybe I should attach more screenshot to make it easier to understand the "build" or "re-build"~ Anyway, thanks for your ask :D |
|
Ah yes, you make a good point. I use Portainer for managing my containers instead of QNAP's Container Manager.
In any case, the issue remains for me as it seems the global command for smartctl is not being read by the config.
Paul Morabito
…On 4 Jan 2024 at 19:17 +0100, Chrishg ***@***.***>, wrote:
> @chrisuhg Thanks for the info. Although, I'm not sure why you need to rebuild the container when my config files are stored outside of it and the container reads the config upon every start/restart?
I knew the container will reads config when every start option, but the Container Manager of the Synology NAS app can not following after i edited the compose.yaml file.
so I though the Start/Stop of the GUI button is equal docker run/stop , the option > build button is equal docker-compose -config compose.yml
image.png (view on web)
Maybe I should attach more screenshot to make it easier to understand the "build" or "re-build"~
Anyway, thanks for your ask :D
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
I also have a QNAP and had the same issue as you, @paulmorabito. The advice from @chrisuhg helped me get it working. Note: I've initially attempted to set the global command arguments in the config, since all my drives are SATA, but that didn't work for me. collector.yaml: |
|
Thanks for the reply @pheetr. I've taken a look with fresh eyes and my config was pointing to the wrong location. I don't check Scrutiny very often and perhaps at some point it was changed to opt/scrutiny/config? In any case, I had "type: sat" previously set so pointing to the correct config sorted that. I also noticed on restarting that I now have 4 "[/DEV/ -" devices that can't be clicked on or deleted. There was quite a few DB migrations on restart so its perhaps a side effect of it? Also noted that the global "commands" doesn't seem to work but that's a separate issue to this. I'll close for now as the reported issue is fixed. |
Using scrutiny on my QNAP TS453BE and the latest version of scrutiny and QNAP firmware is once again giving smartctl errors. Compose and logs are below:
logs:
Please let me know if there is any further debugging or logging needed and I'll get to it.
Thanks,
The text was updated successfully, but these errors were encountered: