zag

Hello, Sorry that did not answer for a long time, there was no possibility. Thank you for showing interest in my problem. 1. Orange PI PC plus version 1.1 2. Armbian_5.25_Orangepipcplus_Ubuntu_xenial_default_3.4.113_desctop 3. Log from the console when loading in the attached file. 4. After the installation of the "Armbian", everything worked correctly. After about 2-3 months the browser stopped working (I do not remember with what error it was not started). After a short time the card stopped loading, that is, the download sometimes occurred, but for the most part it stopped. I was trying to boot from the SD card with the version of the operating system 5.30 (Armbian_5.25_Orangepipc_Ubuntu_xenial_default_3.4.113_desctop), everything was loaded and worked fine. I wanted to reset "Armbian" to internal memory, but the utility "nand-site-install" does not see EMMC memory. Is it possible to somehow format the internal memory and reinstall everything? OPCPlusProblem.txt

Good day, Here it produces and reboots again. The card boots normally, but does not see the flash memory. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 5.352628] Btrfs loaded Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.27.1 [/sbin/fsck.ext2 (1) -- /dev/mmcblk0p1] fsck.ext2 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1 contains a file system with errors, check forced. /dev/mmcblk0p1: Duplicate or bad block in use! /dev/mmcblk0p1: Multiply-claimed block(s) in inode 374953: 1545728 /dev/mmcblk0p1: Multiply-claimed block(s) in inode 375076: 1545728 /dev/mmcblk0p1: (There are 2 inodes containing multiply-claimed blocks.) /dev/mmcblk0p1: File /var/lib/AccountsService/users/gena.4FCWFZ (inode #374953, mod time Mon Mar 19 14:48:19 2018) has 1 multiply-claimed block(s), shared with 1 file(s): /dev/mmcblk0p1: /var/lib/dhcp/dhclient.eth0.leases (inode #375076, mod time Mon Mar 19 14:48:06 2018) /dev/mmcblk0p1: /dev/mmcblk0p1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) fsck exited with status code 4 done. Failure: File system check of the root filesystem failed The root filesystem on /dev/mmcblk0p1 requires a manual fsck Rebooting automatically due to panic= boot argument I correctly understood that the problem is in flash memory? Can this be somehow corrected?