mav3r1ck

We all know that we can see LimeTech's online status. It also looks like Tom has found a way of having other users speak for him. No offense! Maybe there's nothing to be said, but there have been several discussions on Tom's absence (postings). It would be best to just give us an overview of the current beta plans.

I feel that everything below kernel 3.0.3 suits the AOC-SASLP-MV8's best

I was thinking of doing the exact same thing.. Please let us know if the m1015 runs with no errors.. It looks very promising sofar, But then again the system has only been running for 1 day and 20 hrs. Tune back in tomorrow. Normally within or shortly after 2 days the BLK error arises. Running smoothly for 2+ days now. You can never be a 100% sure on this, but removing the AOC-SASLP-MV8's replacing them by LSI 9211 8i's or IBM 1015 cards resolves the BLK_Not_HANDLED_ errors for me. In my case I don't have so much time to wait for a solution. My system: unRAID Version: unRAID Server Pro, Version 5.0-beta12a Case: Norco 4224 Motherboard: Supermicro X8ST3 BIOS: American Megatrends Inc, Version: 2.0, Release Date: 07/29/10 Processor: Intel® CoreTM i7 CPU 950 @ 3.07GHz Memory: 8GB Kingston 1333 MHz (0.8ns) Network: 1000Mb/s Full Duplex Harddrives: 14x 2TB Hitachi_HDS723020BLA642 2x 1.5TB SAMSUNG_HD154U

I was thinking of doing the exact same thing.. Please let us know if the m1015 runs with no errors.. It looks very promising sofar, But then again the system has only been running for 1 day and 20 hrs. Tune back in tomorrow. Normally within or shortly after 2 days the BLK error arises.

I moved to an IBM M1015 SATA/RAID card (Rebranded LSI 9211-8i) and also bought a genuine LSI 9211-8i. Flashed the 2 cards to IT-mode and I am currently starting my unRAID b12-a performing the first parity build/check. A fresh system and hopefully a fresh and good start without that annoying "BLK_EH error" In other words. I returned the AOC-SASLP-MV8's

I have the exact same issues as you describe above. I've been waiting for quite some time to get feedback, but radio silence seems to be normal. As I can't continue my project and part of my business I am moving towards another platform called FreeNAS. Another option would be ZFSguru. The current SATA controllers "AOC-SASLP-MV8" also have issues with FreeNAS. I've purchased IBM M1015 SATA RAID cards (rebranded LSI cards). I will be flashing them to IT-mode to remove the RAID functionality as FreeNAS works best with its OS having full harddrive control. It seems that these IBM/LSI cards (reading through unRAID topics) work fine with unRAID, so I might still be able to use my purchased Pro key after all.

It's all guessing what Tom is currently up to. It would be best if Tom would just inform us on the current unRAID beta activities he is working on. I understand that it's not possible to respond to every user/tester asking for support, but as mentioned above there's been radio silence for quite some time. No is also an answer ;-) Thanks!

Precleared 14 drives. All OK. Running 5 B12a I was gone for the weekend. The server is running 100% idle, nothing to do.... and there you are again: Sep 25 06:51:20 Goliath kernel: sas: command 0xee5d6180, task 0xf7600640, timed out: BLK_EH_NOT_HANDLED By default (within 2-3 days max) it results in a BLK_EH_NOT_HANDLED. Looks like 4.7 is the only other option for now. It's probrably in another topic, but can you switch from version 5 bxxx to 4.7 without too many bumps? @MikeL What's your hardware besides the AOC card

Good answer. Thanks So the preclearing of my drives in this beta 12a stage will probrably not help in getting rid of this "BLK_NOT_HANDLED"

Not sure, but .21 --> http://bit.ly/rphlMp also ain't your friend when it comes to the "BLK_NOT_HANDLED" How can I easily CLI the firmware version of my SASLP?

It does work, but I was told that it only takes 2TB instead of the total 3TB.. my supplier confirmed this after talking to Supermicro.

@Lars Olof, don't be sorry for the 'rant' .. I can take it ;-) I didn't start with 4.7 as I wanted to start with 3TB drives, but along the road I came to the conclusion that my "Supermicro 8-Port SAS/SATA Cards (3xAOC-SASLP-MV8) don't support >2TB. I am fully aware of the BETA stages and I respect them, but let's say 4.7 works without the "BLK_NOT_HANDLED" issue, why would this be an issue in the new beta serie (5bxx)? We perform regression tests to keep the current functional design operational not sure how that works for Lime. We will wait and see.

We have seen quite some cases with the "BLK_NOT_HANDLED" situation. A VERY annoying one. I still have this issue and for me the whole unRAID setup is worthless at the moment (Pro license, B12A) We have also seen users providing their FULL syslogs. Where's the support on this? I hope it's being looked at in the 'back office'. I work with developers everyday and I understand that at some point you will make rules in order to give quality feedback. Just now I am performing a Preclear run for all my brand new disks (13x2.0TB, Hitachi -HDS723020BLA642) and will try again when this finishes (takes forever ) What's the status? Thanks

Looks to be a problem with 'Plus' key - I'll fix it ASAP and post -beta8a. Hello Tom, I have the same issue running b12a for my PRO key... Sep 11 21:03:19 Goliath emhttp: Copyright © 2005-2011, Lime Technology, LLC Sep 11 21:03:19 Goliath emhttp: Pro key detected, GUID: 13FE-XXXX-XXXX-XXXXXXXXXXXX Sep 11 21:03:19 Goliath emhttp: get_config_idx: fopen /boot/config/flash.cfg: No such file or directory - assigning defaults Sep 11 21:03:19 Goliath emhttp: rdevName.22 not found Sep 11 21:03:20 Goliath emhttp: diskFsStatus.1 not found Sep 11 21:03:20 Goliath kernel: emhttp[13311]: segfault at 0 ip b74a6760 sp bf8961b0 error 4 in libc-2.11.1.so[b742d000+15c000] As you say above 'looks like a problem with the PLUS key' Thanks for your quick response

Looks to be a problem with 'Plus' key - I'll fix it ASAP and post -beta8a. Hello Tom, I have the same issue running b12a for my PRO key... Sep 11 21:03:19 Goliath emhttp: Copyright © 2005-2011, Lime Technology, LLC Sep 11 21:03:19 Goliath emhttp: Pro key detected, GUID: 13FE-XXXX-XXXX-XXXXXXXXXXXX Sep 11 21:03:19 Goliath emhttp: get_config_idx: fopen /boot/config/flash.cfg: No such file or directory - assigning defaults Sep 11 21:03:19 Goliath emhttp: rdevName.22 not found Sep 11 21:03:20 Goliath emhttp: diskFsStatus.1 not found Sep 11 21:03:20 Goliath kernel: emhttp[13311]: segfault at 0 ip b74a6760 sp bf8961b0 error 4 in libc-2.11.1.so[b742d000+15c000] As you say above 'looks like a problem with the PLUS key' Thanks for your quick response