Fixing Read-Only Mode on eLux Thin Clients

If your eLux device boots into a read-only filesystem or prevents saving changes, it’s usually due to the write filter or system protection settings. Here’s how to identify and fix the issue.

Common Causes

• Write Filter is enabled (RAM overlay by default)
• System partition is locked as part of image protection
• Corrupted overlay from improper shutdown

Fix 1: Temporarily Remount as Read/Write

sudo mount -o remount,rw /

This allows you to make temporary changes. They will be lost after reboot unless you adjust the image or profile settings.

Fix 2: Enable Persistent Mode via the EIS Tool

1. Open your image project in the EIS Tool
2. Go to the Settings tab
3. Locate the write filter or storage persistence section
4. Set it to Persistent Storage
5. Export the updated image and redeploy

Fix 3: Enable Persistence via Scout Configuration Profile

1. Open Scout Enterprise Console
2. Go to Configuration > Profiles
3. Edit the assigned profile
4. Enable options like:
   • Persistent user data
   • Persistent certificate storage
   • Persistent logging
5. Save and reassign the profile

Fix 4: Reimage the Device

• If the system is damaged or stuck in read-only permanently, use a USB stick or PXE deployment to reflash the device.
• Ensure the new image has persistence enabled in the EIS Tool before deploying.

Check Filesystem Mount Status

mount | grep ' / '

If you see (ro) in the output, the system is in read-only mode.

Final Notes

• eLux protects system partitions by design — use Scout and EIS Tool to make lasting changes
• Remounting manually is fine for diagnostics but not a long-term fix
• Always test changes on a test device before rolling out to production