Dent sweet roderick nathan
On Nov 11, 2010 9:29 AM, <[email protected]> wrote:
Send Linux-PowerEdge mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Linux-PowerEdge digest..."
Today's Topics:
1. RE: Getting iscsi offload on a M610 to work ([email protected])
2. Perc 6/i Puncturing bad blocks (Jacob P)
3. Re: megaraid_sas from RHEL5.5 kernel 2.6.18-194.26.1.el5
(Richard Chadwick)
----------------------------------------------------------------------
Message: 1
Date: Thu, 11 Nov 2010 21:47:01 +0530
From: <[email protected]>
Subject: RE: Getting iscsi offload on a M610 to work
To: <[email protected]>
Cc: [email protected]
Message-ID:
<
dbfb1b45af80394abd1c807e9f28d1570262f40...@blrx7mcdc203.amer.dell.com>
Content-Type: text/plain; charset="us-ascii"
> -----Original Message-----
> From: Ton Damen [mailto:[email protected]]
> Sent: Thursday, November 11, 2010 11:07 AM
> To: Iyer, Shyam
> Cc: linux-poweredge-Lists
> Subject: Re: Getting iscsi offload on a M610 to work
>
> [email protected] wrote:
> >
> >> -----Original Message-----
> >> From: linux-poweredge-bounces-Lists On Behalf Of Ton Damen
> >> Sent: Thursday, November 11, 2010 10:40 AM
> >> To: linux-poweredge-Lists
> >> Subject: Getting iscsi offload on a M610 to work
> >>
> >> Hi,
> >>
> >> I'm trying to get offload iscsi (rhel 5.5) to work on a PowerEdge M610
> >> and bnx2i.
> >> The thing is that I get it to work through the normal tcp/ip stack but
> >> not by specifying an iface which suppose to do offload iscsi.
> >> The discovery step works, but as I understood, this goes through the
> >> normal ip routing. The login step however just hangs.
> >> Here are some configuration details:
> >>
> >> # lspci:
> >> 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709S
> >> Gigabit Ethernet (rev 20)
> >> 01:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709S
> >> Gigabit Ethernet (rev 20)
> >>
> >>
> >> # ifconfig eth1
> >> eth1 Link encap:Ethernet HWaddr 00:26:B9:FD:41:42
> >> inet addr:172.16.17.19 Bcast:172.16.17.255
Mask:255.255.255.0
> >> inet6 addr: fe80::226:b9ff:fefd:4142/64 Scope:Link
> >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> >> RX packets:604 errors:0 dropped:0 overruns:0 frame:0
> >> TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
> >> collisions:0 txqueuelen:1000
> >> RX bytes:141966 (138.6 KiB) TX bytes:8996 (8.7 KiB)
> >> Interrupt:24 Memory:dc000000-dc012800
> >>
> >> # iscsiadm -m iface
> >> default tcp,<empty>,<empty>,<empty>,<empty>
> >> iser iser,<empty>,<empty>,<empty>,<empty>
> >> bnx2i.00:26:b9:fd:41:41
bnx2i,00:26:b9:fd:41:41,172.16.17.21,<empty>,<empty>
> >> bnx2i.00:26:b9:fd:41:43
bnx2i,00:26:b9:fd:41:43,172.16.17.20,<empty>,<empty>
> >> bnx2i.00:00:00:00:00:00 bnx2i,00:00:00:00:00:00,<empty>,<empty>,<empty>
> >>
> >> # iscsiadm -m iface -I bnx2i.00:26:b9:fd:41:43
> >> # BEGIN RECORD 2.0-871
> >> iface.iscsi_ifacename = bnx2i.00:26:b9:fd:41:43
> >> iface.net_ifacename = <empty>
> >> iface.ipaddress = 172.16.17.20
> >> iface.hwaddress = 00:26:b9:fd:41:43
> >> iface.transport_name = bnx2i
> >> iface.initiatorname = <empty>
> >> # END RECORD
> >>
> >> Then running:
> >>
> >> # iscsiadm -m discovery -t st -p 172.16.17.243 -I
bnx2i.00:26:b9:fd:41:43
> >> 172.16.17.243:3260,1 iqn.2002-10.com.infortrend:raid.sn7740362.101
> >> #
> >>
> >> and
> >>
> >> # iscsiadm -m node -T iqn.2002-10.com.infortrend:raid.sn7740362.101
--login
> >> Logging in to [iface: bnx2i.00:26:b9:fd:41:43, target:
> >> iqn.2002-10.com.infortrend:raid.sn7740362.101, portal:
172.16.17.243,3260]
> >>
> >>
> >
> > Do you have an offload key plugged into the motherboard. If not you
might see offload not supported
> messages in /var/log/messages..
> >
> Broadcom NetXtreme II CNIC Driver cnic v2.1.0 (Oct 10, 2009)
> cnic: Added CNIC device: eth0
> cnic: Added CNIC device: eth1
> Broadcom NetXtreme II iSCSI Driver bnx2i v2.1.0 (Dec 06, 2009)
> iscsi: registered transport (bnx2i)
> scsi1 : Broadcom Offload iSCSI Initiator
> scsi2 : Broadcom Offload iSCSI Initiator
> iscsi: registered transport (tcp)
> iscsi: registered transport (iser)
> iscsi: registered transport (be2iscsi)
>
You will see the messages when the login is being attempted and not during
driver load.
> > Also see if you can restart iscsid. ( The difference is that iscsid
reloads the bnx2i driver.)
> >
> No luck. I'm afraid. A reboot hangs also because it tries to login to
> the target over this bnx2i interface
> Ton
>
1) Does the BIOS have "Windows MBA mode" Enabled. This also can cause login
to not occur.
You can find this option in the CTRL+K option on the Broadcom Nic option ROM
during post.
2) Do you see any segfault messages in the /var/log/messages for
brcm_iscsiuio ?
3) Using ps command can you determine if the brcm_iscsuio daemon is still
running ?
4) If you could post your /var/log/messages and /var/log/brcm-iscsi.log to
some paste-bin, equivalent that would be great. Or send me over email.
-Shyam
>
>
> --
> A.C.M. Damen
> Computer Technologie Groep
> NIKHEF - Dutch National Institute for Sub-atomic Physics
> Kruislaan 409 1098 SJ Amsterdam
> Tel. +3125925121
------------------------------
Message: 2
Date: Thu, 11 Nov 2010 10:24:09 -0600
From: Jacob P <[email protected]>
Subject: Perc 6/i Puncturing bad blocks
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hello,
I'm having an issue with a PERC 6/i card and I was hoping to get some
guidance from the gurus on this list.
We're having an issue with the controller 'puncturing bad blocks', but
it's 'remembering' the sectors after swapping out with a hotspare.
Example:
*Nov 1st -> hotswapped S3*
a0 PERC 6/i Integrated bios:2.04.00 fw:1.22.02-0612 encl:1
ldrv:2 rbld:30% mem:256MiB batt:good/4054mV/26C
a0d0 136GiB RAID 1 1x2 optimal
row 0: a0e32s0 a0e32s1
a0d1 2TiB RAID 5 1x4 optimal
row 0: a0e32s2 a0e32s3 a0e32s4 a0e32s5
a0e32s0 SEAGATE ST3146356SS rev:HS0F s/n:3QN23Y2J
136GiB a0d0 online
a0e32s1 SEAGATE ST3146356SS rev:HS0F s/n:3QN260CF
136GiB a0d0 online
a0e32s2 SEAGATE ST31000640SS rev:MS0A s/n:9QJ5NX2F
931GiB a0d1 online
a0e32s3 SEAGATE ST31000640SS rev:MS0A s/n:9QJ5NDVC
931GiB a0d1 online errs: media:76 other:2
a0e32s4 SEAGATE ST31000640SS rev:MS0A s/n:9QJ6BWRR
931GiB a0d1 online
a0e32s5 SEAGATE ST31000640SS rev:MS0A s/n:9QJ5NX2V
931GiB a0d1 online
*Nov 3rd -> hotswapped s4*
a0 PERC 6/i Integrated bios:2.04.00 fw:1.22.02-0612 encl:1
ldrv:2 rbld:30% mem:256MiB batt:good/4044mV/26C
a0d0 136GiB RAID 1 1x2 optimal
row 0: a0e32s0 a0e32s1
a0d1 2TiB RAID 5 1x4 optimal
row 0: a0e32s2 a0e32s3 a0e32s4 a0e32s5
a0e32s0 SEAGATE ST3146356SS rev:HS0F s/n:3QN23Y2J
136GiB a0d0 online
a0e32s1 SEAGATE ST3146356SS rev:HS0F s/n:3QN260CF
136GiB a0d0 online
a0e32s2 SEAGATE ST31000640SS rev:MS0A s/n:9QJ5NX2F
931GiB a0d1 online
a0e32s3 SEAGATE ST31000640SS rev:0004 s/n:9QJ1WP3P
931GiB a0d1 online errs: media:0 other:1
a0e32s4 SEAGATE ST31000640SS rev:MS0A s/n:9QJ6BWRR
931GiB a0d1 online errs: media:76 other:0
*Nov 4th -> hotswapped s3*
a0 PERC 6/i Integrated bios:2.04.00 fw:1.22.02-0612 encl:1
ldrv:2 rbld:30% mem:256MiB batt:good/4038mV/26C
a0d0 136GiB RAID 1 1x2 optimal
row 0: a0e32s0 a0e32s1
a0d1 2TiB RAID 5 1x4 optimal
row 0: a0e32s2 a0e32s3 a0e32s4 a0e32s5
a0e32s0 SEAGATE ST3146356SS rev:HS0F s/n:3QN23Y2J
136GiB a0d0 online
a0e32s1 SEAGATE ST3146356SS rev:HS0F s/n:3QN260CF
136GiB a0d0 online
a0e32s2 SEAGATE ST31000640SS rev:MS0A s/n:9QJ5NX2F
931GiB a0d1 online
a0e32s3 SEAGATE ST31000640SS rev:0004 s/n:9QJ1WP3P
931GiB a0d1 online errs: media:76 other:1 predictive-failure
a0e32s4 SEAGATE ST31000640SS rev:MS0A s/n:9QJ63CGY
931GiB a0d1 online
a0e32s5 SEAGATE ST31000640SS rev:MS0A s/n:9QJ5NX2V
931GiB a0d1 online
*Today:
*a0 PERC 6/i Integrated bios:2.04.00 fw:1.22.02-0612 encl:1
ldrv:2 rbld:30% mem:256MiB batt:good/4019mV/26C
a0d0 136GiB RAID 1 1x2 optimal
row 0: a0e32s0 a0e32s1
a0d1 2TiB RAID 5 1x4 optimal
row 0: a0e32s2 a0e32s3 a0e32s4 a0e32s5
a0e32s0 SEAGATE ST3146356SS rev:HS0F s/n:3QN23Y2J
136GiB a0d0 online
a0e32s1 SEAGATE ST3146356SS rev:HS0F s/n:3QN260CF
136GiB a0d0 online
a0e32s2 SEAGATE ST31000640SS rev:MS0A s/n:9QJ5NX2F
931GiB a0d1 online
a0e32s3 SEAGATE ST31000640SS rev:MS04 s/n:9QJ636RE
931GiB a0d1 online errs: media:76 other:0
a0e32s4 SEAGATE ST31000640SS rev:MS0A s/n:9QJ6C4XE
931GiB a0d1 online
a0e32s5 SEAGATE ST31000640SS rev:MS0A s/n:9QJ5NX2V
931GiB a0d1 online
As you can see, the '76' errors seem to be moving from pd to pd, but
even though they are different drives. This is leading me to believe
that some how the controller is taking these sectors offline because
it's remembering them somehow. Has anyone seen this before, or perhaps
have any suggestions on how I should proceed?
Wall of text logs below. Thanks again for any help!!
11/07/10 19:16:55: EVT#00372-11/07/10 19:16:55: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f e9 00 00 00 80 00,
Sense: 3/11/00
11/07/10 19:16:55: Raw Sense for PD 3: f0 00 03 74 2f e9 37 0a 00 00 00
00 11 00 81 80 00 96
11/07/10 19:16:55: DEV_REC:Medium Error DevId[3] Tgt 3 RDM=a05caa00
retires=0
11/07/10 19:16:55: MedErr is for: cmdId=422, ld=1, src=4, cmd=1,
lba=e85fd2, cnt=80, rmwOp=0
11/07/10 19:16:55: -> recoveryChild: ld=1 orgLi=0 recPhysArm=2
badPhysArm=ff doneFun=a0c02268 sRef=0 eRef=7f recFlags=0
11/07/10 19:16:55: -> RecParent: cmdId=422, src=4, cmd=1, lba=e85fd2,
cnt=80, rmwOp=0, refs=0/7f
11/07/10 19:16:55: ErrLBAOffset (37) LBA(742fe900) BadLba=742fe937
11/07/10 19:16:55: EVT#00373-11/07/10 19:16:55: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fe937
11/07/10 19:16:55: BBMProcessReadError: RECOVERY, pd=03,
pdErrLba=742fe937 - puncture source/target drives
11/07/10 19:16:55: BBMMarkBadBlock: pd=03, pdLBA=742fe937
11/07/10 19:16:55: BBMMarkBadBlock: pd=04, pdLBA=742fe937
T51: EVT#00046-T51: 91=Inserted: PD 03(e0x20/s3)
T51: EVT#00047-T51: 247=Inserted: PD 03(e0x20/s3) Info: enclPd=20,
scsiType=0, portMap=03, sasAddr=5000c50010157171,0000000000000000
T56: EVT#00055-T56: 114=State change on PD 03(e0x20/s3) from
UNCONFIGURED_GOOD(0) to ONLINE(18)
T49: EVT#00087-T49: 91=Inserted: PD 03(e0x20/s3)
T49: EVT#00088-T49: 247=Inserted: PD 03(e0x20/s3) Info: enclPd=20,
scsiType=0, portMap=03, sasAddr=5000c50010157171,0000000000000000
11/07/10 19:16:55: EVT#00372-11/07/10 19:16:55: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f e9 00 00 00 80 00,
Sense: 3/11/00
11/07/10 19:16:55: EVT#00373-11/07/10 19:16:55: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fe937
11/07/10 19:16:58: EVT#00374-11/07/10 19:16:58: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f e9 38 00 00 48 00,
Sense: 3/11/00
11/07/10 19:16:58: EVT#00375-11/07/10 19:16:58: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fe938
11/07/10 19:17:01: EVT#00376-11/07/10 19:17:01: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f ed 00 00 00 80 00,
Sense: 3/11/00
11/07/10 19:17:01: EVT#00377-11/07/10 19:17:01: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fed49
11/07/10 19:17:04: EVT#00378-11/07/10 19:17:04: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f f1 00 00 00 80 00,
Sense: 3/11/00
11/07/10 19:17:04: EVT#00379-11/07/10 19:17:04: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742ff15b
11/07/10 19:17:06: EVT#00380-11/07/10 19:17:06: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f e9 39 00 00 47 00,
Sense: 3/11/00
11/07/10 19:17:06: EVT#00381-11/07/10 19:17:06: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fe93a
11/07/10 19:17:08: EVT#00382-11/07/10 19:17:08: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f ed 4a 00 00 36 00,
Sense: 3/11/00
11/07/10 19:17:09: EVT#00383-11/07/10 19:17:09: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fed4a
11/07/10 19:17:11: EVT#00384-11/07/10 19:17:11: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f e9 3b 00 00 45 00,
Sense: 3/11/00
11/07/10 19:17:11: EVT#00385-11/07/10 19:17:11: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fe93b
11/07/10 19:17:14: EVT#00386-11/07/10 19:17:14: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f ed 4b 00 00 35 00,
Sense: 3/11/00
11/07/10 19:17:14: EVT#00387-11/07/10 19:17:14: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fed4d
11/07/10 19:17:17: EVT#00388-11/07/10 19:17:17: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f f1 5c 00 00 24 00,
Sense: 3/11/00
11/07/10 19:17:17: EVT#00389-11/07/10 19:17:17: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742ff15c
11/07/10 19:17:20: EVT#00390-11/07/10 19:17:20: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f e9 3c 00 00 44 00,
Sense: 3/11/00
11/07/10 19:17:20: EVT#00391-11/07/10 19:17:20: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fe93c
11/07/10 19:17:23: EVT#00392-11/07/10 19:17:23: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f ed 4e 00 00 32 00,
Sense: 3/11/00
11/07/10 19:17:23: EVT#00393-11/07/10 19:17:23: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fed50
11/07/10 19:17:26: EVT#00394-11/07/10 19:17:26: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f f1 5d 00 00 23 00,
Sense: 3/11/00
11/07/10 19:17:26: EVT#00395-11/07/10 19:17:26: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742ff15e
11/07/10 19:17:29: EVT#00396-11/07/10 19:17:29: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f f9 00 00 00 80 00,
Sense: 3/11/00
11/07/10 19:17:29: EVT#00397-11/07/10 19:17:29: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742ff97d
11/07/10 19:17:32: EVT#00398-11/07/10 19:17:32: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f e9 3d 00 00 43 00,
Sense: 3/11/00
11/07/10 19:17:32: EVT#00399-11/07/10 19:17:32: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fe93d
11/07/10 19:17:34: EVT#00400-11/07/10 19:17:34: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f ed 51 00 00 2f 00,
Sense: 3/11/00
11/07/10 19:17:34: EVT#00401-11/07/10 19:17:34: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fed51
11/07/10 19:17:37: EVT#00402-11/07/10 19:17:37: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f f1 5f 00 00 21 00,
Sense: 3/11/00
11/07/10 19:17:37: EVT#00403-11/07/10 19:17:37: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742ff15f
11/07/10 19:17:40: EVT#00404-11/07/10 19:17:40: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f f9 80 00 00 80 00,
Sense: 3/11/00
11/07/10 19:17:40: EVT#00405-11/07/10 19:17:40: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742ff981
11/07/10 19:17:43: EVT#00406-11/07/10 19:17:43: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f e9 3e 00 00 42 00,
Sense: 3/11/00
11/07/10 19:17:43: EVT#00407-11/07/10 19:17:43: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fe93e
11/07/10 19:17:45: EVT#00408-11/07/10 19:17:45: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f f9 7e 00 00 02 00,
Sense: 3/11/00
11/07/10 19:17:46: EVT#00409-11/07/10 19:17:46: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742ff97e
11/07/10 19:17:48: EVT#00410-11/07/10 19:17:48: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f ed 52 00 00 2e 00,
Sense: 3/11/00
11/07/10 19:17:48: EVT#00411-11/07/10 19:17:48: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fed55
11/07/10 19:17:51: EVT#00412-11/07/10 19:17:51: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f f1 60 00 00 20 00,
Sense: 3/11/00
11/07/10 19:17:51: EVT#00413-11/07/10 19:17:51: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742ff160
11/07/10 19:17:54: EVT#00415-11/07/10 19:17:54: 113=Unexpected sense: PD
03(e0x20/s3) Path 5000c50010157171, CDB: 28 00 74 2f e9 3f 00 00 41 00,
Sense: 3/11/00
11/07/10 19:17:54: EVT#00416-11/07/10 19:17:54: 111=Unrecoverable medium
error during recovery on PD 03(e0x20/s3) at 742fe93f
11/07/10 19:17:55: EVT#00419-11/07/10 19:17:55: 97=Puncturing bad block
on PD 03(e0x20/s3) at 742ff981
11/07/10 19:17:55: EVT#00424-11/07/10 19:17:55: 97=Puncturing bad block
on PD 03(e0x20/s3) at 742ff97d
11/07/10 19:17:55: EVT#00426-11/07/10 19:17:55: 97=Puncturing bad block
on PD 03(e0x20/s3) at 742ff97e
11/07/10 19:17:55: EVT#00428-11/07/10 19:17:55: 97=Puncturing bad block
on PD 03(e0x20/s3) at 742fed55
11/07/10 19:17:55: EVT#00429-11/07/10 19:17:55: 97=Puncturing bad block
on PD 03(e0x20/s3) at 742fed51
11/07/10 19:17:56: EVT#00430-11/07/10 19:17:56: 97=Puncturing bad block
on PD 03(e0x20/s3) at 742fed50
11/07/10 19:17:56: EVT#00431-11/07/10 19:17:56: 97=Puncturing bad block
on PD 03(e0x20/s3) at 742fed4d
11/07/10 19:17:56: EVT#00432-11/07/10 19:17:56: 97=Puncturing bad block
on PD 03(e0x20/s3) at 742fed4a
11/07/10 19:17:56: EVT#00433-11/07/10 19:17:56: 97=Puncturing bad block
on PD 03(e0x20/s3) at 742fed49
------------------------------
Message: 3
Date: Thu, 11 Nov 2010 13:24:53 -0400
From: Richard Chadwick <[email protected]>
Subject: Re: megaraid_sas from RHEL5.5 kernel 2.6.18-194.26.1.el5
To: Bob Huisman <[email protected]>
Cc: Rainer Traut <[email protected]>, "[email protected]"
<[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
That message concerns the Fusion mpt drivers for SAS 5 and SAS 6 controllers
not the megaraid drivers for the PERC family.
Check out
http://www.centos.org/modules/newbb/viewtopic.php?topic_id=24433&forum=39
<http://www.centos.org/modules/newbb/viewtopic.php?topic_id=24433&forum=39>
and
http://elrepo.org/tiki/kmod-mptfusion
for details
PS I haven't this updated driver yet.
On 11 November 2010 09:34, Bob Huisman <[email protected]> wrote:
> So, the kernel from RHEL includes the latest recommended driver? I
upgraded
> a lab system to the kernel 2.6.18-194.26.1.el5 (well ok, CentOS), but OMSA
> still reports the storage controller as warning (incorrect driver
version):
>
> Driver Version 3.04.13rh
> Minimum Required Driver Version 3.12.29.00
>
> Is it safe to ignore this or am I still missing packages?
>
> Kind regards,
>
> Bob Huisman
>
>
> -----Original Message-----
> From: [email protected] [mailto:
> [email protected]] On Behalf Of Rainer Traut
> Sent: donderdag 11 november 2010 11:08
> To: [email protected]
> Subject: Re: megaraid_sas from RHEL5.5 kernel 2.6.18-194.26.1.el5
>
> Am 10.11.2010 14:10, schrieb Rainer Traut:
> >
> > Does this mean this new driver supersedes dell's recommended driver
> > v00.00.04.29 ?
> >
> > So there is no need to install the dkms package anymore?
>
> Thanks to Dell support to inform me that it is indeed true and the dkms
> megaraid update is not needed anymore with this kernel.
>
> Rainer
>
> _______________________________________________
> Linux-PowerEdge mailing list
> [email protected]
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
>
> _______________________________________________
> Linux-PowerEdge mailing list
> [email protected]
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20101111/b5502bb2/attachment.htm
------------------------------
_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
End of Linux-PowerEdge Digest, Vol 77, Issue 13
***********************************************
_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
