MORERAM up date this morning makes a Pi 500+ desktop unusable

[CraigsBar]

Confirmations

• I searched for similar bug reports in https://github.com/Botspot/pi-apps/issues and found none were relevant.
• I tried updating Pi-Apps and the issue is still not fixed. How to update Pi-Apps?
• IMPORTANT: I promise to respond to comments on this issue and write a good bug report https://www.softwaretestinghelp.com/how-to-write-good-bug-report/

What happened?

After installing the current update to MORERAM the pi 500+ can no longer boot correctly

Description

This morning I recieved a notification of the MoreRam update, I applied it to my Pi 500+

WHen completed I rebooted the computer and the desktop wallpaper did not load, the ZRAM is not present. Shutdown scripts also hang.

Reinstalled a fres 64 Raspberry Pi OS and installed all updates. the installed Pi-Apps and tried to install the new MoreRam on this clean install. The install fails.

I will not be installing this on my other Pi's (2 Pi 5's and a Pi 400) as this does not install even on a fresh Raspberry Pi OS on a Pi 500+

What are your system specs (run the following command in your terminal)?

craig@raspberrypi:~ $ ~/pi-apps/api get_device_info
OS: Debian GNU/Linux 13 (trixie)
OS architecture: 64-bit
Last updated Pi-Apps on: 05/05/2026
Latest Pi-Apps version: 05/05/2026
Kernel: aarch64 6.12.75+rpt-rpi-2712
Device model: Raspberry Pi 500 Rev 1.0
SOC identifier: bcm2712
Machine-id (hashed): 6403be99a5d4e5a8d7fb33b20b62acff04874707
Serial-number (hashed): 8894cd478b002433ebfeab1ac972a3a14e3628bc
Cpu name: Cortex-A76
Ram size: 16.21 GB
Raspberry Pi OS image version: 2026-04-21
Language: en_US.UTF-8
craig@raspberrypi:~ $ 

(Recommended) Error log? Terminal output? Debug messages?

Unavailable

[Botspot]

The only change made was an improvement to the way the auxiliary file storage mount was set up. See for yourself at 1c6b0f4 I can't imagine how that could possibly cause an issue, unless your mount command does not recognize that option but mine (bookworm) does. Before pushing the change I ran it through some testing and saw nothing amiss, but sometimes something subtle can get missed.

What was the error you were getting when more ram was updated? Was it related to this change to the mount command, or something else?

[CraigsBar]

I will repeat the fresh install of Raspberry Pi OS tonight and capture failing installation. Fortunately the Pi500+ is used as test platform so I have no problem doing this.

[CraigsBar]

This mornings testing with a fresh install is that the installer hangs when setting up zram_swap.

[CraigsBar]

The install on a fresh Raspberry Pi OS hangs on the following step

[brixitomas-jpg]

Same problem as CraigsBar. I have Raspberry 5/8GB. Linux 12 (bookworm). Help! I can't afford a new system installation, I have important data on it.

[Botspot]

I've spent several hours today trying to get some sort of bug to occur, but was unsuccessful. It works great for me on trixie 64-bit and bookworm 64-bit, before and after an apt upgrade and reboot.

However, since 2 people reported some sort of issue here, I've reverted the change. That mount option was meant to help improve long-term RAM recovery after thousands of files are created and deleted from the /zram folder, so while beneficial, it's not worth it if it causes a weird issue like this.

If anyone can help pinpoint an specific error message or more precise output from running sudo zram.sh start, that would be great.

[CraigsBar]

Thanks so much. I can confirm the old one works and is now correction installed on my Pi500+

Since the machine became largely unusable with the other one I am not sure I can assit in testing with manually starting the zram. Maybe @brixitomas-jpg still has the situation where the not working one is installed, they may be able to help.

[brixitomas-jpg]

Sorry, I don't speak English. I use Google Translate. My Raspberry 5/8GB is equipped with a 256GB SSD, I don't use an SD card. After installing the Pi-Apps update and trying to install MoreRam, a black screen without wallpaper, I can't start the PCManFM and FileZilla file managers. Shutdown and Reboot get stuck, Raspberry has to be disconnected from the power supply to turn it off. Chromium, Thunderbird, Terminal and other programs work. Some Windows 11 programs work in the Botspot Virtual Machine, but they can't be expanded to the entire screen window. Please, what should I enter in the Terminal to return the apparently incorrectly partitioned SSD disk to its original state? Please provide instructions for a layman, I'm not that familiar with Linux, and there's a language barrier. Thank you

[Botspot]

@brixitomas-jpg I think there is no disk corruption, and no need to partition the ssd disk.
Simply remove this file:

/usr/bin/zram.sh

[brixitomas-jpg]

@brixitomas-jpg I think there is no disk corruption, and no need to partition the ssd disk. Simply remove this file:

/usr/bin/zram.sh

Ok, that helped, thank you