[SOLVED] fsck error 8

[jmadero]

Hi All,

I've gotten this error every time I've installed over the past couple weeks (I've installed Ubuntu about 4 times and Kubuntu probably 10....kde 4 bugs....) so here is what happens:

When I install the first OS (dual booting Ubuntu/Kubuntu) everything works fine. Then when I install the second one the first one gets corrupted somehow, when I choose it from the Grub menu it spits out this error

fsck 1.41.3 (12-Oct-200
/dev/sda5: clean, 23455/5316608 files, 11817126/21239930 blocks
fsck.ext3: Unable to resolve 'UUID=55d4d337-488d-45dc-8110-e7a62a2d1720'
fsck died with exit status 8

This happens regardless if I install Ubuntu or Kubuntu first (I prefer Ubuntu being installed second because I like Grub auto updating my Ubuntu and I haven't figured out how to make it auto update both).

Any ideas what's causing this? I have checked the UUID vs what's listed with ls and it's the same. my /dev/sda5 is swap, but it's still swap on after I boot into the OS's (the error spits out something like "push cntrl+d to continue" when I do that it boots with no problem). The second OS installed doesn't have the issue at all.

Thanks all. Let me know if I can post any more details or outputs.

[D-cat]

This is odd behavior. fsck doesn't handle swap partitions; if you want to check it, you use mkswap -c (device) . I'd check with fdisk -l to make sure the partition designation is correct. Then I'd check the /etc/fstab to again make sure the designations are correct (and maybe if exist replace the UUID token with the /dev/sda5).

Good Luck.

[jmadero]

I lied, it's my home folder. I have two users, one for gnome and the other for kde so it shouldn't be crossing over at all. I have started with new users when I install again and it doesn't help the problem at all. Also I have replaced the UUID with the device and that doesn't help anything. Any other suggestions. I appreciate the advice, this is a bit frustrating having to do cntrl+d every time I want to boot my non main OS

[D-cat]

Hmmm, it has to be getting the (apparently obsolete) UUID number from somewhere.

We can find out what it's supposed to be with ls -l /dev/disk/by-uuid

As far as where it's coming from, I've been poking around in the scripts and I'm not coming up with anything useful. I might be able to stop the Ctrl-D thing by cheating, but I'm not seeing the right way to solve it yet.

You know, I'm finding this use of UUID's seems to break more things than it's meant to solve.

edit: Also try sudo vol_id /dev/sda5 . I'd also like to see the current /etc/fstab.

[jmadero]

lrwxrwxrwx 1 root root 10 2009-02-09 21:31 0c0cecf7-cd52-4016-8744-c47903b4d464 -> ../../sda1
lrwxrwxrwx 1 root root 10 2009-02-09 21:31 68910a81-8c2c-4d06-9e0b-5660346c3f74 -> ../../sda5
lrwxrwxrwx 1 root root 10 2009-02-09 21:31 71e25d47-dc45-48fe-a292-38e6bc00230e -> ../../sda2
lrwxrwxrwx 1 root root 10 2009-02-09 21:31 970f6aa6-059a-42df-a291-34837ab830e8 -> ../../sda6







ID_FS_TYPE=ext3
ID_FS_VERSION=1.0
ID_FS_UUID=68910a81-8c2c-4d06-9e0b-5660346c3f74
ID_FS_UUID_ENC=68910a81-8c2c-4d06-9e0b-5660346c3f74
ID_FS_LABEL=
ID_FS_LABEL_ENC=
ID_FS_LABEL_SAFE=




Thanks a lot for putting the time into this. I've dual booted before and never seen this problem but....each time is a new experience

[jmadero]

So weird....it was /dev/sda1 not /dev/sda5 that was screwed up. The UUID was wrong, I compared fstabs and saw the problem immediately. It's fixed Thanks for all the help