Firstly, Thank you Mathias for the help.
I fsck'ed the piratebox's filesystem, however the problem persisted.
e2fsck 1.42.13 (17-May-2015)
/dev/loop0: recovering journal
/dev/loop0: clean, 1075/25688 files, 33802/102400 blocks
So I went on to resintall the lighttpd, but my setup has no /mnt/install/cache/, and I didn't find any package cache elsewhere.
I will reinstall the piratebox, but what I am more concerned is on why this has been happening. I wonder if that's due to an unstable power supply, as the flash drive stays plugged to the box the whole time.
But thank you anyway. It was a great help.
I've just found out. This is the one available for download in the librarybox website for this router's model. I am running piratebox with the librarybox configuration.Quote
oh, you are using the development version? Interesting
Based on that message, I suppose the filesystem became corrupt. That happens. However, what bugs me is that, for the second time having this same problem, lighttpd is the service that stops working. I wonder if anyone has experienced this kind of problem.Quote
The problem is a problem of the ext. device, exactly shown in this line
I fsck'ed the piratebox's filesystem, however the problem persisted.
Output:Quote
3. The output shows the device node, run fsck.ext4 against it
e2fsck 1.42.13 (17-May-2015)
/dev/loop0: recovering journal
/dev/loop0: clean, 1075/25688 files, 33802/102400 blocks
So I went on to resintall the lighttpd, but my setup has no /mnt/install/cache/, and I didn't find any package cache elsewhere.
I will reinstall the piratebox, but what I am more concerned is on why this has been happening. I wonder if that's due to an unstable power supply, as the flash drive stays plugged to the box the whole time.
But thank you anyway. It was a great help.