On Fri, Sep 3, 2010 at 11:19 PM, rohan nigam <locaterohan@yahoo.com>
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
> done.
> 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
>
>
> /dev/hda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> (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.
>
> Thanks,
> Rohan
>
> PS: The ''xm list'' still lists the crashed domu in a
blocked state.
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
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
SoftDux
Website: http://www.SoftDux.com
Technical Blog: http://Blog.SoftDux.com
Office: 087 805 9573
Cell: 082 554 7532
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users