Kaldek

Members
 View Profile  See their activity

  • Posts

    101

  • Joined

  • Last visited

 Content Type 

Everything posted by Kaldek

  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
    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?
  15. Kaldek
    Changed Status to Closed
  16. Kaldek
    Confirmed at my end that not using Active/Backup NIC Failover has kept my system stable for 25 days.
  17. Kaldek
    Fair enough. Not sure if I'm game to turn active/backup back on and wait for a crash again. I had so many crashes I think I'm still in the "just want stability for a while" phase. I guess if that means this bug report has to be closed due to that, I'll just have to live with it.
  18. Kaldek
    Yeah I did plan on that but given the fact that I wasn't even getting Kernel Panic messages on the console, and the fact that it's core network driver related, the chances of that syslog message even getting out were...low.
  19. Kaldek
    Unfortunately I do not have any diagnostics files from during this issue as the system insta-reboots when this issue occurs and leaves no logs at all. I recently enabled link bonding (active/backup) on unRAID 6.12.6 between a dual port Intel 10Gb/s XFP module (ixgbe driver) using eth0, and the onboard gigabit Intel NIC (igb driver) at eth2. My server started rebooting every few days, with no pause for kernel dumps or anything. The issue did not go away until I removed the active/backup link bond and shut down the eth2 NIC again. Some additional useful information is that, whilst in the same Layer-2 broadcast domain, eth0 and eth2 are connected to different switches. Diagnostics file attached but note that it does not have the active/backup config in it. unraid-diagnostics-20240110-1155.zip
  20. Kaldek
    Was this plugin never updated? Is it now an orphaned plugin?
  21. Kaldek
    Support had to do a manual key replacement to fix this issue. I literally just listened to the unRAID podcast where the support guys were saying license key management was a major headache. Guess there's still a lot of work to do at the back end.
  22. Kaldek
    I have access to all that, and it looks like the image below. Unfortunately there appears to be no documentation on "Signing Out" a key and what that all means. It drives me up the freaking wall when I find this lack of documentation update. Documentation must never be delayed and must be part of the release process! It keeps a high workload on the tech support folks when there's just no need if the damned documentation would be updated.
  23. Kaldek
    I bit the bullet and did it. I confirmed that keeping Pool Slot assignments also keeps ZFS pools.
  24. Kaldek
    I just installed a new DOM-based USB key for my server, following all of the instructions located at https://docs.unraid.net/unraid-os/manual/changing-the-flash-device. There is NO "Replace USB key" option, and it appears this is because I upgraded my license on the 14th of July. I have had this USB key for over four years. This is ridiculous, why is a license upgrade classed as a "key replacement"?
  25. Kaldek
    Folks it's a bit of a worry that I'm getting zero response to this question, and makes me scared to use ZFS on unRAID at all. Can *somebody* reply?