Got a really huge amount of errors trying to install the latest version:
unable to remove newly-extracted version of /usr/share/kodi/addons/pvr.dvblink/resources/settings.xml': Input/output error dpkg: error while cleaning up: unable to remove newly-extracted version of /usr/bin/kodi’: Read-only file system
dpkg: error while cleaning up:
unable to remove newly-extracted version of /usr/bin/mediacenter': Read-only file system dpkg: error while cleaning up: unable to remove newly-extracted version of /usr/bin/kodi-standalone’: Read-only file system
dpkg: error while cleaning up:
unable to securely remove ‘/var/lib/dpkg/tmp.ci’: Read-only file system
dpkg: error while cleaning up:
unable to securely remove ‘/var/lib/dpkg/reassemble.deb’: Read-only file system
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for mime-support (3.58) …
dpkg: unrecoverable fatal error, aborting:
unable to flush updated status of `mime-support’: Read-only file system
osmc@osmc:~$ top
-bash: /usr/bin/top: Input/output error
That may make it reboot but not magically heal the SD Card. You will be defiantly in danger for corruption. If it boots after power plug then monitor kernel log closely in the next days
Moved you out of the V17 thread as the topic is not related.
Cloning the SD card would work. While cloning is done on a bit level so it doesn’t matter which filesystem OSMC is using. OSMC uses Fat for the boot partition and ext4 for root partition.
But if files are already have been damaged a cloning will not be to smart.
There is no need to format if you are going to dd or use the OSMC installer to write a new image to the card. These are block level operations.
Certainly a backup you have made could already contain file system corruption which you are simply rewriting to the card each time you try to restore it.
Thanks for the info @ActionA
Guess the backup was corrupted!
One last question: I’ve backed up a couple of folders, my fstab, my crontab to my local NFS-share.
Can these be corrupted too? Thus, could they corrupt my fresh SD-install after putting them back?
osmc@osmc:~$ sudo apt-get upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
The following packages will be upgraded:
base-files-osmc libc-bin libc6 libgcrypt20 mediacenter-addon-osmc multiarch-support perl-base
7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 24.8 MB of archives.
After this operation, 21.5 kB disk space will be freed.
Do you want to continue? [Y/n] Y
Get:1 http://security.debian.org/ jessie/updates/main perl-base armhf 5.20.2-3+deb8u4 [1126 kB]
Get:2 http://apt.osmc.tv/ jessie/main base-files-osmc all 1.8.6 [15.4 kB]
Get:3 http://apt.osmc.tv/ jessie/main mediacenter-addon-osmc all 3.0.610 [18.0 MB]
Get:4 http://security.debian.org/ jessie/updates/main libc-bin armhf 2.19-18+deb8u3 [1161 kB]
Get:5 http://security.debian.org/ jessie/updates/main libc6 armhf 2.19-18+deb8u3 [3961 kB]
Get:6 http://security.debian.org/ jessie/updates/main libgcrypt20 armhf 1.6.3-2+deb8u1 [354 kB]
Get:7 http://security.debian.org/ jessie/updates/main multiarch-support armhf 2.19-18+deb8u3 [179 kB]
Fetched 24.8 MB in 4s (5750 kB/s)
Preconfiguring packages …
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)ead-only file system file system
E: Sub-process /usr/bin/dpkg returned an error code (2)
E: Failed to write temporary StateFile /var/lib/apt/extended_states.tmp
osmc@osmc:~$ sudo apt-get upgrade
-bash: /usr/bin/sudo: No such file or directory
osmc@osmc:~$ top
-bash: /usr/bin/top: Input/output error
osmc@osmc:~$