ATTENTION Crucial M4 SSD owners

[Britton30]

Right here Steve

http://www.sevenforums.com/news/206828-attention-crucial-m4-ssd-owners-8.html#post1743562

 

[Anak]

Thanks Britton! My eyes, and memory aren't what they used to be!

 

[Britton30]

Thanks Britton! My eyes, and memory aren't what they used to be!

:roflmao:I resemble that remark! Smartyeyeball was the sharp one who got us on the right path.

 

[Dickos Rig]

I know this thread is old but I am having this exact problem.

For some reason the firmware update will not take.
I cant get it to recognise the drive no matter what I do.
any thoughts please.

 

[smarteyeball]

Can the drive be seen in BIOS Y/N?

Is the drive visible in Windows Y/N?

 

[Dickos Rig]

Hi thanks for the reply.
Yes to both.
The drive did disapear once but an easy fix in BIOS.
It is fine for an hour, then I need to re boot.
The firmware update just says it cant find the drive, or no drive needs an update.

 

[smarteyeball]

How old is the drive?

In device manager, click on you drive and under hardware lds, what does it show the current firmware as?

 

[Dickos Rig]

Thanks again.
Drive is about 9 Months old. On almost all the time.
Would be about the 5k hours now.
Firmware is 0002

 

[smarteyeball]

Are you using the Windows based update utility or the bootable ROM method?

 

[Dickos Rig]

Have tried both.
Windows based says there in no drive needing an update.
Bootable method hangs and does not find the drive. Just keeps trying to find it. gggrrrr

 

[Dickos Rig]

Could it be worth trying to update in another rig.

 

[smarteyeball]

Mines on firmware 309 and the Win based updater can't find the drive either.

What is your BIOS set to, IDE, AHCI or RAID? (mines in Raid) I'm about to switch the BIOS to IDE and run the bootable method.

Could it be worth tryig to update in another rig.

If all local possibilities are exhausted, yes. But try switching your BIOS to IDE to start with and re-try the manual boot.

 

[Dickos Rig]

I am in AHCI, I thought it said that problem was fixed.
Perhaps I should try IDE.
Was not even sure the system would start in IDE.

 

[Dickos Rig]

OK, I will try IDE later.
Thanks very much for your help.
If all else fails I will try in another system.
It is so strange it runs well, just shuts down every hour.
Just shut down 5 mins ago.

 

[smarteyeball]

AHCi 'should' work -but IDE is the quickest way to eliminate shannaingans,

I just reset my Raid to IDE, booted from the disc found the drive and the update went cleanly.

If it works, just make sure you reset your Sata config back to AHCI otherwise your OS won't boot. (But IDE will boot the firmware disc perfectly fine)

 

[Dickos Rig]

Thanks for this.
I will do it this way. I wont forget to change back to AHCI, I spend a lot of time in BIOS, I love overclocking.
Let you know later if this works.

 

[smarteyeball]

OK, I will try IDE later.
Thanks very much for your help.

No worries mate. (it literally takes 2-3 mins for the whole process including changing to IDE, updating and back again)

If all else fails I will try in another system.

Fingers crossed it won't be necessary.

It is so strange it runs well, just shuts down every hour.
Just shut down 5 mins ago.

Yep, that's the bug all right. Once updated it'll be back to non-stop operation

Let you know later if this works.

Cool - just send me a visitor message saying "it worked" or ask for more help if it didn't. I think you'll be fine

 

[Dickos Rig]

No luck.
But I think I have the SSD connected to one of the Marvell SATA controllers.
Is this a problem?
Do I need to connect to another connector?
I have 2 Marvell and 2 normal SATA III, all currently being used.

 

[smarteyeball]

The marvel controller might indeed be an issue.

Simply swap to to one of the non-mavell controllers while you update. It won't affect anything else since you won't be booting into Windows.

 

[Dickos Rig]

I think I read somewhere that you cant be connected to a Marvell controller.
This is a pain in the a**.
I will do tomorrow. Cant be bothered now.
Thanks again. Post results later tomorrow.
At least this system works, just have to turn off every 50 mins or thereabouts.