Adding partitions to a DASD which is in use fails
This document (3515220) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise Server 10
SUSE Linux Enterprise Server 9
Adding partitions to a DASD which is in use (mounted file system on a partition or part of an active LVM volume group) fails.
The DASD driver does not allow writing a modified disk label (which contains the information about the partitions) if one of the existing partitions is in use. Such a disk can be modified only byumounting all filesystems or deactivating the volume group which are active on the disk. In case this is not possible, a workaround is to shut down the Linux system, IPL the installation system and use the partitioner to modify the disk. Be careful not to actually start an installation in this case, though.
Ignoring the three warnings that fdasd wasn't able to write the partitions table, YaST failed to create the filesystem and YaST not being able to mount the filesystem on the new partition, results in an entry in /etc/fstab which refers to a non-existing partition. The system then won't come up properly after a reboot and requires manual intervention on the 3270 terminal. After entering the root password, the entry can be removed from /etc/fstab for example with sed '/^.dev.dasda2/d'/etc/fstab.1 (if /dev/dasda2 is the non-existing partition). Check whether the resulting file /etc/fstab.1 is correct. If it is, run mv /etc/fstab.1 /etc/fstab and exit the rescue shell. The system will then reboot and should come up correctly again.
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:3515220
- Creation Date: 21-Jun-2007
- Modified Date:04-Mar-2021
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: email@example.com