美文网首页
android 10 长时间卡在logo界面 挂载分区时报如下错

android 10 长时间卡在logo界面 挂载分区时报如下错

作者: gale_小米 | 来源:发表于2024-01-31 14:47 被阅读0次
......
[    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");

相关文章

  • mac 编译 Android 系统杂记

    挂载android分区sudo hdiutil attach ~/android_code/android7.dm...

  • Ubuntu 卡在logo界面

    常规方法 1：在开机选择从U盘启动后（我是用U盘装的）会有几个选项让选择，最重要的两个是让你选择使用而不安装还是安...

  • ubuntu 12.04 卡在logo界面

    sudo apt-get purge lightdmsudo apt-get install gdm

  • 日常实用技能

    1. Ubuntu下硬盘加载故障 解决方法： 在终端输入如下命令，查看分区挂载情况 修复挂载错误的相应的分区,如提...

  • Ubuntu20.04开机自动挂载硬盘

    1. 查看硬盘情况 2. 创建好挂载位置 3. 获取要自动挂载的分区的UUID和分区类型TYPE 显示信息如下，这...

  • Ubuntu: 分区只读

    分区只读，可以尝试如下方式方式1：重新挂载 方式2：ntfsfix

  • Android 8.1下内置存储sdcard无法挂载

    平台： Rockchip 3399Android 8.1 问题： 开机后，内置/sdcard分区不可访问，无法挂载...

  • Ubuntu 乌班图系统使用

    1，Ubuntu Linux 永久挂载(mount)分区 1）挂载分区 sudo fdisk -l 查看所有分区 ...

  • merlin挂载swap分区

    采用挂载文件的方式 首先创建分区文件 把文件格式化成分区 挂载swap分区 查看swap分区大小

  • 创建pv失败

    如创建某个硬盘如/dev/sda创建的pv时报错（如下）： 原因：此硬盘已经分区，存在分区表，可以将某个分区划分为...

网友评论

      本文标题：android 10 长时间卡在logo界面 挂载分区时报如下错

      本文链接：https://www.haomeiwen.com/subject/glfaodtx.html

      延伸阅读

      深度阅读

      • 您也可以注册成为美文阅读网的作者，发表您的原创作品、分享您的心情！

      栏目导航

      热点阅读

      关于我们|服务条款|联系我们|android 10 长时间卡在logo界面 挂载分区时报如下错|投稿指南|网站地图|RSS订阅|排版工具|手机版

      提供经典美文摘抄,优美散文欣赏,现代诗歌精选,短篇小说,心情随笔,表白情书范文,故事会在线阅读欣赏

      Copyright © 2014-2023 Haomeiwen.com All Rights Reserved. 好美文阅读网 版权所有

      备案信息：桂公网安备 45052102000051号 · 桂ICP备13007215号-3

      本站所收录作品、热点评论等信息部分来源互联网，目的只是为了系统归纳学习和传递资讯

      所有作品版权归原创作者所有，与本站立场无关，如不慎侵犯了你的权益，请联系我们告知，我们将做删除处理！