many thnx for advice. I will try to do it so.
Nevertheless I still wonder for what system wants to use volume mmcblk0p2 when in fstab only mmcblk0p1 and sdc1 volumes are set.
@indian, please report back whether you have managed to reanimate the system.
Anyway, Sam (Nazarko) is selling some reliable SD cards, so we should avoid buying SD cards from dodgy sources, in order to have one variable less in our equation.
1 Like
The system tries to mount all visible partitions during boot. If you are no longer using the mmcblk0p2 partition you could use another computer to simply delete that partition and normal service may be resumed.
BUT! If mmcblk0p2 has a problem because the card is physically faulty then it may not be long until mmcblk0p1 (/boot) also goes corrupt so a replacement card is the more complete answer.
please report back whether you have managed to reanimate the system.
I made new install using another sd card I found at home. Before the new install I backuped the content of .kodi folder on usb flash stick so I reached quite easilly the recent system config.
What remains me unclear why the system update crashed on inpossibility to mount mmcblk0p2 when such partition was not in the system configured (not mentioned in fstab).
mmcblk0p2 is the root partition (the largest of the two partitions) on the SD card. It doesn’t show up in /etc/fstab as it is mounted directly the initramfs during the boot process.
It the root partition became mounted read-only then this would suggest the SD card is failing.
Ok, thnx for response. Last question, this partition is always created even USB install is used?
Depends how you did the USB install. However if you have a USB install then mmcblk0p2 being readonly would not stop an upgrade.