Don't know quite what to title this one.
Since I left my computer off for a while without a keyboard, it has developed a strange sympton.
If I boot by picking my /dev/sdb1 system as the default OS in grub and booting that, it hangs with a big blue Kubuntu page. If I connect via the recovery mode of the same system, I can connect. So I change the grub default OS by modifying only GRUB_DEFAULT to a value of 4 (maybe any non-zero value would work), do an update-grub, then reboot and select manually the /dev/sdb1 system (not the recovery mode), it shows me the same screen, but then changes to the normal login screen and everything works.
If I put the default system back on /dev/sdb1, it hangs again.
This is Lucid with Grub2.
One other thing. The rescue disk with rescuecd does not boot the system: I have to use the alternate rescuecd. I have no idea what the difference may be.
What in the world could this be due to. Has grub stopped liking the default OS somehow?
Since I left my computer off for a while without a keyboard, it has developed a strange sympton.
If I boot by picking my /dev/sdb1 system as the default OS in grub and booting that, it hangs with a big blue Kubuntu page. If I connect via the recovery mode of the same system, I can connect. So I change the grub default OS by modifying only GRUB_DEFAULT to a value of 4 (maybe any non-zero value would work), do an update-grub, then reboot and select manually the /dev/sdb1 system (not the recovery mode), it shows me the same screen, but then changes to the normal login screen and everything works.
If I put the default system back on /dev/sdb1, it hangs again.
This is Lucid with Grub2.
One other thing. The rescue disk with rescuecd does not boot the system: I have to use the alternate rescuecd. I have no idea what the difference may be.
What in the world could this be due to. Has grub stopped liking the default OS somehow?
Comment