RPi 2 RC3 fails to boot with multiple errors

Everything was working fine with all updates applied. Returned home to an unresponsive device.

Now, when I try to reboot, I get a series of pretty serious sounding error messages on the screen:

Reading through the various systemd status messages it seems like everything is failing due to the filesystem being in read only mode.

When I try to edit any files on the device via SSH I get an error about the file system being mounted in read only mode.

Some basic debugging that I tried (none of the output means anything to me):

osmc@osmc:~$ sudo systemctl status systemd-remount-fs.service
* systemd-remount-fs.service - Remount Root and Kernel File Systems
   Loaded: loaded (/lib/systemd/system/systemd-remount-fs.service; static)
   Active: failed (Result: exit-code) since Tue 2015-06-23 14:27:28 NZST; 3min 33s ago
     Docs: man:systemd-remount-fs.service(8)
  Process: 378 ExecStart=/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
 Main PID: 378 (code=exited, status=1/FAILURE)

Jun 23 14:27:28 osmc systemd-remount-fs[378]: mount: / not mounted or bad option
Jun 23 14:27:28 osmc systemd-remount-fs[378]: In some cases useful info is found in syslog - try
Jun 23 14:27:28 osmc systemd-remount-fs[378]: dmesg | tail or so.
Jun 23 14:27:28 osmc systemd[1]: systemd-remount-fs.service: main process exited, code=exited, status=1/FAILURE
Jun 23 14:27:28 osmc systemd[1]: Failed to start Remount Root and Kernel File Systems.
Jun 23 14:27:28 osmc systemd[1]: Unit systemd-remount-fs.service entered failed state.


osmc@osmc:~$ sudo dmesg | tail
[    6.647463] systemd-journald[104]: Received request to flush runtime journal from PID 1
[    7.006000] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    7.006277] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    8.481383] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    8.483410] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[    8.506166] 8021q: 802.1Q VLAN Support v1.8
[  302.583756] EXT4-fs (mmcblk0p2): error count since last fsck: 4
[  302.583808] EXT4-fs (mmcblk0p2): initial error at time 1431854200: htree_dirblock_to_tree:896: inode 259667: block 1056753
[  302.583846] EXT4-fs (mmcblk0p2): last error at time 1431854201: htree_dirblock_to_tree:896: inode 259667: block 1056753
[  632.306914] EXT4-fs (mmcblk0p2): Couldn't remount RDWR because of unprocessed orphan inode list.  Please umount/remount instead

I’m happy to provide more information if someone can help get this working without a complete reinstall :slight_smile:

Edit: Replaced second image with better quality.

Edit 2: I suspect that we may have had a power cut today so it’s quite possible that power was lost unintentionally and suddenly. This makes me suspecious of some kind of filesystem corruption?

You definitely have file system corruption that is causing it to mount read only - as the dmesg above says.

Try booting up with shift held down - this should run a file system scan before dropping you to the recovery console, then type exit.

If you can’t do that, try running the following from ssh: (which should work as your file system is currently read only)

fsck /

What brand and model of SD card are you using ?


No attached keyboard so I used the SSH fsck option. It gave me 5-7 different errors, I just hit “y” to repair each one. Then a reboot, and everything seems to be working perfectly again.

@DBMandrake, you are an absolute champion. Thanks a lot!

Should I check anything else or am I safe to assume that everything is OK?

I am using the NOOBS 8GB MicroSD card, I think it’s a SanDisk.

The official 8GB noobs card I believe is a rebranded samsung card and is a good card.

I think you’ve just been unlucky and had a power cut at a bad moment when data was being written as I have pulled the power out of my test Pi 2 many times during development/testing work (while it was idle) and not suffered any corruption. (It’s certainly not recommended though!)

Yeah, I’ve inadvertently cut power to the unit several times before and never had any issues. I guess I got unlucky this time. A good reminder to do a full SD card image backup…

@DBMandrake Is it common when running fsck / to get several errors (like hundreds)?

Only if you are consistently allowing dirty shutdowns or have a near to failure SDcard.

Nothing in this thread is going to be particularly relevant after so long. If you are having a problem, it would be best to create a new and appropriately titled thread with relevant info for your problem.

@ActionA Then should I wait until the fsck -f -y / ends and backup the card immediately or just ctrl+c and backup the card?

I’d wait and see if fsck is successful.

I waited and got a warning saying the system still has some errors. However, the boot was successful but after 3~4 min the sd card was unmounted :frowning:

Any suggestion would be great!

Since you refuse to follow simple advise on how to best receive support, the only thing I will recommend will be replace your card and/or get a more suitable power supply.

I see that you flagged @ActionA’s post, saying that he does not ‘know how to interact on a public forum’. Please remember that OSMC moderators help other users in their own free time. They have absolutely no obligation to do so. To help us help you, you should read the Wiki and provide relevant information when necessary. When you signed up to this forum and before you made your first post, you clicked a box saying you had read the Wiki, yet you do not appear to have done so.

This is vague and does not provide insight in to what your problem actually is. This is akin to saying that your car does not start.

The moderator simply closed the thread, perhaps hoping that you start a new thread with more detailed information. If we are to discuss public forum etiquette, we should perhaps remark that it’s not good to resurrect a thread that is over a year old. You should start a new one, as you are not running a pre-release build of OSMC (which the thread was regarding) and your symptoms will almost certainly not be the same.

I already PMed you some advice, but you have not opened the message. This is more time spent resolving a question for which an answer is already available, instead of doing what I prefer, which is spending more time working on OSMC to make it better for everyone.


This is vague and does not provide insight in to what your problem actually is. This is akin to saying that your car does not start.

This was the output of the fsck command:

********** WARNING: Filesystem still has errors **********


Come back when you are willing to work with us.

Sure… This is an amazing software/community. I can’t wait to have another problem and post it.

I’m not sure you’ve read the Wiki or my PM offering advice. Come back when you are willing to work with us.