RE: System hanging with MD3000i with Debian Etch
Yeah, that worked; thanks guys. I did see the ib_iser errors on startup but it looks like it just didn't load due to the symbol problems discussed in the readme. aptitude install linux-headers-`uname -r` wget http://www.open-iscsi.org/bits/open-iscsi-2.0-869.2.tar.gz tar -xvzf open-iscsi-2.0-869.2.tar.gz cd open-iscsi-2.0-869.2 make dpkg-divert --divert /lib/modules/2.6.18-6-686/kernel/drivers/scsi/libiscsi.ko /lib/modules/2.6.18-6-686/kernel/drivers/scsi/libiscsi.ko.debian dpkg-divert --divert /lib/modules/2.6.18-6-686/kernel/drivers/scsi/iscsi_tcp.ko /lib/modules/2.6.18-6-686/kernel/drivers/scsi/iscsi_tcp.ko.debian dpkg-divert --divert /lib/modules/2.6.18-6-686/kernel/drivers/scsi/scsi_transport_iscsi.ko /lib/modules/2.6.18-6-686/kernel/drivers/scsi/scsi_transport_iscsi.ko.debian cp kernel/iscsi_tcp.ko /lib/modules/2.6.18-6-686/kernel/drivers/scsi/ cp kernel/libiscsi.ko /lib/modules/2.6.18-6-686/kernel/drivers/scsi/ cp kernel/scsi_transport_iscsi.ko /lib/modules/2.6.18-6-686/kernel/drivers/scsi/ -Original Message- From: Andrew Moise [mailto:[EMAIL PROTECTED] Sent: Friday, May 16, 2008 10:16 PM To: open-iscsi@googlegroups.com; Bryan Mclellan Subject: Re: System hanging with MD3000i with Debian Etch On Fri, May 16, 2008 at 5:30 PM, Bryan Mclellan <[EMAIL PROTECTED]> wrote: > I have a debian etch (vmware guest) box running 2.6.18-6-686. With both > open-iscsi 2.0.730-1etch1 and 2.0.869.2-2 (from sid) the system hangs when > trying to log in to the MD3000i. Not having done this before I'm fooling > around with directions from [1] and running: The 2.6.18 kernel that ships with etch has some problems with iscsi; what worked for me was to divert the Debian iscsi modules and install ones that I compiled from the open-iscsi tarball. There should be instructions on how to do that in the open-iscsi README. Alternatively, you can install a 2.6.25 or newer kernel; I preferred to stay with the Debian kernel to get security updates and whatnot, but I also tried 2.6.25 and it survived some amount of iscsi stress testing. Cheers. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: System hanging with MD3000i with Debian Etch
Bryan Mclellan wrote: > I have a debian etch (vmware guest) box running 2.6.18-6-686. With both > open-iscsi 2.0.730-1etch1 and 2.0.869.2-2 (from sid) the system hangs when > trying to log in to the MD3000i. Not having done this before I'm fooling > around with directions from [1] and running: > The newer tools do not support the kernel modules in 2.6.18*. The interface was not stablized until 2.6.22. If you want to use the 2.6.18-6-686 you have to use the kernel modules that come with the open-iscsi.org releases. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
RE: System hanging with MD3000i with Debian Etch
) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:MOUS] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
Using IPI No-Shortcut mode
ACPI: (supports S0 S1 S5)
Freeing unused kernel memory: 196k freed
input: AT Translated Set 2 keyboard as /class/input/input0
Time: pit clocksource has been installed.
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not
present [20060707]
ACPI: Getting cpuindex for acpiid 0x1
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not
present [20060707]
ACPI: Getting cpuindex for acpiid 0x2
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not
present [20060707]
ACPI: Getting cpuindex for acpiid 0x3
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot :00:07.1
PCI: Enabling device :00:07.1 ( -> 0001)
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
PIIX4: neither IDE port enabled (BIOS)
SCSI subsystem initialized
Fusion MPT base driver 3.04.01
Copyright (c) 1999-2005 LSI Logic Corporation
Fusion MPT SPI Host driver 3.04.01
ACPI: PCI Interrupt :00:10.0[A] -> GSI 17 (level, low) -> IRQ 169
mptbase: Initiating ioc0 bringup
Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI
Copyright (c) 1999-2006 Intel Corporation.
ioc0: 53C1030: Capabilities={Initiator}
scsi0 : ioc0: LSI53C1030, FwRev=h, Ports=1, MaxQ=128, IRQ=169
Vendor: VMware, Model: VMware Virtual S Rev: 1.0
Type: Direct-Access ANSI SCSI revision: 02
target0:0:0: Beginning Domain Validation
target0:0:0: Domain Validation skipping write tests
target0:0:0: Ending Domain Validation
target0:0:0: FAST-160 WIDE SCSI 320.0 MB/s DT IU RDSTRM RTI WRFLOW PCOMP (6.25
ns, offset 127)
ACPI: PCI Interrupt :00:11.0[A] -> GSI 18 (level, low) -> IRQ 177
PCI: Setting latency timer of device :00:11.0 to 64
SCSI device sda: 6291456 512-byte hdwr sectors (3221 MB)
sda: Write Protect is off
sda: Mode Sense: 5d 00 00 00
sda: cache data unavailable
sda: assuming drive cache: write through
SCSI device sda: 6291456 512-byte hdwr sectors (3221 MB)
sda: Write Protect is off
sda: Mode Sense: 5d 00 00 00
sda: cache data unavailable
sda: assuming drive cache: write through
sda: sda1 sda2 < sda5 >
sd 0:0:0:0: Attached scsi disk sda
e1000: :00:11.0: e1000_probe: (PCI:66MHz:32-bit) 00:0c:29:6b:c6:d0
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
ACPI: PCI Interrupt :00:12.0[A] -> GSI 19 (level, low) -> IRQ 185
PCI: Setting latency timer of device :00:12.0 to 64
e1000: :00:12.0: e1000_probe: (PCI:66MHz:32-bit) 00:0c:29:6b:c6:da
e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
Attempting manual resume
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
input: PC Speaker as /class/input/input1
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
piix4_smbus :00:07.3: Found :00:07.3 device
piix4_smbus :00:07.3: Host SMBus controller not enabled!
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 440BX Chipset.
agpgart: AGP aperture is 64M @ 0xec00
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
Real Time Clock Driver v1.12ac
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Adding 192740k swap on /dev/sda5. Priority:-1 extents:1 across:192740k
EXT3 FS on sda1, internal journal
input: ImPS/2 Generic Wheel Mouse as /class/input/input2
ts: Compaq touchscreen protocol output
loop: loaded (max 8 devices)
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: [EMAIL PROTECTED]
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
e1000: eth1: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
-Original Message-
From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Konrad
Rzeszutek
Sent: Monday, May 19, 2008 6:28 AM
To: open-iscsi@googlegroups.com
Subject: Re: System hanging with MD3000i with Debian Etch
On Sun, May 18, 2008 at 06:21:17PM -0700, Bryan Mclellan wrote:
>
> Of the linux servers console? Sure I can dig one up, it's the first two lines
> of the scsi disk sort of display, twice. Something sort of like:
Preferably the whole thing from start. Not just the last X lines.
>
> D
Re: System hanging with MD3000i with Debian Etch
On Sun, May 18, 2008 at 06:21:17PM -0700, Bryan Mclellan wrote: > > Of the linux servers console? Sure I can dig one up, it's the first two lines > of the scsi disk sort of display, twice. Something sort of like: Preferably the whole thing from start. Not just the last X lines. > > Disk: DELL Model: MD3000 > Blah blah blah blah > > I don't recall exactly what it said, but it wasn't very interesting. It is for kernel engineers. Also please pass in as bootup parameter this value 'loglevel=8'. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
RE: System hanging with MD3000i with Debian Etch
Of the linux servers console? Sure I can dig one up, it's the first two lines of the scsi disk sort of display, twice. Something sort of like: Disk: DELL Model: MD3000 Blah blah blah blah I don't recall exactly what it said, but it wasn't very interesting. -Original Message- From: open-iscsi@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Konrad Rzeszutek Sent: Saturday, May 17, 2008 5:52 AM To: open-iscsi@googlegroups.com Subject: Re: System hanging with MD3000i with Debian Etch Can you attach the serial output or a screen shot? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: System hanging with MD3000i with Debian Etch
On Fri, May 16, 2008 at 02:30:16PM -0700, Bryan Mclellan wrote: > > I have a debian etch (vmware guest) box running 2.6.18-6-686. With both > open-iscsi 2.0.730-1etch1 and 2.0.869.2-2 (from sid) the system hangs when > trying to log in to the MD3000i. Not having done this before I'm fooling > around with directions from [1] and running: > > iscsiadm --mode discovery --type sendtargets --portal 10.0.9.10 > iscsiadm -m node -T > iqn.1984-05.com.dell:powervault.6001c23000d59fc64754447a -p > 10.0.9.10:3260 -l -d 8 > > and I get [2], where the system locks up after: > > Logging in to [iface: default, target: > iqn.1984-05.com.dell:powervault.6001c23000d59fc64754447a, portal: > 10.0.9.10,3260] Can you attach the serial output or a screen shot? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: System hanging with MD3000i with Debian Etch
On Fri, May 16, 2008 at 5:30 PM, Bryan Mclellan <[EMAIL PROTECTED]> wrote: > I have a debian etch (vmware guest) box running 2.6.18-6-686. With both > open-iscsi 2.0.730-1etch1 and 2.0.869.2-2 (from sid) the system hangs when > trying to log in to the MD3000i. Not having done this before I'm fooling > around with directions from [1] and running: The 2.6.18 kernel that ships with etch has some problems with iscsi; what worked for me was to divert the Debian iscsi modules and install ones that I compiled from the open-iscsi tarball. There should be instructions on how to do that in the open-iscsi README. Alternatively, you can install a 2.6.25 or newer kernel; I preferred to stay with the Debian kernel to get security updates and whatnot, but I also tried 2.6.25 and it survived some amount of iscsi stress testing. Cheers. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
System hanging with MD3000i with Debian Etch
I have a debian etch (vmware guest) box running 2.6.18-6-686. With both open-iscsi 2.0.730-1etch1 and 2.0.869.2-2 (from sid) the system hangs when trying to log in to the MD3000i. Not having done this before I'm fooling around with directions from [1] and running: iscsiadm --mode discovery --type sendtargets --portal 10.0.9.10 iscsiadm -m node -T iqn.1984-05.com.dell:powervault.6001c23000d59fc64754447a -p 10.0.9.10:3260 -l -d 8 and I get [2], where the system locks up after: Logging in to [iface: default, target: iqn.1984-05.com.dell:powervault.6001c23000d59fc64754447a, portal: 10.0.9.10,3260] Two lines are printed on the console where you can see it's starting to detect the disks, where it displays that it's an MD3000i. MDSM reports: Date/Time: 5/16/08 2:16:57 PM Sequence number: 953 Event type: 180D Description: Session terminated unexpectedly Event specific codes: 0/0/0 Event category: Internal Component type: RAID Controller Module Firmware Component location: None Logged by: RAID Controller Module in slot 0 Similarly: # iscsiadm -m node -l Logging in to [iface: default, target: iqn.1984-05.com.dell:powervault.6001c23000d59fc64754447a, portal: 10.0.9.12,3260] Logging in to [iface: default, target: iqn.1984-05.com.dell:powervault.6001c23000d59fc64754447a, portal: 10.0.9.13,3260] Logging in to [iface: default, target: iqn.1984-05.com.dell:powervault.6001c23000d59fc64754447a, portal: 10.0.9.10,3260] Logging in to [iface: default, target: iqn.1984-05.com.dell:powervault.6001c23000d59fc64754447a, portal: 10.0.9.11,3260] I've added the host on the MD3000i and configured the virtual disk mapping but haven't set up any sort of authentication. Does anyone have any tips? Bryan [1] http://www.howtoforge.com/iscsi_on_linux [2] iscsiadm: Max file limits 1024 1024 iscsiadm: exec_node_op: : node [iqn.1984-05.com.dell:powervault.6001c23000d59fc64754447a,10.0.9.10,3260] iscsiadm: searching iqn.1984-05.com.dell:powervault.6001c23000d59fc64754447a iscsiadm: found 10.0.9.12,3260,2 iscsiadm: iface iter found default. iscsiadm: updated 'node.name', '' => 'iqn.1984-05.com.dell:powervault.6001c23000d59fc64754447a' iscsiadm: updated 'node.tpgt', '-1' => '2' iscsiadm: updated 'node.startup', 'manual' => 'manual' iscsiadm: updated 'iface.hwaddress', 'default' => 'default' iscsiadm: updated 'iface.iscsi_ifacename', 'default' => 'default' iscsiadm: updated 'iface.net_ifacename', 'default' => 'default' iscsiadm: updated 'iface.transport_name', 'tcp' => 'tcp' iscsiadm: updated 'node.discovery_address', '' => '10.0.9.10' iscsiadm: updated 'node.discovery_port', '0' => '3260' iscsiadm: updated 'node.discovery_type', 'static' => 'send_targets' iscsiadm: updated 'node.session.initial_cmdsn', '0' => '0' iscsiadm: updated 'node.session.initial_login_retry_max', '4' => '4' iscsiadm: updated 'node.session.cmds_max', '128' => '128' iscsiadm: updated 'node.session.queue_depth', '32' => '32' iscsiadm: updated 'node.session.auth.authmethod', 'None' => 'None' iscsiadm: updated 'node.session.timeo.replacement_timeout', '120' => '120' iscsiadm: updated 'node.session.err_timeo.abort_timeout', '15' => '15' iscsiadm: updated 'node.session.err_timeo.lu_reset_timeout', '30' => '20' iscsiadm: updated 'node.session.err_timeo.host_reset_timeout', '60' => '60' iscsiadm: updated 'node.session.iscsi.FastAbort', 'Yes' => 'Yes' iscsiadm: updated 'node.session.iscsi.InitialR2T', 'No' => 'No' iscsiadm: updated 'node.session.iscsi.ImmediateData', 'Yes' => 'Yes' iscsiadm: updated 'node.session.iscsi.FirstBurstLength', '262144' => '262144' iscsiadm: updated 'node.session.iscsi.MaxBurstLength', '16776192' => '16776192' iscsiadm: updated 'node.session.iscsi.DefaultTime2Retain', '0' => '0' iscsiadm: updated 'node.session.iscsi.DefaultTime2Wait', '2' => '2' iscsiadm: updated 'node.session.iscsi.MaxConnections', '1' => '1' iscsiadm: updated 'node.session.iscsi.MaxOutstandingR2T', '1' => '1' iscsiadm: updated 'node.session.iscsi.ERL', '0' => '0' iscsiadm: updated 'node.conn[0].address', '' => '10.0.9.12' iscsiadm: updated 'node.conn[0].port', '3260' => '3260' iscsiadm: updated 'node.conn[0].startup', 'manual' => 'manual' iscsiadm: updated 'node.conn[0].tcp.window_size', '524288' => '524288' iscsiadm: updated 'node.conn[0].tcp.type_of_service', '0' => '0' iscsiadm: updated 'node.conn[0].timeo.logout_timeout', '15' => '15' iscsiadm: updated 'node.conn[0].timeo.login_timeout', '30' => '15' iscsiadm: updated 'node.conn[0].timeo.auth_timeout', '45' => '45' iscsiadm: updated 'node.conn[0].timeo.noop_out_interval', '5' => '5' iscsiadm: updated 'node.conn[0].timeo.noop_out_timeout', '5' => '5' iscsiadm: updated 'node.conn[0].iscsi.MaxRecvDataSegmentLength', '131072' => '131072' iscsiadm: updated 'node.conn[0].iscsi.HeaderDigest', 'None,C
