chompy18

Dozzle supports a main instance and multiple agent instances that act as agents. I was able to load it in unraid as a compose file, but it would be ideal to extend the wrapper. ``` version: '3.8' services: dozzle: container_name: dozzle image: amir20/dozzle:latest command: agent <---------- restart: always environment: - tailSize=1000 - DOZZLE_HOSTNAME=<redacted> volumes: - /var/run/docker.sock:/var/run/docker.sock ports: - 9095:7007 ```

For docker "sequence" you can use the docker-compose extension and the depends-on property

I saw it is relatively simple to add the above by modifying `utils/extractServerDetails.ts` to extract the values - and I am happy to fork and implement, but unfortunately I was unable to run it locally running `npm run dev` - I am getting errors in `npm install` Are there any instructions on how to run this locally in dev mode?

@BoKKeR First - I'd like ti thank you for this! It has a lot of usefulness I am using unraid 6.12.6 and latest container, everything works well for me. I was wondering if it is possible, in addition to the array info (utilization, free space, etc) to also get info about individual HDDs in the array - specifically space used + free and the HDD temperature - it would be great to implement an alert automation when unraid detects a HDD is too hot Plus - any information on the machine itself - CPU load, Memory, etc. - that would be awesome if possible

Ok, but I don't see it under tools. I see two options for an app install, one is a docker and the other a plugin that fails to install due to unmet requirements...

While I'm waiting for parity to build... Assuming this is a faulty HDD, Is there some way to mark bad sectors so unraid will not use them to write data on?

OK, I stopped the array and removed it and now building the parity again. Once that is completed I will re-introduce it to the array and if the errors are reported again, I'll run the SMART test and update here. Thanks for the reply 😁

Hey, I have one disk in the array that has me buffled. I purchased 4 identical WD red pro HDDs, 4TB each. I added them to array that already contained 3 HDD (one as parity, the others as part of the array) - so total 2 parity and 5 storage. unRaid immediately started to parity recalculation and one of the new disks started reporting a large amount of write errors by them time parity was done computing (179,089 errors). I am wondering if this is something to do with my setup or a faulty HDD that needs to be replaced... Any suggestions on how to trouble shoot this would be greatly appreciated 😀 I am attaching a few diagnistics outputs I collected, hopefully someone here can help 🙏 (The faulty one is WXL2AA2RSL70). enps-diagnostics-20230620-0908.zip enps-diagnostics-20230619-1937.zip enps-diagnostics-20230619-1938.zip enps-diagnostics-20230619-1953.zip enps-diagnostics-20230619-2025.zip