Please pardon my idiocy, but I'm a complete newcomer to iSCSI. I have a Dell Workstation that I'm trying to set up as an iSCSI target. I have a bunch of hard drives that I've set up in RAIDS on an Adaptec 2200S, using the BIOS utility available at bootup. These are completely fine (I used them before on Windows), and even show up with the "container list" command in the AACLI that I access via RAID tools from the DSS-LITE console. The proper names, sizes, and SCSI IDs are there. However, in the web setup, under configuration->volume manager, it says "no units found". Under setup->H/W RAID, it just gives the info about "Adaptec administration". I rescan, rebooted several times, and even ran the "container clear" from CLI---but nothing I do gets me to be able to see the RAIDS in the web interface. The two RAIDs are a 200 GB RAID 5, involving 4 drives, and a 550 GB RAID0, involving two drives.
I'm probably doing something really stupid, so any advice on how to fix the problem would be greatly appreciated. Thanks!
From the GUI in Status > Hardware does the DSS LITE recognise the 2200S for the driver being loaded. Also check to see if the 2200S firmware is the latest, looks like the latest is
v8205. If you go into the SW RAID tool from the GUI do you see any of the drives availble.
Any chance you can download the Demo-CD of DSS from link below. I want to see if it will work with this or not. Also are you able to use the Adaptec Storage Manager from a another system to access it. We don't have ingrate GUI access for Adaptec only for 3Ware, Areca, HighPoint and Promise.
From the BIOS of the Adaptec once creating the RAID sets you should see them in the Volume Manager - though there might be something in the BIOS preventing us from seeing the RAIDs just not sure what it could be as it should be simple. Try testing with the with just the drives as single drives just to see if we are seeing them independently from the GUI SW RAID tool.
If possible go to Status > Hardware > Logs > then click on the Download button and download the logs. Look at the dmesg log to see any errors from the Adaptec controller or drives.
I took out my CD drive when I installed all of the hard drives, so if a CD could be avoided at the moment, that would be good (though I can move hardware around if need be).
I've installed the Adaptec Storage Manager (ASM), though I've only used it locally (internal card on a Windows system in the past). I'm not sure how to connect; I put in the IP address of the DSS-Lite box, but ASM couldn't connect directly.
The logs show that I can access both RAIDs, and have cleared the logical disk volumes from the CLI:
Here's RaidEvtA.log (cutting out a bunch of redundant lines):
------------------------------------------------
July 26, 2008 3:24:34 AM CEST INF 212:A00C-S--L-- dss Task Scheduler: Task 1 scheduled successfully..
July 26, 2008 3:56:05 AM EDT INF dss File system changed: controller 1, logical device 2
July 26, 2008 3:56:05 AM EDT INF dss Container changed: controller 1, logical device 2
July 26, 2008 3:56:05 AM EDT INF dss Running: Clear logical disk. 0%. 0 bad sectors. Controller 1, logical device 2
July 26, 2008 3:56:05 AM EDT INF dss File system changed: controller 1, logical device 1
July 26, 2008 3:56:07 AM EDT INF 342:A01C-S--L02 dss Clearing: controller 1, logical device 2 ("550RAID0").
July 26, 2008 3:56:13 AM EDT INF dss Container changed: controller 1, logical device 1
July 26, 2008 3:56:13 AM EDT INF dss Running: Clear logical disk. 0%. 0 bad sectors. Controller 1, logical device 1
July 26, 2008 3:56:15 AM EDT INF 342:A01C-S--L01 dss Clearing: controller 1, logical device 1 ("PeterLu1").
July 26, 2008 3:57:07 AM EDT INF dss Running: Clear logical disk. 5%. 0 bad sectors. Controller 1, logical device 1
...
July 26, 2008 4:18:25 AM EDT INF dss Complete: Clear logical disk. 100%. 0 bad sectors. Controller 1, logical device 1
July 26, 2008 4:18:25 AM EDT INF dss Complete: Clear logical disk. 100%. 0 bad sectors. Controller 1, logical device 1
July 26, 2008 4:18:25 AM EDT INF dss Container changed: controller 1, logical device 1
July 26, 2008 4:18:25 AM EDT INF dss Container changed: controller 1, logical device 1
July 26, 2008 4:18:27 AM EDT INF 345:A01C-S--L01 dss Logical device is normal: controller 1, logical device 1 ("PeterLu1").
July 26, 2008 4:18:27 AM EDT INF 343:A01C-S--L01 dss Clear complete: controller 1, logical device 1 ("PeterLu1").
...
July 26, 2008 5:11:27 AM EDT INF 345:A01C-S--L02 dss Logical device is normal: controller 1, logical device 2 ("550RAID0").
July 26, 2008 5:11:27 AM EDT INF 343:A01C-S--L02 dss Clear complete: controller 1, logical device 2 ("550RAID0").
------------------------------------------------
At the same time, some errors were generated. Here's RaidErrA.log
------------------------------------------------
26 Jul 2008 03:24:26,841 [main] WARN MasterDataProc.<init>:130 - Discovered controllers: ARC
26 Jul 2008 03:24:34,604 [main] ERROR JCRMUtil.AgentErrorLog:90 - Security Manager io exception, creating a new list.
26 Jul 2008 03:30:35,021 [AutoDiscoveryEngine] WARN SLPManager.handleMessage:722 - Could not send ServiceReply
org.ch.ethz.iks.slp.ServiceLocationException: Network is unreachable target address: 192.168.0.220 portInfo: 34580
at org.ch.ethz.iks.slp.impl.SLPManager.sendMessage(SL PManager.java:947)
at org.ch.ethz.iks.slp.impl.SLPManager.handleMessage( SLPManager.java:720)
at org.ch.ethz.iks.slp.impl.SLPManager.multicastConve rgenceRequest(SLPManager.java:1164)
at org.ch.ethz.iks.slp.impl.SLPManager.request(SLPMan ager.java:1051)
at org.ch.ethz.iks.slp.impl.LocatorImpl.findServices( LocatorImpl.java:128)
at com.ibm.sysmgt.raidmgr.agent.AutoDiscoveryEngine.g etLocalDiscoveryAgents(AutoDiscoveryEngine.java:34 7)
at com.ibm.sysmgt.raidmgr.agent.AutoDiscoveryEngine.h eartbeat(AutoDiscoveryEngine.java:268)
at com.ibm.sysmgt.raidmgr.agent.AutoDiscoveryEngine.r un(AutoDiscoveryEngine.java:235)
26 Jul 2008 03:45:34,537 [main] WARN MasterDataProc.<init>:130 - Discovered controllers: ARC
26 Jul 2008 11:48:41,405 [main] WARN MasterDataProc.<init>:130 - Discovered controllers: ARC
26 Jul 2008 11:58:53,264 [main] WARN MasterDataProc.<init>:130 - Discovered controllers: ARC
26 Jul 2008 12:41:45,313 [main] WARN MasterDataProc.<init>:130 - Discovered controllers: ARC
------------------------------------------------
***I've changed the IP address of the box to 192.168.1.120, but the SLPManager is looking at the default 192.168.0.220, according to the error message log. Can I change this somewhere?***
When installing the Adaptec Storage Manager on another system try entering either Internal then right click to Add managed system and enter the port "34,571", 3. Enter the ip address of the DSS LITE in Host name/IP address then Enter "raid" in "User name" and "Password" entry to see if you can access it.
The reason for the CD was to verify any issues with DSS LITE vs. the CD version.
Thanks for the ASM instructions. It works just fine, and I can see both of the RAIDs I created from the other machine; the properties are all as they should be.
I'm not sure what specifically to look for in the dmesg log, so I'll post it in the next message (which I presume you can delete later if you want to shorten this thread).
Simple Boot Flag value 0x87 read from CMOS RAM was invalid
Simple Boot Flag at 0x7a set to 0x1
* This chipset may have PM-Timer Bug. Due to workarounds for a bug,
* this time source is slow. If you are sure your timer does not have
* this bug, please use "pmtmr_good" to disable the workaround
IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com>
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: disabled - APM is not SMP safe.
audit: initializing netlink socket (disabled)
audit(1217076038.104:1): initialized
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
SGI XFS with ACLs, security attributes, realtime, large block numbers, no debug enabled
SGI XFS Quota Management subsystem
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
vesafb: framebuffer at 0xe8000000, mapped to 0xf8880000, using 1875k, total 131072k
vesafb: mode is 800x600x16, linelength=1600, pages=2
vesafb: protected mode interface info at c000:e4e0
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 100x37
fbsplash: console 0 using theme 'default'
fb0: VESA VGA frame buffer device
vga16fb: initializing
vga16fb: mapped to 0xc00a0000
fb1: VGA16 VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 131072K size 1024 blocksize
loop: loaded (max 255 devices)
nbd: registered device at major 43
ipddp.c:v0.01 8/28/97 Bradford W. Johnson <johns393@maroon.tc.umn.edu>
ipddp0: Appletalk-IP Encap. mode by Bradford W. Johnson <johns393@maroon.tc.umn.edu>
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH4: IDE controller at PCI slot 0000:00:1f.1
PCI: Enabling device 0000:00:1f.1 (0000 -> 0003)
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 16
ICH4: chipset revision 1
ICH4: not 100% native mode: will probe irqs later
ICH4: neither IDE port enabled (BIOS)
Probing IDE interface ide0...
Probing IDE interface ide1...
ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 128 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 17, io mem 0xfe500000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 18, io base 0x00001000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001020
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 16, io base 0x00001040
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usb 1-2: new high speed USB device using ehci_hcd and address 2
Initializing USB Mass Storage driver...
usb 1-2: configuration #1 chosen from 1 choice
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 4 ports detected
usb 1-4: new high speed USB device using ehci_hcd and address 3
usb 1-4: configuration #1 chosen from 1 choice
usb 1-2.4: new low speed USB device using ehci_hcd and address 4
usb 1-2.4: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver hiddev
input: Logitech USB Receiver as /class/input/input0
input: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:1d.7-2.4
input: Logitech USB Receiver as /class/input/input1
input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:1d.7-2.4
usbcore: registered new driver usbhid
/home/src/MF/kernel.org/trunk/drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
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
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: automatically using best checksumming function: pIII_sse
pIII_sse : 3455.000 MB/sec
raid5: using function: pIII_sse (3455.000 MB/sec)
raid6: int32x1 713 MB/s
raid6: int32x2 691 MB/s
raid6: int32x4 550 MB/s
raid6: int32x8 635 MB/s
raid6: mmxx1 2135 MB/s
raid6: mmxx2 2728 MB/s
raid6: sse1x1 1175 MB/s
raid6: sse1x2 2416 MB/s
raid6: sse2x1 1882 MB/s
raid6: sse2x2 3004 MB/s
raid6: using algorithm sse2x2 (3004 MB/s)
md: raid6 personality registered for level 6
md: multipath personality registered for level -4
md: faulty personality registered for level -5
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
device-mapper: 4.6.0-ioctl (2006-02-17) initialised: dm-devel@redhat.com
device-mapper: dm-multipath version 1.0.4 loaded
device-mapper: dm-round-robin version 1.0.0 loaded
ip_conntrack version 2.4 (8192 buckets, 65536 max) - 200 bytes per conntrack
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
NET: Registered protocol family 5
Starting balanced_irq
Using IPI Shortcut mode
Freeing unused kernel memory: 240k freed
squashfs: version 3.2-r2 (2007/01/15) Phillip Lougher
aufs 20070903
attempt to access beyond end of device
loop0: rw=0, want=66, limit=8
isofs_fill_super: bread failed, dev=loop0, iso_blknum=16, block=32
attempt to access beyond end of device
loop0: rw=0, want=68, limit=8
attempt to access beyond end of device
loop0: rw=0, want=1252, limit=8
attempt to access beyond end of device
loop0: rw=0, want=1028, limit=8
UDF-fs: No partition found (1)
XFS: bad magic number
XFS: SB validate failed
Vendor: USB Model: DISK 2.0 Rev: 0828
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sda: 1966080 512-byte hdwr sectors (1007 MB)
sda: Write Protect is off
sda: Mode Sense: 43 00 00 00
SCSI device sda: 1966080 512-byte hdwr sectors (1007 MB)
sda: Write Protect is off
sda: Mode Sense: 43 00 00 00
sda: sda1
sd 0:0:0:0: Attached scsi removable disk sda
usb-storage: device scan complete
UDF-fs: No VRS found
XFS: bad magic number
XFS: SB validate failed
UDF-fs: No VRS found
XFS: bad magic number
XFS: SB validate failed
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-0, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
attempt to access beyond end of device
dm-1: rw=0, want=66, limit=8
isofs_fill_super: bread failed, dev=dm-1, iso_blknum=16, block=32
attempt to access beyond end of device
dm-1: rw=0, want=68, limit=8
attempt to access beyond end of device
dm-1: rw=0, want=1252, limit=8
attempt to access beyond end of device
dm-1: rw=0, want=1028, limit=8
UDF-fs: No partition found (1)
XFS: bad magic number
XFS: SB validate failed
UDF-fs: No VRS found
XFS: bad magic number
XFS: SB validate failed
UDF-fs: No VRS found
XFS: bad magic number
XFS: SB validate failed
UDF-fs: No VRS found
XFS: bad magic number
XFS: SB validate failed
UDF-fs: No VRS found
XFS: bad magic number
XFS: SB validate failed
attempt to access beyond end of device
dm-6: rw=0, want=386, limit=384
isofs_fill_super: bread failed, dev=dm-6, iso_blknum=96, block=192
UDF-fs: No VRS found
XFS: bad magic number
XFS: SB validate failed
From the dmesg logs it shows nothing about the Adaptec yet in the Status > Hardware gui your seeing it....
So from the dmesg log let's approach this at the hardware layer, try turning of any power management features of the motherboard or move to another slot to test. Any settings in the Adaptec that you can test.. turning off the BIOS or other options that might affect the issue. I know that you have removed the CD-ROM any chance you can test w/ the Demo-CD.
Coming up blank as I don't have this card with me. You can send me the whole logs and maybe something might show up.