Latest Update has got me stuck in an unhappy face loop

I’ve just gone to use my Pi 2 with RC3 and after clicking OK to install updates it’s now stuck in a loop where it trys to boot and then I get an error/unhappy face.

Is there anything I can do to recover it or shall I wipe the install?

Did your Pi dies part way through the update process? (I think if you hold SHIFT while booting it will try to fix a corrupted update.)

Thanks, is there a solution that doesn’t rely on the keyboard? I don’t have one!

Based on the post at: Kodi update crash - OSMC RC3 , raspberry pi 2

I’ve managed to get the logs from the commands that are mentioned. These are at: and


Your second log file is blank and the first one is only a Kodi log, so not very helpful in this situation.

Can you provide these two logs ?

paste-log /var/log/apt/term.log
paste-log /var/log/apt/history.log

I suspect I know what your problem is so you could try the following to fix it from ssh: (after providing the above two logs, and please check that you can see the log on the paste site so that we can post-mortem the problem)

sudo dpkg --configure -a
sudo apt-get update
sudo apt-get -f -y dist-upgrade

Hi @DBMandrake,

come home today to also find my Pi runnning RC3 with a sad face.
When trying your comments

I get dpkg: error: unknown option --reconfigure

I executed the other commands and that fixed the issue. Any idea what caused this issue?

Sorry, that should be

sudo dpkg --configure -a

I would recommend that you run that command.

Can’t be sure without seeing your log files so please upload your debug logs.

Hi @DBMandrake,

many thanks for your update. Actually no need for the logfile. Because when I wanted to upload the logfile I figured out what caused my issues.
No space on the root drive left. Sorry that I didn’t see that before.
Currently using a 2GB card, was waiting for the Final Release before using my 8GB card, seems that was a mistake.



Ah, yes no free space will cause updates to fail, (apt is supposed to check there is enough space left, but we may need to add additional checks of our own) and 2GB is very marginal. I personally wouldn’t use less than 8GB for a “real” system that you are planning to scan a large library into, and 4GB would be bare minimum.

Yeah, as mentioned the 2GB was just for testing. While the strange thing is that apt-get did not fail at all. Maybe it just had fit but when Kodi was trying to write files it failed.

The logs would probably show what went wrong, especially the APT logs, assuming there was enough space left to write a log before it died :slight_smile:

For your viewing pleasure
osmc@osmc:~$ paste-log /var/log/apt/history.log
osmc@osmc:~$ paste-log /var/log/apt/term.log

Hi @DBMandrake,

I’ve just got the chance to try your tips. When I try:

sudo dpkg --configure -a

I get the error:

dpkg: error: unable to access dpkg status area: Read-only file system

Any other ideas or is the file system corrupt and I’d be easier to reinstall?

Don’t worry about this issue and thanks for your help.

With the ease of reinstalling, I’ve just gone down that route to rule out any corruption of the SD card.


A read only file system is due to file system corruption being detected at the start of boot. Holding down shift for the recovery console when powering on will run a full fsck automatically to attempt to repair this, however if corruption was serious I would be inclined to do a fresh install anyway.

Thanks for following that up.

It might be worth getting a cheap keyboard that I can use for that purpose then.