Hmm ... the plot thickens.
At the time I had not yet run fsck on the / fs. For whatever reason the crash took place, inc. the state of the fs, it seems it was remounted as ro when it errored out.
This is what it looks like presently:
Code:
root@mutant51:~# mount
/dev/mmcblk0p3 on / type ext4 (rw,relatime,data=ordered)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=190260k,nr_inodes=47565,mode=755)
tmpfs on /media type tmpfs (rw,relatime,size=64k)
/dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
tmpfs on /var/volatile type tmpfs (rw,relatime)
/dev/sda1 on /media/hdd type ext4 (rw,relatime,data=ordered)
/dev/sdb1 on /media/usb type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
/etc/auto.network on /media/autofs type autofs (rw,relatime,fd=6,pgrp=2100,timeout=5,minproto=5,maxproto=5,indirect)
However, the file it is looking for above is no where to be found?
Code:
root@mutant51:~# ls -la /etc/enigma2/timers.xml.writing
ls: /etc/enigma2/timers.xml.writing: No such file or directory
root@mutant51:~# ls -la /etc/enigma2/timers.xml
-rw-r--r-- 1 root root 32952 Feb 7 14:05 /etc/enigma2/timers.xml