WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] how to run fsck for a crashed domU?

To: Rudi Ahlers <Rudi@xxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] how to run fsck for a crashed domU?
From: MS <ms@xxxxxxxxxx>
Date: Fri, 01 Aug 2008 14:07:02 +0200
Cc:
Delivery-date: Fri, 01 Aug 2008 05:07:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080801135141.mrkyj00vi8888888@localhost>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20080801135141.mrkyj00vi8888888@localhost>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.16 (Windows/20080708)
Do this:

fsck.ext2 -y -f /home/vm/vm01.img
or
fsck.ext2 -y -f /home/vm/vm01.img
or
xfs_check -f /home/vm/vm01.img

... the case for your filesystem type.

Rudi Ahlers schrieb:
Hi all

I have a CentOS Xen domU, on a CentOS server, which crashed and doesn't boot up. The domU uses a disk image, /home/vm/vm01.img

I get the following in the console:

----snip----

Scanning logical volumes
  Reading all physical volumes.  This may take a while...
  Found volume group "VolGroup00" using metadata type lvm2
Activating logical volumes
  2 logical volume(s) in volume group "VolGroup00" now active
Creating root device.
Mounting root filesystem.
kjournald starting.  Commit interval 5 second

-----snip-----

So, it's using an LVM file system, on top of the Xen image.
But, then I get this:

----snip-----
Setting up Logical Volume Management: 2 logical volume(s) in volume group "VolGroup00" now active
[  OK  ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/VolGroup00/LogVol00
/dev/VolGroup00/LogVol00 contains a file system with errors, check forced.
/dev/VolGroup00/LogVol00: Inode 67830 has illegal block(s).

/dev/VolGroup00/LogVol00: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    (i.e., without -a or -p options)
[FAILED]

*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.


----snip-----


So, how can I run fsck on that file system?

I have tried to mount /home/vm/vm01.img - but it fails:

# mount -o loop /home/vm/vm01.img /mnt/vm01/
mount: you must specify the filesystem type



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users