aptosid.com

Installation - from sidux to aptosid :Grub2 "verification" does n

Barlafuss - 19.09.2010, 15:57
Post subject: from sidux to aptosid :Grub2 "verification" does n
I did all the steps for switching to aptosid (with the exception of installing kernel-2.6.35, since I do it manually not by dist-upgrade) . Now I still can boot choosing from grub my old kernel 2.6.34, but if I try the first choice "Chainload into GRUB 2", system hangs and I can only reboot.
Pls see menu.lst/grub.cfg and grub2 images at:
http://www.esnips.com/web/aptosid/.

Is it supposed that choice "Chainload into GRUB 2" brings to boot the system or I'm misunderstanding completely the sense?

Thanks,
Barlafuss
muchan - 19.09.2010, 20:55
Post subject: RE: from sidux to aptosid :Grub2 "verification" do
      Quote:

Is it supposed that choice "Chainload into GRUB 2" brings to boot the system or I'm misunderstanding completely the sense?


Yes, it is.
In your uploaded file, Grub-legacy's menu-list calls
      Quote:

title Chainload into GRUB 2
root (hd1,0)
kernel /boot/grub/core.img


Here it seems identical to mine, except mine is (hd0,0).
Your sidux kernels are all on (hd1,0).
Ubuntu kernel on hd2 was not listed in menu.list.

At first glance I can't tell what is wrong. I'd first check if
/boot/grub/core.img file exists in the (hd1,0) = /dev/sdb1
Barlafuss - 20.09.2010, 17:21
Post subject: RE: from sidux to aptosid :Grub2 "verification" do
hi muchan, thanks for your replay.

Yes, /boot/grub/core.img file exists in the (hd1,0) = /dev/sdb1
      Code:
$df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1              29G  9.4G   19G  35% /
tmpfs                1013M     0 1013M   0% /lib/init/rw
udev                 1008M  212K 1008M   1% /dev
tmpfs                1013M  4.0K 1013M   1% /dev/shm

$ls /boot/grub/*.img
/boot/grub/boot.img    /boot/grub/core.img      /boot/grub/grldr.img   /boot/grub/lnxboot.img
/boot/grub/cdboot.img  /boot/grub/diskboot.img  /boot/grub/kernel.img  /boot/grub/pxeboot.img



I see it is a binary file, so not sure how to check it is OK.

Barlafuss
Barlafuss - 23.09.2010, 19:54
Post subject: RE: from sidux to aptosid :Grub2 "verification" do
Any idea how to fix this issue?
Otherwise I re-install completely grub-legacy, removing grub2, until I can stay with it.

Thanks,
Barlafuss
muchan - 23.09.2010, 21:41
Post subject: RE: from sidux to aptosid :Grub2 "verification" do
I can't say for sure, but before trying reinstall, at least worth trying
to update-grub (to partition, test, then to MBR...)

or, as bandaid but, you can manually edit menu.list of grub-legacy to boot
with the current kernel.
devil - 24.09.2010, 00:02
Post subject: RE: from sidux to aptosid :Grub2 "verification" do
sdb1, according to new grub2 denotation, would be (hd1,1)

greetz
devil
Barlafuss - 24.09.2010, 16:12
Post subject: RE: from sidux to aptosid :Grub2 "verification" do
@devil
yes I know, but (if this is the suggestion) changing
      Code:

title           Chainload into GRUB 2
root            (hd1,0)
kernel          /boot/grub/core.img

in
      Code:

title           Chainload into GRUB 2
root            (hd1,1)
kernel          /boot/grub/core.img


system answers it cannot find mountable partition (something like this ...) and hangs.

@muchan

      Quote:
at least worth trying
to update-grub (to partition, test, then to MBR...)


Already tried once, it "breaks" completely the boot - then I restored backup image-

I installed the last kernel.
These are the last rows of the post-install log
      Code:

Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.35-5.slh.3-aptosid-686
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.35-5.slh.3-aptosid-686 /boot/vmlinuz-2.6.35-5.slh.3-aptosid-686
run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.35-5.slh.3-aptosid-686 /boot/vmlinuz-2.6.35-5.slh.3-aptosid-686
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 2.6.35-5.slh.3-aptosid-686 /boot/vmlinuz-2.6.35-5.slh.3-aptosid-686
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.35-5.slh.3-aptosid-686
Found initrd image: /boot/initrd.img-2.6.35-5.slh.3-aptosid-686
Found linux image: /boot/vmlinuz-2.6.35-4.slh.9-aptosid-686
Found initrd image: /boot/initrd.img-2.6.35-4.slh.9-aptosid-686
Found linux image: /boot/vmlinuz-2.6.34-0.slh.11-sidux-686
Found initrd image: /boot/initrd.img-2.6.34-0.slh.11-sidux-686
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
  No volume groups found
  Found Ubuntu 6.10 (6.10) on /dev/sda3
  done


/boot/grub/menu.lst has been not updated, I did it manually, and then I rebooted in the new kernel, again via grub-legacy.

I do not understand why grub2 is not working on my linuxbox, it is nothing special ...

Thanks,
Barlafuss
muchan - 24.09.2010, 23:18
Post subject: RE: from sidux to aptosid :Grub2 "verification" do
About (hd1,0)=/dev/sdb1, this is still in Grub-legacy, about to chainload
to Grub2 on /deb/sdb1, so I think (hd1,0), aka, old notation, was right.

Now then question is if update-grub installed grub2 on the /deb/sdb1 partition...
Barlafuss - 27.09.2010, 17:04
Post subject: RE: from sidux to aptosid :Grub2 "verification" do
I tried to (re)install grub2 on /dev/sdb1 - supposing is not yet present -.
      Code:

$ sudo grub-setup --force /dev/sdb1
 
grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR.  This is a BAD idea..
grub-setup: warn: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..


Does it explains why I cannot boot with grub2?

Thanks,
Barlafuss
All times are GMT - 12 Hours
Powered by PNphpBB2 © 2003-2010 The Zafenio Group
Credits