• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help syslog mmcblk1 ERROR - is it time to get a new SD Card?

Jump to latest Follow Reply
Sort by date Sort by votes
moja4tatu

moja4tatu

Lurker
Jan 6, 2013
4
0
NJ
#1
I checked syslog to diagnose an unrelated problem, and found some messages that I find disturbing. I'm afraid that maybe my SD Card is going bad?

I saw this message in syslog:

01/04/2013 21:23:37 [ERROR] mmcblk1: error -110 transferring data, sector 254256, nr 8, card status 0x20090

In the syslog I exported, it appears 63 times over a 40 minute period.

Does this mean it's time to back up the card & replace it?

Here's the error in a little context:

01/04/2013 21:23:37 [INFORMATION] PM: Syncing filesystems ...
01/04/2013 21:23:37 [WARNING] mmcblk1: retrying using single block read
01/04/2013 21:23:37 [ERROR] mmcblk1: error -110 transferring data, sector 254256, nr 8, card status 0x20090
01/04/2013 21:23:37 [ERROR] end_request: I/O error, dev mmcblk1, sector 254256
01/04/2013 21:23:37 [WARNING] mmcblk1: retrying using single block read
01/04/2013 21:23:37 [ERROR] mmcblk1: error -110 transferring data, sector 254256, nr 8, card status 0x20090
01/04/2013 21:23:37 [ERROR] end_request: I/O error, dev mmcblk1, sector 254256
01/04/2013 21:23:37 [INFORMATION] Core dump to |/system/bin/coredump Thread-14 8522 1357352614 pipe failed
01/04/2013 21:23:37 [WARNING] done.


Here's a longer snippet. (If anyone wants to take a shot at explaining the "platform_pm_suspend returns -16" error I wouldn't mind that either!)

01/04/2013 21:23:32 [DEBUG] PM: Preparing system for mem slee
01/04/2013 21:23:32 [WARNING] Freezing user space processes ... (elapsed 0.06 seconds) done.
01/04/2013 21:23:33 [WARNING] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done
01/04/2013 21:23:33 [DEBUG] PM: Entering mem sleep
01/04/2013 21:23:33 [WARNING] Suspending console(s) (use no_console_suspend to debug)
01/04/2013 21:23:33 [ERROR] pm_op(): platform_pm_suspend+0x0/0x54 returns -16
01/04/2013 21:23:33 [ERROR] PM: Device alarm failed to suspend: error -16
01/04/2013 21:23:33 [ERROR] PM: Some devices failed to suspend
01/04/2013 21:23:33 [DEBUG] PM: Finishing wakeup.
01/04/2013 21:23:33 [WARNING] Restarting tasks ... done.
01/04/2013 21:23:33 [INFORMATION] suspend: exit suspend, ret = -16 (2013-01-05 02:23:29.761047343 UTC
01/04/2013 21:23:36 [WARNING] mmc0: Starting deferred resume
01/04/2013 21:23:36 [WARNING] mmc1: Starting deferred resume
01/04/2013 21:23:36 [WARNING] mmc0: Deferred resume complete
01/04/2013 21:23:36 [INFORMATION] mmc1 set to SECTOR mode
01/04/2013 21:23:36 [WARNING] mmc1: Deferred resume complete
01/04/2013 21:23:37 [INFORMATION] suspend: enter suspend
01/04/2013 21:23:37 [INFORMATION] PM: Syncing filesystems ...
01/04/2013 21:23:37 [WARNING] mmcblk1: retrying using single block read
01/04/2013 21:23:37 [ERROR] mmcblk1: error -110 transferring data, sector 254256, nr 8, card status 0x20090
01/04/2013 21:23:37 [ERROR] end_request: I/O error, dev mmcblk1, sector 254256
01/04/2013 21:23:37 [WARNING] mmcblk1: retrying using single block read
01/04/2013 21:23:37 [ERROR] mmcblk1: error -110 transferring data, sector 254256, nr 8, card status 0x20090
01/04/2013 21:23:37 [ERROR] end_request: I/O error, dev mmcblk1, sector 254256
01/04/2013 21:23:37 [INFORMATION] Core dump to |/system/bin/coredump Thread-14 8522 1357352614 pipe failed
01/04/2013 21:23:37 [WARNING] done.
01/04/2013 21:23:37 [DEBUG] PM: Preparing system for mem sleep
 
#2
moja4tatu said:
I checked syslog to diagnose an unrelated problem, and found some messages that I find disturbing. I'm afraid that maybe my SD Card is going bad?

I saw this message in syslog:

01/04/2013 21:23:37 [ERROR] mmcblk1: error -110 transferring data, sector 254256, nr 8, card status 0x20090

In the syslog I exported, it appears 63 times over a 40 minute period.

Does this mean it's time to back up the card & replace it?

Here's the error in a little context:

01/04/2013 21:23:37 [INFORMATION] PM: Syncing filesystems ...
01/04/2013 21:23:37 [WARNING] mmcblk1: retrying using single block read
01/04/2013 21:23:37 [ERROR] mmcblk1: error -110 transferring data, sector 254256, nr 8, card status 0x20090
01/04/2013 21:23:37 [ERROR] end_request: I/O error, dev mmcblk1, sector 254256
01/04/2013 21:23:37 [WARNING] mmcblk1: retrying using single block read
01/04/2013 21:23:37 [ERROR] mmcblk1: error -110 transferring data, sector 254256, nr 8, card status 0x20090
01/04/2013 21:23:37 [ERROR] end_request: I/O error, dev mmcblk1, sector 254256
01/04/2013 21:23:37 [INFORMATION] Core dump to |/system/bin/coredump Thread-14 8522 1357352614 pipe failed
01/04/2013 21:23:37 [WARNING] done.


Here's a longer snippet. (If anyone wants to take a shot at explaining the "platform_pm_suspend returns -16" error I wouldn't mind that either!)

01/04/2013 21:23:32 [DEBUG] PM: Preparing system for mem slee
01/04/2013 21:23:32 [WARNING] Freezing user space processes ... (elapsed 0.06 seconds) done.
01/04/2013 21:23:33 [WARNING] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done
01/04/2013 21:23:33 [DEBUG] PM: Entering mem sleep
01/04/2013 21:23:33 [WARNING] Suspending console(s) (use no_console_suspend to debug)
01/04/2013 21:23:33 [ERROR] pm_op(): platform_pm_suspend+0x0/0x54 returns -16
01/04/2013 21:23:33 [ERROR] PM: Device alarm failed to suspend: error -16
01/04/2013 21:23:33 [ERROR] PM: Some devices failed to suspend
01/04/2013 21:23:33 [DEBUG] PM: Finishing wakeup.
01/04/2013 21:23:33 [WARNING] Restarting tasks ... done.
01/04/2013 21:23:33 [INFORMATION] suspend: exit suspend, ret = -16 (2013-01-05 02:23:29.761047343 UTC
01/04/2013 21:23:36 [WARNING] mmc0: Starting deferred resume
01/04/2013 21:23:36 [WARNING] mmc1: Starting deferred resume
01/04/2013 21:23:36 [WARNING] mmc0: Deferred resume complete
01/04/2013 21:23:36 [INFORMATION] mmc1 set to SECTOR mode
01/04/2013 21:23:36 [WARNING] mmc1: Deferred resume complete
01/04/2013 21:23:37 [INFORMATION] suspend: enter suspend
01/04/2013 21:23:37 [INFORMATION] PM: Syncing filesystems ...
01/04/2013 21:23:37 [WARNING] mmcblk1: retrying using single block read
01/04/2013 21:23:37 [ERROR] mmcblk1: error -110 transferring data, sector 254256, nr 8, card status 0x20090
01/04/2013 21:23:37 [ERROR] end_request: I/O error, dev mmcblk1, sector 254256
01/04/2013 21:23:37 [WARNING] mmcblk1: retrying using single block read
01/04/2013 21:23:37 [ERROR] mmcblk1: error -110 transferring data, sector 254256, nr 8, card status 0x20090
01/04/2013 21:23:37 [ERROR] end_request: I/O error, dev mmcblk1, sector 254256
01/04/2013 21:23:37 [INFORMATION] Core dump to |/system/bin/coredump Thread-14 8522 1357352614 pipe failed
01/04/2013 21:23:37 [WARNING] done.
01/04/2013 21:23:37 [DEBUG] PM: Preparing system for mem sleep
Click to expand...


I would definitely backup the card and perhaps try another card to see if you have the same problem.
 
Upvote 0
You must log in or register to reply here.

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones

Best Android Phones

See All
  1. Google Pixel 8 Pro Check Price
  2. Samsung Galaxy S23 Ultra Check Price
  3. Samsung Galaxy Z Fold5 Check Price
  4. Google Pixel 8 Check Price
  5. Samsung Galaxy S23 Check Price

Upcoming

See All
  1. Samsung Galaxy S24 Early Access

Best iPhones

See All
  1. Apple iPhone 15 Pro Max Check Price
  2. Apple iPhone 15 Pro Check Price
  3. Apple iPhone 15 Plus Check Price
  4. Apple iPhone 15 Check Price
  5. Apple iPhone SE (2022) Check Price

Upcoming

See All
  1. Apple iPhone 16 Early Access

Tablets

Best Tablets

See All
  1. Samsung Galaxy Tab S9 Ultra Check Price
  2. Apple iPad Pro (2022) Check Price
  3. Apple iPad Air (2022) Check Price
  4. Apple iPad Mini (2021) Check Price
  5. Microsoft Surface Pro 9 Check Price

Upcoming

See All
  1. Apple iPad Air 6 Early Access
  2. Apple iPad Fold Early Access

Laptops

Best Laptops

See All
  1. Apple Macbook Pro Check Price
  2. Apple Macbook Air (2023) Check Price
  3. Dell XPS 13 Check Price
  4. Acer Chromebook Spin 714 Check Price
  5. Dell Alienware m18 (2022) Check Price

Upcoming

See All
  1. Microsoft Surface Laptop 6 Early Access
  2. Microsoft Surface Pro 10 Early Access

Televisions

Best TVs

See All
  1. Samsung The Frame TV Check Price
  2. Samsung Neo QLED 4K QN90C Check Price
  3. LG G3 OLED Check Price
  4. LG A2 OLED Check Price
  5. ROKU Plus Series Check Price
  6. Samsung S90C OLED Check Price
  7. SunBriteTV Veranda 3 Check Price

Upcoming

See All
  1. Hisense 110UX ULED X TV Early Access

Game Consoles

Best Game Consoles

See All
  1. Nintendo Switch OLED Check Price
  2. Microsoft XBOX Series X Check Price
  3. Sony Playstation 5 Check Price
  4. Microsoft XBOX Series S Check Price
  5. Nintendo Switch Lite Check Price

Upcoming

See All
  1. Nintendo Switch 2 Early Access

Wearables

Best Wearables

See All
  1. Oura Ring 3 Check Price
  2. Apple Watch Series 9 Check Price
  3. Google Pixel Watch 2 Check Price
  4. Samsung Galaxy Watch 6 Classic Check Price
  5. Fitbit Inspire 3 Check Price
  6. Amazfit Amazfit Band 7 Check Price
  7. Apple Watch SE Check Price
  8. Apple Watch Ultra 2 Check Price

Upcoming

See All
  1. Samsung Galaxy Watch 7 Early Access

Smart Home

Smart Home Tech

See All
  1. Amazon Echo (4th Gen) Check Price
  2. Schlage Encode Smart Lock Check Price
  3. Amazon Blink Smart Cameras Check Price
  4. Google Nest Thermostat Check Price
  5. Phillips Hue Smart Lights Check Price

Upcoming

See All
  1. Apple Homepod Vision Early Access

Similar threads

B
Root [DEV] Triumph Kernel Thread (01/19/2013)
Replies
13
Views
3K
Smartphones
BSydz
B
R
NEVER utilize Motorola support for repairs- A horror story
Replies
4
Views
2K
Smartphones
SayOw
SayOw
A
Help HELP Samsung s6500D wifi driver problem or my phone is broke
Replies
3
Views
17K
Smartphones
angel2004
A
M
Possible Relief for Several A500 ICS Related Symptoms/Problems
Replies
43
Views
42K
Smartphones
Pimpernel
P
scotty85
Root [GSM] [guide]how to downgrade hboot 1.49.xxxx
Replies
9
Views
10K
Smartphones
jinextomy
J
Top Bottom
Back
Jump to latest Follow Reply
Jump to latest Follow Reply