vm issue **file system was modified**

Hi
I updated the kernels on host and guests.
Then rebooted.
1 VM didn't start up with this error

.. failed : Using config file "/xen/travelsuite.cfg". WARNING:root:Unknown directive root WARNING:root:Unknown directive kernel
WARNING:root:Unknown directive initrd Traceback (most recent call last): File "/usr/bin/pygrub", line 684, in ? data = fs.open_file(chosencfg["kernel"]).read()
IOError: [Errno 2] No such file or directory No handlers could be found for logger "xend"
Error: Boot loader didn't return any data!
Usage: xm create [options] [vars]
Create a domain based on . Options: -h, --help
Print this help. --help_config
Print the available configuration variables (vars) for the configuration script. -q, --quiet
Quiet. --path=PATH
Search path for configuration scripts. The value of PATH is a colon-separated directory list.
-f=FILE, --defconfig=FILE Use the given Python configuration script.
The configuration script is loaded after arguments have been processed.
Each command-line option sets a configuration variable named after its long option name, and these variables are placed in the environment of the script before it is loaded.
Variables for options that may be repeated have list values.
Other variables can be set using VAR=VAL on the command line.
After the script is loaded, option values that were not set on the command line are replaced by the values set in the script. -F=FILE, --config=FILE
Domain configuration to use (SXP).
SXP is the underlying configuration format used by Xen.
SXP configurations can be hand-written or generated from Python configuration scripts, using the -n (dryrun) option to print the configuration.
-n, --dryrun Dry run - prints the resulting configuration in SXP but does not create the domain.
-p, --paused Leave the domain paused after it is created.
-c, --console_autoconnect Connect to the console after the domain is created.

I then changed the Boot method from PYgrub to Host kernel and got this error

failed : Disk check failed : fsck 1.39 (29-May-2006) e2fsck 1.39 (29-May-2006)
Superblock last mount time is in the future. Fix? yes
Superblock last write time is in the future. Fix? yes Pass
1: Checking inodes, blocks, and sizes Pass
2: Checking directory structure Pass
3: Checking directory connectivity Pass
4: Checking reference counts Pass
5: Checking group summary information /xen/domain.img:
***** FILE SYSTEM WAS MODIFIED ***** /xen/domain.img: 73983/3639264 files (1.9% non-contiguous), 557751/7417856 blocks

I then went into the /xen/domain.cfg and changed the bottom 2 lines
from
vfb = ['type=vnc,vncunused=1,vncpasswd=PASSWORD,vnclisten=0.0.0.0'] bootloader = "/usr/bin/pygrub"

to
kernel = "/xen/vmlinuz-vm2-xenU" ramdisk = "/xen/initrd.vm2.xenU.img" root = "/dev/sda1 ro"

now it runs again
there seems to be unwanted issues with PYgrub ..

Ronald