Debian fails to boot

satimis · 10-14-2012, 09:53 AM

Hi all,

Fedora 17 64bit
Debian 6.0.6 64bit
Dualboot

On Debian ran;
# apt-get -t squeeze-backports install linux-image-3.2.0-0.bpo.3-amd64 firmware-linux-free

Rebooted
New kernel not found on GRUB prompt only old kernel there

Code:

Linux version 2.6.32-5-amd64 (Debian 2.6.32-46)

Debian still can be booted.

Then on Fedora ran;
$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg

Rebooted and on GRUB prompt Debian new kernel was still not displayed. The new kernel was found under "Advanced Option" of Debian.

Started Debian with new kernel a black screen displayed finally. Pressed [Ctrl]+[Alt]+/F1/F2/F4 etc with no action.

Then forced-rebooted PC and booted Debian new kernel recovery mode. It was dropped to Shell.

Then I ran;
# blkid
found the device of Debian

# fsck -yf /dev/sda3 (device of Debian)

Rebooted.

Debian is now completely not shown up on GRUB prompt.

Please help. TIA

B.R.
satimis

Dutch Master · 10-14-2012, 09:28 PM

I understand you installed Debian first, then put Fedora next to it, correct? If so, this is essentially a Fedora issue

Key is that Fedora controls the Grub menu in that case, so when fsck has finished, run the update command for grub:

Code:

update-grub

Then, if you choose to have Grub controlled by Debian, install Grub from Debian with

Code:

grub-install /dev/sda

It's wise (but probably not necessary) to re-run the grub update command again. It reports the entries it has found, so you can take action before rebooting if something goes haywire

satimis · 10-14-2012, 11:07 PM

Quote:

Originally Posted by Dutch Master

I understand you installed Debian first, then put Fedora next to it, correct?

Yes,that is correct.

Quote:

If so, this is essentially a Fedora issue

Key is that Fedora controls the Grub menu in that case, so when fsck has finished, run the update command for grub:

Code:

update-grub

Now I can't start Debian any more. It is not displayed on GRUB prompt. Where shall I run "update-grub"?

Quote:

Then, if you choose to have Grub controlled by Debian, install Grub from Debian with

Code:

grub-install /dev/sda

It's wise (but probably not necessary) to re-run the grub update command again. It reports the entries it has found, so you can take action before rebooting if something goes haywire

I'll come to this step later.

Thanks

satimis

el chapulín · 10-15-2012, 03:44 AM

In a dual boot scenario only one of the installed OS can control the bootloader, so you don't need to install grub in both - just install it from the first OS on the disk and control it from there.

satimis · 10-15-2012, 03:52 AM

Quote:

Originally Posted by el chapulín

In a dual boot scenario only one of the installed OS can control the bootloader, so you don't need to install grub in both - just install it from the first OS on the disk and control it from there.

Please advise how can I correct it. I installed Debian first. I expect Debian to have grub installed there. Thanks

B.R.
satimis

Randicus Draco Albus · 10-15-2012, 05:24 AM

Quote:

Originally Posted by satimis

Please advise how can I correct it. I installed Debian first. I expect Debian to have grub installed there.

Dutch Master already gave you the reason.

Quote:

Key is that Fedora controls the Grub menu in that case, so when fsck has finished, run the update command for grub:

When you installed Fedora, you installed GRUB again (correct?). That means, at the moment it is Fedora's GRUB. You need to update it to include both systems.

el chapulín · 10-15-2012, 05:50 AM

Boot into fedora and try doing the following:

Code:

# os-prober
# update-grub

satimis · 10-15-2012, 07:21 AM

Quote:

Originally Posted by el chapulín

Boot into fedora and try doing the following:

Code:

# os-prober
# update-grub

# os-prober

Code:

  No volume groups found
/dev/sda5:Debian GNU/Linux (6.0.6):Debian:linux

# update-grub

Code:

bash: update-grub: command not found...

# yum install update-grub

Code:

Loaded plugins: langpacks, presto, refresh-packagekit
No package update-grub available.
Error: Nothing to do

Dutch Master · 10-15-2012, 07:27 AM

update-grub is not a program/package, it's part of Grub2, so you can't install it separately.

Code:

yum install grub2

Alternatively, boot a Knoppix CD and install Grub from there.

satimis · 10-15-2012, 07:53 AM

Quote:

Originally Posted by Dutch Master

update-grub is not a program/package, it's part of Grub2, so you can't install it separately.

Code:

yum install grub2

Alternatively, boot a Knoppix CD and install Grub from there.

# yum install grub2

Code:

Loaded plugins: langpacks, presto, refresh-packagekit
Package 1:grub2-2.0-0.38.beta6.fc17.x86_64 already installed and latest version
Nothing to do

# update-grub

Code:

bash: update-grub: command not found...

Quite strange ?

Previously I ran;
$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg

Code:

[sudo] password for satimis:
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.6.1-1.fc17.x86_64
Found initrd image: /boot/initramfs-3.6.1-1.fc17.x86_64.img
Found linux image: /boot/vmlinuz-3.5.6-1.fc17.x86_64
Found initrd image: /boot/initramfs-3.5.6-1.fc17.x86_64.img
Found linux image: /boot/vmlinuz-3.3.4-5.fc17.x86_64
Found initrd image: /boot/initramfs-3.3.4-5.fc17.x86_64.img
  No volume groups found
done

el chapulín · 10-15-2012, 10:15 AM

There is probably no "update-grub" script in fedora... so instead do it the manual way:

Code:

grub2-mkconfig -o /boot/grub2/grub.cfg

For some other distros it may be

Code:

grub-mkconfig -o /boot/grub/grub.cfg

This will regenerate the config.

Warning: When fiddling with bootloaders it's a good idea to have some kind of livecd handy to enable you to chroot into the system if it becomes unbootable.

satimis · 10-15-2012, 10:30 AM

Quote:

Originally Posted by el chapulín

There is probably no "update-grub" script in fedora... so instead do it the manual way:

Code:

grub2-mkconfig -o /boot/grub2/grub.cfg

# grub2-mkconfig -o /boot/grub2/grub.cfg

Code:

Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.6.1-1.fc17.x86_64
Found initrd image: /boot/initramfs-3.6.1-1.fc17.x86_64.img
Found linux image: /boot/vmlinuz-3.5.6-1.fc17.x86_64
Found initrd image: /boot/initramfs-3.5.6-1.fc17.x86_64.img
Found linux image: /boot/vmlinuz-3.3.4-5.fc17.x86_64
Found initrd image: /boot/initramfs-3.3.4-5.fc17.x86_64.img
  No volume groups found
Found Debian GNU/Linux (6.0.6) on /dev/sda5
done

Debian found

Quote:

For some other distros it may be

Code:

grub-mkconfig -o /boot/grub/grub.cfg

This will regenerate the config.

# ls /boot/grub/

Code:

splash.xpm.gz

No grub.cfg file there

Edit:
Rebooted PC

Debian is NOT showing up at GRUB prompt

satimis · 10-15-2012, 10:43 AM

Quote:

Originally Posted by el chapulín

In a dual boot scenario only one of the installed OS can control the bootloader, so you don't need to install grub in both - just install it from the first OS on the disk and control it from there.

Noted. Thank

During installation
- created LVM group
- created LVM partions taking up half HD space leaving the rest unused
- installed Debian
- installed Fedora on the unused space. But I was not allowed to create another LV group. The new LVM partitions still remained in the original LVM group