Advertisement
Guest User

Xiaomi Mi5 Mattia

a guest
Sep 18th, 2019
132
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Bash 5.76 KB | None | 0 0
  1. [    4.795117] Begin: Running /scripts/nfs-top ... done.
  2. [    4.795273] Begin: Running /scripts/nfs-premount ... done.
  3. [    4.795420] Begin: Running /scripts/local-top ... done.
  4. [    4.795536] Begin: Running /scripts/local-premount ... done.
  5. [    4.810682] initrd: checking filesystem integrity for the userdata partition
  6. [    4.814071] EXT4-fs (sda14): couldn't mount as ext3 due to feature incompatibilities
  7. [    4.814508] EXT4-fs (sda14): couldn't mount as ext2 due to feature incompatibilities
  8. [    4.816434] EXT4-fs warning (device sda14): ext4_enable_quotas:5332: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
  9. [    4.816562] EXT4-fs (sda14): mount failed
  10. [    4.817921] F2FS-fs (sda14): Magic Mismatch, valid(0xf2f52010) - read(0x1906e0)
  11. [    4.817940] F2FS-fs (sda14): Can't find valid F2FS filesystem in 1th superblock
  12. [    4.818098] F2FS-fs (sda14): Magic Mismatch, valid(0xf2f52010) - read(0x100000)
  13. [    4.818111] F2FS-fs (sda14): Can't find valid F2FS filesystem in 2th superblock
  14. [    4.818133] F2FS-fs (sda14): Magic Mismatch, valid(0xf2f52010) - read(0x1906e0)
  15. [    4.818142] F2FS-fs (sda14): Can't find valid F2FS filesystem in 1th superblock
  16. [    4.818151] F2FS-fs (sda14): Magic Mismatch, valid(0xf2f52010) - read(0x100000)
  17. [    4.818159] F2FS-fs (sda14): Can't find valid F2FS filesystem in 2th superblock
  18. [    4.818569] mount: mounting /dev/sda14 on /tmpmnt failed: Invalid argument
  19. [    4.819605] umount: can't umount /tmpmnt: Invalid argument
  20. [    4.846266] initrd: checking filesystem for userdata took (including e2fsck) 0 seconds
  21. [    4.848510] dumpe2fs 1.43.4 (31-Jan-2017)
  22. [    4.851495] initrd: mounting /dev/sda14
  23. [    4.861207] ufshcd 624000.ufshc: ufshcd_ioctl: User buffer is NULL!
  24. [    4.864401] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support!
  25. [    4.864424] EXT4-fs (sda14): couldn't mount as ext3 due to feature incompatibilities
  26. [    4.864845] EXT4-fs (sda14): Mount option "data=journal" incompatible with ext2
  27. [    4.866513] EXT4-fs warning (device sda14): ext4_enable_quotas:5332: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
  28. [    4.866638] EXT4-fs (sda14): mount failed
  29. [    4.867654] F2FS-fs (sda14): Magic Mismatch, valid(0xf2f52010) - read(0x1906e0)
  30. [    4.867669] F2FS-fs (sda14): Can't find valid F2FS filesystem in 1th superblock
  31. [    4.867822] F2FS-fs (sda14): Magic Mismatch, valid(0xf2f52010) - read(0x100000)
  32. [    4.867832] F2FS-fs (sda14): Can't find valid F2FS filesystem in 2th superblock
  33. [    4.867846] F2FS-fs (sda14): Magic Mismatch, valid(0xf2f52010) - read(0x1906e0)
  34. [    4.867853] F2FS-fs (sda14): Can't find valid F2FS filesystem in 1th superblock
  35. [    4.867861] F2FS-fs (sda14): Magic Mismatch, valid(0xf2f52010) - read(0x100000)
  36. [    4.867869] F2FS-fs (sda14): Can't find valid F2FS filesystem in 2th superblock
  37. [    4.868027] mount: mounting /dev/sda14 on /tmpmnt failed: Invalid argument
  38. [    4.870790] initrd: boot mode: halium
  39. [    4.870896] initrd: Halium rootfs is  
  40. [    4.871424] initrd: mounting system rootfs at /halium-system
  41. [    4.872483] initrd: WARNING: Android system image not found.
  42. [    4.872561] initrd: mounting   (user mode)
  43. [    4.873275] mount: can't find /halium-system in /proc/mounts
  44. [    4.873669] initrd: mounting android system image (/tmpmnt/android-rootfs.img) ro, in /android-unknown (unknown mode)
  45. [    4.873731] initrd: mounting android system image from system rootfs
  46. [    4.875190] mount: mounting /halium-system/var/lib/lxc/android/android-rootfs.img on /android-unknown failed: No such file or directory
  47. [    4.875461] initrd: WARNING: Failed to mount Android system.img.
  48. [    4.876046] initrd: Normal boot
  49. [    4.876676] mount: mounting /halium-system on /root failed: Invalid argument
  50. [    4.878321] mount: mounting /tmpmnt on /root/userdata failed: Invalid argument
  51. [    4.879045] mount: mounting /android-rootfs on /root/var/lib/lxc/android/rootfs failed: No such file or directory
  52. [    4.884136] grep: /android-system/build.prop: No such file or directory
  53. [    4.884918] initrd: WARNING: Didn't find a device name. Is the Android system image mounted correctly?
  54. [    4.884970] initrd: device is unknown
  55. [    4.885045] initrd: This rootfs does not have any writable-paths defined
  56. [    4.885130] initrd: checking fstab /root/var/lib/lxc/android/rootfs/fstab* for additional mount points
  57. [    4.887177] cat: can't open '/root/var/lib/lxc/android/rootfs/fstab*': No such file or directory
  58. [    4.888080] initrd: moving Android system to /android/system
  59. [    4.888746] mount: mounting /android-system on /root/android/system failed: Invalid argument
  60. [    4.889147] Begin: Running /scripts/local-bottom ... done.
  61. [    4.889309] done.
  62. [    4.889456] Begin: Running /scripts/nfs-bottom ... done.
  63. [    4.889726] Begin: Running /scripts/init-bottom ...
  64. [    4.894824] mount: mounting /dev on /root/dev failed: No such file or directory
  65. [    4.895458] mount: mounting /dev on /root/dev failed: No such file or directory
  66. [    4.895911] done.
  67. [    4.896549] mount: mounting /run on /root/run failed: No such file or directory
  68. [    4.897385] run-init: current directory on the same filesystem as the root: Not a typewriter
  69. [    4.897540] Target filesystem doesn't have requested /sbin/init.
  70. [    4.898057] run-init: current directory on the same filesystem as the root: Not a typewriter
  71. [    4.898646] run-init: current directory on the same filesystem as the root: Not a typewriter
  72. [    4.899222] run-init: current directory on the same filesystem as the root: Not a typewriter
  73. [    4.899804] run-init: current directory on the same filesystem as the root: Not a typewriter
  74. [    4.900451] run-init: current directory on the same filesystem as the root: Not a typewriter
  75. [    4.901429] No init found. Try passing init= bootarg.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement