Salta al contenuto principale

Failure copying and restoring onto EeePC 901 Mini eSATA II SSD

Thread needs solution

Dear Acronis support, dear community

I have following problem.

Last year...
---------------
I have bought a slow no-name 64GB SSD for my Asus EeePC 901 one year ago. I backed up the partitions from original Asus 8GB SSD with Acronis True Image 2009 Home (small note: my old version did not work with the EeePC, but 2009 Home does) before I exchanged this by the this old no-name 64GB SSD.

I could partition it with Paragon Partition Manager 8.5 (PPM 8.5) and could restore the image back to the old no-name 64GB SSD. Everything was fine. It was slow, but worked fine. But I could not use it as boot partition with operating system - it was much too slow.

Last month...
-----------------
Because I was nerved by this slow SSD and wanted to have a bigger OS partition (e.g. hibernate does not work because of too less disc space), I bought Super*Talent Mini eSATA II SSD model FPM64GLSE in Sept. 2009. I replaced the old no-name 64GB SSD after I created a new Acronis image. The EeePC recognizes it as Primary Slave device, while the 4GB internal OS SSD is Secondary Master. I still have the original BIOS version which was shipped with my EeePC.

The first partitioning worked fine with PPM 8.5.

But for my surprise the image restore failed at the very end of the restore process, while the image consistent check that I performed before has been succesful. "Restore failed". Great. The partition I had created was destroyed. When I restore it using PPM 8.5 (it had vanished), it is completely filled again, but with 0 bytes free. It is simply not accessible then and corrupt.

It became even worse -.-

When I repeated the process of partitioning and restoring the image (I tried restoring from SD-Card, USB-HD, tried copying the 4GB internal SSD with the operating system) the errors increased... Later on Acronis told me about like "could not write to sector 0","could not write to sector 63", a.s.o. PPM 8.5 told me about "I/O errors", "performing tasks failed" -.-

Then I returned Super Talent FPM64GLSE to the trader of my trust.

Yesterday...
----------------
My online trader was so kind to send a new one which came in to me yesterday...

Okay. Put on my anti static gloves. Grabbed my screwdriver. Replaced the SSD again. It said hello. I could partition it with PPM 8.5 easily. Fine I thought - until now it works the same way as the old FPM64GLSE that I had returned...

And unfortunately it went exactly on like this. The Acronis image restore failed at the very end -.- I was totally depressed :cry: . I decided to ask my trader if I can exchange Super*Talent FPM64GLSE by a model of a different brand. But promised to check out all support sites and forums before during the next week before I return it to my online shop.

Now it is your turn...
--------------------------

I could not find any compatibility lists until now...

Do you have an idea whether my EeePC 901 is simply incompatible to Super Talent FPM64GLSE?
Could a BIOS upgrade help?
Could a new Acronis True Image release help?
Do you recommend a different partitioning tool?

I will also post in Asus and Super*Talent forums...

Thanks and kind regards!

0 Users found this helpful

Meanwhile I received answers from Asus and Super*Talent forums...

But it seems usually people succeed in using this FPM64GLSE together with EeePC 901... but I don't really see this for me -.-

But what have I done since yesterday...
---------------------------------------------------

Don't ask -.- I tried following: I have searched for deleted partitions with Partition Manager 8.5. Like I already mentioned, you can find it, but 0 bytes were free. Good. So I tried to give it a boot try nevertheless: I simply tried to boot from the internal EeePC 4GB SSD (Windows OS partition), with FPM64GLSE as drive D partition. And it worked. But Windows Explorer showed a full drive D.

I could solve this problem with Windows chkdsk. It has found and repaired a lot of things. After that I have 30GB of space on drive D smile Fine.

Now I copied the internal EeePC 4GB SSD to the 1st primary partition of FPM64GLSE and made drive D (DATA partition) a logical partition. Then I set the internal EeePC 4GB SSD invisible and inactive. That prevents the boot warning of EeePC when I disable the whole SSD and you can simply boot from the new FPM64GLSE. It worked! And wow, it is fast!!! The only thing was that Star Office crashed on startup suddenly...

BUT: Ran chkdsk again... and now he fould lots of defect clusters -.- After he repaired them, many other applications besides Star Office also crashed... chkdsk seems to have destroyed some files - or at least tried to move them to valid working clusters and while doing this some data got lost.

Okay. All I tried afterwards was to reinstall Firefox and uninstall Star Office to install lastest OpenOffice with JRE. The installation took really, really long... but was successful.

Result...
-----------

I have a running system now on the FPM64GLSE!

My fears...
--------------

But I'm sure the problems will return if I ever want to restore an image again. Unfortunately I also expect further defect clusters coming up soon, though chkdsk has marked the already found defect clusters as defect and not to be used by the OS.

Ergo...
---------

But could it really be that I received 2 defect SSDs of same type in a row?

I'm gonna try the BIOS upgrade and will maybe invest in the new True Image release.

brgds

Hi all.

I gave up yesterday and sent it back to the online shop this morning...

Even after a BIOS upgrade it did not work and I got I/O and sector errors. Maybe it would have worked if I had done the BIOS upgrade before doing anything on the SSD. Maybe I will give a different model a try later on.

Further I saw that Super*Talent seems to only support using their SSDs as storage enhancement for EeePC's Windows Drive D... At least I did not find other documents regarding running an operating system on FPM64GLSE or related models.

BTW: I saw there is a special Netbook version of Acronis True Image 2010. But it only fixes a display problem ('moving' screen and no downscale of 1024x768 screen to 1024x600) with the normal version, it seems. Further with the new BIOS upgrade the display problem disappeared, despites.

Thanks for your support!