Join now - be part of our community!

SD card gets corrupted after Marshmallow update

SOLVED
Ashay
Visitor

SD card gets corrupted after Marshmallow update

Since Marshmallow (6.0) update on my Xperia M5 Dual SD card showing corrupted. but previously it was working fine on the lollipop.
after formatting the SD card in the safe mode, Phone detected the SD card.

but i cant copy paste anything into it.

when i use camera (data storage is set to SD card)  pics are not saving on SD card, it is showing "There is some problem with your data storage"

I checked the SD card it is working in all other phones.
Any solution Please ..

76 REPLIES 76
Sh84
Visitor

I m also suffering with the same problem i formatted 2-3 times each time i deleted some important files too but the problem is persist...every time i restart my mobile the notification appears.... And transferring data from mobile to sd card losses every time for large file like greater than 1 gb all data doesn't transfer and corrupted data
Georges98
Visitor

According to Xperia Check and Xperia firm new update is coming out for xperia M5 Dual E5643

(30.2.B.0.110) from (30.2.B.0.100) , maybe is a fix Grinning_Face 

chorno12
Visitor

most stupid phone ever.... now all my picture, music, video gone inside the sd card after restart phone.. going to throw outside my xperia M5, 

JoshJustDied
Visitor

Actually, i don't blame the phone. I'd just hope that the new OS Update would fix this since it's clearly the OS' fault or maybe some comaptibility issues with the OS and the Card function.

Sh84
Visitor

Don't need to format sd card after restarting the mobile wait for the massage and then remove sd card and put again do the same untill massage gone....
And wait for update may be fixed by it because m5 is good mobile only problem with the software
MBoti
Visitor

Bad news, I already have the update 30.2.B.0.110, and the issues with sd card was not solved. I'm thinking about to leave my mobile in a Sony service to be fixed.
DEAN23
Visitor

Don't bother, my man - I just spoke to customer services, and he spoke about these issue:

1) That the corruption of the sd card depends on the size of sd card, so I'm guessing 32gb and up, you'll have problems.

2) That there is a go-around, which is to create a partition on the card, whatever that means.

3) That there is an update upcoming for it, which will solve all problems involving this, however there is no known time when this will come....

Angry_Face

Thetheone
Visitor

Sh84 and DEAN23 thanks for the info you provided. After trying that, message is gone right but the card is still corrupted, I can copy files to the card but when system tries to read them some of them obviously gives corrupted error. 

I wonder why none of the Staff Members answer to this topic yet ? 
You may not have the solution yet I understand that, but informing us would be good ! .. 

DEAN23
Visitor

I think the only way to manage it is, depending on the size of the SD Card, get a usb of the same size.  If it's bigger than 32gb, convert it to fat32, using a PC (I would recommend getting the fat32 formatter from ridgecrop in regards to that), backup the sd onto usb, convert that to fat32 also, put everything on your usb, back onto your sd card, and put your sd card in your phone.

From here, you may get that Format message on your phone again, but try taking your SD Card out, and putting it in again.  If that doesn't change, then format it again. And then put your files back from your usb to your sd card again.  The beauty is that unlike the M4, the M5 allows for usb otg capabilities, so if your sd card runs funny in regards to files, use an otg cable with the usb, or if the usb has otg built in, use that, and then just copy the files over, replacing the corrupted files like that.

That's the only way to manage it, until the update fix is finally released.

blackdiamond
Visitor

Faced with the same issue after updating to Marshmallow. Part of data becomes unreadable. Tried to perform low level format, format by Xperia device, FAT32 and extFat but it doesn't help. After returning to Lollipop issue dissapeared.