makkish

Members
  • Posts

    17
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

makkish's Achievements

Newbie

Newbie (1/14)

3

Reputation

  1. I encountered the same error when I tried to purge an old worker. I got the following suggestion from Guy in the Discord channel, which resolved it: 1) Stop Machinaris container in Unraid Admin UI 2) Delete only this file: /mnt/user/appdata/machinaris/machinaris/dbs/machinaris.db 3) Start Machinaris container in Unraid Admin UI 4) Wait about ~3-5 minutes for everything to start and get re-populated. Then try clicking around in Machinaris WebUI.
  2. Thank you! It seems to help by deleting smart-one.cfg and reapply the settings again.
  3. Hello! I have a SSD mounted as a UD, everything works fine but the SSD is giving me CRC errors (SMART attribute 199), and this is fine. It's not critical and I am planning to replace the SSD or the cable at a later time. However, I have toggled notifications off for just attribute 199 but it does not "take". I still get notifications, Another thing I noticed is that when the error appears, there is no "orange thumb" on the device which means I can't acknowledge the error. /boot/config/smart-one.cfg [KINGSTON_SA400S37960G_XXXXXX] smEvents="5|187|197|198" Device settings I am on Unraid 6.9.2, but it also happened on 6.9.1. It seem to have started after updating to 6.9.1 but I'm not sure. Have any one else encountered this? Thanks!
  4. Hi, Well, now I feel a bit stupid. Of course I had it in the configuration, I did not think of what it meant when I installed it the first time. I removed everything with MQTT/HomeAssistant and the queries stopped. Thank you!
  5. Hello, First of all, thanks for a great plugin that opens many doors. One question, I can see in the pihole logs that as soon as I start the container it starts querying hassio every second. Why is that?
  6. Yes, I have added the disk as a 2nd vDisk location It has nothing to do with UD then I guess. Thanks for the clarification. I just figured out another issue, despite the warnings of CRC errors, SMART appear as healthy on the dashboard: I guess I should continue my issues in another forum instead, since this seem to have nothing to do with UD.
  7. Hello! I am not completely sure that this is a UD problem, but i'll start here. I have a SSD mounted as a UD, this is then passed through to a VM. Everything works fine but the SSD is giving me CRC errors (SMART attribute 199), and this is fine. It's not critical and I am planning to replace it at a later time. However, I have toggled notifications off for just attribute 199 but it does not "take". I still get notifications, /boot/config/smart-one.cfg [KINGSTON_SA400S37960G_XXXXXX] smEvents="5|187|197|198" Device settings I am on Unraid 6.9.1 and UD 2021.03.20. Have any one else encountered this? Like I said, I am not sure if this is a UD or Unraid issue. Thanks!
  8. Thank you for the suggestion. It gave me the option to open a link that way, It did however not help for me neither.
  9. Hello, First of all, thank you very much for your work in this. I do have some problems with the icons, for some reason they are not images that I can right click. I can see the "broken icons" but I have no option to open the link in a new tab when I right click. This happens on different browsers. The API connection works fine in general, I still get the data as expected.
  10. Hello, I can confirm that my scheduled parity check did not pause either. I changed the settings and then back, the .cron look correct but it did not pause anyway. It did however pause correctly if I set "Use increments for Unscheduled Parity Check" to Yes. Edit: I'm on Unraid 6.8.3 and Parity Check Tuning 2020.05.11
  11. The plugin does not seem to honor the tuning schedule. I have my parity check to pause at 4:30AM, but when I woke up today the parity check was still running. I can see the following in the log at the time it was supposed to pause, 2021-01-02 04:30:01 5 unraid01 CROND exit status 126 from user root /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null Edit: 4:30AM not PM.
  12. Seems to be working fine. Thank you!
  13. I am also wondering how to roll back to previous version. I completely missed that you shouldn't update if you're on 6.8.3. Fix Common Problems is now complaining that the plugin is incompatible.
  14. Hello, Sorry to revive this old thread, but did you (or someone else) ever resolve this?
  15. Hi, Thanks for the answer. I think I have some other serious issue with this update. Three times today NFS/Samba completely stops working, my Windows hosts (both physical and virtual) and my Linux hosts (virtual) loses the SMB/NFS connections completely. The only thing that have changed in my Unraid setup today is the update of the SNMP plugin. The first time NFS/Samba stopped working was after I updated the plugin. The second time It happened after a reboot and a fresh installation. Third time was the same as the second one. The first two times I did edit /usr/local/emhttp/plugins/snmp/snmpd.conf and issued bash /etc/rc.d/rc.snmpd stop|start. The third time I only edited /etc/snmp/snmpd.conf without any further commands, it almost instantly dropped NFS/Samba. Not sure at all if the editing of the files have anything to do with it or if it's just a coincidence. Unfortunately I did not download diagnostics until after reboot. I am digging through logs now to see if there is something else that is causing this. Just thought I let you know.