Updating the filesystem package fails with due to /mnt being read-only
This document (7006556) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise Desktop 11
SUSE Linux Enterprise Server 11
During an update or upgrade of a SUSE Linux Enterprise system with zypper the error message "unpacking of archive failed on file /mnt: cpio: chown failed - Read-only filesystem" appears while installing the filesystem package. Zypper then prints the message "Abort, retry, ignore? [a/r/i] (a):" and waits for input.
It's advised to umount active mounts from /mnt before updating the filesystem RPM or performing a system upgrade to avoid this situation. In case it already happened, choosing ignore (i), completing the update and installing the new filesystem RPM by re-running zypper afterwards is safe. Alternatively, umounting /mnt in a different terminal window or console and choosing retry (r) should also work.
The filesystem package contains the basic directory structure for a SUSE Linux Enterprise system, including the default ownerships and permissions of the directories. The directory /mnt is one of those basic directories. Trying to change the owner or permissions of a mounted directory will not affect the mount point itself, but the root directory of the filesystem that has been mounted. In case it is mounted read-only, the change of ownership and permissions will fail. Subsequently, this leads to RPM reporting an error while installing the filesystem package
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7006556
- Creation Date:
- Modified Date:10-Mar-2021
- SUSE Linux Enterprise Desktop
- SUSE Linux Enterprise Server
< Back to Support Search
For questions or concerns with the SUSE Knowledgebase please contact: firstname.lastname@example.org