EdgarWallace Posted February 14, 2011 Share Posted February 14, 2011 Good evening, is anyone having this controller running? Should be supported by Slackware 12 but I can't see it on the webinterface. Thank you. Link to comment
EdgarWallace Posted March 9, 2011 Author Share Posted March 9, 2011 No one? I was sliding-in a disk into the tray which is connected to the SATA adapter. Strange enough the disk is spinning continuously. /sbin/lspci -v is showing the following SATA controllers: 03:00.0 SATA controller: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 03) (prog-if 01 [AHCI 1.0]) Subsystem: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at feafe000 (32-bit, non-prefetchable) [size=8K] Expansion ROM at feae0000 [disabled] [size=64K] Capabilities: [68] Power Management version 2 Capabilities: [50] Express Legacy Endpoint, MSI 01 Kernel driver in use: ahci Kernel modules: ahci 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. Unknown device 82d4 Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 41 I/O ports at a880 [size=8] I/O ports at a800 [size=4] I/O ports at a480 [size=8] I/O ports at a400 [size=4] I/O ports at a080 [size=32] Memory at fe6f8000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/4 Enable+ Capabilities: [70] Power Management version 3 Capabilities: [a8] SATA HBA Capabilities: [b0] Vendor Specific Information Kernel driver in use: ahci Kernel modules: ahci I guess the first one is the Lian Li. Link to comment
abs0lut.zer0 Posted March 9, 2011 Share Posted March 9, 2011 i have one of these fine cards in my system as well and i had the same problem with 5.x upwards and then it i tried on the 4.x range and all is fine. i thought the drivers would be included at a later date but the non reply's to your post leave me doubting.... Link to comment
EdgarWallace Posted March 10, 2011 Author Share Posted March 10, 2011 Thanks a lot for your reply abs0lut.zer0. I bought the adapter because of the positive feedback and it's strange that a driver disappears from one version to the next.... Would be great to get any statement from Limetech what happened to the device driver Btw. what is your jumper configuration? I was trying JBOD and the Port Multiplier settings and experienced no difference. Link to comment
abs0lut.zer0 Posted March 10, 2011 Share Posted March 10, 2011 geez, there is a question i just plonked in the machine and attached my icydock 5 in 3 exp to it and carried on, i can open and look for you later (+/- 5 hours from now) if it's a need. ? in regards to the other thing of the driver issue i was gonna wait for them to come out of beta on v5.x.. and see if it was included??.., maybe now is the time to say something and get the matter resolved ... any idea's from the moderators if they are looking at this thread?? Link to comment
EdgarWallace Posted March 10, 2011 Author Share Posted March 10, 2011 Hi abs0lut.zer0, that would be excellent and might avoid any further hassle. I wrote some lines here: http://lime-technology.com/forum/index.php?topic=11540.msg110828#msg110828 Maybe someone is listening Link to comment
abs0lut.zer0 Posted March 11, 2011 Share Posted March 11, 2011 Hi Edgar sorry for the late reply .... i can confirm i have my card set in port multiplier mode. Link to comment
EdgarWallace Posted March 11, 2011 Author Share Posted March 11, 2011 Excellent, thanks a lot abs0lut.zer0. Highly appreciated. Now let's see if we are lucky with the V.5 Link to comment
EdgarWallace Posted April 21, 2011 Author Share Posted April 21, 2011 I'm running out of disk capacity and might need to upgrade to unRAID Pro. However before I'm doing that I need to be sure that my SATA Adapter is working with unRAID. Is anyone be able to tell me what items I need to check in order to make sure that I can get more disk drive to work? Here is the informationI can pull out unMENU: 03:00.0 SATA controller: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 03) (prog-if 01 [AHCI 1.0]) Subsystem: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at feafe000 (32-bit, non-prefetchable) [size=8K] Expansion ROM at feae0000 [disabled] [size=64K] Capabilities: [68] Power Management version 2 Capabilities: [50] Express Legacy Endpoint, MSI 01 Kernel driver in use: ahci Kernel modules: ahci Link to comment
EdgarWallace Posted May 3, 2011 Author Share Posted May 3, 2011 ...another try to get a reply. Is the issue that I have the unRAID Server Plus version, hence the adapter is not being addressed? I would upgrade to the PRO version but I need to know if my HW is working with it. Link to comment
prostuff1 Posted May 3, 2011 Share Posted May 3, 2011 ...another try to get a reply. Is the issue that I have the unRAID Server Plus version, hence the adapter is not being addressed? I would upgrade to the PRO version but I need to know if my HW is working with it. There is not difference between Plus and Pro as far as driver support goes. Link to comment
EdgarWallace Posted May 3, 2011 Author Share Posted May 3, 2011 i have one of these fine cards in my system as well and i had the same problem with 5.x upwards and then it i tried on the 4.x range and all is fine. This is from an earlier post and this is why I bought the controller and I don't know how I can move forward. Is it a technical or a driver issue? :'( Is there anything I can do in order to provide information how to fix the issue? Link to comment
prostuff1 Posted May 3, 2011 Share Posted May 3, 2011 i have one of these fine cards in my system as well and i had the same problem with 5.x upwards and then it i tried on the 4.x range and all is fine. This is from an earlier post and this is why I bought the controller and I don't know how I can move forward. Is it a technical or a driver issue? :'( Is there anything I can do in order to provide information how to fix the issue? Contact Limetech is about the only thing that can be done. The 5.0bX series uses a different driver for handling some of the cards (like the SASLP) and there may be no support for the card you mention in 5.0. My suggestion is to use 4.X series for now and contact LimeTech about the issue. Link to comment
EdgarWallace Posted June 10, 2011 Author Share Posted June 10, 2011 It has been 5 weeks now since I sent an email to Limetech - no reply. Any more advise? It's annoying that a piece of HW that worked once (...and it's not that old right?) isn't working in a new version of unRAID. Link to comment
abs0lut.zer0 Posted June 10, 2011 Share Posted June 10, 2011 I am also waiting for the outcome of this post to do an upgrade to start testing 5.x series... so bump.. bump.. Link to comment
EdgarWallace Posted August 4, 2011 Author Share Posted August 4, 2011 Since mySQL for XBMC, Airplay and AFP (incl. Time Machine) is now running well on unraid v5b10 I would like to raise the attention on the controller again. I was told that I need to post two log files: the first one with v4.7 (the last unraid version under which die controller was working) and a second log file with v5bx (...where the controller stopped working) in order to see the differences in the kernel or driver behavior. What kind of log file should I post in order to get help from someone much better skilled than I am (...never got any reply from Limetech)? I don't want to risk my data, hence considered to remove all data related drives by pulling the respective SATA cables connected to the mobo SATA ports. Another option would be to deselect all 6 SATA ports in the BIOS. Can someone confirm that this would work? The last question is: would it be enough to just booting with the fresh native unraid v4.7, save the log file and afterwards booting with unraid v5b10? Currently I just have an unformatted 250GB drive attached to the Lian Li IB-01 controller. Please advise, thanks a lot. Link to comment
prostuff1 Posted August 4, 2011 Share Posted August 4, 2011 The last question is: would it be enough to just booting with the fresh native unraid v4.7, save the log file and afterwards booting with unraid v5b10? That should be enough, though we may have to get other things later as we discover more things. Link to comment
EdgarWallace Posted August 5, 2011 Author Share Posted August 5, 2011 prostuff, thanks for your kind offer to help. I removed all drives except the one that is connected to the Lian Li adapter. Here are the results: Booting with unraid 4.7: web front end is showing the disk drive Booting with unraid 5v10: web front end is showing the disk drive Booting with unraid 5v10 and all drives connected: web front end is showing my configuration but is not showing the drive connected to the Lian Li. The hard drive activity LED is always on ... why is that?? Unfortunately I don't have an second empty drive available so that I can't start the test array, hence can't generate a syslog with two drives connected both to the Lian Li. I raised to point earlier but don't want to miss to mention it again: I have the unRAID Server Plus version for 6 drives (incl. parity) and all are connected. My question is: do I have to upgrade to Pro before I move on as I now attach a 7th drive? As long as I don't have a second drive for the test let me provide you with the input I'm able to provide. Here are the important lines I guess: Aug 5 17:11:52 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 5 17:11:52 Tower kernel: ata7.15: Port Multiplier 1.2, 0x197b:0x0325 r0, 15 ports, feat 0x5/0xf Aug 5 17:11:52 Tower kernel: ata7.00: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.00: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.00: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.01: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.01: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.01: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.02: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.02: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.02: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.03: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.03: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.03: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.04: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.04: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.04: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.05: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.05: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.05: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.06: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.06: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.06: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.07: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.07: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.07: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.08: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.08: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.08: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.09: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.09: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.09: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.10: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.10: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.10: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.11: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.11: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.11: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.12: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.12: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.12: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.13: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.13: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.13: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.14: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.14: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.14: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7: EH complete Full log is attached. Thanks a lot. Link to comment
prostuff1 Posted August 5, 2011 Share Posted August 5, 2011 prostuff, thanks for your kind offer to help. I removed all drives except the one that is connected to the Lian Li adapter. Here are the results: Booting with unraid 4.7: web front end is showing the disk drive Booting with unraid 5v10: web front end is showing the disk drive Booting with unraid 5v10 and all drives connected: web front end is showing my configuration but is not showing the drive connected to the Lian Li. The hard drive activity LED is always on ... why is that?? OK, so 4.7 AND 5v10 find the drive just fine. You have a Plus license and if you look here you will see that it allows you to connect 5 data drives. You are at your limit with the current set of drives you have attached as data drives. If you want to use that drive as a cache drive then you should be able to stop the array and assign the drive as a cache drive. Unfortunately I don't have an second empty drive available so that I can't start the test array, hence can't generate a syslog with two drives connected both to the Lian Li. Hell, the drives don't have to be empty. You should be able to attach all the drives to the controller and get them to work. I raised to point earlier but don't want to miss to mention it again: I have the unRAID Server Plus version for 6 drives (incl. parity) and all are connected. My question is: do I have to upgrade to Pro before I move on as I now attach a 7th drive? See above what I said. You should be able to assign that empty drive as a cache drive but nothing more (or swap it out for a data drive that is already in the array). As long as I don't have a second drive for the test let me provide you with the input I'm able to provide. Here are the important lines I guess: Aug 5 17:11:52 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 5 17:11:52 Tower kernel: ata7.15: Port Multiplier 1.2, 0x197b:0x0325 r0, 15 ports, feat 0x5/0xf Aug 5 17:11:52 Tower kernel: ata7.00: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.00: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.00: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.01: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.01: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.01: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.02: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.02: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.02: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.03: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.03: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.03: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.04: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.04: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.04: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.05: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.05: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.05: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.06: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.06: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.06: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.07: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.07: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.07: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.08: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.08: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.08: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.09: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.09: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.09: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.10: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.10: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.10: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.11: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.11: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.11: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.12: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.12: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.12: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.13: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.13: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.13: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7.14: hard resetting link Aug 5 17:11:52 Tower kernel: ata7.14: failed to resume link (SControl 0) Aug 5 17:11:52 Tower kernel: ata7.14: SATA link down (SStatus 0 SControl 0) Aug 5 17:11:52 Tower kernel: ata7: EH complete Full log is attached. Thanks a lot. The above indicated some problem with the link itself. That usually means the drive is not connecting properly and is a hard drive problem. I have not had a chance to look through the log fully but will in a little while. It would be great if I could get all of the below. log file with 4.7 booted and the one drive attached to the controller card log file with 4.7 booted and multiple drives attached to the controller card log file with 5.0b10 booted and one drive attached to the controller card log file with 5.0b10 booted and multiple drives attached to the controller card I want all those as separate log files so that I can do a "diff" between them and see what differences there might be. If you can take screen pictures of all the above scenarios that may also help to nail down the issue. Link to comment
EdgarWallace Posted August 12, 2011 Author Share Posted August 12, 2011 I was able to pre-clear the drive, format it and finally having it attached into the array; this all with 5b10 The caveat is, that the drive is showing strange behaviour: when I configure the BIOS with AHCI the drive activity LED is always on and I will not be able to access the drive when I configure the BIOS with RAID the drive activity LED behavior is correct and I can access the drive, however that might change with the next boot I decided to get rid of the adapter. The question is: what adapter is more reliable? Any advise? Link to comment
abs0lut.zer0 Posted August 13, 2011 Share Posted August 13, 2011 :'( :'( :'( :'( :'( :'( I hope the adapter goes to that nice quiet place where all good adapters go to rest..... Link to comment
EdgarWallace Posted August 15, 2011 Author Share Posted August 15, 2011 abs0lut.zer0 I do not have decided where to rest the adapter and I don't feel good about the system status at all :'( The drive connected to the adapter is marked as red and disabled and the whole system is working but showing "amber" system status. My mobo is having the following expansion slots: 1 x PCIe 2.0 x16 2 x PCIe x1 1 x PCI With 2 adapters supporting 2 SATA connectors each I would be more than happy. Is someone having any advise which adapter to choose or is there any adapter available for the PCIe 2.0 x16 expansion slot? This should be a 4 Port adapter minimum. Link to comment
prostuff1 Posted August 15, 2011 Share Posted August 15, 2011 abs0lut.zer0 I do not have decided where to rest the adapter and I don't feel good about the system status at all :'( The drive connected to the adapter is marked as red and disabled and the whole system is working but showing "amber" system status. My mobo is having the following expansion slots: 1 x PCIe 2.0 x16 2 x PCIe x1 1 x PCI With 2 adapters supporting 2 SATA connectors each I would be more than happy. Is someone having any advise which adapter to choose or is there any adapter available for the PCIe 2.0 x16 expansion slot? This should be a 4 Port adapter minimum. for the x16 slot get a Supermicro SASLP, for the x1 slots get a cheap 2 port SATA card from somewhere like monoprice. Link to comment
AndreM Posted September 2, 2011 Share Posted September 2, 2011 So from this I gather this card works on unRAID 4, but it no longer works in unRAID 5? I was also considering getting two of these cards for my migration to unRAID, it's about the only one available here that will work with my current setup. Link to comment
EdgarWallace Posted September 2, 2011 Author Share Posted September 2, 2011 I changed it against 2 Adaptec 1220SA adapters and this setup was working without any further hassle (attached to the 2 x PCIe x1 slots, so that I have the PCIe 2.0 x16 slot still available) Where are you living? If in Germany I can send my card over for testing purpose before you spend any money and time. Cheers Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.