NASLite Network Attached Storage

This Intel RAID controller is not on the hardware list. However it uses a driver, present in the 2.6 kernel. Will this card be recognized in NL?



Thanks for answering.

No, it won't.

If the PCI IDs for that card are not in the source then it will not be detected. What does HDT show for that card?

Interesting! Never used the Hardware Detection Tool (HDT) before. Shouldn't there be a download link in a sticky post in the beginning of this hardware forum? I couldn't find the iso, but by sheer coincidence it was in my NASLite download folder already.

Anyway, the Intel controller reads like this:

Vendor: Intel Corporation
Product: ICP Vortex GDT 8546RZ
Location: 00:09.0
PCI ID: 8086:0600 [8086:01c1]
IRQ: 4
Latency: 32
Module: gdth

When I noticed that the controller was recognized, I connected a sata hard drive to the card, and initialized it in the card BIOS as a host drive. I think that that must have gone wrong the first time. The BIOS settings are a bit awkward compared to the 3Ware BIOS, for instance. The drive was formatted, and is currently mounted, and visible as a network drive.

Meaning that you can add the 4-port Intel SRCS14L RAID Controller to the hardware list!

ICP Vortex was acquired by Adaptec a few years ago. Sad since they made some good RAID cards. The support of Adaptec sucks ass. this means that the support for the ICP cards will only go down from there.

Don't know much about them now.

Mike

Could Tony/Ralph have a look at the '[5]' Syslog lines?

# May 14 19:42:35 [4] GDT-HA: Storage RAID Controller Driver. Version: 3.05
# May 14 19:42:35 [4] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 4
# May 14 19:42:35 [1] PCI: setting IRQ 4 as level-triggered
# May 14 19:42:35 [2] gdth 0000:00:07.0: PCI INT A -> Link[LNKB] -> GSI 4 (level, low) -> IRQ 4
# May 14 19:42:35 [4] Configuring GDT-PCI HA at 0/7 IRQ 4
# May 14 19:42:35 [4] IRQ 4/gdth: IRQF_DISABLED is not guaranteed on shared IRQs
# May 14 19:42:35 [4] GDT-HA 0: Name: SRCS14L
# May 14 19:42:35 [2] scsi0 : SRCS14L
# May 14 19:42:35 [3] scsi 0:0:0:0: Direct-Access Intel Host Drive #00 PQ: 0 ANSI: 2
# May 14 19:42:35 [3] scsi 0:0:1:0: Direct-Access Intel Host Drive #01 PQ: 0 ANSI: 2
# May 14 19:42:35 [2] usb 1-2: new low speed USB device using uhci_hcd and address 2
# May 14 19:42:36 [2] usb 1-2: configuration #1 chosen from 1 choice
# May 14 19:42:36 [2] 8139too Fast Ethernet driver 0.9.28
# May 14 19:42:36 [2] 8139too 0000:00:08.0: enabling device (0004 -> 0007)
# May 14 19:42:36 [4] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
# May 14 19:42:36 [1] PCI: setting IRQ 10 as level-triggered
# May 14 19:42:36 [2] 8139too 0000:00:08.0: PCI INT A -> Link[LNKA] -> GSI 10 (level, low) -> IRQ 10
# May 14 19:42:36 [2] eth0: RealTek RTL8139 at 0xa800, 00:10:a7:10:93:be, IRQ 10
# May 14 19:42:36 [1] eth0: Identified 8139 chip type 'RTL-8139C'
# May 14 19:42:36 [2] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
# May 14 19:42:37 [2] ide-gd driver 1.18
# May 14 19:42:37 [2] hda: max request size: 128KiB
# May 14 19:42:37 [2] hda: 249984 sectors (127 MB) w/1KiB Cache, CHS=248/16/63
# May 14 19:42:37 [2] hda: hda1 hda2
# May 14 19:42:38 [2] ide-cd driver 5.00
# May 14 19:42:38 [2] ide-cd: hdc: ATAPI 16X DVD-ROM DVD-R/RAM CD-R/RW drive, 2048kB Cache
# May 14 19:42:38 [2] Uniform CD-ROM driver Revision: 3.20
# May 14 19:42:38 [2] input: NOVATEK USB Keyboard as /devices/pci0000:00/0000:00:04.2/usb1/1-2/1-2:1.0/input/input3
# May 14 19:42:38 [2] generic-usb 0003:0603:00F2.0001: input: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-0000:00:04.2-2/input0
# May 14 19:42:38 [2] input: NOVATEK USB Keyboard as /devices/pci0000:00/0000:00:04.2/usb1/1-2/1-2:1.1/input/input4
# May 14 19:42:38 [2] generic-usb 0003:0603:00F2.0002: input: USB HID v1.10 Device [NOVATEK USB Keyboard] on usb-0000:00:04.2-2/input1
# May 14 19:42:38 [2] usbcore: registered new interface driver usbhid
# May 14 19:42:38 [2] usbhid: v2.6:USB HID core driver
# May 14 19:42:38 [4] Driver 'sd' needs updating - please use bus_type methods
# May 14 19:42:38 [3] sd 0:0:0:0: [sda] 625057020 512-byte hardware sectors: (320 GB/298 GiB)
# May 14 19:42:38 [3] sd 0:0:0:0: [sda] Assuming Write Enabled
# May 14 19:42:38 [5] sd 0:0:0:0: [sda] Assuming drive cache: write through
# May 14 19:42:38 [3] sd 0:0:0:0: [sda] Assuming Write Enabled
# May 14 19:42:38 [5] sd 0:0:0:0: [sda] Assuming drive cache: write through
# May 14 19:42:38 [2] sda:
# May 14 19:42:38 [3] sd 0:0:1:0: [sdb] 625057020 512-byte hardware sectors: (320 GB/298 GiB)
# May 14 19:42:38 [3] sd 0:0:1:0: [sdb] Assuming Write Enabled
# May 14 19:42:38 [5] sd 0:0:1:0: [sdb] Assuming drive cache: write through
# May 14 19:42:38 [3] sd 0:0:1:0: [sdb] Assuming Write Enabled
# May 14 19:42:38 [5] sd 0:0:1:0: [sdb] Assuming drive cache: write through
# May 14 19:42:38 [2] sdb:
# May 14 19:42:38 [2] sda1
# May 14 19:42:38 [4] sdb1
# May 14 19:42:38 [3] sd 0:0:0:0: [sda] Attached SCSI disk
# May 14 19:42:38 [3] sd 0:0:1:0: [sdb] Attached SCSI disk
# May 14 19:43:06 [2] eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
# May 14 19:43:07 [5] hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
# May 14 19:43:07 [5] hda: task_no_data_intr: error=0x04 { DriveStatusError }
# May 14 19:43:07 [5] hda: possibly failed opcode: 0xb0
# May 14 19:43:09 [2] kjournald starting. Commit interval 5 seconds
# May 14 19:43:09 [2] EXT3 FS on sda1, internal journal
# May 14 19:43:09 [2] EXT3-fs: mounted filesystem with writeback data mode.
# May 14 19:43:09 [2] kjournald starting. Commit interval 5 seconds
# May 14 19:43:09 [2] EXT3 FS on sdb1, internal journal
# May 14 19:43:09 [2] EXT3-fs: mounted filesystem with writeback data mode.
# May 14 22:17:04 [2] warning: `smbd' uses 32-bit capabilities (legacy support in use)

Thanks!