Olá meus caros companheiros...
ps.: não sou petista não!!!
Como solucionar o conflito descrito abaixo?
+ Este é o meu /boot/grub/menu.list +
*******************************************************************************
# menu.lst - See: grub(
, info grub, update-grub(
# grub-install(
, grub-floppy(
,
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#
#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hda5 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,4)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single
## nonaltoption boot targets option
## This option controls options to pass to only the
## primary kernel menu item.
## You can have ONLY one nonaltoptions line
# nonaltoptions=quiet splash
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## ## End Default Options ##
title Ubuntu, kernel 2.6.12-10-386
root (hd0,4)
kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/hda5 ro quiet splash
initrd /boot/initrd.img-2.6.12-10-386
savedefault
boot
#title Ubuntu, kernel 2.6.12-10-386 (recovery mode)
root (hd0,4)
kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/hda5 ro single
initrd /boot/initrd.img-2.6.12-10-386
boot
#title Ubuntu, kernel 2.6.12-9-386
root (hd0,4)
kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/hda5 ro quiet splash
initrd /boot/initrd.img-2.6.12-9-386
savedefault
boot
#title Ubuntu, kernel 2.6.12-9-386 (recovery mode)
root (hd0,4)
kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/hda5 ro single
initrd /boot/initrd.img-2.6.12-9-386
boot
#title Ubuntu, memtest86+
root (hd0,4)
kernel /boot/memtest86+.bin
boot
### END DEBIAN AUTOMAGIC KERNELS LIST
# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/hda8.
#title Kurumin (on /dev/hda8)
root (hd0,7)
kernel /boot/vmlinuz-2.6.8.1-kanotix-10 root=/dev/hda8 ro append = "splash=silent apm=power-off nomce quiet devfs=mount
initrd /boot/initrd-ksplash
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/hda8.
#title memtest86 (on /dev/hda8)
root (hd0,7)
kernel /boot/memtest86.bin root=/dev/hda8 ro append = "splash=silent apm=power-off nomce quiet devfs=mount
savedefault
boot
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Microsoft Windows XP Professional
root (hd0,0)
savedefault
makeactive
chainloader +1
*************************************************************************************************************
Como percebe-se, eu tenho o Windows + o Ubuntu, sendo este último o sistema padrão no Grub.
no hda8, tinha instalado o Kurumim, mas não conseguia acessá-lo quando escolhia no menu do Grub.
Comentei as linhas referentes à esta partição e ao Memtest no Grub para não serem listadas na inicialização e, posteriormente, através do GPARTED, converti a partição " /dev/hda8 - Kurumin, para Fat 32, apagando todos os dados da mesma.
Agora qaundo inicializo o sistema, o Grub informa esta MENSAGEM, que, eu até consigo entender, mas não sei como resolver.
Segue exatamente o que aparece na inicialização e onde para :
* Checking allfiles systems...
fsck ext3:Bad magic number in super-block while trying to open /dev/hda8 /devhda8:
The superblock could not be read or does not discribe a correct ext2 filesystem. If the
device is valid and it really contains an ext2 filesystem, them the superblock is corrupt,
an you might try running e2fsck with an alternate superblock:
e2fsck - b 8193 <device> [fail]
* fsck failed. Please repair manually.
* CONTROL-D will exit from the shell an continue system startup
root(nome)~#
:::::::: Como já disse, entendo que talvez o grub não identifique corretamente o /hda8.
Consigo iniciar osistema com o ctrl +D, porém, imagino que haja uma solução!
Como solucionar sem ter que, talvez, reinstalar novamente o Ubuntu?
Lembrando que tenho o Windows também.
:::::::::::
Por enquanto, abraços e aguardo orientação de como resolver este conflito.
abçs,
Reinaldo