Another UUID problem

[penguin.ch]

Re: Another UUID problem

CONTOL-D will terminate this shell and resume system boot.

Remove the "single" keyword from the according boot menu entry.

a last line in fstab. Whatever that means?

Add a new (read: empty) line to the end of the "fstab" in question.

/dev/hda8 is mounted. e2fsck: Cannot continue, aborting.

Such checks are to be conducted on unmounted file systems only.

So how do I repair what "manually"?

Read the according man page(s) and follow the advise given there.

[GANDOLF]

Re: Another UUID problem

Thanks rider.
Well I did steps 1-3.
No difference

The man pages were informative (thank you) but I am not sure as to which option to use -a or -y and if I have to do this at boot or from a terminal.

[GANDOLF]

Re: Another UUID problem

Okay I ran fsck -y /devhda8 from pclinuxos and got this:

[root@dhcppc0 ~]# fsck -y /dev/hda8
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
/dev/hda8 is mounted.

WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? yes

/dev/hda8: recovering journal
/dev/hda8: clean, 175080/951552 files, 1028679/1901686 blocks
[root@dhcppc0 ~]#


When I reboot into Feisty (hda8) I still get this error:

/dev/hda8 is mounted.e2fsck: cannot continue. aborting

fsck dies with exit status 8
and have to do ctrl-d to continue.

what am I doing wrong?

[nejode]

Re: Another UUID problem

GANDOLF:

About a month ago I had your same problem after installing Xubuntu to another partition on a test machine. The only way I could fix it was generatin new UUID's for all existing partitions and updating the /boot/grub/menu.lst and /etc/fstab accordingly. To generate the new UUID's you can use these commands:

1) blkid: ...will give you the UUID's of all your ext2/ext3 partitions.
2) vol_id -u /dev/hdXx: ...will display the UUID of that particular partition.
3) tune2fs -l /dev/hdXx | grep UUID: ...same as above

...hope it helps...

[GANDOLF]

Re: Another UUID problem

@nelode: Thanks did that feisty still wasn't happy.

Thanks guys/girls? for all the help. Well there was no way around it I just had to reinstall feisty.
The install went fine.

I imediately did the update and quess what? First synaptic told me that I had a problem with openoffice crystal theme. It refused to install a lot of tty fonts, and OO stuff, etc. If I would have known what would happen next I would have copied the error message. So I go to reboot and login into user but find out I cannot open any apps, no terminal, synaptic, konqueror, nada. JUust a jumping cursor.

So I reboot into recovery mode it loads into kde just fine but again no apps. NOTHING! The curser jumps up and down for a while but nothing loads.

Would someone tell me what this is about?

I like gutsy but I am not sure it is stable enough. Pclinuxos is fine but veery slow.

Do I go back to Drapper?? Edgy was not that great either.

One very upset trucker > >

[GANDOLF]

Re: Another UUID problem

Noone? I just read something about OO acting up after todays update. So I guess I'll wait for a while to update. I do need to work, and pclinux is slow.