similar to: upgrade issue

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:

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

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, I'm fairly new to centos and to iscsi, I have installed a fresh copy of centos (CentOS release 5 (Final)) and installed iscsi-initator-utils, iscsiadm -V shows iscsiadm version 2.0-865 . when i try to connect to iscsi target it doesnt work ... it just stays idle , i try something like: iscsiadm -m discovery -t st -p 172.20.2.76 show or with -m node .... --login ...etc, none works.

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

- 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 ++++++++++++++++----

Hello We were attempting to use scsi-target-utils, hosted on a xen dom0 vm using localhost, and running into some problems. I was not able to reproduce this on a centos 7.2 server using the default kernel. (From dmesg) Apr 4 11:18:42 funk kernel: [ 596.511204] connection2:0: detected conn error (1022) Apr 4 11:18:42 funk kernel: connection2:0: ping timeout of 5 secs expired, recv

Are folks in the Centos community succesfully using device-mapper-multipath? I am looking to deploy it for error handling on our iSCSI setup but there seems to be little traffic about this package on the Centos forums, as far as I can tell, and there seems to be a number of small issues based on my reading the dm-multipath developer lists and related resources. -geoff Geoff Galitz Blankenheim

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

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've just test an ATI FirePro 2460 graphics card on CentOS 6.4. It connects 4 monitors. It worked with the standard radeon driver. I was able to arrange the monitors into my preferred configuration (as a square array, 1 upper left, 2 lower left, 3 lower right, 4 upper right) simply by clicking System -> Preferences -> Display, and then moving the four monitor images. This creates the

Hi, How do I setup multiple password protected iSCSI targets on Linux? I know that mounting a password protected iSCSI target requires modify these records with the appropriate values: node.session.auth.username = My_ISCSI_USR_NAME node.session.auth.password = MyPassword discovery.sendtargets.auth.username = My_ISCSI_USR_NAME discovery.sendtargets.auth.password = MyPassword But, now I need

Hi all, I have a Dell server running cent 5.6, new install, connecting to an IBM DS3500. I have configured iscsi connections using iscsid and can log into the targets on the IBM. I can also mount the LUNs when accessing them from their active controller path. When I throw multipath into the mix, it fails completely. Multipath is working, when I run multipath -ll it shows me the correct active

Hi, I'm trying to disconnect some iSCSI targets, but can't seem to. [root at localhost ~]# iscsiadm -m session tcp: [1] 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:500gb tcp: [3] 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.thin3.vg0.1tba tcp: [4] 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:extent0 tcp: [5] 192.168.2.200:3260,1

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

Hi All, For my issue, first thanks to ALL, I have some idea of it. Also Thank Peter for his kind remind, I would become one good guy in this list. Most mentioned MTU, but how I assure that the problem is just MTU, how I debug it? Here is my bridge configuration: Internet | | Gateway | | eth0 Ethernet Bridge | eth1 | H u b ( one normal hub

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 pool-define-as \ --name foo \ --type iscsi

I four nodes setup to do active-backup bonding and the drivers loaded for the bonded network interfaces vary between tg3 and e100. All interfaces with the e100 driver loaded report errors much like what you see here: bonding: bond0: link status definitely down for interface eth2, disabling it e100: eth2: e100_watchdog: link up, 100Mbps, full-duplex bonding: bond0: link status definitely up for

Main reason for refactor is no ovirt-node-image binary image allowed in fedora. Moves tools and kickstart files form ovirt-node-image to subpackage ovirt-node-recipe. Removes old sub packages form ovirt-node, stateless, logos, selinux. Modifies init scripts to meet Fedora packaging guidelines: added status, reload, and lockfile, rhbz: 514221 Added License file.

Could the problem be that the e100 can do IP receive checksumming on the board, but the eepro driver doesn't enable it. When the board is doing checksum offload, then the csum field isn't set. Please try disabling receive checksumming on the e100 driver modprobe e100 XsumRX=0 If this is the problem, it exists both 2.4 and 2.6. On Wed, 27 Aug 2003 18:24:57 +0200 Hannes Schulz