本文介绍在OpenHarmony中，如何查看开发版的分区信息

在OpenHarmony中，设备的分区信息在/dev/block/by-name/目录下

1. 查看

查看分区信息，如下

#
# ls dev/block/by-name/ -l
total 0
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 blackbox -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root    root    21 2025-09-09 14:47 boot_a -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root    root    21 2025-09-09 14:47 boot_b -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 cache -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 calinv -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 dtb_a -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 dtb_b -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root    root    21 2025-09-09 14:47 dtbo_a -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root    root    21 2025-09-09 14:47 dtbo_b -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root    root    21 2025-09-09 14:47 fbootlogo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 gpl -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 hypervsior_a -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 hypervsior_b -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_agdsp_a -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_agdsp_b -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_deltanv_a -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_deltanv_b -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_fixnv1_a -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_fixnv1_b -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_fixnv2_a -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_fixnv2_b -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_gdsp_a -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_gdsp_b -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_ldsp_a -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_ldsp_b -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_modem_a -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_modem_b -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_runtimenv1 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 l_runtimenv2 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 logo -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 metadata -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root    root    20 2025-09-09 14:47 misc -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 ueventd ueventd 20 2025-09-09 14:47 miscdata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 pm_sys_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 pm_sys_b -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 ueventd ueventd 20 2025-09-09 14:47 prodnv -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 ueventd ueventd 20 2025-09-09 14:47 sml_a -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 ueventd ueventd 20 2025-09-09 14:47 sml_b -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root    root    21 2025-09-09 14:47 soc_platform -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 sys_prod -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 sysdumpdb -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root    root    21 2025-09-09 14:47 system -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 teecfg_a -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 teecfg_b -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 ueventd ueventd 20 2025-09-09 14:47 trustos_a -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 ueventd ueventd 20 2025-09-09 14:47 trustos_b -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root    root    20 2025-09-09 14:47 uboot_a -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root    root    20 2025-09-09 14:47 uboot_b -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root    root    21 2025-09-09 14:47 uboot_log -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 updater_a -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 updater_b -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 ueventd ueventd 21 2025-09-09 14:47 userdata -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root    root    21 2025-09-09 14:47 vendor -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root    root    21 2025-09-09 14:47 vendor_boot_a -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root    root    21 2025-09-09 14:47 vendor_boot_b -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root    root    21 2025-09-09 14:47 vendor_boot_updater_a -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root    root    21 2025-09-09 14:47 vendor_boot_updater_b -> /dev/block/mmcblk0p41
#

在我们升级或者刷镜像时，会出现升级前后或者刷镜像前后分区损坏的情况，这时可以把升级前的分区导出，再把升级后的分区导出，进行比对，看是否一致。

2. 导出

比如我们要导出l_fixnv1_a分区信息

l_fixnv1_a -> /dev/block/mmcblk0p13

可以看到l_fixnv1_a分区在/dev/block/mmcblk0p13中

使用dd命令导出分区信息，把分区导出到/data/mmcblk0p13.img中

dd if=/dev/block/mmcblk0p13 of=/data/mmcblk0p13.img bs=4M

#
# dd if=/dev/block/mmcblk0p13 of=/data/mmcblk0p13.img bs=4M
0+1 records in
0+1 records out
2097152 bytes (2.0 M) copied, 0.037215 s, 54 M/s
#

把/data/mmcblk0p13.img导入到电脑中

hdc file recv /data/mmcblk0p13.img D:\data\image\

C:\Users\admin>hdc file recv /data/mmcblk0p13.img D:\data\image\
FileTransfer finish, Size:2097152, File count = 1, time:95ms rate:22075.28kB/s

Android如下

adb pull /data/mmcblk0p13.img d:\data\image\

在电脑的D:\data\image\目录下就有mmcblk0p13.img文件。

3. 对比

然后把升级前后的文件进行比对，看是否一致