I managed to damage fsck... or at least I think it is, it gives a serious warning.

I wanted to remove an partition I didn't use anymore with QTParted. That went well, without any problem. The partition were removed, as I wanted.

However, on the next boot, fsck gave me an error and died with status 8.

This is /var/log/fsck/checkfs:
The symptoms are:
- At boot, I get an error message, after which a maintenance shell is started. I enter 'exit' and boor resumes as normal.
- Reading from removable devices can be messy. Reading from CD-ROM causes the drive to make strange noises, while nothing is read anymore. USB storage media doesn't work.
- Maybe more, that's all I noticed so far.

Since I couldn't find the problem, and had better things to do, I continued. Later, I made the Ubuntu partition (which is, with swap, the only one I left) larger to fill the entire hard disk. I did this with the Ubuntu live-cd, as I had no Knoppix near me.

It didn't affect the problem, but the partition was resized successfully.

Once booted, Linux works as normal (except for above mentioned symptoms) and I can do anything I want.

However, it's starting to be very annoying. Especially in class (it's a laptop), when other people see the error too.

Not sure about some of those symptoms, but as for fsck complaining: edit /etc/fstab and remove the entry for the partition you removed.

Wow, that was easy... it's solved now, thanks.

However, the USB stick still doesn't work. I'll try it out on another computer, maybe it's damaged.

After installing Hardy Alpha2, I got 'fsck died with exit status 8' whenever I tried to boot any pre-existing linux partition on my machine. The source of the complaint was in trying to mount the new hardy partition. If this sounds like you, you might try this seemingly pointless yet effective method:

- #ed
this opens a text editor
- alt+sysreq+k
this kills the text editor, and magically sends you on your way to your desktop. wow.

Now you can go into etc/fstab and comment out the reference to the hardy partition. I did, and the partition booted normally upon restart.

Hope this helps.

i used


to get the right UUID's

and then change them using

to correct it.

In my case I had an extra UUID that was causing the confusion in my system