EXT4 app2sd link2sd 파티션 복구 잘못된 슈퍼블록. Android에서는 파티션을 마운트할 수 없지만 Linux Live에서는 su를 통해 RW를 마운트할 수 있습니다.

내 6개 휴대폰에 128GB 마이크로 SD가 있고 두 번째 파티션(p2) ext4을 10GB 로 포맷했습니다. 모든 애플리케이션(80%)은 이 ext4 파티션에 남아 있습니다. 이 파티션은 지금 마운트할 수 없습니다 - "Unable to mount....kgrinvalid file" 또한 내 데이터를 보관하는 데 사용되는 119GB 기본 fat() 파티션(p1)이 RO로 마운트됩니다. 저는 소니 엑스페리아 Z3를 사용하고 있습니다.app2sdext4Androidapp2sdexFatrooted

간략한 배경:
휴대폰으로 영화를 촬영하고 있었는데 두 번 다시 시작한 후에 작동이 중단되었습니다. 그 후 ext4 파티션이 성공적으로 설치되지 않았습니다.

질문:

-- ext4 파일 시스템에서 fsck를 수행하고 할당 테이블에 불량 블록이 있음을 알리는 방법
-- 불량 블록과 손상을 감지하고 카드를 RO 모드 1 파티션 및 기타 파티션에 넣을 수 있는 메커니즘이 카드에 내장되어 있습니까? 파티션 ext4는 휴대폰에 설치할 수 없습니다
. 이는 카드가 최종 상태에 있고 몇 번의 쓰기 주기 후에 RO가 된다는 의미라는 것을 어딘가에서 읽었습니다. 일부 기술 지원에서는 이런 일이 일어나고 있다고 제안합니다. 나는 그것을 믿을 준비가 되어 있지 않습니다. Amazon에서 구매한 지 4개월밖에 안 됐고 쓸 수 있습니다(나머지 이야기에서 확인하겠습니다)
. ADB 드라이버가 있고 adb에 # 프롬프트를 입력합니다. p1을 RW로 마운트할 수 있습니다. P2가 표시되는 것을 adb에서 확인할 수 있지만 마운트되지는 않습니다.
app2sd를 사용하여 P2를 마운트하고 다시 비즈니스로 돌아갈 수 있도록 하려면 어떻게 해야 합니까?

내가 뭘 한거지

라이브 linuxCD

-- p1과 p2를 RW(명시적 명령 이후)로 마운트할 수 있으며 Su로만 마운트할 수 있습니다. 일반 사용자 - RO가 거부된 사용자입니다. 따라서 라이브 우분투에서는 두 가지 모두에 RW를 수행할 수 있습니다
. P2를 백업한 다음 DEL을 시도하고 P2를 포맷합니다( gparted+ fdisk수동으로). 운이 좋지 않습니다. 둘 다 성공적인 메시지를 제공하지만 새로 고친 후에는 동일한 이전 partitionsP1과 P2가 표시됩니다. Window 7(파라곤 파티션 관리자)에서 동일한 작업을 시도했지만 성공 메시지가 표시되었지만 새로 고침 후에는 이전 구성 P1 및 P2가 표시됩니다.
---Fsck

it@it:~$ sudo fsck.ext4 -v /dev/sdc2
e2fsck 1.43.4 (31-Jan-2017)
app2sd: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? yes
fsck.ext4: unable to set superblock flags on app2sd


app2sd: ********** WARNING: Filesystem still has errors **********

- 백업 슈퍼블록 복구 실행이 도움이 되지 않았습니다.

it@it:~$ sudo mke2fs -n  /dev/sdc2
mke2fs 1.43.4 (31-Jan-2017)
/dev/sdc2 contains a ext4 file system labelled 'app2sd'
    last mounted on /data/sdext2 on Sun Jan  7 07:21:35 2018
Proceed anyway? (y,N) y
Creating filesystem with 2604538 4k blocks and 651520 inodes
Filesystem UUID: 53138787-e743-4160-9041-ac9613d44db8
Superblock backups stored on blocks: 
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

나는 다양한 슈퍼 블록을 시도했지만 운이 없었습니다.

나는 이 가이드를 사용했습니다. 운이 좋지 않습니다.
1) 백업에서 슈퍼블록 복원그리고 2) fsck.ext4는 잘못된 마운트 해제 후 슈퍼블록 플래그를 설정할 수 없습니다.

it@it:~$ sudo e2fsck -b   1605632 -B 4096 /dev/sdc2
e2fsck 1.43.4 (31-Jan-2017)
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
app2sd: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
e2fsck: unable to set superblock flags on app2sd


app2sd: ***** FILE SYSTEM WAS MODIFIED *****

app2sd: ********** WARNING: Filesystem still has errors **********

나는 또한 이것을 시도했고 다음과 같이 B=4096확인했습니다 .testdisk

mke2fs -S

-S    Write  superblock and group descriptors only.  This is useful if all
          of the superblock and backup superblocks are corrupted, and a  last-
          ditch  recovery method is desired.  It causes mke2fs to reinitialize
          the superblock and group descriptors, while not touching  the  inode
          table and the block and inode bitmaps.  The e2fsck program should be
          run immediately after this option is used, and there is no guarantee
          that  any  data  will be salvageable.  It is critical to specify the
          correct filesystem blocksize when using this option, 

이건 뭔가 더 있어
테스트 디스크 로그

Partition table type (auto): Intel
Disk /dev/sdb - 127 GB / 119 GiB - Generic- SD/MMC
Partition table type: Intel

Interface Advanced
Geometry from i386 MBR: head=255 sector=63


test_FAT()
 1 P FAT32 LBA                0  32 33 14247  69 30  228880384
sector_size  512
cluster_size 64
reserved     126
fats         2
dir_entries  0
sectors      0
media        F8
fat_length   0
secs_track   16
heads        4
hidden       2048
total_sect   228880384
check_part_i386 failed for partition type 0C
get_geometry_from_list_part_aux head=255 nbr=2
get_geometry_from_list_part_aux head=8 nbr=1
get_geometry_from_list_part_aux head=255 nbr=2
 1 P FAT32 LBA                0  32 33 14247  69 30  228880384
 2 * Linux                14248   0  1 15544 254 63   20836305 [app2sd]
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 10668 MB / 10173 MiB
search_superblock

recover_EXT2: s_block_group_nr=0/79, s_mnt_count=83/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 2 (block=0, blocksize=4096)

block_group_nr 1

recover_EXT2: "e2fsck -b 32768 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=1/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 262144 (block=32768, blocksize=4096)

block_group_nr 3

recover_EXT2: "e2fsck -b 98304 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=3/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 786432 (block=98304, blocksize=4096)

block_group_nr 5

recover_EXT2: "e2fsck -b 163840 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=5/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 1310720 (block=163840, blocksize=4096)

block_group_nr 7

recover_EXT2: "e2fsck -b 229376 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=7/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 1835008 (block=229376, blocksize=4096)

block_group_nr 9

recover_EXT2: "e2fsck -b 294912 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=9/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 2359296 (block=294912, blocksize=4096)

block_group_nr 25

recover_EXT2: "e2fsck -b 819200 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=25/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 6553600 (block=819200, blocksize=4096)

block_group_nr 27

recover_EXT2: "e2fsck -b 884736 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=27/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 7077888 (block=884736, blocksize=4096)

block_group_nr 49

recover_EXT2: "e2fsck -b 1605632 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=49/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 12845056 (block=1605632, blocksize=4096)
  Linux                14248   0  1 15544 254 62   20836304 [app2sd]
superblock 0, blocksize=4096 [app2sd]
superblock 32768, blocksize=4096 [app2sd]
superblock 98304, blocksize=4096 [app2sd]
superblock 163840, blocksize=4096 [app2sd]
superblock 229376, blocksize=4096 [app2sd]
superblock 294912, blocksize=4096 [app2sd]
superblock 819200, blocksize=4096 [app2sd]
superblock 884736, blocksize=4096 [app2sd]
superblock 1605632, blocksize=4096 [app2sd]

To repair the filesystem using alternate superblock, run
fsck.ext4 -p -b superblock -B blocksize device
search_superblock

recover_EXT2: s_block_group_nr=0/79, s_mnt_count=83/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 2 (block=0, blocksize=4096)

block_group_nr 1

recover_EXT2: "e2fsck -b 32768 -B 4096 device" may be needed

dump2fs 로그 예.
단순히 전체 파일을 스택에 추가할 수는 없습니다.

Partition table type (auto): Intel
Disk /dev/sdb - 127 GB / 119 GiB - Generic- SD/MMC
Partition table type: Intel

Interface Advanced
Geometry from i386 MBR: head=255 sector=63


test_FAT()
 1 P FAT32 LBA                0  32 33 14247  69 30  228880384
sector_size  512
cluster_size 64
reserved     126
fats         2
dir_entries  0
sectors      0
media        F8
fat_length   0
secs_track   16
heads        4
hidden       2048
total_sect   228880384
check_part_i386 failed for partition type 0C
get_geometry_from_list_part_aux head=255 nbr=2
get_geometry_from_list_part_aux head=8 nbr=1
get_geometry_from_list_part_aux head=255 nbr=2
 1 P FAT32 LBA                0  32 33 14247  69 30  228880384
 2 * Linux                14248   0  1 15544 254 63   20836305 [app2sd]
     ext4 blocksize=4096 Large_file Sparse_SB Recover, 10668 MB / 10173 MiB
search_superblock

recover_EXT2: s_block_group_nr=0/79, s_mnt_count=83/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 2 (block=0, blocksize=4096)

block_group_nr 1

recover_EXT2: "e2fsck -b 32768 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=1/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 262144 (block=32768, blocksize=4096)

block_group_nr 3

recover_EXT2: "e2fsck -b 98304 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=3/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 786432 (block=98304, blocksize=4096)

block_group_nr 5

recover_EXT2: "e2fsck -b 163840 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=5/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 1310720 (block=163840, blocksize=4096)

block_group_nr 7

recover_EXT2: "e2fsck -b 229376 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=7/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 1835008 (block=229376, blocksize=4096)

block_group_nr 9

recover_EXT2: "e2fsck -b 294912 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=9/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 2359296 (block=294912, blocksize=4096)

block_group_nr 25

recover_EXT2: "e2fsck -b 819200 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=25/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 6553600 (block=819200, blocksize=4096)

block_group_nr 27

recover_EXT2: "e2fsck -b 884736 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=27/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 7077888 (block=884736, blocksize=4096)

block_group_nr 49

recover_EXT2: "e2fsck -b 1605632 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=49/79, s_mnt_count=0/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 12845056 (block=1605632, blocksize=4096)
  Linux                14248   0  1 15544 254 62   20836304 [app2sd]
superblock 0, blocksize=4096 [app2sd]
superblock 32768, blocksize=4096 [app2sd]
superblock 98304, blocksize=4096 [app2sd]
superblock 163840, blocksize=4096 [app2sd]
superblock 229376, blocksize=4096 [app2sd]
superblock 294912, blocksize=4096 [app2sd]
superblock 819200, blocksize=4096 [app2sd]
superblock 884736, blocksize=4096 [app2sd]
superblock 1605632, blocksize=4096 [app2sd]

To repair the filesystem using alternate superblock, run
fsck.ext4 -p -b superblock -B blocksize device
search_superblock

recover_EXT2: s_block_group_nr=0/79, s_mnt_count=83/20, s_blocks_per_group=32768, s_inodes_per_group=32320
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2604538
recover_EXT2: part_size 20836304
Ext2 superblock found at sector 2 (block=0, blocksize=4096)

block_group_nr 1

recover_EXT2: "e2fsck -b 32768 -B 4096 device" may be needed

노드 목록을 반복합니다.
또 다른 시도: 테스트 디스크 로그 및 루프에서 모든 백업 슈퍼노드 목록을 가져옵니다. 이것은 흥미롭습니다. 실행하면 esfsck -b <n> -B <N> /devpath아래와 동일한 표준 o/p를 얻습니다. 다르지 않습니다.

    + sudo e2fsck -b 163840 -B 4096 -y /dev/sdc2
    e2fsck 1.43.4 (31-Jan-2017)
    Superblock needs_recovery flag is clear, but journal has data.
    Recovery flag not set in backup superblock, so running journal anyway.
    app2sd: recovering journal
    Superblock needs_recovery flag is clear, but journal has data.
    Recovery flag not set in backup superblock, so running journal anyway.
    Superblock needs_recovery flag is clear, but journal has data.
    Recovery flag not set in backup superblock, so running journal anyway.
    e2fsck: unable to set superblock flags on app2sd


    app2sd: ***** FILE SYSTEM WAS MODIFIED *****

    app2sd: ********** WARNING: Filesystem still has errors **********

그러나 파일(testdisk.log)에서 로드된 목록을 반복할 때 일부 노드의 경우 일부 복구를 수행한 것처럼 긴 o/p를 제공합니다. 희미한 희망이 있습니다. 그 후 나는 리눅스를 만들었습니다.REISUB 닫기그리고 다시 efsck를 해보세요. 불운

efsck 순환 로그 및 복구 섹션.

블록 번호를 수정하려는 사람들을 위해 명령줄에서 백업 슈퍼블록을 설정하려고 시도했지만 도움이 되지 않았습니다. 원점으로 돌아갔습니다!

+ for i in $(grep e2fsck testdisk.log | uniq | cut -d " " -f 4)
+ sudo e2fsck -b 229376 -B 4096 -y /dev/sdc2
e2fsck 1.43.4 (31-Jan-2017)
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
app2sd: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Inode 69709 extent tree (at level 1) could be shorter.  Fix? yes

Inode 97187 extent tree (at level 1) could be shorter.  Fix? yes

Inode 98194 extent tree (at level 1) could be shorter.  Fix? yes

Inode 98215 extent tree (at level 1) could be shorter.  Fix? yes

Inode 98646 extent tree (at level 1) could be shorter.  Fix? yes

Inode 99795 extent tree (at level 1) could be shorter.  Fix? yes

Inode 100170 extent tree (at level 1) could be shorter.  Fix? yes

Inode 100186 extent tree (at level 1) could be shorter.  Fix? yes

Inode 100825 extent tree (at level 1) could be shorter.  Fix? yes

Inode 129341 extent tree (at level 1) could be shorter.  Fix? yes

Inodes that were part of a corrupted orphan linked list found.  Fix? yes

Inode 129343 was part of the orphaned inode list.  FIXED.
Inode 129344 was part of the orphaned inode list.  FIXED.
Inode 129345 was part of the orphaned inode list.  FIXED.
Inode 129371 extent tree (at level 1) could be shorter.  Fix? yes

Inode 129414 extent tree (at level 1) could be shorter.  Fix? yes

Inode 129418 extent tree (at level 1) could be shorter.  Fix? yes

Inode 129437 extent tree (at level 1) could be shorter.  Fix? yes

Inode 162145 extent tree (at level 1) could be shorter.  Fix? yes

Inode 162147 extent tree (at level 1) could be shorter.  Fix? yes

Inode 162151 extent tree (at level 1) could be shorter.  Fix? yes

Inode 194325 extent tree (at level 1) could be shorter.  Fix? yes

Inode 194408 extent tree (at level 1) could be shorter.  Fix? yes

Inode 194464 extent tree (at level 1) could be shorter.  Fix? yes

Deleted inode 195640 has zero dtime.  Fix? yes

Deleted inode 196040 has zero dtime.  Fix? yes

Inode 235473 is in use, but has dtime set.  Fix? yes

Inode 235473 has imagic flag set.  Clear? yes

Inode 235473 has a extra size (25959) which is invalid
Fix? yes

Inode 235474 has INLINE_DATA_FL flag on filesystem without inline data support.
Clear? yes

Inode 235473, i_size is 7019251879657894515, should be 0.  Fix? yes

Inode 235473, i_blocks is 81858393236329, should be 0.  Fix? yes

Inode 388501 extent tree (at level 1) could be shorter.  Fix? yes

Inode 420685 extent tree (at level 1) could be shorter.  Fix? yes

Inode 452971 extent tree (at level 1) could be shorter.  Fix? yes

Inode 452978 extent tree (at level 1) could be shorter.  Fix? yes

Inode 452981 extent tree (at level 1) could be shorter.  Fix? yes

Inode 550513 extent tree (at level 1) could be shorter.  Fix? yes

Inode 550523 extent tree (at level 1) could be shorter.  Fix? yes

Inode 550524 extent tree (at level 1) could be shorter.  Fix? yes

Inode 550525 extent tree (at level 1) could be shorter.  Fix? yes

Inode 551843 extent tree (at level 1) could be shorter.  Fix? yes

Inode 582085 has an invalid extent node (blk 593131, lblk 0)
Clear? yes

Inode 582085 extent tree (at level 1) could be shorter.  Fix? yes

Inode 582085, i_blocks is 40, should be 0.  Fix? yes

Inode 582132 extent tree (at level 1) could be shorter.  Fix? yes

Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Directory inode 97167, block #0, offset 0: directory corrupted
Salvage? yes

Missing '.' in directory inode 97167.
Fix? yes

Setting filetype for entry '.' in ??? (97167) to 2.
Missing '..' in directory inode 97167.
Fix? yes

Setting filetype for entry '..' in ??? (97167) to 2.
Directory inode 97176, block #0, offset 0: directory corrupted
Salvage? yes

Missing '.' in directory inode 97176.
Fix? yes

Setting filetype for entry '.' in ??? (97176) to 2.
Missing '..' in directory inode 97176.
Fix? yes

Setting filetype for entry '..' in ??? (97176) to 2.
Directory inode 97213, block #0, offset 0: directory corrupted
Salvage? yes

Missing '.' in directory inode 97213.
Fix? yes

Setting filetype for entry '.' in ??? (97213) to 2.
Missing '..' in directory inode 97213.
Fix? yes

Setting filetype for entry '..' in ??? (97213) to 2.
Directory inode 161950, block #0, offset 0: directory corrupted
Salvage? yes

Missing '.' in directory inode 161950.
Fix? yes

Setting filetype for entry '.' in ??? (161950) to 2.
Missing '..' in directory inode 161950.
Fix? yes

Setting filetype for entry '..' in ??? (161950) to 2.
Inode 235473 (/data/com.abhivyaktyapps.learn.sanskrit/app_Parse/CommandCache/CachedCommand_00000160cc4ef3d9_00000000_-1326099007) has invalid mode (0166654).
Clear? yes

완전히 죽은 말이라면 라이브 상태에서 RW를 마운트하고 Android를 종료할 수 있는 이유는 무엇입니까? flag불량하거나 손상된 블록이 감지되면 여기에 일종의 설정이 있는 것 같습니다 superblock. 항상 P1을 RO로 로드하고 P2는 로드할 가치가 없습니다. 이 플래그를 어떻게 지우나요? 내 안드로이드 폰에는 # via가 있습니다. ADBLive에서처럼 Android에서도 마운트할 수 있는 이유는 무엇인가요?