The blues

It began with me wanting to do some website editing with Bluefish on my Ubuntu laptop. It would clock but then would not actually start. I rebooted, restored Bluefish, and rebooted again all to the same result. I did a complete uninstall and noticed that my Bonager application was informing me that a file system check was due to be done on the next boot so I booted again.

* Checking root file system...
fsck 1.40.2 (12-Jul-2007)
os_part contains a file system with errors, check forced.
os_part: |==================================================| 100%

(there may have been more here but it rolled off the screen)

os_part Inode 131111300 has illegal blocks(s)

os_part: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck died with exit status 4

*An automatic file system check (fsck) of the root filesystem failed
A manual fsck must be performed, then the system restarted.
The fsck should be performed in maintenance mode with the
root filesystem mounted in read-only mode.
*The root filesystem is currently mounted in read-only mode.
A maintenance shell will now be started.
After performing system maintenance, press CONTROL-D
to terminate the maintenance shell and restart the system.
bash: no job control in this shell
bash: groups: command not found
bash lesspipe: command not found
bash: command: command not found
bash: The: command not found
bash: dircolors: command not found
bash: command: command not found
bash: The: command not found
root@dell:~#

I entered

root@dell:~# fsck /dev/sda6

fsck 1.40.2 (12-Jul-2007)
e2fsck 1.40.2 (12-Jul 2007)
os_part contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes

this ran for 10 minutes

Inode 131111300 has illegal blocks(s). Clear? yes

Illegal block #12 (247843560) in inode 131111300. CLEARED.

there were then 10 additional illegal blocks cleared

Too many illegal blocks in Inode 131111300.
Clear inode? yes

Restarting e2fsck from the beginning...
os_part contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes

after 15 minutes it got to

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

It threw some sort of error with a gazillion blocks and asked if I wanted to fix them

Free blocks count wrong for group #12804 (2, counted=1198).
Fix? yes

There were scores of these questions. I just held down the "Y" key for 40 seconds.

os_part: ***** FILE SYSTEM WAS MODIFIED *****
os_part: ***** REBOOT LINUX *****
os_part: 143595/14195712 files (5.9% non-contiguous), 20304605/113563452 blocks
root@dell:~#

A ctrl-d rebooted and the mess was apparently cleared up. OK, so where was I? Oh, yes. Bluefish. I tried re-installing aaaaaand. . . . it still won't run.