Android8 Filesystem not Mounted(To boot from the SD card)

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Android8 Filesystem not Mounted(To boot from the SD card)

2,688件の閲覧回数
crl6crl6
Contributor III

HI, All,

I'm using imx6q Android 8 BSP. Android not able to mount the system.img.

To boot from the SD card, perform the following operations:

crl6@crl6:~/android_build/out/target/product/sabresd_6dq$ pwd
/home/crl6/android_build/out/target/product/sabresd_6dq
crl6@crl6:~/android_build/out/target/product/sabresd_6dq$ cat /etc/issue
Ubuntu 16.04.3 LTS \n \l

crl6@crl6:~/android_build/out/target/product/sabresd_6dq$ sudo ../../../../device/fsl/common/tools/fsl-sdcard-partition.sh -f imx6q -c 14 /dev/sdb


the board log is at below:
................................
mmc1: host does not support reading read-only switch, assuming write-enable
mmc1: new high speed SDHC card at address 0001
mmcblk1: mmc1:0001 SD16G 14.6 GiB 
Primary GPT is invalid, using alternate GPT.
mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11
caam algorithms registered in /proc/crypto
.........................................

init: First stage mount skipped (missing/incompatible fstab in device tree)

..............................................

selinux: SELinux: Loaded property_contexts from /plat_property_contexts & /nonplat_property_contexts.

init: Running restorecon...
selinux: SELinux: Could not stat /dev/block: No such file or directory.

init: waitpid failed: No child processes
init: Couldn't load property file: Unable to open '/system/etc/prop.default': No such file or directory: No such file or directory
init: Couldn't load property file: Unable to open '/prop.default': No such file or directory: No such file or directory
init: Couldn't load property file: Unable to open '/odm/default.prop': No such file or directory: No such file or directory
init: Couldn't load property file: Unable to open '/vendor/default.prop': No such file or directory: No such file or directory

.................................................

the fsl-sdcard-partition.sh log is at below:

crl6@crl6:~/android_build/out/target/product/sabresd_6dq$ sudo ../../../../device/fsl/common/tools/fsl-sdcard-partition.sh -f imx6q -c 14 /dev/sdb
[sudo] password for crl6:
make gpt partition for android: partition-table-14GB.img
17+0 records in
17+0 records out
17408 bytes (17 kB, 17 KiB) copied, 0.0331121 s, 526 kB/s

/dev/sdb:
re-reading partition table
GPT fdisk (gdisk) version 1.0.1

Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.

Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.

Warning! One or more CRCs don't match. You should repair the disk!

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged

****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************

Command (? for help):
Recovery/transformation command (? for help): Warning! This will probably do weird things if you've converted an MBR to
GPT form and haven't yet saved the GPT! Proceed? (Y/N):
Recovery/transformation command (? for help): Warning! Secondary header is placed too early on the disk! Do you want to
correct this problem? (Y/N): Have moved second header and partition table to correct location.

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/sdb.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
formating android images
format_partition: userdata:/dev/sdb10 ext4
mke2fs 1.42.13 (17-May-2015)
/dev/sdb10 contains a ext4 file system labelled 'userdata'
created on Fri Sep 7 08:26:59 2018
Creating filesystem with 3095040 4k blocks and 775200 inodes
Filesystem UUID: 56b8df6f-c0e1-49c6-86f4-fd46739d41c3
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

format_partition: cache:/dev/sdb4 ext4
mke2fs 1.42.13 (17-May-2015)
/dev/sdb4 contains a ext4 file system labelled 'cache'
created on Fri Sep 7 08:27:09 2018
Creating filesystem with 131072 4k blocks and 32768 inodes
Filesystem UUID: c5d090e1-ef30-46c4-b5e5-5cfba62b1e7f
Superblock backups stored on blocks:
32768, 98304

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

erase_partition: presistdata : /dev/sdb8 1M
1+0 records in
1+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0826361 s, 12.7 MB/s
erase_partition: fbmisc : /dev/sdb11 1M
1+0 records in
1+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0710868 s, 14.8 MB/s
erase_partition: misc : /dev/sdb5 4M
4+0 records in
4+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.539992 s, 7.8 MB/s
flash_partition: boot-imx6q.img ---> /dev/sdb1
21994+1 records in
21994+1 records out
11261224 bytes (11 MB, 11 MiB) copied, 11.6947 s, 963 kB/s
flash_partition: recovery-imx6q.img ---> /dev/sdb2
28822+1 records in
28822+1 records out
14757164 bytes (15 MB, 14 MiB) copied, 13.9557 s, 1.1 MB/s
flash_partition: system_raw.img ---> /dev/sdb3
3145728+0 records in
3145728+0 records out
1610612736 bytes (1.6 GB, 1.5 GiB) copied, 1458.58 s, 1.1 MB/s
flash_partition: vendor_raw.img ---> /dev/sdb9
229376+0 records in
229376+0 records out
117440512 bytes (117 MB, 112 MiB) copied, 116.352 s, 1.0 MB/s
erase_partition: uboot : /dev/sdb
flash_partition: u-boot-imx6q.imx ---> /dev/sdb
the bootloader partition size: 8191
8191+0 records in
8191+0 records out
8387584 bytes (8.4 MB, 8.0 MiB) copied, 9.47907 s, 885 kB/s
607+0 records in
607+0 records out
621568 bytes (622 kB, 607 KiB) copied, 0.344803 s, 1.8 MB/s
crl6@crl6:~/android_build/out/target/product/sabresd_6dq$
crl6@crl6:~/android_build/out/target/product/sabresd_6dq$ sync

Regards,

crr6

タグ(1)
0 件の賞賛
返信
2 返答(返信)

1,922件の閲覧回数
igorpadykov
NXP Employee
NXP Employee

Hi crr6

reason may be due to programming sd image, please try with mfg tool:

i.MX 6/7D Series Manufacturing Toolkit for Android O8.0.0_1.0.0 Release

https://www.nxp.com/webapp/Download?colCode=IMX_O8.0.0_1.0.0_TOOL&appType=license&location=null&Pare... 

i.MX Software|NXP 

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 件の賞賛
返信

1,922件の閲覧回数
crl6crl6
Contributor III
0 件の賞賛
返信