Kaldek

Members
 View Profile  See their activity

  • Posts

    101

  • Joined

  • Last visited

Recent Profile Visitors

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

Kaldek's Achievements

Apprentice

Apprentice (3/14)

14

Reputation

2

Community Answers

  1. Kaldek
    I get that - it's more that this should be a call-out about impact to reboots. Like, I was utterly confused by this as there was no warning *what* was delaying the reboot. Lots of unRAID users out there less technical than me.
  2. Kaldek
    The root cause here appears to be entries in the file /boot/logs/syslog-previous related to the previous execution of the Mover when Mover Logging is enabled. The diagnostics script sees these, and runs the "sed -i" command for every entry found in the syslog-previous file. Deleting the syslog-previous file stops this issue from occurring, as would not having Mover Logging enabled I suspect. I do not recall a warning for Mover logging about it impacting Diagnostics. I know it mentions potentially filling up log files, but not an impact to the diagnostics script.
  3. Kaldek
    Changed Priority to Minor
  4. Kaldek
    OK, I had to delete the file /boot/logs/syslog-previous to remove the constant banging on about these non-existent files.
  5. Kaldek
    Post reboot and the GUI diagnostics is still waffling on about these files that just don't exist on the cache drive.
  6. Kaldek
    Array stop and reboot is working at this point, after performing the mover. Will run diagnostics interactively after reboot to see if the mover has all the weird sed commands on non-existent files still.
  7. Kaldek
    WebGUI just died with this message:
  8. Kaldek
    I have no idea what all this "syslog-previous" stuff is for.
  9. Kaldek
    I just moved all files off the cache: However when I run the Diagnostics command in the WebGUI agian it is still referring to these files??
  10. Kaldek
    I am unable to refresh the browser tab with the Diagnostics page, nor even change the URL to, say, the Dashboard. The tab has to be closed and a new unraid tab opened to access the Web GUI again.
  11. Kaldek
    However a completed file named "unraid-diagnostics-20240408-1001.zip" now exists in /boot/log.
  12. Kaldek
    The GUI execution has now hung here. There is no file attempting to download.
  13. Kaldek
    The command being run is "sed -i" as per the attached image:
  14. Kaldek started following Diagnostics never finishes due to huge # of files
  15. Kaldek
    I cannot reboot my unRAID server without terminating the diagnostics process, nor can I run diagnostics. This is because I have a share used by Frigate NVR called "cctv" with 53,000 small MP4 files inside it and 3,400 of these are on the cache right now. The diagnostics process tries to collect data on all of these files and when running diagnostics via the GUI the web interface hangs after a few minutes of reporting the logging of all these file names. At reboot time, all I see is "starting diagnostics collection". How do I stop collection of data on all these files so that diagnostics completes?
  16. Kaldek
    Changed Status to Closed