What to do with this Firecuda 530?

sg0

sg0

Associate
Joined
10 Jan 2013
Posts
269
Morning all, I purchased a 2tb firecuda 530 from OC back in June last year to put in my new system, slot m2 1 gen 5. I also installed my old 970 evo in another slot. When setting up windows in the new build I could not get it to boot from the firecuda but the 970 worked.The firecuda works in windows as it should. I assumed perhaps there was a setting in the bios to correct this inability because the slot itself used different pcie lanes etc plus the faf removing the gpu, heatsinks etc. So I just left as is and used the pc as normal. forgot all about it.

So this weekend I wanted to set up dual booting. After trying to install windows again on this drive it's the same issue, then I remembered the initial problem last year. So after more faffing around with the bios I finally give up and removed all the obstacles and switch ssd's and the 970 installs fine in slot m2 1. So for some reason booting from firecuda is not possible.

What are my options with returns or fix? Thanks.
 
Last edited:
If ocuk sold it with 1 year warranty
You would have to rma to manufacturer
Could phone ocuk or send them a web note
To see where you stand

If it works fine in windows that's curious
You could try a cloning software
And see if can successfully clone to it
And then boot off it
 
Have you tried a firmware update?
Just updated it an hour ago from xxx005 to xxx100. What a ball ache that was. Still no joy . Windows Files and folder are there bios sees drive (not as bootable though) just no startup. Windows cannot repair. I might try and copy efi from another disk.
 
What is the boot order in bios?
Just UEFI bios scandsk etc. from the install usb. 1tb 970 evo is fine get this showing as bootable (in list) after win11 install. 2tb firecuda not showing after install but setup finishes fine. Did notice 1tb has a 200mb efi partition and 2tb firecuda has a 300mb efi.
 
Last edited:
I assumed perhaps there was a setting in the bios to correct this inability
The only setting I'm aware of that can impact booting is CSM/legacy mode, because this is intended for MBR, whereas CSM disabled is for UEFI/GPT.

That shouldn't be an issue if you're installing fresh on the drive, unless the format as MBR is being preserved, but I shouldn't think so.
 
Update: Windows 10 install works?? It’s bootable. Things I’ve noticed so far . Efi partition is only 100mb compared to 300mb on win 11. I’m thinking this is significant only because when setting up efi manually using win11 install media and diskpart, I was not allowed to create efi/system partition of less than 2xxmb.

Why does win 10 boot work??
 
Update: Windows 10 install works?? It’s bootable. Things I’ve noticed so far . Efi partition is only 100mb compared to 300mb on win 11. I’m thinking this is significant only because when setting up efi manually using win11 install media and diskpart, I was not allowed to create efi/system partition of less than 2xxmb.

Why does win 10 boot work??
You shouldn't need to do anything manually? I'd just delete all of the drive partitions in the installer and then let Windows do what it does.

Can you confirm that this is formatted to GPT and that CSM is disabled?
 
You shouldn't need to do anything manually? I'd just delete all of the drive partitions in the installer and then let Windows do what it does.

Can you confirm that this is formatted to GPT and that CSM is disabled?
I was hoping that but the computing gods felt I should be done sideways.

Yes CSM disabled and GPT enabled.

Update: seeing that win 11 upgrade from win 10 worked on this drive and is now booting as is I thought I try a fresh install from win11 setup media and it’s looking good. Just got to finish the updates. It’s restarted a few time and continues the process. This never happened before the win 10 install.

I do apologise, I did state above that in post 6 that setup finishes fine which I made a mistake. It’s the initial copying and installing that finished but on the restart it never booted from the nvme in question. It’s now progressing past this point
 
Last edited:
Update: seeing that win 11 upgrade from win 10 worked on this drive and is now booting as is I thought I try a fresh install from win11 setup media and it’s looking good. Just got to finish the updates. It’s restarted a few time and continues the process. This never happened before the win 10 install.
Great! Maybe the Windows 10 install fixed the partitions?
 
  • Like
Reactions: sg0
That's computers for you
Stuff that should work doesn't always
And stuff that shouldn't work does sometimes

Maybe will work fine from now on
Maybe it won't
Regarding installing windows
You probably don't feel like erasing it
And trying again to see which happens

Now it's running
Would suggest use the manufacturers software
To check it's health /smart status
As a precaution
 
Back
Top Bottom