The source thread is only one post long, but the problem it describes is important: a user installed CasaOS on Linux, later removed CasaOS with the official uninstall command, and then discovered that their Samba setup from before CasaOS no longer worked. Investigation showed that the original smb.conf had been renamed when CasaOS was installed, while the CasaOS-generated Samba configuration remained active after uninstall.
Because the thread has no staff reply or complete cleanup inventory, the correct page should stay narrow. It can explain the confirmed Samba side effect and give a safe post-uninstall audit method, but it should not invent a definitive list of every file CasaOS leaves on every Linux distribution.
What Was Actually Confirmed
The user had Samba shares before CasaOS. Those shares worked with Kodi on a TV. A few days after uninstalling CasaOS, Kodi could no longer access them.
The user then found that CasaOS installation had moved or renamed the original Samba configuration and installed its own. The uninstall process did not automatically restore the previous smb.conf, so the machine continued using the CasaOS-era configuration.
Uninstalling an Application Is Not the Same as Rolling Back the Host
CasaOS runs on top of a Linux distribution and integrates with services such as Docker, storage paths, and Samba. If installation replaces or modifies a configuration file, removing the CasaOS binaries does not necessarily reconstruct the host exactly as it existed before installation.
This is a general Linux administration principle: “package removed” and “system restored to previous configuration” are different operations.
The Current CasaOS Uninstaller Has Optional Removal Choices
IceWhale's maintained CasaOS project still exposes casaos-uninstall as the normal removal command. The current uninstaller asks separately whether to remove Docker, CasaOS containers, and CasaOS files.
Review the current CasaOS removal path before uninstalling a modern system, because the exact prompts and cleanup behavior can change between releases.
Before Uninstalling, Back Up Host-Level Configuration
If CasaOS is being tested on a server that already has services, save copies of important host configuration before removal. Examples include:
- Samba configuration and share definitions;
- custom systemd units;
- reverse-proxy configuration;
- Docker Compose files not owned by CasaOS;
- firewall or network configuration;
- mount definitions and storage configuration.
This is especially important on a “real” Linux server where CasaOS is not the only workload.
Restore Samba by Comparing Known-Good Files
If a pre-CasaOS smb.conf still exists under a renamed or backup filename, do not simply overwrite the active configuration immediately. First preserve both versions, compare the share definitions, and validate the intended configuration.
A syntax error can take all Samba shares offline. If possible, use Samba's own configuration validation tools before restarting or reloading the service.
Do Not Delete /DATA or Docker Storage as “Cleanup” Without Inspection
CasaOS deliberately stores application and user data in persistent locations so uninstalling the management layer does not automatically destroy user data. The same safety can look like “leftovers” after removal.
Do not recursively delete /DATA, Docker volumes, container data, or application folders until you have identified which files belong to CasaOS and which belong to applications you still need.
A Safe Post-Uninstall Audit
- Confirm CasaOS services no longer run.
- Review the active Samba configuration and compare it with pre-CasaOS backups.
- List remaining CasaOS containers before deleting Docker data.
- Inspect persistent data directories rather than deleting them by name.
- Check whether any host-level service still references CasaOS-created files.
- Only remove leftovers after confirming they are not required by other services.
What the Source Thread Does Not Establish
The post does not prove that every CasaOS uninstall leaves Samba behind, does not list every leftover file, and does not include an IceWhale response explaining whether the behavior was considered a bug. The confirmed fact is narrower: this user's pre-existing Samba configuration was not restored automatically.
CasaOS Uninstall Cleanup FAQ
Does casaos-uninstall necessarily remove Docker?
No. The maintained uninstaller treats Docker removal as a separate choice.
Why did the user's old Samba shares stop working?
The active smb.conf remained the CasaOS-created version instead of returning to the pre-CasaOS configuration.
Should I delete every CasaOS-looking directory after uninstall?
No. Persistent directories can contain application or user data that the uninstall intentionally did not destroy.
