android 10 长时间卡在logo界面 挂载分区时报如下错误，循环很长(2分钟甚至更长时间)

于 2024-04-15 22:20:56 发布
阅读量470 收藏 4
点赞数 5
文章标签： android 开发语言
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/m0_59162559/article/details/137797908
版权 
......
[    5.121452] selinux: SELinux: Loaded file_contexts
[    5.121452] 
[    5.128739] ueventd: Parsing file /ueventd.rc...
[    5.135133] ueventd: Parsing file /vendor/ueventd.rc...
[    5.141832] ueventd: Parsing file /odm/ueventd.rc...
[    5.147466] ueventd: Unable to read config file '/odm/ueventd.rc': open() failed: No such file or directory
[    5.158466] ueventd: Parsing file /ueventd.sun50iw10p1.rc...
[    5.164867] ueventd: Unable to read config file '/ueventd.sun50iw10p1.rc': open() failed: No such file or directory
[    5.420707] ueventd: Coldboot took 0.242 seconds
[    5.540699] Registered swp emulation handler
[    5.594330] init: wait for '/dev/block/by-name/media_data' took 0ms
[    5.604273] FAT-fs (mmcblk0p16): bogus number of reserved sectors
[    5.611180] FAT-fs (mmcblk0p16): Can't find a valid FAT filesystem
[    5.662106] logd.auditd: start
[    5.673529] fsck.f2fs: Info: Fix the reported corruption.
[    5.673529] 
[    5.681445] fsck.f2fs:   Info: No support kernel version!
[    5.681445] 
[    5.689144] fsck.f2fs: Info: Segments per section = 1
[    5.689144] 
[    5.696531] fsck.f2fs: Info: Sections per zone = 1
[    5.696531] 
[    5.703640] fsck.f2fs: Info: sector size = 512
[    5.703640] 
[    5.710390] fsck.f2fs: Info: total sectors = 53305791 (26028 MB)
[    5.710390] 
[    5.718853] fsck.f2fs: Info: MKFS version
[    5.718853] 
[    5.725065] fsck.f2fs:   "4.9.170 #6 SMP PREEMPT Mon Jan 22 11:42:44 CST 2024"
[    5.725065] 
[    5.734877] fsck.f2fs: Info: FSCK version
[    5.734877] 
[    5.741045] fsck.f2fs:   from "4.9.170 #6 SMP PREEMPT Mon Jan 22 11:42:44 CST 2024"
[    5.741045] 
[    5.876054] F2FS-fs (mmcblk0p17): recover_inode: ino = ae1, name = <encrypted>, inline = 1
[    5.886176] F2FS-fs (mmcblk0p17): recover_dentry: ino = ae1, name = <encrypted>, dir = 60, err = 0
[    5.896291] F2FS-fs (mmcblk0p17): recover_data: ino = ae1 (i_size: recover) recovered = 4, err = 0
[    5.906337] F2FS-fs (mmcblk0p17): recover_inode: ino = ae2, name = <encrypted>, inline = 1
[    5.916012] F2FS-fs (mmcblk0p17): recover_dentry: ino = ae2, name = <encrypted>, dir = 60, err = 0
[    5.926139] F2FS-fs (mmcblk0p17): recover_data: ino = ae2 (i_size: recover) recovered = 12, err = 0
[    5.936284] F2FS-fs (mmcblk0p17): recover_inode: ino = ae3, name = <encrypted>, inline = 1
[    5.946175] F2FS-fs (mmcblk0p17): recover_dentry: ino = ae3, name = <encrypted>, dir = c6, err = 0
[    5.956251] F2FS-fs (mmcblk0p17): recover_data: ino = ae3 (i_size: recover) recovered = 1, err = 0
[    5.966297] F2FS-fs (mmcblk0p17): recover_inode: ino = ae4, name = <encrypted>, inline = 1
[    5.976618] F2FS-fs (mmcblk0p17): recover_dentry: ino = ae4, name = <encrypted>, dir = 526, err = 0
[    5.986802] F2FS-fs (mmcblk0p17): recover_data: ino = ae4 (i_size: recover) recovered = 1, err = 0
[    5.996850] F2FS-fs (mmcblk0p17): recover_inode: ino = ae5, name = <encrypted>, inline = 1
[    6.006474] F2FS-fs (mmcblk0p17): recover_dentry: ino = ae5, name = <encrypted>, dir = 526, err = 0
[    6.016645] F2FS-fs (mmcblk0p17): recover_data: ino = ae5 (i_size: recover) recovered = 1, err = 0
[    6.026692] F2FS-fs (mmcblk0p17): recover_inode: ino = ae6, name = <encrypted>, inline = 1
[    6.036920] F2FS-fs (mmcblk0p17): recover_dentry: ino = ae6, name = <encrypted>, dir = 27d, err = 0
[    6.047383] F2FS-fs (mmcblk0p17): recover_data: ino = ae6 (i_size: recover) recovered = 1, err = 0
[    6.057440] F2FS-fs (mmcblk0p17): recover_inode: ino = ae7, name = <encrypted>, inline = 1
[    6.067328] F2FS-fs (mmcblk0p17): recover_dentry: ino = ae7, name = <encrypted>, dir = 27e, err = 0
[    6.077506] F2FS-fs (mmcblk0p17): recover_data: ino = ae7 (i_size: recover) recovered = 1, err = 0
[    6.087556] F2FS-fs (mmcblk0p17): recover_inode: ino = ae8, name = <encrypted>, inline = 1
[    6.097489] F2FS-fs (mmcblk0p17): recover_dentry: ino = ae8, name = <encrypted>, dir = 27f, err = 0
[    6.107675] F2FS-fs (mmcblk0p17): recover_data: ino = ae8 (i_size: recover) recovered = 1, err = 0
[    6.117723] F2FS-fs (mmcblk0p17): recover_inode: ino = ae9, name = <encrypted>, inline = 1
[    6.127701] F2FS-fs (mmcblk0p17): recover_dentry: ino = ae9, name = <encrypted>, dir = 280, err = 0
[    6.137878] F2FS-fs (mmcblk0p17): recover_data: ino = ae9 (i_size: recover) recovered = 1, err = 0
[    6.147927] F2FS-fs (mmcblk0p17): recover_inode: ino = aea, name = <encrypted>, inline = 1
[    6.157909] F2FS-fs (mmcblk0p17): recover_dentry: ino = aea, name = <encrypted>, dir = 81, err = 0
[    6.168017] F2FS-fs (mmcblk0p17): recover_data: ino = aea (i_size: recover) recovered = 7, err = 0
[    6.178064] F2FS-fs (mmcblk0p17): recover_inode: ino = aeb, name = <encrypted>, inline = 1
[    6.187687] F2FS-fs (mmcblk0p17): recover_dentry: ino = aeb, name = <encrypted>, dir = 60, err = 0
[    6.197766] F2FS-fs (mmcblk0p17): recover_data: ino = aeb (i_size: recover) recovered = 1, err = 0
[    6.207813] F2FS-fs (mmcblk0p17): recover_inode: ino = aec, name = <encrypted>, inline = 1
[    6.217835] F2FS-fs (mmcblk0p17): recover_dentry: ino = aec, name = <encrypted>, dir = 52a, err = 0
[    6.228016] F2FS-fs (mmcblk0p17): recover_data: ino = aec (i_size: recover) recovered = 1, err = 0
[    6.238071] F2FS-fs (mmcblk0p17): recover_inode: ino = aed, name = <encrypted>, inline = 1
[    6.247349] F2FS-fs (mmcblk0p17): recover_dentry: ino = aed, name = <encrypted>, dir = 60, err = 0
[    6.257700] F2FS-fs (mmcblk0p17): recover_data: ino = aed (i_size: recover) recovered = 4, err = 0
[    6.267753] F2FS-fs (mmcblk0p17): recover_inode: ino = aee, name = <encrypted>, inline = 1
[    6.277117] F2FS-fs (mmcblk0p17): recover_dentry: ino = aee, name = <encrypted>, dir = 60, err = 0
[    6.287286] F2FS-fs (mmcblk0p17): recover_data: ino = aee (i_size: recover) recovered = 12, err = 0
[    6.297455] F2FS-fs (mmcblk0p17): recover_inode: ino = aef, name = <encrypted>, inline = 1
[    6.306752] F2FS-fs (mmcblk0p17): recover_dentry: ino = aef, name = <encrypted>, dir = c6, err = 0
[    6.316839] F2FS-fs (mmcblk0p17): recover_data: ino = aef (i_size: recover) recovered = 1, err = 0
[    6.326886] F2FS-fs (mmcblk0p17): recover_inode: ino = af0, name = <encrypted>, inline = 1
[    6.337104] F2FS-fs (mmcblk0p17): recover_dentry: ino = af0, name = <encrypted>, dir = c7, err = 0
[    6.347198] F2FS-fs (mmcblk0p17): recover_data: ino = af0 (i_size: recover) recovered = 4, err = 0
[    6.357247] F2FS-fs (mmcblk0p17): recover_inode: ino = af1, name = <encrypted>, inline = 1
[    6.366937] F2FS-fs (mmcblk0p17): recover_dentry: ino = af1, name = <encrypted>, dir = 5a3, err = 0
[    6.377127] F2FS-fs (mmcblk0p17): recover_data: ino = af1 (i_size: recover) recovered = 4, err = 0
[    6.387175] F2FS-fs (mmcblk0p17): recover_inode: ino = af1, name = <encrypted>, inline = 1
[    6.396479] F2FS-fs (mmcblk0p17): recover_data: ino = af1 (i_size: recover) recovered = 4, err = 0
[    6.406528] F2FS-fs (mmcblk0p17): recover_inode: ino = af1, name = <encrypted>, inline = 1
[    6.415832] F2FS-fs (mmcblk0p17): recover_data: ino = af1 (i_size: recover) recovered = 4, err = 0
[    6.425872] F2FS-fs (mmcblk0p17): recover_inode: ino = af1, name = <encrypted>, inline = 1
[    6.435167] F2FS-fs (mmcblk0p17): recover_data: ino = af1 (i_size: recover) recovered = 4, err = 0
[    6.445206] F2FS-fs (mmcblk0p17): recover_inode: ino = af1, name = <encrypted>, inline = 1
[    6.454507] F2FS-fs (mmcblk0p17): recover_data: ino = af1 (i_size: recover) recovered = 4, err = 0
[    6.464549] F2FS-fs (mmcblk0p17): recover_inode: ino = af1, name = <encrypted>, inline = 1


...........


[  377.351559] F2FS-fs (mmcblk0p17): recover_inode: ino = 35af, name = <encrypted>, inline = 1
[  377.360901] F2FS-fs (mmcblk0p17): recover_dentry: ino = 35af, name = <encrypted>, dir = 7a4, err = 0
[  377.371136] F2FS-fs (mmcblk0p17): recover_data: ino = 35af (i_size: recover) recovered = 1, err = 0
[  377.381245] F2FS-fs (mmcblk0p17): recover_inode: ino = 35b0, name = <encrypted>, inline = 1
[  377.390588] F2FS-fs (mmcblk0p17): recover_dentry: ino = 35b0, name = <encrypted>, dir = 7a4, err = 0
[  377.400824] F2FS-fs (mmcblk0p17): recover_data: ino = 35b0 (i_size: recover) recovered = 1, err = 0
[  377.410934] F2FS-fs (mmcblk0p17): recover_inode: ino = 35b1, name = <encrypted>, inline = 1
[  377.420276] F2FS-fs (mmcblk0p17): recover_dentry: ino = 35b1, name = <encrypted>, dir = 7a4, err = 0
[  377.430513] F2FS-fs (mmcblk0p17): recover_data: ino = 35b1 (i_size: recover) recovered = 1, err = 0
[  377.440625] F2FS-fs (mmcblk0p17): recover_inode: ino = 35b2, name = <encrypted>, inline = 1
[  377.449967] F2FS-fs (mmcblk0p17): recover_dentry: ino = 35b2, name = <encrypted>, dir = 7a4, err = 0
[  377.460200] F2FS-fs (mmcblk0p17): recover_data: ino = 35b2 (i_size: recover) recovered = 1, err = 0

从日志上看起来像是emmc物料有问题；

设备不带电池,预装客户客制应用，然后长时间老化测试突然断电再上电;

但是多次测试后发现是由于内置了客户的应用引起的这种现象,从日志上客户应用似乎又没有做什么特殊操作；
1）正常关机重启是不回出现这种现象的;
2）结束客户应用进程后断电重启似乎也没有问题;

分析原因可能本身物料是有些瑕疵，然后客户应用也有可能中间占用了磁盘读写操作引起;

那么就主动同步磁盘数据

Index: SystemUIApplication.java
===================================================================
--- SystemUIApplication.java    (revision 38790)
+++ SystemUIApplication.java    (revision 38791)
@@ -59,7 +59,7 @@
 // AW:Added for BOOTEVENT
 import java.io.FileOutputStream;
 import java.io.FileNotFoundException;
-import java.io.IOException;
+import java.io.File;
 
 /* Add for disconnect Wi-Fi disconnect after screen off */
 import android.app.AlarmManager;
@@ -109,6 +109,7 @@
 import com.android.systemui.statusbar.CommandQueue;
 import android.os.BatteryManager;
 import android.os.SystemProperties;
+import android.os.SystemClock;



 +private int timeCount=0;


@@ -393,6 +394,7 @@
         bootToostFilter.addAction(Intent.ACTION_BATTERY_CHANGED);
         bootToostFilter.addAction(ACTION_DEVICE_IDLE);
         bootToostFilter.addAction(WifiManager.NETWORK_STATE_CHANGED_ACTION);
+        bootToostFilter.addAction(Intent.ACTION_TIME_TICK);
 
         registerReceiver(new BroadcastReceiver() {
             @Override
@@ -505,6 +507,20 @@
                     } else {
                         mBatteryPlugged = false;
                     }
+                } else if (Intent.ACTION_TIME_TICK.equals(intent.getAction())) {
+                   timeCount++;
+                    if (timeCount > 20) {//20分钟同步一次，测试时间老化半小时以上才会出现上述问题
+                            fileSync();
+                            timeCount=0;
+                    }
                 }
             }
         }, bootToostFilter);
@@ -549,11 +565,45 @@
                Settings.System.putInt(context.getContentResolver(), "check_battery", mHasBattery?1:0); 
             }
         },new IntentFilter(Intent.ACTION_BATTERY_CHANGED));
-   mHasBattery = (hasBattery(batteryBroadcast)||sysCheckBattery());
+          mHasBattery = (hasBattery(batteryBroadcast)||sysCheckBattery());
         Settings.System.putInt(getContentResolver(), "check_battery", mHasBattery?1:0); 
     }
 
+    // add start
+    private static void fileSync() {
+        Runtime runtime = Runtime.getRuntime();
+        try {
+            runtime.exec("sync");
+            android.util.Log.e(TAG, "fileSync");
+        } catch (IOException e) {
+            e.printStackTrace();
+            android.util.Log.e(TAG, "fileSync IOException");
+        }
+    }
+    // add end*/
 

     boolean hasBattery(Intent batteryBroadcast){
         if(batteryBroadcast==null){
             Log.d(TAG, "hasBattery intent=null");

最后

如果想要成为架构师或想突破20~30K薪资范畴，那就不要局限在编码，业务，要会选型、扩展，提升编程思维。此外，良好的职业规划也很重要，学习的习惯很重要，但是最重要的还是要能持之以恒，任何不能坚持落实的计划都是空谈。

如果你没有方向，这里给大家分享一套由阿里高级架构师编写的《Android八大模块进阶笔记》，帮大家将杂乱、零散、碎片化的知识进行体系化的整理，让大家系统而高效地掌握Android开发的各个知识点。
img
相对于我们平时看的碎片化内容，这份笔记的知识点更系统化，更容易理解和记忆，是严格按照知识体系编排的。

欢迎大家一键三连支持，若需要文中资料，直接扫描文末CSDN官方认证微信卡片免费领取↓↓↓（文末还有ChatGPT机器人小福利哦，大家千万不要错过）

PS:群里还设有ChatGPT机器人，可以解答大家在工作上或者是技术上的问题
图片

大鱼Ss
关注
  • 5
    点赞
  • 踩
  • 4
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
【Linux】SD卡调试
vickytong1018的博客
02-09 2539
1）hotplugEventsocket = socket(PF_NETLINK, SOCK_DGRAM, NETLINK_KOBJECT_UEVENT);socket 返回Protocol not supported，跟踪libc库中的文件socketcalls.c，socket的系统调用：int socket(int family, int type, int protocol){     u...
linux sd卡格式化
cao711707的博客
11-23 3166
验证sd卡性能时，用脚本向sd中不停写入数据 验证方法一 不断的向sd卡中拷贝340M的文本文件，直到sd卡空间占满，再全部删除sd卡内容，重复此操作。 1)     单纯进行sd卡的读写操作时，擦除10次TF读写依然正常 2)     擦写sd卡加上不断重启设备，擦除1-2次之后，sd卡就变成只读，此时umount也执行失败，插拔sd卡也不能恢复，mount -o remount r
RK3288 android 7.1 EMMC 问题导致卡死在开机logo 界面
qq_35003588的博客
03-27 4936
1、在调试 rk3288 android 7.1 遇到部分机器不能开机的问题 logo 如下： init: Waiting for /dev/.coldboot_done... [ 3.024810] init: Waiting for /dev/.coldboot_done took 0.00s. [ 3.024848] init: /dev/hw_random not found...
android 新增分区以及挂载方法
06-28
android 新增分区以及挂载方法
Android2.3实现SD卡与U盘自动挂载的方法
09-02
主要介绍了Android2.3实现SD卡与U盘自动挂载的方法,较为详细的分析了Android2.3实现SD卡与U盘自动挂载的具体步骤与相关技巧,需要的朋友可以参考下
Android N获取外置SD卡或挂载U盘路径的方法
08-27
"Android N获取外置SD卡或挂载U盘路径的方法" 在 Android N 中，获取外置 SD 卡或挂载 U 盘路径是件复杂的事情。因为 Android N 并不提供直接的方法来获取外置 SD 卡或挂载 U 盘路径，这使得开发者需要通过间接的...
Android判断SD卡是否已经挂载的方法
01-04
本文实例讲述了Android判断SD卡是否已经挂载的方法。分享给大家供大家参考。具体如下： 提供一个监听方法BroadcastReceiver 设置IntentFilter为： Intent.ACTION_MEDIA_MOUNTED Intent.ACTION_MEDIA_EJECT Intent....
ueventd 启动慢分析
lihailin560的博客
07-02 1280
1.ueventd 启动 init.c的main()函数中有一个巧妙的处理：可以通过判断第一个运行参数来启动不同的进程： 如果执行“./ueventd”，进入第一个条件分支，执行uevent_main()函数； 如果执行“./watchdog”，进入第二个条件分支，执行watchdogd_main()函数； 如果执行”./init”，跳过所有分支条件，继续执行main()函数。 system/core/init/main.cpp 51 int main(int argc, char** arg.
android启动失败，分区metadata没找到
m0_37287937的博客
05-22 4360
android启动失败，分区metadata没找到
linux开机启动挂载mmc错误解决
老鹏
06-27 2万+
1. 简介：         项目中用am3359从TF卡的reiser文件系统转到ext4文件。转化原因是reiser文件系统的官网都没有了，还有文章提到reiserfs4的代码风格不符合linux代码风格，因此，linux不再主动将reiserfs的代码融合到linux中，即使reiserfs开发团队说会提供linux内核的补丁，但是，在查找网络上的文章的时候，资料实在是少，也不知道是不是网
解决：Android模拟器一直停留在开机画面
热门推荐
wjl15989的专栏
07-15 3万+
之前一直都用不了Android4.1.2的模拟器，总是停留在开机画面，一直进不去 后来经过一番研究，发现网上所谓的改什么Scale display to real size， 勾选snapshot等等都不管用。之前我是想，我在用的是Nexus one的模拟器机型，如果换成更新的机型，比如Galaxy Nexus或者Nexus 4可能可以解决。但是我改了机型之后又发现出现一条警告：On win
手机开机卡在android画面,手机一直停在开机画面怎么解决【图文】
weixin_39946534的博客
05-25 1万+
手机我相信人们不会不知道，这几年手机的发展速度非常地快，不知道大家平时使用手机的过程之中出现一些故障没有，相信大多数的用户是碰到过的，但是我相信大多数的手机用户是不会解决碰到的故障的。大家平时遇到最对的故障是什么呢?手机开机后一直停在开机界面这种情况相信大家都经历过吧!今天小编就教教大家如何解决这种故障。手机开机后一直停在开机界面怎么办top1:长按电源键12S左右重启手机手机在执行系统升级，刷机...
4412烧写Android后启动界面总停在android logo，为什么
yhy450165258的博客
06-07 1244
> EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem 估计是有些分区没有正确的格式化导致，建议lowformat 并重烧

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值