Hello,
My nano pi r5c is no more booting from.the internal EMmc card. If I flash the dietpi on a SD card it’s booting fine.
Any help appreciated @MichaIng
1 Like
Did you tried booting any other os from emmc?
Tried any image from the official download site non is working or flashing the internal EMmc …I tried also to unbrick the device according the wiki on Linux everything is fine and I can flash minimal.bin but on windows I can’t. But still after flashing minimal.bin the device is not working properly
you tried the way describe on Friendlyelec wiki? ( 4.4.3.1 Option 1: Install OS via TF Card) NanoPi R5C - FriendlyELEC WiKi
There seems to be a challenge with the device if official os not working as well.
Just to rule that out: you do not have any SD card attacked when trying to boot from eMMC, do you?
No no sd card attached
Okay. AFAIK, no dedicated flashing method is needed. When you boot from SD card and flash the extracted img file to the eMMC with dd or any flashing tool, it should just boot, as it contains a bootloader. I do not have an R5C, but an R5S, where this works. I hope it is no hardware defect. What happens when you do an fsck of the eMMC root filesystem from the system booted from SD card?
@MichaIng
Output
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk1 179:0 0 28.9G 0 disk
└─mmcblk1p1 179:1 0 28.8G 0 part
mmcblk1boot0 179:32 0 4M 1 disk
mmcblk1boot1 179:64 0 4M 1 disk
mmcblk0 179:96 0 28.8G 0 disk
└─mmcblk0p1 179:97 0 28.8G 0 part /
fsck /dev/mmcblk1
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk1
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
Found a gpt partition table in /dev/mmcblk1
gdisk -l /dev/mmcblk1
GPT fdisk (gdisk) version 1.0.9
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!
Main header: OK
Backup header: ERROR
Main partition table: OK
Backup partition table: ERROR
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.
****************************************************************************
Disk /dev/mmcblk1: 60620800 sectors, 28.9 GiB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 73987B6B-4974-4C94-A3E8-58AB2EB7A946
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 60620766
Partitions will be aligned on 2048-sector boundaries
Total free space is 286686 sectors (140.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 286720 60620766 28.8 GiB 8300
I copied with dd the sd dietpi on it again now it looks like
e2fsck /dev/mmcblk1p1
e2fsck 1.47.0 (5-Feb-2023)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/mmcblk1p1
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
gdisk -l /dev/mmcblk1
GPT fdisk (gdisk) version 1.0.9
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/mmcblk1: 60620800 sectors, 28.9 GiB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 73987B6B-4974-4C94-A3E8-58AB2EB7A946
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 60620766
Partitions will be aligned on 2048-sector boundaries
Total free space is 286686 sectors (140.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 286720 60620766 28.8 GiB 8300 r
mke2fs -n /dev/mmcblk1
mke2fs 1.47.0 (5-Feb-2023)
Found a gpt partition table in /dev/mmcblk1
Proceed anyway? (y,N) y
Creating filesystem with 7577600 4k blocks and 1896832 inodes
Filesystem UUID: 1ca07f90-634f-42f6-aea7-09bb4c3cc420
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
I fixed it
- erasing the flash via minimal image and than flashing a image via USB…
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.