[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: rohan nigam <locaterohan@xxxxxxxxx>
  • From: Rudi Ahlers <Rudi@xxxxxxxxxxx>
  • Date: Sat, 4 Sep 2010 00:04:00 +0200
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 03 Sep 2010 15:05:41 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=softdux.com; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject:To:Cc:Content-Type:X-Assp-Whitelisted:X-Assp-Envelope-From:X-Assp-Intended-For:X-Source:X-Source-Args:X-Source-Dir; b=alIl/A/mABlRHNKSOsmnTwecdvM/6Rul1mWOkueE+hJ2Y5r37VA72BfDJrzE4ugdBHAtRiXM1LaVmNnZEttPl/aEcO6VzCdSVN/x/xXbRF+aU+5wJan8Mr2/GPZaf+WT;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Fri, Sep 3, 2010 at 11:19 PM, rohan nigam <locaterohan@xxxxxxxxx> wrote:
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

You can either mount the image (mount -o loop img /mnt/img) and run fsck that way. Or, mount the image, edit /mnt/img/etc/shadow and remove the root password, then login with a blank root password :) Remember to change the root password as soon as fsck is complete

Kind Regards
Rudi Ahlers

Website: http://www.SoftDux.com
Technical Blog: http://Blog.SoftDux.com
Office: 087 805 9573
Cell: 082 554 7532
Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.