Clock skew and filesystem checks on RPi

[Chymera]

Hello, something happened to my rpi during a world update (I am thinking someone might have unplugged it) and now I am having trouble getting back into my system. I am getting a number of errors at boot, and then am forced to boot in read-only mode.

Here's a screenshot of what happens at boot. I think the crux of the matter is the clock skew and the failed fsck.

On my RPi, I have tried:

• Setting the clock with date and saving with

  Code:

  /lib/rc/sbin/swclock --save

  
  
• Remounting with

  Code:

  mount -o remount,rw /

  
  
• Rebooting without fsck via

  Code:

  shutdown -f

  
  
• Running fsck manually
  
• Setting swclock to the sysinit runlevel (currently it is on the boot runlevel, and it may or may not be run before fsck)
  
• Combinations of the above
  

Generally speaking, not matter what changes I made to the system - even if they seem to be written in the session in which I make them, disappear after I reboot the rpi.


I have also tried taking the card out, plugging it into another machine, and running fsck from there. That gives me an entirely different error:

[bbgermany]

Hi,

i have swclock in runlevel default. You should try starting it before a shutdown. Also try to get the time via ntp or even run a ntpd on the rpi:

[Irre]

I think your ext4 file system is corrupt. If possible remove SD-card and try to run fsck from another system (/dev/mmcblk0p2 ). I gave up linux on SD-cards (except the boot partition, mounted ro). Linuxes on external USB-disks work fine for me.