BBG stopped reponding

Embedded Linux Discussions
1

Hi,

I have been using bbg running ubuntu 20.04, which is build using Rootfs builder. Recently I upgraded the filesystem. It is running over a few weeks and one day bbg stopped responding and observed the below error:

61145.707069] sdhci-omap 48060000.mmc: error -110 requesting status
33 [61145.707101] mmcblk0: recovery failed!
34 [61145.707182] blk_update_request: I/O error, dev mmcblk0, sector 3994280 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
35 [61145.715788] sdhci-omap 48060000.mmc: error -110 requesting status
36 [61145.715814] mmcblk0: recovery failed!
37 [61145.715870] blk_update_request: I/O error, dev mmcblk0, sector 3994280 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
38
39 [61156.068870] sdhci-omap 48060000.mmc: error -110 requesting status
40 [61156.068904] mmcblk0: recovery failed!
41 [61156.068969] blk_update_request: I/O error, dev mmcblk0, sector 3988120 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
42 [61156.079623] sdhci-omap 48060000.mmc: error -110 requesting status
43 [61156.079650] mmcblk0: recovery failed!
44 [61156.079711] blk_update_request: I/O error, dev mmcblk0, sector 3988128 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
45 [61156.087233] sdhci-omap 48060000.mmc: error -110 requesting status
46 [61156.087261] mmcblk0: recovery failed!
47 [61156.087323] blk_update_request: I/O error, dev mmcblk0, sector 3988128 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
48 [61156.318440] sdhci-omap 48060000.mmc: error -110 requesting status
49 [61156.318474] mmcblk0: recovery failed!
50 [61156.318531] blk_update_request: I/O error, dev mmcblk0, sector 3988128 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
51 [61156.334024] sdhci-omap 48060000.mmc: error -110 requesting status
52 [61156.334048] mmcblk0: recovery failed!
53 [61156.334105] blk_update_request: I/O error, dev mmcblk0, sector 3988128 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
54 [61156.568700] sdhci-omap 48060000.mmc: error -110 requesting status
55 [61156.568733] mmcblk0: recovery failed!
56 [61156.568794] blk_update_request: I/O error, dev mmcblk0, sector 3988128 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
57 [61156.579724] sdhci-omap 48060000.mmc: error -110 requesting status
58 [61156.579749] mmcblk0: recovery failed!
59 [61156.579808] blk_update_request: I/O error, dev mmcblk0, sector 3988128 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
60 [61156.610426] sdhci-omap 48060000.mmc: error -110 requesting status
61 [61156.610453] mmcblk0: recovery failed!
62 [61156.610532] blk_update_request: I/O error, dev mmcblk0, sector 904240 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
63 [61156.618277] sdhci-omap 48060000.mmc: error -110 requesting status
64 [61156.618307] mmcblk0: recovery failed!
65 [61156.618382] blk_update_request: I/O error, dev mmcblk0, sector 904240 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
66 [61156.627142] sdhci-omap 48060000.mmc: error -110 requesting status
67 [61156.627174] mmcblk0: recovery failed!
68 [61156.627237] blk_update_request: I/O error, dev mmcblk0, sector 904240 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
69 [61156.635709] sdhci-omap 48060000.mmc: error -110 requesting status
70 [61156.635743] mmcblk0: recovery failed!
71 [61156.643865] sdhci-omap 48060000.mmc: error -110 requesting status
72 [61156.643895] mmcblk0: recovery failed!
73 [61156.651731] sdhci-omap 48060000.mmc: error -110 requesting status
74 [61156.651761] mmcblk0: recovery failed!
75 [61156.659566] sdhci-omap 48060000.mmc: error -110 requesting status
76 [61156.659591] mmcblk0: recovery failed!
77 [61156.694069] sdhci-omap 48060000.mmc: error -110 requesting status
78 [61156.694095] mmcblk0: recovery failed!
79 [61156.702659] sdhci-omap 48060000.mmc: error -110 requesting status
80 [61156.702686] mmcblk0: recovery failed!
81 [61156.711343] sdhci-omap 48060000.mmc: error -110 requesting status
82 [61156.711375] mmcblk0: recovery failed!
83 [61156.719933] sdhci-omap 48060000.mmc: error -110 requesting status
84 [61156.719965] mmcblk0: recovery failed!
85 [61156.728193] sdhci-omap 48060000.mmc: error -110 requesting status
86 [61156.728226] mmcblk0: recovery failed!
87 [61156.736179] sdhci-omap 48060000.mmc: error -110 requesting status
88 [61156.736208] mmcblk0: recovery failed!
89 [61156.744037] sdhci-omap 48060000.mmc: error -110 requesting status
90 [61156.744067] mmcblk0: recovery failed!
91 [61156.752237] sdhci-omap 48060000.mmc: error -110 requesting status
92 [61156.752270] mmcblk0: recovery failed!
93 [61156.760234] sdhci-omap 48060000.mmc: error -110 requesting status
94 [61156.760263] mmcblk0: recovery failed!
95 [61156.769281] sdhci-omap 48060000.mmc: error -110 requesting status
96 [61156.769311] mmcblk0: recovery failed!
97 [61156.777328] sdhci-omap 48060000.mmc: error -110 requesting status
98 [61156.777361] mmcblk0: recovery failed!
99 [61156.785294] sdhci-omap 48060000.mmc: error -110 requesting status
100 [61156.785322] mmcblk0: recovery failed!
101 [61156.793188] sdhci-omap 48060000.mmc: error -110 requesting status
102 [61156.793220] mmcblk0: recovery failed!
103 [61156.826662] sdhci-omap 48060000.mmc: error -110 requesting status
104 [61156.826694] mmcblk0: recovery failed!
105 [61156.826989] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1534: inode #3710: comm accounts-daemon: reading directory lblock 0
106 [61156.835070] sdhci-omap 48060000.mmc: error -110 requesting status
107 [61156.835102] mmcblk0: recovery failed!
108 [61156.835178] Buffer I/O error on dev mmcblk0p1, logical block 0, lost sync page write
109 [61156.835280] EXT4-fs (mmcblk0p1): I/O error while writing superblock
110 [61156.897379] sdhci-omap 48060000.mmc: error -110 requesting status
111 [61156.897412] mmcblk0: recovery failed!
112 [61156.922206] sdhci-omap 48060000.mmc: error -110 requesting status
113 [61156.922241] mmcblk0: recovery failed!
114 [61157.014437] sdhci-omap 48060000.mmc: error -110 requesting status
115 [61157.014464] mmcblk0: recovery failed!
116 [61157.022311] sdhci-omap 48060000.mmc: error -110 requesting status
117 [61157.022340] mmcblk0: recovery failed!
118 [61157.292706] sdhci-omap 48060000.mmc: error -110 requesting status
119 [61157.292734] mmcblk0: recovery failed!
120 [61157.303856] sdhci-omap 48060000.mmc: error -110 requesting status
121 [61157.303882] mmcblk0: recovery failed!
122 [61157.533046] sdhci-omap 48060000.mmc: error -110 requesting status
123 [61157.533081] mmcblk0: recovery failed!
124 [61157.541572] sdhci-omap 48060000.mmc: error -110 requesting status
125 [61157.541604] mmcblk0: recovery failed!
126 [61157.549886] sdhci-omap 48060000.mmc: error -110 requesting status
127 [61157.549917] mmcblk0: recovery failed!
128 [61157.557742] sdhci-omap 48060000.mmc: error -110 requesting status
129 [61157.557771] mmcblk0: recovery failed!
130 [61157.565546] sdhci-omap 48060000.mmc: error -110 requesting status
131 [61157.565574] mmcblk0: recovery failed!
132 [61157.573814] sdhci-omap 48060000.mmc: error -110 requesting status
133 [61157.573842] mmcblk0: recovery failed!
134 [61157.581709] sdhci-omap 48060000.mmc: error -110 requesting status
135 [61157.581735] mmcblk0: recovery failed!
136 [61157.589787] sdhci-omap 48060000.mmc: error -110 requesting status
137 [61157.589821] mmcblk0: recovery failed!
138 [61157.597875] sdhci-omap 48060000.mmc: error -110 requesting status
139 [61157.597902] mmcblk0: recovery failed!
140 [61157.605968] sdhci-omap 48060000.mmc: error -110 requesting status
141 [61157.605996] mmcblk0: recovery failed!
142 [61157.614010] sdhci-omap 48060000.mmc: error -110 requesting status
143 [61157.614037] mmcblk0: recovery failed!
144 [61157.622097] sdhci-omap 48060000.mmc: error -110 requesting status
145 [61157.622125] mmcblk0: recovery failed!
146 [61157.630873] sdhci-omap 48060000.mmc: error -110 requesting status
147 [61157.630898] mmcblk0: recovery failed!
148 [61157.638783] sdhci-omap 48060000.mmc: error -110 requesting status
149 [61157.638807] mmcblk0: recovery failed!
150 [61157.646913] sdhci-omap 48060000.mmc: error -110 requesting status
151 [61157.646938] mmcblk0: recovery failed!
152 [61157.654780] sdhci-omap 48060000.mmc: error -110 requesting status
153 [61157.654808] mmcblk0: recovery failed!
154 [61157.663115] sdhci-omap 48060000.mmc: error -110 requesting status
155 [61157.663144] mmcblk0: recovery failed!
156 [61157.670927] sdhci-omap 48060000.mmc: error -110 requesting status
157 [61157.670952] mmcblk0: recovery failed!
158 [61157.678838] sdhci-omap 48060000.mmc: error -110 requesting status
159 [61157.678863] mmcblk0: recovery failed!
160 [61157.686914] sdhci-omap 48060000.mmc: error -110 requesting status
161 [61157.686941] mmcblk0: recovery failed!
162 [61157.687075] EXT4-fs error (device mmcblk0p1): __ext4_find_entry:1534: inode #3710: comm accounts-daemon: reading directory lblock 0
163 [61157.694336] sdhci-omap 48060000.mmc: error -110 requesting status
164 [61157.694362] mmcblk0: recovery failed!
165 [61157.694434] Buffer I/O error on dev mmcblk0p1, logical block 0, lost sync page write
166 [61157.694524] EXT4-fs (mmcblk0p1): I/O error while writing superblock
167

I have been debugging this issue for a long time. It happened once and could not reproduce.

Please provide your suggestions/ thoughts.

Thanks

2

Your microSD or eMMC on the BBG has now worn out and is dead…

Regards,

3

Thanks Robert for your prompt reply.

I did reboot the BBG and then it seems working well. So far i have not observed this issue again,

Please suggest fix or detection methods to resolve this issue.

4

Pull important data off of it, and start prepping to use a new microSD, i wouldn’t trust it.

Regards,

5

Okay, Sure. Appreciate your suggestions.
Meanwhile, I started exploring the images that can be flashed to internal memory eMMC. The current filesystem I built using rootfs image builder for ubuntu 20.04. Do we have any method that can convert this filesystem to eMMC format that allows us to use internal memory? or Can I have process for building image which can be flashed to eMMC?

6

The scrpts are built-into your image:

Install flashing scripts:

sudo apt-get update
sudo apt-get install bb-beagle-flasher

Configure microSD → eMMC mode:

sudo cp -v /etc/beagle-flasher/beaglebone-black-microsd-to-emmc /etc/default/beagle-flasher

Then, start flasher, will start copying microSD to eMMC…

sudo beagle-flasher

Regards,

7

Thank you for your prompt response. will try the same.

Thanks

8

Is there a application like raspberry pi sd card speed test for BBG

9

Both devices run Linux. Same tool should work on both.

Regards,