Close

What are you looking for?

cancel
Showing results for 
Search instead for 
Did you mean: 

Original topic:

An SD card was removed unsafely. To prevent your phone from restarting... notification

(Topic created on: 28/02/21 12:19)
utopic
Explorer
Options
Galaxy S10 Series

Ever since the big update to Android 11 / One UI 3 I've been getting the

"An SD card was removed unsafely. To prevent your phone from restarting unexpectedly, save unsaved data and restart your phone"

notification, many times a day.

 

After the update and prior to having this error, I have not messed with the card or the SIM, connected the phone to the PC, dropped the phone or done anything that might lead to this - the card had been inserted months ago in the phone and left untouched.

 

I don't seem to have any issues using the phone, can access the card OK for both reading & writing. 

I can't turn the bloody notification off and it's driving me up the wall as I'm getting it even during the night.

 

Have tried:

  • restarting the phone
  • unmounting the card and restarting the phone
  • physically removing and card from the phone and putting it back
  • removing the card and error checking it (in windows, using a card reader)
  • copying the card contents to the PC, formatting the card in the phone, then copying the contents back (via the windows file explorer)
  • getting into the recovery mode (which was pain the *ss) and wiping the dalvik cache
  • full/factory reset

The model # is SM-G970F/DS, kernel version is 4.14.113-20607146, latest available updates are installed, phone is stock, non rooted, non carrier locked.

Any suggestions?

160 REPLIES 160
sarasphotobox
Voyager
Options
Galaxy S10 Series
maybe is the SD card corrupted ? usually when a SD card has unknown errors it could relate to corrupted SD card. I would suggest backup SD card data onto laptop if u have then format SD card either on your laptop
Pugs1957
Superuser I
Superuser I
Options
Galaxy S10 Series
Did you clear the system cache after the update?
0 Likes
utopic
Explorer
Options
Galaxy S10 Series

Thank you both for your suggestions.

> format SD card either on your laptop

I've done that, in the phone, and there was no change.

> Did you clear the system cache after the update? 

I did not, but I think I did restart after the update process. I would have expected the cache to be cleared as part of the update, without manual steps on my part.

Out of desperation, I went ahead and fully reset my phone, re configured everything from scratch to avoid any possible issues due to maybe restoring a corrupted backup.

I'm still getting the "sd card was removed..." message, so the full reset didn't fix anything.

 

GeekGirl
First Poster
Options
Galaxy S10 Series

I'm having the same issue with S20 FE, started after Android 11 update.  I did most of the same steps you did, without the factory reset.  Error persists.  Did you try contacting Samsung?

0 Likes
utopic
Explorer
Options
Galaxy S10 Series

Hi, I did not manage to find time for that too.

 

If you do manage to find a solution outside the forums, please, also post here.

0 Likes
GeekGirl
First Poster
Options
Galaxy S10 Series

Samsung suggested a new Memory Card.  I purchased a Class 10, UHS Speed Class 3, Video speed V30 card and I am no longer getting the error.  Maybe my other card was too slow?  Anyway it's fixed. 😊

scuthber
Apprentice
Options
Galaxy S10 Series

I have the same issue after the last update. This has happened before though on a different Samsung and a different card. It seems that updates can mess up the card. I am going to copy everything off, format and copy back on, but it's really annoying. 

I am planning on unmounting/removing the SD card before the next update!

0 Likes
utopic
Explorer
Options
Galaxy S10 Series

Your steps did not work for me - I also copied files, formatted the card from within the phone, and copied back - and the issue persisted.

scuthber
Apprentice
Options
Galaxy S10 Series

Time will tell... Annoyed that it worked fine for a year and only failed after the last update. There were two updates, in fact, one about a week or so after the other. Problem started after the first update.

0 Likes