/var/log/boot.0 has
Code: Select all
Fri Apr 15 18:58:35 2011: Checking file systems...fsck from util-linux-ng 2.17.2
Fri Apr 15 18:58:35 2011: fsck.ext3: No such file or directory while trying to open /dev/hda4
Fri Apr 15 18:58:35 2011: /dev/hda4:
Fri Apr 15 18:58:35 2011: The superblock could not be read or does not describe a correct ext2
Fri Apr 15 18:58:35 2011: filesystem. If the device is valid and it really contains an ext2
Fri Apr 15 18:58:35 2011: filesystem (and not swap or ufs or something else), then the superblock
Fri Apr 15 18:58:35 2011: is corrupt, and you might try running e2fsck with an alternate superblock:
Fri Apr 15 18:58:35 2011: e2fsck -b 8193 <device>
Fri Apr 15 18:58:35 2011:
Fri Apr 15 18:58:35 2011: fsck died with exit status 8
Fri Apr 15 18:58:35 2011: ^[[31mfailed (code 8).^[[39;49m
Fri Apr 15 18:58:35 2011: File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ... ^[[31mfailed!^[[39;49m
Fri Apr 15 18:58:35 2011: A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ... ^[[33m(warning).^[[39;49m
Fri Apr 15 18:58:35 2011: Give root password for maintenance
Fri Apr 15 18:58:35 2011: (or type Control-D to continue):
Fri Apr 15 18:59:05 2011: ^[[01;31mroot@bikertest3^[[00m:^[[01;34m~^[[00m# reboot
Code: Select all
Log of fsck -C -R -A -a
Fri Apr 15 20:02:03 2011
fsck from util-linux-ng 2.17.2
/dev/hda4: clean, 3000/1463504 files, 234147/5853684 blocks (check after next mount)
Fri Apr 15 20:02:03 2011
Code: Select all
Log of fsck -C -a -t ext3 /dev/hda3
Fri Apr 15 20:02:03 2011
fsck from util-linux-ng 2.17.2
/dev/hda3: clean, 107399/408800 files, 705865/1632605 blocks (check after next mount)
Fri Apr 15 20:02:03 2011
Code: Select all
harry@bikertest3:~$ ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 Apr 15 2011 1A20A02E20A01335 -> ../../hda1
lrwxrwxrwx 1 root root 10 Apr 15 2011 38d34375-a4c6-4fda-bcc7-736eeb487061 -> ../../hda5
lrwxrwxrwx 1 root root 10 Apr 15 2011 4135d1be-5d75-40b1-bf22-77fca31c6960 -> ../../hda4
lrwxrwxrwx 1 root root 10 Apr 15 2011 4B5F-B945 -> ../../hda7
lrwxrwxrwx 1 root root 10 Apr 15 2011 8636ecf8-4f87-4b70-94a0-5a559c4029f1 -> ../../hda3
lrwxrwxrwx 1 root root 10 Apr 15 2011 93317189-8b9c-440a-9224-0799fa567f9b -> ../../hda6
Code: Select all
title antiX at hda3, kernel 2.6.32-1-mepis-smp
root (hd0,2)
kernel /boot/vmlinuz-2.6.32-1-mepis-smp root=/dev/hda3 nomce quiet nosplash vga=normal
initrd /boot/initrd.img-2.6.32-1-mepis-smp
boot
###UUID KERNEL ENTRIES BELOW######
title Debian GNU/Linux, kernel 2.6.32-1-mepis-smp
root (hd0,2)
kernel /boot/vmlinuz-2.6.32-1-mepis-smp root=UUID=8636ecf8-4f87-4b70-94a0-5a559c4029f1 ro nosplash quiet
initrd /boot/initrd.img-2.6.32-1-mepis-smp
title Debian GNU/Linux, kernel 2.6.38-2.dmz.2-liquorix-686
root (hd0,2)
kernel /boot/vmlinuz-2.6.38-2.dmz.2-liquorix-686 root=UUID=8636ecf8-4f87-4b70-94a0-5a559c4029f1 ro nosplash quiet
initrd /boot/initrd.img-2.6.38-2.dmz.2-liquorix-686
so kinda stymied with this. Older liqourix or even Stevos 2.6.34 vanilla kernel gives me the same symptoms. Am I missing the rattle snake sitting in front of me (old country boy saying when the answer in so obvious if it was a snake it would have bit ya). __{{emoticon}}__
Ya know. I haven't tried booting the Debian GNU/Linux, kernel 2.6.32-1-mepis-smp UUID entries yet. Edit: Booted up OK so scratch the Maybe they are no good also. Because antiX at hda3, kernel 2.6.32-1-mepis-smp boots just fine. This has been a ongoing problem with me and AntiX 11 Tests I have done on this Laptop. When I ran 8.5. Stevos vanilla kernel ran OK on this laptop. But not with AntiX 11 (previous tests only).
I don't think this is a /boot/grub/menu.lst problem. Seems more file and kernel related than anything. __{{emoticon}}__