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/
Home Products Support Community News


[Xen-users] DomU goes into fsck error at boot up.

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] DomU goes into fsck error at boot up.
From: rohan nigam <locaterohan@xxxxxxxxx>
Date: Fri, 3 Sep 2010 14:19:19 -0700 (PDT)
Delivery-date: Fri, 03 Sep 2010 14:21:09 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1283548759; bh=uEzdk/AgbuXXnnbKR7734vCrEvB6/XVMtSkqJmUhDoA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=WQcfoCD6+A07qj47Vx6VcwZvuZaAaFWHw6HUsMSu3dhCeXFsltTfgxsN+/CINk5Ry2GIZL+Uoc66WREHPjKRQMrZRDqbLbHh3kFXMdFY90TiFR8UgBcc4LNw7jd7QOAd6P32VlC32OG+ws1ejiOwLHfoI6S+7I90+Y1pJQSCh6g=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=m9BSL/794NG9PaqJ09ZDSGoLRKK2IrvR1rLfOhnEgGpkchKI9EwHDiEpNFXtVnqyJbmz7md5jnWvF7ZkRBd22mSwAfS+d5Y1Fb9I85Jz+dnJrRy27bCRcro+5mlS9j9lowqIjDJr9+LY4IJ08I+9pkKgfigD1EBOXPIkAO3dUnw=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi Guys,

I have a xen set up with two domu VM's. One of these VM has recently crashed and was running lot of web services. When I tried to xm shutdown and xm create -c domainname, it directly starts fsck and ends up with the following:

INIT: version 2.86 booting
Starting the hotplug events dispatcher: udevd[    2.724077] udevd version 125 started
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...done.
Setting the system clock.
Unable to set System Clock to: Fri Sep 3 20:30:12 UTC 2010 (warning).
Activating swap...[    4.517198] Adding 524280k swap on /dev/hda1.  Priority:-1 extents:1 across:524280k
Checking root file system...fsck 1.41.3 (12-Oct-2008)
/dev/hda2 contains a file system with errors, check forced.
/dev/hda2:                                                                      Unattached inode 403

        (i.e., without -a or -p options)
fsck died with exit status 4
failed (code 4).
An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode. failed!
The root filesystem is currently mounted in read-only mode. A maintenance shell will now be started. After performing system maintenance, press CONTROL-D to terminate the maintenance shell and restart the system. (warning).
Give root password for maintenance
(or type Control-D to continue):
Login incorrect.

Now, this might sound stupid but I do not have the root password for maintenance. Used sudo su - access all this while and I am also in a remote location.

Do any of you know if we can do anything with the .img domu files directly and run manual fsck or at least change the root password for automatic maintainance?

Please help me get around this problem with some quick suggestions.


PS: The 'xm list' still lists the crashed domu in a blocked state.

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>