Wait a few? more days for the Intel 520.
Printable View
Wait a few? more days for the Intel 520.
It's not space I need but speed, in the 1000mB/s range for 5k video work.
Not sure if the Intel 520 will be available that quickly in France and in a similar price range as the M4 or Vertex 3.
Thanks for the feedback on the Vertex 3 though. I'm now curious as to which alternative already available I could go for if the Vertex is not a good candidate. Could not find a precise reference for the Samsung you mentioned. Is it a SAS drive?
The Samsung mentioned is the new 830, availability is sparse but should be getting better shortly.
(The Samsung 830 is SATA 6Gb/s)
Bump:
Any news for m4 fix?
I need the fix NOW! or many weeks ago :p
Received this is today's mail, may be the Areca/LSI issue after all!
email going out to Areca as we speak :)Quote:
Paul,
We continued to see no problems in our lab. At the end of last week, however, I got the following message from my contact at Areca:
Our engineer said ARC-1880i will perform the same as ARC-1880x for the issue. Thus, you should be able to duplicate the problem by using ARC-1880i with the procedure mentioned before.
However, LSI released a new PL microde, version, 11.0.1.0, which solve the compatible problem with M4. I've attached it for your reference. You may want to update your card for further testing.
So, Micron is taking no further action in this matter. We may do some validation activities on the side as a low priority action, but we continue to believe that the C400 is properly following the SATA specification.
Best regards,
I am glad that a fix is finally on the way! How do we update the PL microcode? Is it done through the web interface?
good news! :)
Alrighty, of course these things happen when i am away from home and cannot test...so...razor-nizzen YHPM :)
Yes me too, amazing news!
But does that mean we get to install a new firmware for the Areca 1880i?
I could not find any information on this, does somebody has a link?
Can you confirm that the M4s are really working in RAID0 with the Areca 1880i?
Thanks
Thanks, but no luck here. It still hangs during boot. Doing the unplug all the drives then plug them back in one at a time trick still works. It is getting really annoying, though.
Tired of waiting for M4 to work properly with 1880. Now 4xM4 is connected to IBM 1015, and Areca going to have 4xsamsung 830 for OS. The upside is more writespeed on the OS array :)
Yes this wait really sucks, I'm also about to buy 8 Samsung 830 but they are about 30e more expensive than the M4 here in France...
Anybody seen the Intel 520 out yet? Or even better tested them with the Areca?
I hate this bug, I have pretty much stopped using my main machine because it takes forever to get it to boot.
It is very distressing, i agree. I have some M4s laying around i would love to play with...last i heard they do have a fix for the non-expander versions of the card, which i have tested with the 1882 and it works.
For the versions with the expander, they are having issues seeing what is wrong "behind" the integrated expander when doing their tests.
Just a headsup:
Almost new driver: arcs64_V6.20.00.22_111006_WHQL.zip (17.11.2011) :eek: That is not often!
ftp://ftp.areca.com.tw/RaidCards/AP_...4Bit/storport/
Still waiting for a fix for M4 :(
Compu, I still haven't gotten around to trying the fix you gave me. My rig is still in pieces, but I should be back in business by mid next week. By the way, have you figured out how to put that command in? Do I need to use the serial port on the card? I assumed so, but I have never messed with that part of the card. Can I telnet/ssh into it?
nope, been busy with various projects tbh. I will be getting around to that soon though. Not sure if they have a preboot CLI with Areca, but i will find out.
Could you do a test with the M4's on the 9265 if you've still got it?
My 0002 drives work OK but the upgraded ones (0009) aren't detected at start-up, they sometimes are detected when inserted while monitoring in MSM.
This is getting pretty sad, I do like the M4's but I was planning on using them on a raid controller...
ok here is the deal, they are saying that the timeout can fix it,
but it has to be done from CLI, which i am not familiar with. I will forward you an email so you can test
Quote:
It seems that new Pl microcode code can solve the issue from the directly attach.
But it needs to change the spin up time on the SAS expander to solve it.
Could you use the CLI command to change the Spin up time from 1024ms to 128ms to see the result?
Drive SpinUp Control spin Delay(D)[ms] Num(D)
MegaCli -AdpSetProp SpinupDelay -val -a0
-val = not sure on what the measurement is for val, ms ?
Hope this helps
Grrr, Ignore this, double post, site seems really slow today
no, absolutely no idea tbh. but they use the same roc...dont know.Quote:
and you are quite sure that this would work on the LSI 9265?
My 9265 has the exact same issue. I would not expect it to be detected on that card either.
it IS a microcode from LSI...
Come on guys do I have to do everything ;) to get current value of spinup:
MegaCli -AdpGetProp SpinupDelay -a0
The 9265 is just a 9260 with dual core ROC
It will work.
This can be used when the card boots and you press CTRL+Y at the LSI BIOS splash screen, just remove the 'Megacli' for each command.
MegaCLI for DOS also works
For some reason Megacli for Win7 doesn't see my IBM M5015, can't quite work this out.