AVAGO 9341-8i issues


Recommended Posts

Hello - this is pretty much my first post.  I did report an error to Lime but haven't heard back...

 

I have a Dell T5600, 32GB ram, 4 x Barracuda 4TB drives - one of which is parity, 500GB Samsung "Cache" drive.  I think I have a problem with my Avago controller but I am coming here for some guidance.

 

I am having drives disabling on me.  This is not restricted to one drive - I have had 9 different instances where drives have been disabled in unRaid.  I have replaced the SFF Sata cables (at some expense) and tried everything EXCEPT changing controller card.  The card is in the PCI x16 slot as the T5600 has no graphics card connected (no need for one).

 

I think the controller is the problem and would really appreciate confirmation of this and advice as to how to fix it - here is an extract of the period in the syslog when I know I have an instance of a drive being disabled (sff):

 

Mar 17 09:33:32 mSpark kernel: docker0: port 1(veth3326240) entered blocking state
Mar 17 09:33:32 mSpark kernel: docker0: port 1(veth3326240) entered disabled state
Mar 17 09:33:32 mSpark kernel: device veth3326240 entered promiscuous mode
Mar 17 09:33:32 mSpark kernel: IPv6: ADDRCONF(NETDEV_UP): veth3326240: link is not ready
Mar 17 09:33:32 mSpark kernel: eth0: renamed from veth897f3d9
Mar 17 09:33:32 mSpark kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3326240: link becomes ready
Mar 17 09:33:32 mSpark kernel: docker0: port 1(veth3326240) entered blocking state
Mar 17 09:33:32 mSpark kernel: docker0: port 1(veth3326240) entered forwarding state
Mar 17 09:33:32 mSpark kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
Mar 17 09:33:33 mSpark kernel: sd 1:0:13:0: target reset called for scmd(ffff8804bc121d48)
Mar 17 09:33:33 mSpark kernel: sd 1:0:13:0: attempting target reset! scmd(ffff8804bc121d48) tm_dev_handle 0xc
Mar 17 09:33:34 mSpark avahi-daemon[11177]: Joining mDNS multicast group on interface veth3326240.IPv6 with address fe80::7870:baff:fe2e:be1e.
Mar 17 09:33:34 mSpark avahi-daemon[11177]: New relevant interface veth3326240.IPv6 for mDNS.
Mar 17 09:33:34 mSpark avahi-daemon[11177]: Registering new address record for fe80::7870:baff:fe2e:be1e on veth3326240.*.
Mar 17 09:33:34 mSpark kernel: sd 1:0:13:0: [sde] tag#0 megasas: target reset SUCCESS!!
Mar 17 09:33:34 mSpark kernel: sd 1:0:15:0: target reset called for scmd(ffff8808bad7f948)
Mar 17 09:33:34 mSpark kernel: sd 1:0:15:0: attempting target reset! scmd(ffff8808bad7f948) tm_dev_handle 0x9
Mar 17 09:33:34 mSpark kernel: sd 1:0:15:0: [sdf] tag#1 megasas: target reset SUCCESS!!
Mar 17 09:33:34 mSpark avahi-daemon[11177]: Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:eaff:fee7:e37b.
Mar 17 09:33:34 mSpark avahi-daemon[11177]: New relevant interface docker0.IPv6 for mDNS.
Mar 17 09:33:34 mSpark avahi-daemon[11177]: Registering new address record for fe80::42:eaff:fee7:e37b on docker0.*.
Mar 17 09:33:43 mSpark kernel: sd 1:0:15:0: [sdf] tag#1 Controller reset is requested due to IO timeout
Mar 17 09:33:43 mSpark kernel: SCSI command pointer: (ffff8808bad7f948)	 SCSI host state: 5	 SCSI 
Mar 17 09:33:53 mSpark kernel: sd 1:0:15:0: Device offlined - not ready after error recovery
Mar 17 09:33:53 mSpark kernel: sd 1:0:15:0: [sdf] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Mar 17 09:33:53 mSpark kernel: sd 1:0:15:0: [sdf] tag#1 Sense Key : 0x2 [current] 
Mar 17 09:33:53 mSpark kernel: sd 1:0:15:0: [sdf] tag#1 ASC=0x4 ASCQ=0x2 
Mar 17 09:33:53 mSpark kernel: sd 1:0:15:0: [sdf] tag#1 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
Mar 17 09:33:53 mSpark kernel: print_req_error: I/O error, dev sdf, sector 0
Mar 17 09:33:54 mSpark kernel: sd 1:0:12:0: target reset called for scmd(ffff8804babe8148)
Mar 17 09:33:54 mSpark kernel: sd 1:0:12:0: attempting target reset! scmd(ffff8804babe8148) tm_dev_handle 0xb
Mar 17 09:33:54 mSpark kernel: sd 1:0:12:0: [sdd] tag#0 megasas: target reset SUCCESS!!
Mar 17 09:34:03 mSpark kernel: sd 1:0:12:0: [sdd] tag#0 Controller reset is requested due to IO timeout
Mar 17 09:34:03 mSpark kernel: SCSI command pointer: (ffff8804babe8148)	 SCSI host state: 5	 SCSI 
Mar 17 09:34:14 mSpark kernel: sd 1:0:15:0: rejecting I/O to offline device
Mar 17 09:34:14 mSpark kernel: md: disk1 read error, sector=3908368816
Mar 17 09:34:14 mSpark kernel: sd 1:0:8:0: target reset called for scmd(ffff88049d7ba948)
Mar 17 09:34:14 mSpark kernel: sd 1:0:8:0: attempting target reset! scmd(ffff88049d7ba948) tm_dev_handle 0xa
Mar 17 09:34:14 mSpark kernel: sd 1:0:8:0: [sdc] tag#2 megasas: target reset SUCCESS!!
Mar 17 09:34:24 mSpark kernel: sd 1:0:8:0: [sdc] tag#2 Controller reset is requested due to IO timeout
Mar 17 09:34:24 mSpark kernel: SCSI command pointer: (ffff88049d7ba948)	 SCSI host state: 5	 SCSI 
Mar 17 09:34:34 mSpark kernel: sd 1:0:15:0: rejecting I/O to offline device
Mar 17 09:34:35 mSpark kernel: md: disk1 write error, sector=3908368816
Mar 17 10:40:52 mSpark kernel: mdcmd (48): spindown 0
Mar 17 10:40:53 mSpark kernel: mdcmd (49): spindown 3
Mar 17 10:43:47 mSpark kernel: mdcmd (50): spindown 2
Mar 17 16:42:17 mSpark kernel: sd 1:0:8:0: target reset called for scmd(ffff8804ba88e548)
Mar 17 16:42:17 mSpark kernel: sd 1:0:8:0: attempting target reset! scmd(ffff8804ba88e548) tm_dev_handle 0xa
Mar 17 16:42:17 mSpark kernel: sd 1:0:8:0: [sdc] tag#0 megasas: target reset SUCCESS!!
Mar 17 16:42:27 mSpark kernel: sd 1:0:8:0: [sdc] tag#0 Controller reset is requested due to IO timeout
Mar 17 16:42:27 mSpark kernel: SCSI command pointer: (ffff8804ba88e548)	 SCSI host state: 5	 SCSI 

 

I am currently trying to start again with spindown disabled but I am also keen to know whether there is any crossflashing options for the Avago 9341-8i

 

Another thought I had was to solely use the 9341-8i for SSDs only.

 

Alternatively, are there any solid controller cards sub £100 that would work?  What chipset of controller should I look for if I have to replace the 9341-8i???

Link to comment

Thank you for replying.

 

Whilst it is a RAID controller I have it running in JBOD mode - but I get the feeling that there is still an issue - with recovering from spindown.

 

I've been researching crossflashing and it looks like I can go across to the 9300-8i firmware!

 

Pretty daunting but I am going to give it a pop this evening then post my discoveries / progress - just in case there may be others hitting my predicament.

Link to comment

Ah - I see.  Learning new things all the time!

 

I'll definitely crossflash the card over to a 9300-8i this evening then.  What a great saturday night in for me..... and it's my birthday lol!

 

Thank you for your help.  Much appreciated

Link to comment

So - I managed to crossflash my 9341-8i to a 9300-8i... I'm currently going through the process of putting my original (6 x 4TB drive + 500GB SSD Cache) back together so that I can see what happens over the coming days.

 

Unraid is using mptsas instead of megasas so fingers crossed all will be fine.

 

In terms of giving guidance as to how to do it - it was not an ideal process:

 

  • I followed this guide: flash-lsi-sas-3008-hba
  • I found that my system froze at the rebooting device - so I had to reboot my machine
  • I then had to do each flash individually, firstly the BIN, then the next two ROM files
  • I then had to add the SAS controller ID

I have version P14 which was downloaded from the Broadcom site: sas-9300-8i#tab-archive-drivers1-abc

 

Thank you johnnie.black !!  I was considering buying myself a £50 to £100 SATA controller - so glad I didn't - well, so far!

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.