mifronte Posted May 19, 2011 Share Posted May 19, 2011 I would like to change my current SIL3124 controller to either the SIL3132 or the JMicron JMB362 to see if I can get rid of these errors on a parity check: May 19 10:16:18 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 19 10:16:18 Beanstalk kernel: ata20.00: irq_stat 0x00020002, failed to transmit command FIS (Minor Issues) May 19 10:16:18 Beanstalk kernel: ata20.00: failed command: READ DMA EXT (Minor Issues) May 19 10:16:18 Beanstalk kernel: ata20.00: cmd 25/00:00:ff:92:ae/00:01:11:00:00/e0 tag 0 dma 131072 in (Drive related) May 19 10:16:18 Beanstalk kernel: res 25/00:00:ff:92:ae/00:01:11:00:00/e0 Emask 0x12 (ATA bus error) (Errors) May 19 10:16:18 Beanstalk kernel: ata20.00: status: { DF ERR } (Drive related) May 19 10:16:18 Beanstalk kernel: ata20: hard resetting link (Minor Issues) May 19 10:16:20 Beanstalk kernel: ata20: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) May 19 10:16:20 Beanstalk kernel: ata20.00: configured for UDMA/100 (Drive related) May 19 10:16:20 Beanstalk kernel: ata20: EH complete (Drive related) May 19 10:18:41 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 19 10:18:41 Beanstalk kernel: ata20.00: irq_stat 0x00020002, failed to transmit command FIS (Minor Issues) May 19 10:18:41 Beanstalk kernel: ata20.00: failed command: READ DMA EXT (Minor Issues) May 19 10:18:41 Beanstalk kernel: ata20.00: cmd 25/00:00:27:f7:87/00:04:12:00:00/e0 tag 0 dma 524288 in (Drive related) May 19 10:18:41 Beanstalk kernel: res 25/00:00:27:f7:87/00:04:12:00:00/e0 Emask 0x12 (ATA bus error) (Errors) May 19 10:18:41 Beanstalk kernel: ata20.00: status: { DF ERR } (Drive related) May 19 10:18:41 Beanstalk kernel: ata20: hard resetting link (Minor Issues) May 19 10:18:43 Beanstalk kernel: ata20: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) May 19 10:18:43 Beanstalk kernel: ata20.00: configured for UDMA/100 (Drive related) May 19 10:18:43 Beanstalk kernel: ata20: EH complete (Drive related) May 19 10:19:50 Beanstalk ntpd[3474]: synchronized to 132.163.4.103, stratum 1 May 19 10:20:43 Beanstalk kernel: ata19.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 19 10:20:43 Beanstalk kernel: ata19.00: irq_stat 0x00020002, failed to transmit command FIS (Minor Issues) May 19 10:20:43 Beanstalk kernel: ata19.00: failed command: READ DMA EXT (Minor Issues) May 19 10:20:43 Beanstalk kernel: ata19.00: cmd 25/00:00:8f:2c:40/00:01:13:00:00/e0 tag 0 dma 131072 in (Drive related) May 19 10:20:43 Beanstalk kernel: res 25/00:00:8f:2c:40/00:01:13:00:00/e0 Emask 0x12 (ATA bus error) (Errors) May 19 10:20:43 Beanstalk kernel: ata19.00: status: { DF ERR } (Drive related) May 19 10:20:43 Beanstalk kernel: ata19: hard resetting link (Minor Issues) May 19 10:20:45 Beanstalk kernel: ata19: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) May 19 10:20:45 Beanstalk kernel: ata19.00: configured for UDMA/100 (Drive related) May 19 10:20:45 Beanstalk kernel: ata19: EH complete (Drive related) May 19 10:21:05 Beanstalk kernel: ata19.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 19 10:21:05 Beanstalk kernel: ata19.00: irq_stat 0x00020002, failed to transmit command FIS (Minor Issues) May 19 10:21:05 Beanstalk kernel: ata19.00: failed command: READ DMA EXT (Minor Issues) May 19 10:21:05 Beanstalk kernel: ata19.00: cmd 25/00:00:97:71:5f/00:01:13:00:00/e0 tag 0 dma 131072 in (Drive related) May 19 10:21:05 Beanstalk kernel: res 25/00:00:97:71:5f/00:01:13:00:00/e0 Emask 0x12 (ATA bus error) (Errors) May 19 10:21:05 Beanstalk kernel: ata19.00: status: { DF ERR } (Drive related) May 19 10:21:05 Beanstalk kernel: ata19: hard resetting link (Minor Issues) May 19 10:21:07 Beanstalk kernel: ata19: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) May 19 10:21:07 Beanstalk kernel: ata19.00: configured for UDMA/100 (Drive related) May 19 10:21:07 Beanstalk kernel: ata19: EH complete (Drive related) May 19 10:21:33 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 19 10:21:33 Beanstalk kernel: ata20.00: irq_stat 0x00020002, failed to transmit command FIS (Minor Issues) May 19 10:21:33 Beanstalk kernel: ata20.00: failed command: READ DMA EXT (Minor Issues) May 19 10:21:33 Beanstalk kernel: ata20.00: cmd 25/00:00:97:a8:87/00:01:13:00:00/e0 tag 0 dma 131072 in (Drive related) May 19 10:21:33 Beanstalk kernel: res 25/00:00:97:a8:87/00:01:13:00:00/e0 Emask 0x12 (ATA bus error) (Errors) May 19 10:21:33 Beanstalk kernel: ata20.00: status: { DF ERR } (Drive related) May 19 10:21:33 Beanstalk kernel: ata20: hard resetting link (Minor Issues) May 19 10:21:36 Beanstalk kernel: ata20: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) May 19 10:21:36 Beanstalk kernel: ata20.00: configured for UDMA/100 (Drive related) May 19 10:21:36 Beanstalk kernel: ata20: EH complete (Drive related) May 19 10:21:41 Beanstalk kernel: ata19.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 (Errors) May 19 10:21:41 Beanstalk kernel: ata19.00: irq_stat 0x00020002, device error via D2H FIS (Errors) May 19 10:21:41 Beanstalk kernel: ata19.00: failed command: READ DMA EXT (Minor Issues) May 19 10:21:41 Beanstalk kernel: ata19.00: cmd 25/00:00:97:94:8f/00:04:13:00:00/e0 tag 0 dma 524288 in (Drive related) May 19 10:21:41 Beanstalk kernel: res 51/84:7f:97:94:8f/00:01:13:00:00/e0 Emask 0x10 (ATA bus error) (Errors) May 19 10:21:41 Beanstalk kernel: ata19.00: status: { DRDY ERR } (Drive related) May 19 10:21:41 Beanstalk kernel: ata19.00: error: { ICRC ABRT } (Errors) May 19 10:21:41 Beanstalk kernel: ata19: hard resetting link (Minor Issues) May 19 10:21:43 Beanstalk kernel: ata19: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) May 19 10:21:43 Beanstalk kernel: ata19.00: configured for UDMA/100 (Drive related) May 19 10:21:43 Beanstalk kernel: ata19: EH complete (Drive related) May 19 10:22:48 Beanstalk kernel: ata20: limiting SATA link speed to 1.5 Gbps (Drive related) May 19 10:22:48 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 19 10:22:48 Beanstalk kernel: ata20.00: failed command: READ DMA EXT (Minor Issues) May 19 10:22:48 Beanstalk kernel: ata20.00: cmd 25/00:00:e7:a5:c3/00:04:13:00:00/e0 tag 0 dma 524288 in (Drive related) May 19 10:22:48 Beanstalk kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) May 19 10:22:48 Beanstalk kernel: ata20.00: status: { DRDY } (Drive related) May 19 10:22:48 Beanstalk kernel: ata20: hard resetting link (Minor Issues) May 19 10:22:50 Beanstalk kernel: ata20: SATA link up 1.5 Gbps (SStatus 113 SControl 10) (Drive related) May 19 10:22:50 Beanstalk kernel: ata20.00: configured for UDMA/100 (Drive related) May 19 10:22:50 Beanstalk kernel: ata20.00: device reported invalid CHS sector 0 (Drive related) May 19 10:22:50 Beanstalk kernel: ata20: EH complete (Drive related) My SuperMicro X7SBE has a PCIeX4 and PCIeX8 slot and so I plan on intalling the new 2 ports controller and just move the two SATA cables over to the new controller. 01. Would either the SIL3132 or the JMicron JMB362 be able to run in a PCIeX4 slot? 02. Which of the two cards is more reliable to work with unRAID? 02. What would I need to do when unRAID starts with the two disks connected to the new controller? Quote Link to comment
Rajahal Posted May 19, 2011 Share Posted May 19, 2011 01. Would either the SIL3132 or the JMicron JMB362 be able to run in a PCIeX4 slot? Yes, but of course it will only run at x1 speed. 02. Which of the two cards is more reliable to work with unRAID? I've found the SIL3132 to be about 95% reliable. I've had at least 20 of the cards pass through my hands, and only one defective one thus far. As long as the card isn't defective, it is fully compatible with unRAID. I have no personal experience with the JMicron card, but if you look through this thread you'll see a mix of success and failures. It seems that the card itself is more cheaply made, so you are more likely to receive a defective one. However, if they work they seem to work well. I personally would recommend the SIL3132. It costs a bit more, but shipping is much faster and you are likely to have less hassle with it. 02. What would I need to do when unRAID starts with the two disks connected to the new controller? Just reassign the disks to the proper drive slots on the devices page. That's it. It is a good idea to take a screenshot of your devices page BEFORE installing the new controller just so you know you can match up the drive serial numbers with the drive slots without issue. Quote Link to comment
defected07 Posted May 19, 2011 Share Posted May 19, 2011 Why not get the 2 port cards from Monoprice or eBay? eBay one was like $7.00 shipped--took like 3 weeks to receive, but if you're in no rush.. Monoprice one is I believe $15 shipped. Quote Link to comment
Rajahal Posted May 19, 2011 Share Posted May 19, 2011 Those are the two he's talking about....the SIL3132 card is the monoprice card (about $20 shipped), and the JMicron is the eBay card (about $8 shipped). Quote Link to comment
defected07 Posted May 19, 2011 Share Posted May 19, 2011 Wow, brain fart on my part. Actually, I haven't had a chance to try the card yet, since my recent Hitachi was DOA, and the other port is used for pre-clear topdock (DOA drive = no pre-clear). Hopefully I'm on the "winning" team of users. Quote Link to comment
mifronte Posted May 19, 2011 Author Share Posted May 19, 2011 Does the SIL3132 from Monoprice behaves in unRAID, meaning, it supports all drive commands and does not cause any errors like the ones that I posted? My SIL3124 card works fine except during parity check where it does not like some commands. Quote Link to comment
prostuff1 Posted May 19, 2011 Share Posted May 19, 2011 Rajahal and myself have used a number of the monoprice cards and I don't believe either of us have had a problem with them, short of getting a bad one from the start. Quote Link to comment
Rajahal Posted May 20, 2011 Share Posted May 20, 2011 Correct, no errors whatsoever. The monoprice controllers 'behave' as well as any others I've seen. Quote Link to comment
KYThrill Posted May 24, 2011 Share Posted May 24, 2011 You also have the option of a Rosewill RC-211 for $30. http://www.newegg.com/Product/Product.aspx?Item=N82E16816132008&cm_re=Rosewill_SATA-_-16-132-008-_-Product I've used several of the Rosewill cards (but never a RC-211) and have never had a problem with any of them. They seem to be of good quality. I would probably get the Monoprice vs Rosewill because of the price difference, but when I have bough them in the past on New Egg, they were also a deal or I had a 20% off code. So if you aren't in a hurry, you may be able to watch for a deal on one. Quote Link to comment
defected07 Posted May 24, 2011 Share Posted May 24, 2011 I'll verify my SATA card today, since my Hitachi arrived, I'll be able to run a pre-clear utilizing the new card. If it works, it's pretty damn hard to beat a 2 port PCIe SATA card for $8 Quote Link to comment
Rajahal Posted May 24, 2011 Share Posted May 24, 2011 If it works, it's pretty damn hard to beat a 2 port PCIe SATA card for $8 True, but 3 week shipping and a 50% failure rate are also pretty hard to beat I hope it works for you. Quote Link to comment
defected07 Posted May 25, 2011 Share Posted May 25, 2011 True, but 3 week shipping and a 50% failure rate are also pretty hard to beat I hope it works for you. So far so good. Read the disk around 120 MB/s in preclear. We'll see when I transfer. Quote Link to comment
lionelhutz Posted May 25, 2011 Share Posted May 25, 2011 True, but 3 week shipping and a 50% failure rate are also pretty hard to beat I hope it works for you. I spent 3 weeks trying 2 3132 based cards and RMA'ing both of them, so 3 weeks and having 3 cards with 0% failure was a much better outcome for me. Not sure how you know 50% of the cards are DOA anyways... Peter Quote Link to comment
Rajahal Posted May 25, 2011 Share Posted May 25, 2011 True, but 3 week shipping and a 50% failure rate are also pretty hard to beat I hope it works for you. I spent 3 weeks trying 2 3132 based cards and RMA'ing both of them, so 3 weeks and having 3 cards with 0% failure was a much better outcome for me. Not sure how you know 50% of the cards are DOA anyways... Peter I've run into defective SIL3134 cards, but I've never used SIL3132 cards. Sorry, typo. All the cards I've used have been SIL3132. Defects happen. Still, the failure rate with the SIL3132 cards that I've personally seen has been pretty low, maybe 5% or less. I don't know absolutely that the Jmicron cards are DOA half of the time, that's just the impression I get from the mixed successes and failures reported in this thread. Quote Link to comment
lionelhutz Posted May 25, 2011 Share Posted May 25, 2011 I don't think most of those problems are dead cards, they are incompatability problems. Peter Quote Link to comment
mifronte Posted May 26, 2011 Author Share Posted May 26, 2011 NewEgg lists the Rosewill RC-211 as a SIL3132 which is the same as the Monoprice card. Rahahal, which SIL3134 card are you referring to? I installed the Monoprice SIL3132 card, but have not run a parity check yet to see if they are error free. However, I see this in the syslog: May 25 21:55:24 Beanstalk kernel: scsi17 : sata_sil24 (Drive related) May 25 21:55:24 Beanstalk kernel: ata17: SATA max UDMA/100 host m128@0xd0d04000 port 0xd0d00000 irq 16 (Drive related) May 25 21:55:24 Beanstalk kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) I noticed it only support UDMA/100 and not UDMA/133 like the SuperMicro AOC-SAT3-MVL8 controllers. Quote Link to comment
Rajahal Posted May 27, 2011 Share Posted May 27, 2011 NewEgg lists the Rosewill RC-211 as a SIL3132 which is the same as the Monoprice card. Rahahal, which SIL3134 card are you referring to? I installed the Monoprice SIL3132 card, but have not run a parity check yet to see if they are error free. However, I see this in the syslog: May 25 21:55:24 Beanstalk kernel: scsi17 : sata_sil24 (Drive related) May 25 21:55:24 Beanstalk kernel: ata17: SATA max UDMA/100 host m128@0xd0d04000 port 0xd0d00000 irq 16 (Drive related) May 25 21:55:24 Beanstalk kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) I noticed it only support UDMA/100 and not UDMA/133 like the SuperMicro AOC-SAT3-MVL8 controllers. Sorry, that was a typo. I've only used SIL3132 cards, I haven't ever used SIL3134 cards (not even sure they exist). I don't think the UDMA differences are anything to worry about. The cards still report as SATA 3.0 Gbps, so you are getting full speed either way. Quote Link to comment
Kaygee Posted June 3, 2011 Share Posted June 3, 2011 Have you tried using the other two ports on the SIL3124 card? I recall my syslog showing minor errors but only when using port multipliers. As straight sata controller it was clean, havn't used it for a long time though...still got it here somewhere could stick it in tomorrow if you tell what version of unRaid you are running and run a quick parity check on my test system? Quote Link to comment
PeterB Posted June 4, 2011 Share Posted June 4, 2011 Have you tried using the other two ports on the SIL3124 card? I recall my syslog showing minor errors but only when using port multipliers. I've read reports on other forums of SAS2008 cards failing (Phase 9 firmware) when using port multipliers - I would recommend avoiding the use of multipliers! Quote Link to comment
Recommended Posts
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.