May 24May 24 15 minutes ago, johner said:Thanks Ricardo777, to be honest, because i'm not very good with paint! I think I created that one with gemini originally and AI can't create transparent backgrounds. If you have time and want to tweak it or send another, I'd be happy to consider replacing it? Else, I'll probably have a play when i get a spare hour (which isn't looking likely for a while, I have a 3rd plugin in the creation!)Thank you for the quick reply. I also generated some images with AI, but removed the BG, here is a zip attatched with your orginal logo with removed bacground and also a vector file. And some other version, you may want to use if you like them more. Thank you for the plugin, hope my VM will now stay online.You can temporary download the files here: https://temp.sh/mYxTy/Zram.zip
May 25May 25 20 hours ago, johner said:ok i went with one of yours in the end. let me know if it shows ok.Thank you, will await the new update to try. Tried the master repo but this uses some private git.
May 25May 25 Hi johner,Found a bug on 7.3.0 worth flagging.If the tier 2 (disk-backed) swapfile lives on a share in the boot pool (drive partitioned so Unraid boots from one partition and the rest is used as a data pool), the swapfile fails to release when the array stops. This causes the array to hang on stop/shutdown.Workaround: manually deleting the swapfile via the plugin page clears the hang and lets the array stop normally. [Tested on a single-disk NVMe boot pool with both XFS and ext4, same result either way]Hope this helps!
May 27May 27 On 5/24/2026 at 12:45 PM, johner said:ok i went with one of yours in the end. let me know if it shows ok.I tested the image by replacing it by hand in the plugin directory. In Unraid I use dark mode as theme, and with the new black icon this does not work nicely. Attached is a version for the dark mode theme, I don't know if you can swap them out checking the used theme in Unraid.
May 28May 28 Author On 5/25/2026 at 10:51 PM, jf457 said:Hi johner,Found a bug on 7.3.0 worth flagging.If the tier 2 (disk-backed) swapfile lives on a share in the boot pool (drive partitioned so Unraid boots from one partition and the rest is used as a data pool), the swapfile fails to release when the array stops. This causes the array to hang on stop/shutdown.Workaround: manually deleting the swapfile via the plugin page clears the hang and lets the array stop normally.[Tested on a single-disk NVMe boot pool with both XFS and ext4, same result either way]Hope this helps!Thanks for letting me know, I’ll get on it.
May 28May 28 Author 23 hours ago, Ricardo777 said:I tested the image by replacing it by hand in the plugin directory. In Unraid I use dark mode as theme, and with the new black icon this does not work nicely. Attached is a version for the dark mode theme, I don't know if you can swap them out checking the used theme in Unraid.I did think about this but went looking for a theme option and couldn’t find one, clearly I should have googled it! Let me explore the options.
June 1Jun 1 Author On 5/28/2026 at 4:54 PM, johner said:I did think about this but went looking for a theme option and couldn’t find one, clearly I should have googled it! Let me explore the options.I went with Orange as Unraid uses 'awesome fonts' for icons and I didn't find a suitable one, and the theme engine doesn't allow for multiple image files.
June 17Jun 17 After every reboot, ZRAM fails to auto-create. The init script tries to reset /dev/zram0, but the kernel already created it when the zram module loaded. The device is empty (disksize=0, not in /proc/swaps), so the reset is unnecessary and fails:[INFO] Creating ZRAM: size=8G, algo=zstd, priority=100[ERROR] Failed to create ZRAM device: zramctl: /dev/zram0: failed to reset: Device or resource busyClicking "Create" in the dashboard works fine every time , only the boot-time init fails.When disksize=0 and the device isn't in /proc/swaps, the reset could be skipped. Alternatively zramctl --find would avoid the conflict.Unraid 7.1.3, plugin version 2026.06.17.01, 56 GB RAM. Reproducible on every reboot.
June 18Jun 18 Author 6 hours ago, martinjuhasz said:After every reboot, ZRAM fails to auto-create. The init script tries to reset /dev/zram0, but the kernel already created it when the zram module loaded. The device is empty (disksize=0, not in /proc/swaps), so the reset is unnecessary and fails:[INFO] Creating ZRAM: size=8G, algo=zstd, priority=100[ERROR] Failed to create ZRAM device: zramctl: /dev/zram0: failed to reset: Device or resource busyClicking "Create" in the dashboard works fine every time , only the boot-time init fails.When disksize=0 and the device isn't in /proc/swaps, the reset could be skipped. Alternatively zramctl --find would avoid the conflict.Unraid 7.1.3, plugin version 2026.06.17.01, 56 GB RAM. Reproducible on every reboot.Hi, thanks for reporting. This should be fixed now, I'd appreciate it if you could test and let me know as I wasn't able to reproduce on my servers, but claude found a reason why this would happen for some.ThanksJohn
June 29Jun 29 Plugin persistence is a problem for me. I'm on the latest UNRAID release 7.3.1 w 64G RAM and plugin version 2026.06.17.02, the plugin disappears on reboot. I go into 'previously installed' in the app store and reinstall it without issue, and the settings I made previously are picked up. everything seems to be ok until a reboot. This has happened twice today. Edited June 29Jun 29 by blender50
July 13Jul 13 On 6/29/2026 at 8:42 PM, blender50 said:Plugin persistence is a problem for me. I'm on the latest UNRAID release 7.3.1 w 64G RAM and plugin version 2026.06.17.02, the plugin disappears on reboot. I go into 'previously installed' in the app store and reinstall it without issue, and the settings I made previously are picked up. everything seems to be ok until a reboot. This has happened twice today.I had the same thing happening when upgrading unraid to the latest version. Exactly the same thing happend.
August 11Aug 11 On 8/7/2026 at 12:28 PM, johner said:Hi both - it should be fixed now, would you mind giving it a test please?For me it looks fixed. I rebooted a couple times after doing some work, and the plugin is still active and set. Thank you for the fix.
August 30Aug 30 I have an unassigned disk that is normally spun down. Every time I open the Dashboard page, the disk wakes up. I disabled the ZRAM plugin and the problem stopped. Re-enabling it brought the problem back.Looking through the plugin source I found that the Dashboard page tile calls zram_get_our_device(), which runs:blkid -c /dev/null -t LABEL=ZRAM_CARD -o deviceI would think that this wakes up the disk. The disk is not being used for ZRAM or swap. My swap file is on an NVMe drive.Could the ZRAM device lookup be restricted to /dev/zram* or otherwise avoid probing unrelated physical disks? Edited August 30Aug 30 by raphael_
August 30Aug 30 Author 7 hours ago, raphael_ said:I have an unassigned disk that is normally spun down. Every time I open the Dashboard page, the disk wakes up. I disabled the ZRAM plugin and the problem stopped. Re-enabling it brought the problem back.Looking through the plugin source I found that the Dashboard page tile calls zram_get_our_device(), which runs:blkid -c /dev/null -t LABEL=ZRAM_CARD -o deviceI would think that this wakes up the disk. The disk is not being used for ZRAM or swap. My swap file is on an NVMe drive.Could the ZRAM device lookup be restricted to /dev/zram* or otherwise avoid probing unrelated physical disks?Hi, thanks for the detailed analysis, let me check it out and get back to you.
August 31Aug 31 Author On 8/11/2026 at 5:10 PM, Ricardo777 said:For me it looks fixed. I rebooted a couple times after doing some work, and the plugin is still active and set. Thank you for the fix.good news! thx for the update.
August 31Aug 31 19 hours ago, johner said:Hi, thanks for the detailed analysis, let me check it out and get back to you.The updated version works, however updating did not work at first and even reinstalling did not provide the fixed version.The plugin installer script preserves /boot/config/plugins/unraid-zram-card/src.tar.gz, and <FILE> uses the cached version, so it never gets refreshed with a newer version and is skipped on an update or reinstall. Edited August 31Aug 31 by raphael_
September 1Sep 1 Author 20 hours ago, raphael_ said:The updated version works, however updating did not work at first and even reinstalling did not provide the fixed version.The plugin installer script preserves /boot/config/plugins/unraid-zram-card/src.tar.gz, and <FILE> uses the cached version, so it never gets refreshed with a newer version and is skipped on an update or reinstall.Thx again for the analysis! fixed and released.
September 2Sep 2 Currently does not appear to like the 7.4.0-beta.1.Dashboard is flat.Debug Log:11:52:15CMDActivity log cleared.11:52:15INFOLogs cleared by user.11:52:17DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:20DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:23DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:26DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:29DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:32DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:35DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:38DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:41DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:44DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:47DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:50DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:53DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:56DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:59DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:02DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:05DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:08DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:11DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:14DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:17DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:21DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:24DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:27DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:30DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:33DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:36DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:39DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:42DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:45DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:48DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:51DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:54DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:57DEBUGPoll: orig=0MB, used=0MB, load=0%11:54:00DEBUGPoll: orig=0MB, used=0MB, load=0%11:54:03DEBUGPoll: orig=0MB, used=0MB, load=0%11:54:06DEBUGPoll: orig=0MB, used=0MB, load=0%11:54:09DEBUGPoll: orig=0MB, used=0MB, load=0%
September 7Sep 7 Author On 9/3/2026 at 1:55 AM, The_Holocron said:Currently does not appear to like the 7.4.0-beta.1.Dashboard is flat.Debug Log:11:52:15CMDActivity log cleared.11:52:15INFOLogs cleared by user.11:52:17DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:20DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:23DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:26DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:29DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:32DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:35DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:38DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:41DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:44DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:47DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:50DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:53DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:56DEBUGPoll: orig=0MB, used=0MB, load=0%11:52:59DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:02DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:05DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:08DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:11DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:14DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:17DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:21DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:24DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:27DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:30DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:33DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:36DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:39DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:42DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:45DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:48DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:51DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:54DEBUGPoll: orig=0MB, used=0MB, load=0%11:53:57DEBUGPoll: orig=0MB, used=0MB, load=0%11:54:00DEBUGPoll: orig=0MB, used=0MB, load=0%11:54:03DEBUGPoll: orig=0MB, used=0MB, load=0%11:54:06DEBUGPoll: orig=0MB, used=0MB, load=0%11:54:09DEBUGPoll: orig=0MB, used=0MB, load=0%Thanks for the report and the log. I don't have beta running yet, I'll likely give it a couple more releases as I can't risk breaking my dev box. I'll see if i can spin it up on a trial in a VM at somepoint.I, well mainly Claude(!) looked at what changed in 7.4.0-beta.1. The kernel moved from 6.18.38 to 6.18.44 and zramctl is the same util-linux 2.42.2. It found no ZRAM-related change, so I do not think 7.4 broke ZRAM. A flat graph right after an upgrade is usually normal. The upgrade rebooted the server. A reboot empties the ZRAM device and the plugin's graph history. Nothing lands in ZRAM until the kernel is under memory pressure, even with swappiness at 150.The real problem was on my side. The plugin wrote the same "0MB" line whether ZRAM was idle, missing, or broken, so your log could not tell us which one it was. Version 2026.09.06.01 fixes that. It also fixes a separate bug where the dashboard could show 0 bytes used for a busy device.Could you do this for me:1. Update the plugin. Go to Plugins, click Check for Updates, and update ZRAM Compressed Memory to 2026.09.06.01.2. Open a terminal on the server and run these two commands. The script is read-only. It changes no settings.wget -qO /tmp/zram-diag.sh https://forgejo.johnpwhite.com/unraid/unraid-plg-zram/raw/branch/master/tests/beta-diagnostics.shbash /tmp/zram-diag.sh3. Wait about five minutes and run bash /tmp/zram-diag.sh once more.4. Paste the complete output of both runs here, and tell me whether the Dashboard tile shows a ZRAM row with a non-zero Size.The output includes your kernel and Unraid version, the plugin version, the raw zramctl and swap state, what the dashboard reads, and the plugin's last diagnostic lines. A line that says status=healthy_idle with a non-zero disksize means ZRAM is fine and simply has nothing to store yet. The graph will move once the server needs swap. A line that says missing_device, inactive_device, or zramctl_command_failure is a real fault, and the output will show me exactly where to look.
September 11Sep 11 Pardon the delay---it's been a busy week. I know there were a couple of updates along the way. Do you still need me to do the above?
September 12Sep 12 Author 5 hours ago, The_Holocron said:Pardon the delay---it's been a busy week. I know there were a couple of updates along the way. Do you still need me to do the above?only if you're still having issues with the new version, else skip it.
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.