PC-3000 Forum

I've mounted this SSD in an NGFF to SATA Adapter. It goes ready, but any attempt to access the device causes it to go busy and remains busy. I was able to use the short points to force it into a Safe Mode, it IDs as SM2258AB-80-10000000. I attempted to use both the ADATA utility and the Plextor Utility to gain access, both attempted to gain access via the Safe Mode Loader files, but neither was successful.

Anyone have any success accessing this type of drive? The client sent in the drive without the original label, so we are unsure what the actual model number is.

Hello.

Intel seriously protect their internal drive FW, so even support SM2258 controller become unsupported after Intel modification...

Thats unfortunate. Is Ace currently working on gaining access or is the protection too extreme and this is not on the current work list?

We are working under SM2258 full support. Please keep watch our news.

Hi! When can you expect updates? I wouldn't want the client to run away.

Roman_TS wrote:Source of the post We are working under SM2258 full support. Please keep watch our news.

That is great news Roman

digitalsupport wrote:Source of the post

Roman_TS wrote:Source of the post We are working under SM2258 full support. Please keep watch our news.

That is great news Roman

Hello ,
i have started to see some chinese people giving advert for recovery from this controller ,I saw roman say we will have a update of tool soon so maybe we see more innovations soon

Amarbir[CDR-Labs] wrote:

digitalsupport wrote:Source of the post

Roman_TS wrote:Source of the post We are working under SM2258 full support. Please keep watch our news.

That is great news Roman

Hello ,
i have started to see some chinese people giving advert for recovery from this controller ,I saw roman say we will have a update of tool soon so maybe we see more innovations soon

Hi!
after one year acelabs still does not have support(SM2256AB) for this problem and if you know of a solution please inform.

sempre wrote:Source of the post after one year acelabs still does not have support(SM2256AB) for this problem and if you know of a solution please inform.

Sm2258XT-based drives are fully supported in 6.8x

SM2256AB - is not a controller name. There is no such modification. There is SM2256K and SM2256S, while SM2256AB - is a firmware code.

Roman_TS wrote:

sempre wrote:Source of the post after one year acelabs still does not have support(SM2256AB) for this problem and if you know of a solution please inform.

Sm2258XT-based drives are fully supported in 6.8x

SM2256AB - is not a controller name. There is no such modification. There is SM2256K and SM2256S, while SM2256AB - is a firmware code.

Thanks reply!
Sorry is SM2256S !
Not solution is controller!

We support SM2256S in AMD R5 and ADATA SP550. But other drives might have different firmware which is incompatible with our loaders. We are planning to add more of them in future, but unfortunately I don't have any estimate time.

Is there a possibility to add feature where users can create loader from good donor SSD with new or currently unsupported firmware revisions to add more support in shorter times? I remember some similar feature at PC3000 for WD HDD at family selection window (I think it created file with HIF extension? It was long time ago so I do not remember perfectly)

AJ2008 wrote:Source of the post Is there a possibility to add feature where users can create loader from good donor SSD with new or currently unsupported firmware revisions to add more support in shorter times? I remember some similar feature at PC3000 for WD HDD at family selection window (I think it created file with HIF extension? It was long time ago so I do not remember perfectly)

Great idea

Looks like you guys do not understand what is the Loader for SSD so let me try to explain it in a few words without deep things.

Loader - is a seriously modified Firmware, where some background process, verifications and activities are switched off. At the same time, some previously locked options are switched-on, which allows to use the technologic mode commands and communicate with damaged drive: send special command for dump reading, SSD resources backup, factory reset, translator rebuild and etc.

Loader creation - is a serious research experience, which requires a lot of time, testing and debugging. If you are not an SSD developer with experience in Firmware research, you can't add your own loader. Believe me it's a really complex and multi-step procedure

Thanks for clarifying Roman. I guess we were assuming it was more like a HDD loader.