saarg Posted February 25, 2021 Share Posted February 25, 2021 1 hour ago, L0rdRaiden said: Yes Could it be because of this? --cap-add=SYS_RAWIO I have no idea to be honest, but might be one of the --cap-add or privileged doing it. Quote Link to comment
dbzeag Posted March 23, 2021 Share Posted March 23, 2021 On 1/25/2021 at 12:06 PM, viola2572 said: how do I refresh it?????? as it is showing me data from drives a day old, I have uninstalled it and reinstalled it, still old data. I know it does it one a day, but when you have been changing drives, you want a refresh button, please Also it is seeing my WD SAS 3tb and 4tb drives as seagate Parity 2ST4000NM0023_Z1Z0C3DW - 4 TB (sdo)32 C1,216,397163,6080Disk 1ST33000650SS_Z293MTCQ - 3 TB (sdc)25 Same. I replaced a drive and reran the command line command, restarted the docker, etc, but still has the old data. Quote Link to comment
Cpmiller22 Posted April 27, 2021 Share Posted April 27, 2021 When I run the command - scrutiny-collector-metrics run - I get the following errors see below. The data is showing up in the web portal, but I'm wondering why those errors are showing. INFO[0000] Executing command: smartctl --info -j /dev/sdd type=metrics INFO[0000] Generating WWN type=metrics INFO[0000] Executing command: smartctl --info -j /dev/sde type=metrics INFO[0000] Generating WWN type=metrics INFO[0000] Executing command: smartctl --info -j /dev/sdf type=metrics INFO[0000] Generating WWN type=metrics INFO[0000] Executing command: smartctl --info -j -d nvme /dev/nvme0 type=metrics INFO[0000] Using WWN Fallback type=metrics INFO[0000] Executing command: smartctl --info -j /dev/sdb type=metrics INFO[0000] Generating WWN type=metrics INFO[0000] Executing command: smartctl --info -j /dev/sdc type=metrics INFO[0000] Generating WWN type=metrics INFO[0000] Sending detected devices to API, for filtering & validation type=metrics INFO[0000] Collecting smartctl results for sdd type=metrics INFO[0000] Executing command: smartctl -x -j /dev/sdd type=metrics ERRO[0000] smartctl returned an error code (4) while processing sdd type=metrics ERRO[0000] smartctl detected a checksum error type=metrics INFO[0000] Publishing smartctl results for 0x5000c5006e098b8f type=metrics INFO[0000] Collecting smartctl results for sde type=metrics INFO[0000] Executing command: smartctl -x -j /dev/sde type=metrics ERRO[0001] smartctl returned an error code (4) while processing sde type=metrics ERRO[0001] smartctl detected a checksum error type=metrics INFO[0001] Publishing smartctl results for 0x50014ee20a4ab910 type=metrics INFO[0001] Collecting smartctl results for sdf type=metrics INFO[0001] Executing command: smartctl -x -j /dev/sdf type=metrics ERRO[0001] smartctl returned an error code (68) while processing sdf type=metrics ERRO[0001] smartctl detected a checksum error type=metrics INFO[0001] Publishing smartctl results for 0x50014ee25f9a29db type=metrics INFO[0001] Collecting smartctl results for nvme0 type=metrics INFO[0001] Executing command: smartctl -x -j -d nvme /dev/nvme0 type=metrics INFO[0001] Publishing smartctl results for 7fbc071205d900060942 type=metrics INFO[0001] Collecting smartctl results for sdb type=metrics INFO[0001] Executing command: smartctl -x -j /dev/sdb type=metrics INFO[0003] Publishing smartctl results for 0x5000c50066215c45 type=metrics INFO[0003] Collecting smartctl results for sdc type=metrics INFO[0003] Executing command: smartctl -x -j /dev/sdc type=metrics INFO[0004] Publishing smartctl results for 0x5000c500c8f1320e type=metrics INFO[0004] Main: Completed type=metrics Quote Link to comment
ucliker Posted April 27, 2021 Share Posted April 27, 2021 I need help deciphering what these attributes mean in scrutiny. I purchased two Seagate EXOS 8TB hard drives and one (my parity drive) shows failed Read Error Rate. Is this a comparison of data between my drive and Backblaze or is this actually failing? My smart reports all say PASSED. Given that this is my parity drive I would like to know before something really bad happens. Quote Link to comment
ashman70 Posted May 24, 2021 Share Posted May 24, 2021 Just installed this and when I try to run the command scrutiny-collector-metrics run in the Scrutiny console I get: command not found Am I doing something wrong? Quote Link to comment
RadOD Posted May 29, 2021 Share Posted May 29, 2021 The main page shows everything to look good: everything is green and says passed. I have to actually open each one to see any signs of problems -- such as a failed Reallocated Sectors Count. Is that expected behavior? Seems like those failures and warnings should be out in front. Quote Link to comment
ryujin921 Posted July 15, 2021 Share Posted July 15, 2021 is there a way to schedule when it runs? am aware of the interval setting; but i would rather have a specific time (rather than just an offset) so it would run a short while after the mover. currently its spinning up my disks in awkward times. Quote Link to comment
Luc magnum Posted August 2, 2021 Share Posted August 2, 2021 Hello, I have a problem with my scrutiny in docker, it recognizes my seagate disks and my nvme and WD disk.but the S.M.M.A.RT is failed for this last (WD) Has anyone already had this problem or has a solution. I am not unraid but with a synology (dsm) but I don't think that's a problem. Quote Link to comment
trurl Posted August 2, 2021 Share Posted August 2, 2021 17 minutes ago, Luc magnum said: I am not unraid See first post Quote Link to comment
Fuggin Posted October 10, 2021 Share Posted October 10, 2021 Hello. App won't update the harddrives in my array even with the run command in the docker console. Still has 2 older harddrives showing that I removed. Quote Link to comment
RichJacot Posted October 30, 2021 Share Posted October 30, 2021 The only thing I changed was the webui port and it's not picking up all of my drives. Any ideas to try? I tried adding each /dev/sd(x), I gained two additional drives but none of the others. Quote Link to comment
darrenyorston Posted November 4, 2021 Share Posted November 4, 2021 (edited) How do I get the container to show all my drives? I followed the instruction to add '/dev:/dev' to the field '/dev/sda' however it reports server error when I try to start the container. Also adding `--cap-add=SYS_ADMIN` for the NVME drive results in server error. Edited November 4, 2021 by darrenyorston Updated Quote Link to comment
darrenyorston Posted November 10, 2021 Share Posted November 10, 2021 Anyone able to explain how to get the container to see all the drives on my system? At the moment it will only show the two in the /dev/sda and /dev/sdb fields. Nor will it show my NVMe drives. Quote Link to comment
Cpmiller22 Posted November 10, 2021 Share Posted November 10, 2021 13 hours ago, darrenyorston said: Anyone able to explain how to get the container to see all the drives on my system? At the moment it will only show the two in the /dev/sda and /dev/sdb fields. Nor will it show my NVMe drives. I have the same question. Any guidance would be much apprciated! Quote Link to comment
darrenyorston Posted November 24, 2021 Share Posted November 24, 2021 Hello all. Following up on a previous post re Scrutiny. How do you get it to show all the drives in the array? Mine only shows three, though one popped up after a week or so of running. My config has /dev/sda, /dev/sdb, /dev/nvme1n1, and /dev/nvme2n1 in the template but when I start the UI /dev/sdb, /dev/sdh, and /dev/sdi are displayed. Is there another config somewhere I have to change to have it show all 11 drives? Quote Link to comment
darrenyorston Posted November 29, 2021 Share Posted November 29, 2021 On 11/24/2021 at 11:32 AM, darrenyorston said: Hello all. Following up on a previous post re Scrutiny. How do you get it to show all the drives in the array? Mine only shows three, though one popped up after a week or so of running. My config has /dev/sda, /dev/sdb, /dev/nvme1n1, and /dev/nvme2n1 in the template but when I start the UI /dev/sdb, /dev/sdh, and /dev/sdi are displayed. Is there another config somewhere I have to change to have it show all 11 drives? I ended up solving the issue of drives not chowing up. I edited the scrutiny.yaml file in appdata. There is a field called "disks:" I added all my drives and they showed up straight away in the UI. I dont know why but editing the drives in the docker template makes no difference to. The UI always shows what's in the .yaml file. Quote Link to comment
oxideSeven Posted December 1, 2021 Share Posted December 1, 2021 I can't change any settings in scrutiny via the webapp. All the options like trying to get manufacturer info is grayed out. It's also not really registering errors in a real way. One of my drives should be failing but scrutiny says it passes. Quote Link to comment
ThatTallGuy21 Posted December 20, 2021 Share Posted December 20, 2021 Can someone tell me if the Scrutiny container is impacted by the Log4j vulnerability? Quote Link to comment
DeeBo Posted February 10, 2022 Share Posted February 10, 2022 On 10/27/2020 at 11:11 AM, AnalogJ said: Currently there's no way to delete old drives. It's on my to-do list. It's not updating powered on data for your new drives? By default the collector runs once a day, so after 24h you should see a change to that number. If it doesn't can you open an issue on the Github (with logs)? https://github.com/AnalogJ/scrutiny/ Has the ability to remove old drives been added yet or am I missing it? Quote Link to comment
EML Posted May 10, 2022 Share Posted May 10, 2022 The newest release 4.1 and 4.0 added influxdb among other changes and the container template on the community applications page needs to be updated accordingly. You can change the repository field to "lscr.io/linuxserver/scrutiny:8e34ef8d-ls35" until it gets updated. 1 7 Quote Link to comment
1471 Posted May 12, 2022 Share Posted May 12, 2022 On 5/10/2022 at 5:54 AM, EML said: The newest release 4.1 and 4.0 added influxdb among other changes and the container template on the community applications page needs to be updated accordingly. You can change the repository field to "lscr.io/linuxserver/scrutiny:8e34ef8d-ls35" until it gets updated. Thanks, that fixed things for me. Quote Link to comment
Nella Posted May 29, 2022 Share Posted May 29, 2022 On 5/24/2021 at 2:12 PM, ashman70 said: Just installed this and when I try to run the command scrutiny-collector-metrics run in the Scrutiny console I get: command not found Am I doing something wrong? Did you figure this one out? I have tried switching from Bash to Shell and either way it doesn't like the command. Quote Link to comment
de Techneut Posted June 8, 2022 Share Posted June 8, 2022 (edited) I've installed this app because Hotio scrutiny is not supported anymore. Only now everytime I start this dockerI need to manually put in: scrutiny-collector-metrics run Otherwise it won't start. With Hotios version this was not needed. It would start automatically. Is it possible to also possible for this docker to automatically start without putting in the command? Edited June 8, 2022 by de Techneut Quote Link to comment
1471 Posted June 13, 2022 Share Posted June 13, 2022 On 6/8/2022 at 10:17 AM, de Techneut said: I've installed this app because Hotio scrutiny is not supported anymore. Only now everytime I start this dockerI need to manually put in: scrutiny-collector-metrics run Otherwise it won't start. With Hotios version this was not needed. It would start automatically. Is it possible to also possible for this docker to automatically start without putting in the command? Just a heads up, looks like the linux server image is deprecated as well now. From the github page: ---------------------------- This image is deprecated. We will not offer support for this image and it will not be updated. We recommend the official images: https://github.com/AnalogJ/scrutiny#docker ---------------------------- The AnalogJ image is available through CA, using that without any problems 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.