nthu9280

Members
  • Content count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About nthu9280

  • Rank
    Member

Converted

  • Gender
    Undisclosed
  1. Glad to hear it's all working now. Like I said, I lived thru the frustrations too. Some H310 would complete without a hitch in 5 min while other H310 cards would take multiple attempts. As long as Megarec can see the card, it can be flashed. Sent from my Nexus 6 using Tapatalk
  2. It can be frustrating at time and I've gone thru' this pain. Try the following sequence. Someone had reported success with writing empty sbr after cleanflash. The standard sequence is before. Also check the syntax for my steps. I'm typing this on mobile from my memory. Try starting over: 1. megarec -cleanflash 0 2. Megarec writesbr sbrempty.bin 3. Reboot 4. Sas2flsh-p14 (without -o) -f 6gbpsas.fw 5. Reboot 6. Sas2flsh-p20 -f 2118IT.bin 7. Sas2flsh-p20 (sas-add) Sent from my Nexus 6 using Tapatalk
  3. Try the P14 version. Also, copy the FW file in the same directory as the sas2flsh. Not sure if that makes a difference. But just to rule out the quirks. Sent from my Nexus 6 using Tapatalk
  4. The card is not bricked. While the instructions you linked are detailed, it fails to explicitly say to use the older version of SAS2FLSH tool for the first time. You will need SAS2FLSH version (phase) 14 or below for flashing 6gbp SAS FW. Then you can flash the IT mode FW. Sent from my Nexus 6 using Tapatalk
  5. AFAIK, flashing this card requires sas2hax.efi and Motherboard that support/boot to uefi After flashing, you can non-UEFI motherboard.
  6. LSI SAS9207-8i for $99

    HP H220 is the same 9207-8i card and can be had on eBay for ~$40. I tend to stick with used Dell/HP/IBM OEM cards to avoid LSI counterfeit cards. With SAS2308 there are two different steppings C0 and D1. C0 ones are only PCIe 2.0 and need to use 9205 FW for some reason. D1 is PCIe 3.0 and flashes to 9207. There is a thread on STH on this topic. Sent from my Nexus 6 using Tapatalk
  7. @SSD Firmware & BIOS are two different things. IIRC, you are trying to speed up the boot process. So you would be clearing both and flashing the the controller to the latest FW and skipping the BIOS. Sent from my Nexus 6 using Tapatalk
  8. It's based on sas2308 chip. IIRC, 9217 is OEM version of 9207 and that firmware should work if Broadcom doesn't have stock FW updates for 9217. But like you said I also don't know if Dell has any customizations to prevent cross flashing Sent from my Nexus 6 using Tapatalk
  9. Assuming you followed the instructions on the D2607 thread. That card requires correct SBR (A11/A21) and also modified/patched version of sas2flsh (sas2hax) and correct sequence of steps. What perplexes me is that H310 also having the same issue for you. Sbrempty.bin should work fine with this card. You can reflash just the SBR file using megarec and see if rest of the ports are enabled again.
  10. @ezhik /@johnny Please update your guide for the sas2hax flash step with -noreset flag. That will prevent the error message Is it required to flash the FW twice? I only did once. Wasn't planning on adding BIOS. Sent from my Nexus 6 using Tapatalk
  11. @ezhik Thanks! I'm sure these instructions will help many folks. I've reflashed the SBR-A21. I will need to check if it can see drives on both ports and run some tests later. I know it can see the drives on the port it wasn't before. But I didn't check the port that was seeing drives before reflashing SBR can still see them. I'm sure have missed the cleanflash after writing the sbr. sas2hax failed validating the MfgPage2. So I tried multiple times over a span of couple of days and the last flash was successful (with the error I listed in my previous post) I get warnings (IO Base address high or something like that) while running megarec on my SM X10SRA efi board. So just to be safe I do all my DOS tasks on an old Dell T3400 (Core2 Duo) I keep for these purposes. It's kinda PITA moving the card between machines but guess I'll have to get used to it when it requires both EFI & DOS to complete the flash.
  12. Thank you so much for the detailed instructions. I was finally able to flash the -A21 card. Now need to test if it can see all 8 drives. I've already spent 5+ hours on this process in the last few days. Was having trouble flashing with sbr-a21, sbrempty. Not sure which sbr finally worked -- sbr-a11 or sbrfj Megarec did not have any issue with -cleanflash on the first try itself. sas2hax.efi did have issues even on the (seemingly) successful attempt while trying to issue reset. I got the following message. *** Adapter reset failed! Firmware fault occured. Fault code 704 Due to error remaining commands will not be executed unable process commands exiting sas2flash ** Rebooted and sas2hax and sas2flash(p20) could see the card and I could add the SAS Address and issue list, reset commands. So cautiously optimistic I've yesterday tried sas2hax -e 7, 4 and 8. Need to see if I need add any other info such as VPD etc to make sure it's not missing required. If I need any 6gbps HBAs in the future, think I'll stick with H310s as they seem to be fairly straight forward.
  13. True. I've not come across anything on cross flashing 2108 & 2208 based cards to IT mode. They are HW RAID only. Sent from my Nexus 6 using Tapatalk
  14. Jake, Follow-up question. The P4216IP4L unit I bought came with RMS25CB080 mezzanine card. Which is 2208 and to my knowledge can't be cross flashed. They have a ton of RMS25JB080 (appear to be -310 from the pic). Do you know if these can be installed on the IOM mezzanine slot? My other thought is to get the JB and swap out the CB and sell it. Sent from my Nexus 6 using Tapatalk
  15. PSU for new build

    If you don't already have a chassis, the eBay seller kalleyomalley has some really nice Intel New In Box surplus ones that come with a platinum power supply or two depending on the config for < $150 US. They have been discussed on the huge E5-2670 v1 threads here and on STH

Copyright © 2005-2018 Lime Technology, Inc.
unRAID® is a registered trademark of Lime Technology, Inc.