Mounting Xen DomU disk images in Dom0 using lomount
This document (3756370) is provided subject to the disclaimer at the end of this document.
- You do not need network access
- You do not need to access particular devices, rather you need to access the file system
- You are trying to fix boot problems
- A chrooted environment is sufficient
- The disk or file system to be manipulated does NOT use LVM
- You are not trying to repair an underlying filesystem
setup: discovering partitions, mounting and chrooting
- Navigate to the directory where the disk image can be found.
- Determine what loopbacks are
currently being used
- To determine all the loops typels /dev/loop*
- Determine which loops have been assignedlosetup -a
- Pick a loop device which has not been assigned
- Open the disk image using
loopback devices; replace values as appropriatelosetup /dev/loop5 disk0
- Determine what the partitions arefdisk -l /dev/loop5
- Mount partitions that are NOT
type 82 (swap) or type 8e (Linux LVM).
- The syntax is: lomount [-verbose] [OPTIONS] -diskimage FILE -partition NUM [OPTIONS]lomount -t reiserfs -diskimage disk0 -partition 3 /mnt
- Check /mnt or the mount point. If it does not look like the root file system, unmount the file system and try again until you find the root file system.
- Repeat step 5 for each files system. Mount the file systems under their normal mount point, but under /mnt. For example, /var for the DomU should be mount to /mnt/var.
- If the system that you are
accessing is the same architecture, you may chroot to the
cleanup: umounting and removing the loopback device
- Unmount the mounted
- Remove the loop device
setuplosetup -d /dev/loopX
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/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:3756370
- Creation Date:14-FEB-08
- Modified Date:27-APR-12
- SUSESUSE Linux Enterprise Server
Did this document solve your problem? Provide Feedback