H310 $35

rubylaser

Active Member
Jan 4, 2013
842
229
43
Michigan, USA
@rubylaser, are you trying to flash these on a motherboard you have used LSI cards on before? Just checking as I had forgotten about the PCIe problems these have on most Gigabyte and other non-server motherboards and not showing up in BIOS or utilities. Thought I had a couple of failed cards too, but in a SuperMicro board they flashed fine (mine were not from this deal, it was a couple of 9201-16e I think from a Compellant off of ebay.)
I'm flashing these in a UEFI X99 MSI SLI Plus motherboard. I just flashed a different H310 card in this same motherboard following these same directions about a week ago. I can try to view them in my Supermicro X9SRL-F when I get home, but I would think that if the same type of card worked in the same slot a week ago, it's unlikely that this will fix the issue, but I'm open to suggestions.
 

MatrixMJK

Member
Aug 21, 2014
70
27
18
52
Nope, if one showed up and flashed OK in that board, then the other may have a problem. Just wanted to rule that out, in case it needed the "tape over the PCIe connector" fix.
 

rubylaser

Active Member
Jan 4, 2013
842
229
43
Michigan, USA
Nope, if one showed up and flashed OK in that board, then the other may have a problem. Just wanted to rule that out, in case it needed the "tape over the PCIe connector" fix.
Yeah, and I received 2 H310's from this seller and neither appears to be working :( I'll try in my Supermicro board when I get home, but this sucks.
 

T_Minus

Build. Break. Fix. Repeat
Feb 15, 2015
7,046
1,583
113
CA
I've got some things to do then will throw mine in this afternoon and see if any of the 6 I got work.... GRRRRRRRRRR
I need them all to work!!! I'm out of HBAs... might have to hittup @whitey for some of his spares :p :p
 

rubylaser

Active Member
Jan 4, 2013
842
229
43
Michigan, USA
I just got home and put them into my X9SRL-F motherboard. So sas2flash.efi -listall sees the cards but says "ERROR: Failed to Upload Image!". Does anyone know how to fix this?

These appear to be failed flashes and sold on the cheap to be rid of them.

EDIT: only card even gets this far. The other doesn't show up at all in megarec -adpList or in sas2flash -list
 
Last edited:

rubylaser

Active Member
Jan 4, 2013
842
229
43
Michigan, USA
I'm just going to return these two cards. I don't have time to screw around fixing someone's failed flash attempt. Here is what I wrote in my return if anyone wants to use something like it.

Both of these cards do not work. They were packed poorly, 2 in a single Priority Envelope with 1 layer of bubble wrap around them loosely in the envelope. One of the 8087 connections was bent.

The OptionROM does not show up at boot on either of these cards meaning that someone has tried to flash them to IT mode at some point. Neither card is recognized by any Operating System like Windows or Linux. Neither card shows up as an adapter in via megacli -adpList or via sas2flash. It appears someone attempted to flash these cards with IT firmware, failed/bricked them, and then tried to sell them off as working pulls. I am really disappointed in this whole transaction.
 

T_Minus

Build. Break. Fix. Repeat
Feb 15, 2015
7,046
1,583
113
CA
sas2flash.efi - Doesn't find my PERC 310, but when booting BIOS shows the 310...

Going to try in a non-uefi system to see if megarec shows anything...
 

rubylaser

Active Member
Jan 4, 2013
842
229
43
Michigan, USA
sas2flash.efi - Doesn't find my PERC 310, but when booting BIOS shows the 310...

Going to try in a non-uefi system to see if megarec shows anything...
You should be able to boot to legacy boot on most UEFI systems as well. It's funny that it showed up during boot. That means the optionROM is still installed on the card. Did you try any of the others?
 

T_Minus

Build. Break. Fix. Repeat
Feb 15, 2015
7,046
1,583
113
CA
Well... I got it to "work" except I have a problem.

No SAS# on the card.
sas2flsh -list shows
sas address: 000000000000000000-00-00000000000000

???
 
  • Like
Reactions: rubylaser

rubylaser

Active Member
Jan 4, 2013
842
229
43
Michigan, USA
Well... I got it to "work" except I have a problem.

No SAS# on the card.
sas2flsh -list shows
sas address: 000000000000000000-00-00000000000000

???
If just the address is missing, that's easy to add via sas2flash. Does it have a firmware version and show you the other information for the card?
 

T_Minus

Build. Break. Fix. Repeat
Feb 15, 2015
7,046
1,583
113
CA
Firmware: 7.15.08.00
NVData VEndor: Dell

Just no SAS Address....

How do I set/access the address ?
 

T_Minus

Build. Break. Fix. Repeat
Feb 15, 2015
7,046
1,583
113
CA
Rather, how do I make sure I give it the "Right" address.

I'm assuming this technically 're-adds' the address: sasadd
 

PigLover

Moderator
Jan 26, 2011
2,969
1,280
113
On most SAS cards there should be a sticker listing the SAS address assigned at manufacture.
 

T_Minus

Build. Break. Fix. Repeat
Feb 15, 2015
7,046
1,583
113
CA
@rubylaser @PigLover I see the sticker on my m1015 cards but no place on the H310s.

Any ideas? I've got 3 I checked both sides couldn't find any #s at all that vary actually.
 

rubylaser

Active Member
Jan 4, 2013
842
229
43
Michigan, USA
@rubylaser @PigLover I see the sticker on my m1015 cards but no place on the H310s.

Any ideas? I've got 3 I checked both sides couldn't find any #s at all that vary actually.
Mine don't have an address label on them either. You can add any SAS address in the proper format. It will work fine and register as "proper" to the host :)
 
Last edited:

T_Minus

Build. Break. Fix. Repeat
Feb 15, 2015
7,046
1,583
113
CA
Ok, once I do that then I'm doing p7->p20 and hopefully it works :)
 

PigLover

Moderator
Jan 26, 2011
2,969
1,280
113
Just use a relatively random value - it just has to be unique within your local configuration. If your paranoid, look up the IEEE list of assigned manufacturer prefixes and use one that is currently unassigned.