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

Re: HELP! Boot stops at chkrootfs.sh and can't fsck: /sbin/fsck: cannot execute binary file



Thanks for the help.  Not quite sure if I'm providing the right info, but...

1.  I don't know any initrd files in the dom1, only the domU.  The link to the initrd.gz is (from the xen ".cfg"): /boot/initrd.img-2.6.18-6-xen-amd64
2.  The rootdelay=30 did not resolve it.

Here's the configuration for the dom1 (xen1).

-A

#
#  Configuration file for the Xen instance xen1, created on
# Fri Oct 13 11:00:26 2006.
#


#
#  Kernel + memory size
#
kernel  = '/boot/vmlinuz-2.6.18-6-xen-amd64'
ramdisk = '/boot/initrd.img-2.6.18-6-xen-amd64'
extra = 'rootdelay=30'

memory  = '512'


#
#  Disk device(s).
#
root    = '/dev/sda1 ro'

disk    = [ 'phy:vg00/xen1-disk,sda1,w', 'phy:vg00/xen1-swap,sda2,w' ]

#
#  Hostname
#
name    = 'xen1'


#
#  Networking
#
vif  = [ 'ip=128.253.16.121' ]

#
#  Behaviour
#
on_reboot   = 'restart'
on_crash    = 'restart'



On Jan 31, 2008, at 7:47 PM, martin f krafft wrote:

also sprach Ari Epstein <ate2@cornell.edu> [2008.02.01.1056 +1100]:
Console output is as follows:

Can you mount the filesystem and provide me with a link to the
initrd.gz file for the kernel? The RAID does not start and it may be
because the disk names have changed. Also, try adding rootdelay=30
to the kernel command line and see if that fixes it.

-- 
 .''`.   martin f. krafft <madduck@debian.org>
: :'  :  proud Debian developer, author, administrator, and user
  `-  Debian - when you have better things to do than fixing systems

one morning i shot an elephant in my pyjamas.
how he got into my pyjamas i'll never know.
                                                       -- groucho marx


Reply to: