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

[Xen-users] iSCSI root on Dom0


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Joe Royall" <joenukem@xxxxxxxxx>
  • Date: Mon, 31 Mar 2008 16:51:09 -0400
  • Delivery-date: Mon, 31 Mar 2008 13:51:42 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:mime-version:content-type; b=lbuNSBBivgEQUBXKTQAmMGXkF6DDAlMBqWGAiLsHDF3g963t8LP3bYTXJcS+DDk/vlTnBCfGm0GKPbikkXFkj5Gp48oAtfuAqsAKBM+5kbh+sx8eq/AGMpXo3sqLxySWEdrCi6sEgQjoCdjlJD83deNukuyczHum5dblGDuTLbQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I am getting the following error on boot on a new install Centos 51:

#/bin/sh ro no such file or directory
then a kernel panic

I have traced it to the call 'switchroot' in the init script in the initrd.

the exact same build without zen has no problems.

the boot messages look like:

Attaching to iSCSI storage
iscsistart: transport class version 2.0-724. iscsid version 2.0-865
iscsistart: version 2.0-865
scsi0 : iSCSI Initiator over TCP/IP
iscsistart: connection1:0 is operational now
    Vendor: IET    Model: Controler    Rev: 0001
    Type: RAID                ANSI SCSI revision: 05
    Vendor    Model: VIRTUAL-DISK    Rev: 0001
    Type:    Direct -Access        ANSI SCSI revision: 05
SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
SCSI device sda: 20971520 512-byte hdwr sectors (10737 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
    sda: sda1
sd 0:0:0:1: Attached scsi disk sda
Waiting for driver initialization
Scanning and configuring dmraid supported devices
Create root device
Mounting root filesystem.
kjournaled starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with orded data mode.
Setting up other filesystems.
Setting up new root fs
no fstab.sys, mounting internal defaults
Copying DHCP lease
Switching to new root and running init
#/bin/sh ro no such file or directory


/tftpboot/pxelinux.cfg/default .....


default iscsi_root_xen
prompt 0

label manual_install
        KERNEL /Centos/51/kickstart/vmlinuz
        APPEND initrd=/Centos/51/kickstart/initrd.img

label kickstart_xen
        KERNEL /Centos/51/kickstart/vmlinuz
        APPEND initrd=/Centos/51/kickstart/initrd.img ks=http://192.168.1.202/anaconda-ks.cfg ksdevice=link noipv6

label kickstart_noxen
        KERNEL /Centos/51/kickstart/vmlinuz
        APPEND initrd=/Centos/51/kickstart/initrd.img ks=http://192.168.1.202/anaconda-ks.noxen.cfg ksdevice=link noipv6

label iscsi_root_xen
        KERNEL mboot.c32
        APPEND /Centos/boot/xen.gz-2.6.18-53.el5 --- /Centos/boot/vmlinuz-2.6.18-53.el5xen ro root=LABEL=/ noipv6 --- /Centos/boot/initrd-2.6.18-53.el5xen.img


label iscsi_root_noxen
  KERNEL /Centos/boot/vmlinuz-2.6.18-53.el5
  APPEND initrd=/Centos/boot/initrd-2.6.18-53.el5.img ro root=LABEL=/  noipv6


the xen and the noxen have different iscsi partitions and only one is activated at a time.

the xen and noxen kickstarts are the same execpt the xen includes the package @Virtualization

Any ideas?

attached is the anaconda generated init inside initrd.
--
Joe Royall

Attachment: init
Description: Binary data

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

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