similar to: iscsi root + Dracut

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

- dracut does not currently support booting a dmsquash file system on an iscsiroot - can not be configured in standalone mode since networking is not up, although works fine if ovirt-config-setup is run once booted. Signed-off-by: Joey Boggs <jboggs at redhat.com> --- recipe/common-pkgs.ks | 1 + scripts/ovirt-config-boot | 67 ++++++++++++++++----

> On 7 Nov 2016, at 22:16, Derek Atkins <derek@ihtfp.com> wrote: > > Hi, > > My last VM imported in 2 minutes. This one has been sitting for three > hours. I think this is a bug. well, some time it does take a long time. Are you sure it was hung? No I/O going on? adding libguestfs list Thanks, michal > > Just in case it helps, here's a larger piece of

Hi list, I had setup my xen box with bond in active-backup mode. I had install open-iscsi as initiator to attach an external iscsi san to my box but open-iscsi didn''t work. When i run this command: #iscsiadm -m node -T iqn.2008-03.local.foo:iSCSI.test.disk1 -l I retrive, after some seconds, this error Logging in to [iface: iface0, target: iqn.2008-03.local.foo:iSCSI.test.disk1,

Hi all, I have the strangest problem on one of our backup server. iscsi doesn't start at all, and gives the following error: [root at 2U-NAS ~]# /etc/init.d/iscsi status iscsid is stopped [root at 2U-NAS ~]# /etc/init.d/iscsi start iscsid is stopped Starting iSCSI daemon: Unable to create pid file: /var/run/brcm_iscsiuio.pid [FAILED] Setting up iSCSI targets: iscsiadm: No records

Dear Srs, I'm getting this error when trying to connect to a Infortrend A16E- G2130-4 storage v?a iSCSI. > Apr 29 10:24:40 vz-10 kernel: scsi1 : iSCSI Initiator over TCP/IP > Apr 29 10:24:41 vz-10 kernel: Vendor: IFT Model: A16E- > G2130-4 Rev: 361F > Apr 29 10:24:41 vz-10 kernel: Type: Direct- > Access ANSI SCSI revision: 04 > Apr

Greetings ocfs2 folks, A client is experiencing some random deadlock issues within a cluster, wondering if anyone can point us in the right direction. The iSCSI connection seemed to have dropped on one node briefly, ultimately several hours later landing us in a complete deadlock scenario where multiple nodes (Node 7 and Node 8) had to be panic'd (by hand - they didn't ever panic on

Hi. Here is the short version: If dom0 experiences a short (< 120 second) network outage the guests whose disks are on iSCSI LUNs get (seemingly) unrecoverable IO errors. Is it possible to make Xen more resiliant to such problems? And now the full version: We''re testing Xen on iSCSI LUNs. The hardware/software configuration is: * Dom0 and guest OS: SLES10 x86_64 * iSCSI LUN on

I just updated one of my virtual hosts to 5.6 and on rebooted I spotted an error about iscsi. Which surprised me, since I don't use iscsi. Yet there it is... % rpm -qf /etc/init.d/iscsi iscsi-initiator-utils-6.2.0.872-6.el5 And they're configured to start iscsi 0:off 1:off 2:off 3:on 4:on 5:on 6:off iscsid 0:off 1:off 2:off 3:on 4:on

Hello all, I got some severe iscsi connection loss on my dom0 (Gentoo 2.6.20-xen-r6, xen 3.1.1). Happening several times a day. open-iscsi version is 2.0.865.12. Target iscsi is the open-e DSS product. Here is a snip of my messages log file: May 5 16:52:50 ying connection226:0: iscsi: detected conn error (1011) May 5 16:52:51 ying iscsid: connect failed (111) May 5 16:52:51 ying iscsid:

Package: xcp-storage-managers Version: 0.1.1-2 Severity: important Dear Maintainer, I can not create an iSCSI storage resource using the following command: xe sr-create host-uuid=<my-host-uuid> content-type=user name-label="LVM over iSCSI SR"> shared=true device-config:target=192.168.10.100 device-config:targetIQN=<here-target-iqn>

On 12/22/2013 10:09 AM, Marco wrote: > On 2013–12–21 John Ferlan wrote: > >> On 12/17/2013 07:13 PM, Marco wrote: >>> Hi! >>> >>> I'm new to libvirt and face problems connecting to an iSCSI target. >>> What I intend to do is to connect libvirt (I tried virt-manager and >>> virsh) to an iSCSI target and then boot from the LUNs which

Hi, I'm installing CentOS 5.4 on an iSCSI disk. When I choose to install the Server component only, the system boots perfectly from the iSCSI disk. When I choose to install the Server and the Virtualization components, it looks like the lvm root partition can't be mounted, I get the message: iscsistart: could not get boot entry Can't the Xen kernel boot from iSCSI? -Bart

Finally, I was able to find a solution for this. I'm posting the result here, just in case that it's useful for someone else in the future ... The problem was not in initramfs (dracut), but on the fact that /dev/sda2 partition(PV), after I resized it, somehow got 2 partition table signatures. One was set as a "dos" partition with an offset "0x1fe" and second set as

Hi, i have a debian Etch x86_64 with a xen 3.1 on a kernel 2.6.18-xen. I have some DomU with Debian Etch. I installed open-iscsi, configure /etc/iscsi/iscsid.conf: --- node.active_cnx = 1 node.startup = automatic #node.session.auth.username = dima #node.session.auth.password = aloha node.session.timeo.replacement_timeout = 120 node.session.err_timeo.abort_timeout = 10

On 2013–12–21 John Ferlan wrote: > On 12/17/2013 07:13 PM, Marco wrote: > > Hi! > > > > I'm new to libvirt and face problems connecting to an iSCSI target. > > What I intend to do is to connect libvirt (I tried virt-manager and > > virsh) to an iSCSI target and then boot from the LUNs which contain > > the VMs. > > > > I followed the

On 12/17/2013 07:13 PM, Marco wrote: > Hi! > > I'm new to libvirt and face problems connecting to an iSCSI target. > What I intend to do is to connect libvirt (I tried virt-manager and > virsh) to an iSCSI target and then boot from the LUNs which contain > the VMs. > > I followed the documentation¹ but got stuck at section 12.1.5.4.3. > > 1) > virsh

Hi, I am doing a test setup of 11G RAC, and I am using Jeff Hunter's document to achieve this. I have 3 nodes all running Linux Redhat 4 htsscsun06-openfiler htssclin5 htssclin4 I have created the Logical Volumes on htsscsun06-openfiler - fdisk -l shows fdisk -l Disk /dev/hdb: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of

Hello all. We recently purchased HP Proliant DL380 G7 server and also a HP Lefthand P4500 G2 24TB iSCSI box. The server itself has Quad Ethernet based on the BCM5709 Chipset from Broadcom (NetXtreme II). My main question is about iSCSI offload mechanism, as iSCSI itself is pretty new to me but I have gotten a good hold on it tho. I have managed to setup and configured our Lefthand box into

> Yannis Milios wrote: >>> But, what happens if you let the kernel post install scripts do the >>> work or setting up the initrd things? >> >> Initially, I just rebooted from LiveCD and left Grub,kernel and dracut >> do >> their job with the defaults, but unfortunately, boot process stops at >> initrd (dracut) stage with the following error: