Subject: | |
From: | |
Reply To: | |
Date: | Mon, 24 Sep 2007 15:12:54 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Bruce,
Notice that the PERC 5/I in the graphic is not the SAS one.
Bruce Osborne
Liberty University
-----Original Message-----
From: Cisco Clean Access Users and Administrators [mailto:[log in to unmask]] On Behalf Of Bruce A. Locke
Sent: Monday, September 24, 2007 3:00 PM
To: [log in to unmask]
Subject: Re: [CLEANACCESS] Dell 1950 Raid Card
Jackie Cheng (jaccheng) wrote:
> Sorry for the confusion, we will update the doc to be more clear.
>
> Attached is a snapshoot of the supported controller. When ordering 1950,
> at "Primary Controller" section, select "PERC 5/I, Integrated Controller
> Card".
>
Thanks Jackie. I'm going to assume due to the lack of part number in
the screenshot that Part #341-3094 labeled as "PERC 5/i, Integrated
Controller Card" with SAS drives is what we are talking about.
If so then there might be another issue at play. The following is from
such a system and occurs during the first boot after installation from cd:
Red Hat nash version 4.2.15 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading sd_mod.kmegasas: 00.00.02.00-rc4 Fri Sep 16 12:37:08 EDT 2005
o module
Loadinmegasas: 0x1028:0x0015:0x1028:0x1f03: g megaraid_sas.kbus 2:slot
14:func 0
o module
ACPI: PCI Interrupt Link [LK02] enabled at IRQ 6
PCI: setting IRQ 6 as level-triggered
ACPI: PCI interrupt 0000:02:0e.0[A] -> GSI 6 (level, low) -> IRQ 6
scsi0 : LSI Logic SAS based MegaRAID driver base14.5
Vendor: DP Model: BACKPLANE Rev: 1.05
Type: Enclosure ANSI SCSI revision: 05
Vendor: DELL Model: PERC 5/i Rev: 1.03
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 142082048 512-byte hdwr sectors (72746 MB)
SCSI device sda: drive cache: write through
SCSI device sda: 142082048 512-byte hdwr sectors (72746 MB)
SCSI device sda: drive cache: write through
sda: sda1 sda2 sda3
Attached scsi disk sda at scsi0, channel 2, id 0, lun 0
Creating root device
mkrootdev: labelKernel panic - not syncing: Attempted to kill init!
/ not found
Mo unting root filesystem
mount: error 2 mounting ext3
Switching to new root
ERROR opening /dev/console!!!!: 2
error dup2'ing fd of 0 to 0
error dup2'ing fd of 0 to 1
error dup2'ing fd of 0 to 2
unmounting old /proc
unmounting old /sys
switchroot: mount failed: 22
The install media used was "cca-4.1_2-K9.iso" selecting the Server
package set.
Is this a known issue, am I missing something from the documentation, or
should I poke TAC about this?
--
Bruce A. Locke
[log in to unmask]
HAB 50 - (845) 257-3809
Network Administrator
Computer Services
State University of New York at New Paltz
|
|
|