I was running a debug symbols tool for kdenlive, to get a backtrace for a software crash. Replicated the crash but then the system froze. Decided to hard shutdown the machine and now I'm stuck in the above loop.
On boot I get the following:
/scripts/local-premount/resume: line 73: wait-for-root not found
/init: line 73: wait-for-root: not found
/init: line 872: logsave: Text file busy
The root system filesystem on /dev/sda2 requires a manual fsck
BusyBox v1.30.1 (Ubuntu 1:130.1-7ubuntu3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
At this point I followed the steps in the most related topic on here:
(initramfs) fsck -yf /dev/sda2
fsck from util-linux 2.37.2
Pass 1: Checking inodes, blocks and size
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda2: 991851/14188544 files (2.2% non-contiguous), 34066185/56737024 blocks
(initramfs) _
I think when I first ran this there was more output with a lot of yes, but now it runs and then stops on the flash cursor.
If I try exit it repeats the same message about logsave: Text file busy.
I've tried running ps to see if there's a process running called logsave and there doesn't appear to be. I'm guessing that the debug tool crashed and it's still trying to write output somewhere but I can see how to tell it to not?
Pretty sure the program was called dbg but couldn't see that in the process list either.
Not sure what to do at this stage, is my hard drive basically screwed?
If I can get hold of a boot CD tomorrow what would you recommend my next steps to be?
UPDATE: I saw another post which recommended trying an older kernel from the boot option at the Grub menu, that got me into the OS but on reboot it puts me back into the above loop.
Maybe there's something I can whilst back in the OS?
