@fizze wrote:
nah, the logfile is /var/log/messages.
you have to tail its output as root via telnet or ssh, preferably.Anywho, you can just leave that file alone there, and adjust the db_dir in firefly’s webinterface or the config file manually.
I advise to use joe, or just copy the file over to a PC and use $favorite_unix_capable_editor [1] to adjust and then copy it back.
What does e2fsck tell you if you run it on the usb stick?
It gives a warning that its not wise to use on a mounted device, but since you dont really have a choice you have to do it anyway.
There is a mode where it actually doesnt fix anything, but reports errors.[1]wyoedit, ultraedit, textpad32, etc.
That’s good advice. If it’s just one bad block on the stick, just forget about it. Leave the dead journal sitting on the flask, occupying the bad block. Then move db_dir to the hard drive and you should be good.
It will re-create the database when it starts, so it should be okay.
— Ron