All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Paterson-Jones <roland@rolandpj.com>
To: xen-devel@lists.sourceforge.net
Subject: Newbie problem: disk error launching FC3 in non-0 domain
Date: Tue, 08 Feb 2005 16:19:38 +0200	[thread overview]
Message-ID: <4208CA7A.5080102@rolandpj.com> (raw)

Hi again

I have a minimal Fedora Core 3 image running fine as domain 0 (thanks 
and sorry for the previous FAQ query) using both the standard install 
ramdisk image, and the FC3 ramdisk image downloaded from xen sourceforge.

However, I can't get it running in a non-zero domain.

In brief, I have a full FC3 installed on /dev/hda1, which I typically 
use as my domain 0 OS. Then I have a minimal FC3 installed on /dev/hdb2.

I can boot into the minimal FC3 on /dev/hdb2 as domain 0 under Xen 
without a problem.

I'm trying to 'xm create' the minimal FC3 from the full FC3 under Xen, 
but I get a disk error. Here's the relevant log:

------------------------------------------------------------------------------------------------------
<snip>

Creating /dev
Starting udev
Creating root device
Mounting root filesystem
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
Switching to new root
modprobe: FATAL: Could not load /lib/modules/2.6.10-xenU/modules.dep:
No such file or directory

INIT: version 2.85 booting
                Welcome to Fedora Core
                Press 'I' to enter interactive startup.
Starting udev:  [  OK  ]
Initializing hardware...  storage network audio done[  OK  ]
raidautorun: failed to open /dev/md0: 6
Configuring kernel parameters:  [  OK  ]
hwclock is unable to get I/O port access:  the iopl(3) call failed.
Setting clock  (localtime): Tue Feb  8 16:05:19 SAST 2005 [  OK  ]
Setting hostname localhost.localdomain:  [  OK  ]
Checking root filesystem
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/hdb2
/: clean, 46221/4866048 files, 350711/9727357 blocks
Error writing block 1548 (Attempt to write block from filesystem
resulted in short write).  Error writing block 1548 (Attempt to write
block from filesystem resulted in short write).

/: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)


/: 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.
Give root password for maintenance
(or type Control-D to continue):

-----------------------------------------------------------------------------------------

Any idea what the problem is?

Thanks again
Roland



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

             reply	other threads:[~2005-02-08 14:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08 14:19 Roland Paterson-Jones [this message]
2005-02-08 14:28 ` Newbie problem: disk error launching FC3 in non-0 domain Mark A. Williamson
2005-02-08 14:43 ` Roland Paterson-Jones
2005-02-08 21:14 ` Rik van Riel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4208CA7A.5080102@rolandpj.com \
    --to=roland@rolandpj.com \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.