Hi,

This is quite an old thread but seems to be the only one that really talks about this :).

I have the same motherboard, albeit v1.0. It seems to have the issue of only detecting 1.6TB of a 4TB drive.

This is including disk management.

I gather this has something to do with the BIOS compatibility and it not being UEFI? I am in fact not trying to make it a boot drive but simply a data drive. From what I've read, this should work.

However, I can't seem to get it to see all 4TB, no matter which controller I try.

This is for one of the drives. Another drive I have, which was preformatted to begin with, it "saw" 4TB, but seems to only use up 1.6 or 1.8TB before it complains that it is full. The drive shows itself as being completely full but when checking the file size of all the files together, it only reveals it to be half the amount.

I am thus thinking that this has something to do with the BIOS or controller.

I thought the instructions here would maybe enable the allowance to see the drives as they are but I think I'm a bit confused as to how to go about it.

Any clarification and reassurance will be of great help.

Thanks.

Hello @Braxess and @BigDook (and of course @Fernando).

Sorry to resurrect such an old thread. I'm still using this ancient board, and hoping to bring it to life with new Option ROM RAID BIOS.

Do either of you have a copy of the modded BIOS you ended up with? Hoping you can share, to avoid reinventing the wheel.

Short of that, where to obtain the newer OROM version 11.2.0.1527, so I can continue following the guide? All the download links in posts about this seem to have expired.

So far, I am past the 8MB size issue by splitting the file with HxD.

Thank you for any help you can provide!

Excellent, thanks for pointing me to that guide I had not yet seen.

I have the new OROM for v11.2.0.1527 integrated/replaced into a modded ROM with CBROM32_140. However, attempting to display the contents (/D), it seems to hang indefinitely on the Micro Code Information at the bottom. Is this a known issue, or did something go wrong?

C:\bios\f9mod>CBROM32_140.EXE h57musb3_part.f9 /D
CBROM32 V1.40 [04/30/04 release] (C)Phoenix Technologies 2001-2004
 
              ******** h57musb3_part.f9 BIOS component ********
 
 No. Item-Name         Original-Size   Compressed-Size Original-File-Name
================================================================================
  0. System BIOS       20000h(128.00K)  13984h(78.38K)  test.BIN
  1. XGROUP CODE       0E0D0h(56.20K)   0979Ah(37.90K)  awardext.rom
  2. ACPI table        057E0h(21.97K)   01C30h(7.05K)   ACPITBL.BIN
  3. GROUP ROM[18]     04BC0h(18.94K)   02E87h(11.63K)  ggroup.bin
  4. GROUP ROM[20]     04870h(18.11K)   02E8Bh(11.64K)  ffgroup.bin
  5. Other(40CA:0000)  00960h(2.34K)    006DFh(1.72K)   y2group.bin
  6. YGROUP ROM        0D7F0h(53.98K)   076F8h(29.74K)  awardeyt.rom
  7. GROUP ROM[22]     0F630h(61.55K)   02CE5h(11.22K)  tgroup.bin
  8. GROUP ROM[23]     0F630h(61.55K)   040B7h(16.18K)  t1group.bin
  9. GROUP ROM[24]     0F630h(61.55K)   01979h(6.37K)   t2group.bin
 10. GROUP ROM[ 0]     07AA0h(30.66K)   02A70h(10.61K)  _EN_CODE.BIN
 11. Other(4069:0000)  351C0h(212.44K)  351F5h(212.49K) csimemrc.bin
 12. VGA ROM[1]        10000h(64.00K)   094B8h(37.18K)  ild_1973.dat
 13. PCI ROM[B]        04000h(16.00K)   02B4Ah(10.82K)  pchahci.bin
 14. PCI ROM[C]        0F800h(62.00K)   09328h(36.79K)  rtegrom.lom
 15. PCI ROM[D]        08000h(32.00K)   04628h(17.54K)  jmb10706.bin
 16. LOGO BitMap       4B30Ch(300.76K)  1B59Ah(109.40K) usb30.bmp
 17. GV3                037C0h(13.94K)  021D9h(8.46K)   PPMINIT.ROM
 18. OEM0 CODE         03056h(12.08K)   022F4h(8.74K)   SBF.BIN
 19. LOGO1 ROM         00B64h(2.85K)    00520h(1.28K)   dbios.bmp
 20. PCI ROM[A]        1DC00h(119.00K)  10EDFh(67.72K)  pchraidr.bin
 
  Total compress code space  = E3000h(908.00K)
  Total compressed code size = B7369h(732.85K)
  Remain compress code space = 2BC97h(175.15K)
 
                          ** Micro Code Information **
Update ID  CPUID  |  Update ID  CPUID  |  Update ID  CPUID  |  Update ID  CPUID
------------------+--------------------+--------------------+-------------------
 

edit: formatting

@templeofdoom - only certain cbrom versions will display this properly, depends on BIOS and sometimes no matter what fails to display ucodes after being modified making it hard to trust sometimes.
For GigabyteH57 try 115, 198, 219 or 155 (only edit with 155 or below). Did it display the microcodes properly with 140 before you edited it? If yes, I would do the edit again using another version instead.
Gigabyte H55/H57 is a pain for many mods, be prepared for recovery if you flash mod BIOS. This may apply more towards H55 than H57, since I see your BIOS is not 4MB BIOS that I'm most familiar with from H55N

@Lost_N_BIOS: Thanks very much for the guidance.
Now I'm using CBROM32_198 and getting past that issue, I now can display the modded BIOS image that contains the newer RAID OROM.

I'm now getting failed attempt to flash the BIOS: Q-Flash reports "File size incorrect.", and FLASHSPI indicates "!!! Bad BIOS Image !!!". Looks like I have more reading to do if there's a checksum that needs to be corrected or something. Any pointers are much appreciated.

@templeofdoom - Do the mod with 140 again, but check the microcodes in not 140 version (Such as 115 or 195-198 after the mod). Sometimes when I edit BIOS, 155 always fails to display microcodes, or crashes right then, even if BIOS is OK, might be same/similar for 140
So the mod you did originally might be OK. If it's not, try again with 115 for the entire mod, or 195 maybe. Usually above 155 is going to cause issue if you move something above a sensitive module (This case PPMinit)
You can also try with 219, it's older than 155, so still OK to try.

Sorry, I don't have more tips, hopefully you have flash programmer so you can recover easily if needed. H55/H57 is tricky to do, sometimes not possible to edit. Sorry I meant your BIOS is not 8MB when I said 4MB above, but I see it actually is (I was reading your CBROM info and assumed 1MB BIOS )
I will try the edit myself and let you know what I find, but I can only tell you what I see on my end mid-edit, I can't test any BIOS.
I'll update with mod and or info shortly

* Edit - 115 - displays ucodes properly with entire BIOS or BIOS region extracted, but does not display rest of BIOS
155/155.1 - crashes mid-ucode display with either full BIOS or BIOS region only extracted - does not display BIOS contents
199+195+196+198+182+180 - displays ucodes properly with entire BIOS or BIOS region extracted, but does not display rest of BIOS
219,124,208,220,217A - does not display contents or ucodes with full BIOS or Region, but does not crash
123 hard fail, no crash no nothing
602 - displays partial BIOS contents (2 entries) no ucodes, no crash
603B+207,214,201b,205,606,201 - similar to above, but only shows 1 entry

Oddly, with 140 I get crash same as with 155/155.1, and I do not get BIOS contents displayed like you showed above?
Mine shows same build date as yours too. Same with 149.

I don't think this BIOS can or should be edited with cbrom, all similar issues I've ran into with H55N, it's one in an interim period in Gigabyte BIOS where they were switching some things up and BIOS types were partial/mixed and different engineers were building these I think.

I will see if I can figure out how to update the RAID rom for you. You tell me, how you got 140 to display BIOS contents like that above? Nothing for me except two entries (System BIOS and the {SP} NCPU module, then crash at ucode display, even on just the BIOS region extracted)

** Edit 100 -
I found it's using LZH compression (-lh5-) type - compressed bin location starts at 0x776069h and ends at 0x782633h. It's 50KB compressed and it's header checksum is 4d (Located at second byte of the compressed file), and this checksum is also stored at 0x77606Ah
I can create a replacement file, but can only get it down to 68KB no matter what I do, so it wont fit back into same position and I can't find way to properly insert and rebuild without killing the file.
Award BIOS Editor will work with the BIOS and replace the file, but if I insert as is or LZH compressed it's dead after re-opening, so this tool not ideal to work with the BIOS either.

If I could get it to 0xc5cb (Exact hex size), then I could easily replace via hex and update the checksum, but it's too big for this method to work without other tools to rebuild the BIOS.
We can test verify that method would work, using a smaller 83KB or less rom, and test insert that, then you flash, but it's a big risk if you do not have CH341A + SOIC8 test clip cable.

What cbrom did you insert with? Maybe you can just correct the checksum and it will work? Send me your file that you can't flash, but you have updated, and I will see if I can make it flashable for you
Or you can edit that 4d checksum at 0x77606Ah with whatever the value is for your replaced compressed rom, you can find it at the second byte of it's compressed file location. It will be near the address mentioned above I assume and will be the first byte before >> 2d 6c 68 35 2d = -lh5- followed by the pchradr.bin file name.

Hello @Lost_N_BIOS Thank you for the detailed reply.

I got the BIOS file to open/display with CBROM32_140, 149 and 198, but only after splitting the file, as indicated by Fernando in the beginning of this thread. After taking the last 1024K of the file, then CBROM will open it and display the modules.

Seems strange that the first 7 MB is unused filler/garbage?

I have done the integrate/replace with both CBROM32_149 and 198, and it displays correctly (/D), and with 140 it hangs on the Display at the end, as I described before.

BigDook and Braxess seem to have been successful with just this method, so I have some optimism...

I do not have a flash programmer to recover, so I'm trying to be as cautious and informed as possible, but if I brick the board, I'm going to have to buy a new board anyway to get the 4 TB drives to work. So that's my backup plan! :)

Edit: Here's my modded BIOS that won't flash:
https://www.sendspace.com/file/2fkz1k
This was modded using CBROM32_198, after splitting out the last 1024K as mentioned earlier in this thread.

Appreciate any help you can provide!

@templeofdoom - thanks, and sorry I missed this in first part of thread about splitting the file. I was doing myself in my own tests just by default, but I only split the BIOS from the ME part, I didn't know it needed further splitting.
Now, since you showed me this, and 140 works better that way, I will need to recheck all those versions again with the BIOS split that way, maybe better luck with one of the cbrom's
ME region is 5MB, BIOS is 3MB, but seems I did notice that 140 readout properly the other day when I first replied and it's actually a 1MB BIOS in there (Out of the 3MB I pulled to begin my testing). Now, I will split it down more and see if I can get some cbrom to work properly or ABE

In your caution, I would not use 198 modified files. I would possibly use 149, since others had success. I'll check out your BIOS before doing my own re-testing in cbrom and ABE, maybe it's just that checksum you needed to fix.
Ahh! Never mind, I would not trust this file I didn't see until downloading you mentioned it's 198-edit, please upload the 149 edit you made instead, that's less risky of a flash. Both may be fine to flash, but I'd trust versions under 155 much more than above, when you move something from above a sensitive module.
I checked anyway, at least some, and I see that PPMinit module is relocated, I would not flash this file due to that. More info on sensitive modules here - https://forums.mydigitallife.net/threads...ll-of-us.15978/

I could not check your checksum at 77606Ah location (Should be changed from 2d to 83), due to you only uploaded a 1MB BIOS. Unsure if you know, but this can't be flashed as it is, if you were trying that this is why it failed.
You'd need to put this back into the BIOS before you can flash it, if you did that already great, if not this is why you aren't getting anywhere BIOS must be 8MB to flash

Off to try myself and see if I can come up with something that at least looks safe for you to try
*Edit - works fine with 115 as originally suspected, but PMINIT gets moved (Due to larger file size) even if replacing "In-place", I would not trust this either, they all may move this module and it's not good.
155 moves it too, even while replacing in place, it moves the rom below PMINIT while 115 does not. Either way, PMINIT is moved, so not good.
BUT!!! I checked and with both 115 and 155 ENTRYPOINT is re-corrected to be same after each edit, but I'm not 100% this is the key, I think PMINIT needs to remain exact position.
Best method due to file size change needed, is to extract everything from pchraidr.bin down and then reinsert after putting in the new one, making sure to place PMINIT back in it's original exact location hex-wise.
To do that, one of the other roms may need to be placed below PMINIT and a padding/dummy file used in it's place, so there is room above PMINIT for the new larger rom and the padding used to take up space in place of missing to land the PMINIT at it's original exact location
It's very tedious to do this! But, may be only way to make it work, this has been proven to be case on many boards when trying to move something above a sensitive module.


Detailed method laid out here by @SummoneR
[Guide] Enhanced BIOS Modding of Award BIOSes
And again by @aaaaaa889 with less details
Gygabyte GA-880GM-UD2H (rev. 1.3) (3)

@templeofdoom - I think I got it for you! Fingers crossed, but looks good to me
Qflash will let us know if it says bad image, or even if it flashes in you'll know if ROM fails due to no CTRL+I - for initial test, please disconnect RAID arrays so nothing goes wrong if it's not good mod, but I'm not sure, that may cause CTRL+I to not function?



Qflash Checksum should be as follows, and I suggest trying h57musb3M1.f9 first (you may need to shorten name)
4411 for h57musb3M1.f9
8311 for h57musb3M2.f9

http://s000.tinyupload.com/index.php?fil...121543384140862

@Lost_N_BIOS - you magnificent individual!!!!!

It flashed, it updated to 11.2.0.1527, and it WORKS!

Thank you Thank you Thank you! And thank you to @Fernando for hosting and maintaining this fantastic forum!

You are correct, CTRL-I doesn't work when there are no drives connected to the RAID SATA ports. I reconnected some drives and CTRL-I works to verify the Option ROM version and have a look at the RAID volumes.

@templeofdoom -

You're welcome and thank you for quick report back, also thanks for the confirm on the CTRL+I, I thought it was that way about the drives. Great to know all is working perfectly, that's a tough mod to get just right
Did you use h57musb3M1.f9, and was the Qflash checksum 4411 do you remember? I got the value on the file as a whole, but wasn't sure if maybe it could have been on the 1MB file (3F00) instead of overall

I was successful on first try with the first mod, "h57musb3M1.f9". I don't remember catching the Qflash checksum though.

You guys are awesome, I'm so glad I found this forum. I encourage anyone else coming across this thread or forum to please donate so we can keep resources like this around!

@templeofdoom - Thanks for info, I assumed M2 file wouldn't be needed, but made it just in case Qflash gave you issue with M1.
On the Qflash checksum, you can go to Qflash and select that BIOS again, but just don't flash, and I think you can see the checkum that way before you would normally say "Yes = flash" If you wanted to check

Thanks for the kind words and support, we're happy you found us too!

I just wanted to drop in here and say that I just used Lost_N_Bios's modded file and was successful flashing my GA-H57-USB3 (rev2) and can see my 4tb drives. I used Lost_in_bios's h57musb3M1.f9 file and indeed got a checksum of 4411 in Qflash. Thanks Lost_N_Bios and Fernando and templeofdoom!