Problems with GRUB

  • azzapkp
Posted: Thu, 02/12/2009 - 06:06
Hello everyone! I am not new to linux or computer music but am new to Studio64. I have used Jacklab and Ubuntustudio for music, and alot of other distros for general use. Debian architecture is a bit new to me, as I have used mainly rpm systems so far. I have installed the 32bit version of 2.1 - at the end of the install when it tries to install the bootloader it refuses to comply. It gives a fatal error, I have tried various locations including floppy, but to no avail. So I just backed out and finished the installation. I checked md5sums, and re-burnt the disc at 1x and re-installed. I downloaded version 3.0 and couldn't even finish the install procedure (md5sum ok) I don't really wish to use the 3.0alpha but hoped to be able to get a bootable version with a grub I could keep. I am attempting to set it up in a multiboot environment with Ubuntu studio and CentOS; the existing GRUB is from the Ubuntu studio distro... so I attempted to edit the appropriate menu.lst. title Studio64 uuid 3e648608-9622-43bd-855d-ea0166a84e96 kernel vmlinuz-2.6.21-1-multimedia-486 # root=UUID=3e648608-9622-43bd-855d-ea0166a84e96 initrd initrd.img-2.6.21-1-multimedia-486 I used a UUID number as ' root (hd1,2)' couldn't find the partition, now I'm getting an error that the filename is not found. Can anyone provide a menu entry from a booting system please? I could then check my menu.lst and try again. From browsing the forum previously, I suspect that the version of grub I am using is incompatible with Studio64? Is there a version that would be more compatible that I can install? Thanks in advance, really excited about kicking some choons together!

And here mine

  • Pablo
  • 07/11/07
  • Thu, 02/12/2009 - 21:25
Hi azzapkp, As fas as I know, you can't assign a UUID name to the hd partition in the "root" line. You can use it as a substitution of /dev/sdax in the "kernel" line though. But never for (hdx,y). At least, I've never seen this. If I'm wrong, please tell me. Also, I've got the vmlinuz file inside /boot directory... But not Quentin. Check this. You can always edit the grub command and use TAB to autocomplete, and figure out. For example: grub>root hd( #TAB to get list of hard disks. Result: hd0, hd1, hd2. grub>root hd(2, #TAB to get lists of partitions with OS's. Result: hd(2,0) hd(2,4) grub>root hd(2,0) # so far so good grub>kernel /vm #TAB to get the vmlinuz file. Doesn't it autocomplete? Then try: grub>kernel /boot/vm #TAB to autocomplete. Now I have it! grub>kernel /boot/vmlinuz-2.6.21-1-multimedia-486 root=/dev/sda1 (#or by UUID if you wish) and here the options grub>initrd /boot/initrd.img-2.6.21-1-multimedia-486 grub>boot If it does work, copy the appropiate lines to the menu.lst. Here are my lines for the "normal" boot: title 64 Studio, kernel 2.6.21-1-multimedia-486 root (hd0,0) kernel /boot/vmlinuz-2.6.21-1-multimedia-486 root=UUID=12e3e8bc-a801xxxxxxxxxxxx ro quiet splash initrd /boot/initrd.img-2.6.21-1-multimedia-486 quiet As a side note, you'll already know, type: sudo fdisk -l to identify your hard disks and partitions. You can know the UUID by typing sudo vol_id -u /dev/sdax Cheers. Pablo

Hi guys, thanks for the

  • azzapkp
  • 02/12/09
  • Thu, 02/12/2009 - 22:17
Hi guys, thanks for the replies. I've had another run at it this morning, firstly I'll include the main part of my menu lst: title Ubuntustudio uuid 5451581c-edef-4647-ac2d-b97417b7fcd7 kernel /boot/vmlinuz-2.6.27.df003 root=UUID=5451581c-edef-4647-ac2d-b97417b7fcd7 ro quiet splash nohz=no initrd /boot/initrd.img-2.6.27.df003 quiet title CentOS Xen root (hd1,0) kernel /boot/xen.gz-2.6.18-92.1.18.el5 module /boot/vmlinuz-2.6.18-92.1.18.el5xen ro root=LABEL=/12 rhgb quiet module /boot/initrd-2.6.18-92.1.18.el5xen.img savedefault boot title Studio64 uuid 3e648608-9622-43bd-855d-ea0166a84e96 kernel /vmlinuz root=UUID=3e648608-9622-43bd-855d-ea0166a84e96 ro initrd /initrd.img Ubuntu studio boots fine, using the UUID. I got my UUID by typing blkid I have links under / to the kernel and initrd, which are in /boot. When I try to boot with the UUID number, I get Error 15: file not found. When I try Root (hd1, It lists possible partitions, but partition 2 is listed as FS type unkown. If I enter Root (hd1,2) and try to boot, I get Error 17: cannot mount selected partition Now I've just gone through my notes and there used to be an install of Solaris on that partition which worked fine, until I installed UbuntuStudio and the bootloader. A similar problem ocurred then. I never resolved it as I don't use Solaris these days. So now I'm figuring the bootloader won't access the partition for some reason. I'll look into that and see what I can find. I don't remember what version the previous bootloader was but I'm thinking that's where the problem lies

Hmmm... weird stuff

  • azzapkp
  • 02/12/09
  • Sun, 02/15/2009 - 06:53
Hmmm... weird stuff indeed. It appears that something to do with the way that disk was partitioned prevented me from booting into that partition. I installed onto another partition, grub installed fine, all up and running :) Can't boot into Ubuntu studio now :/ Centos boots fine. This gets me into 64studio to have a good look. So all good. Thanks for the replies

Here's mine

  • Quentin Harley
  • 05/24/07
  • Thu, 02/12/2009 - 08:29
Here are my entries for the 2.6.21 kernel - You obviously need to enter the correct UUID for your 64Studio partition in there... title 64 Studio, kernel 2.6.21-1-multimedia-amd64 Default (recovery mode) root (hd0,0) kernel /vmlinuz root=UUID={my-UUID} ro single initrd /initrd.img title 64 Studio, kernel 2.6.21-1-multimedia-amd64 root (hd0,0) kernel /vmlinuz-2.6.21-1-multimedia-amd64 root=UUID={my-UUID} ro quiet splash initrd /initrd.img-2.6.21-1-multimedia-amd64 quiet title 64 Studio, kernel 2.6.21-1-multimedia-amd64 (recovery mode) root (hd0,0) kernel /vmlinuz-2.6.21-1-multimedia-amd64 root=UUID={my-UUID} ro single initrd /initrd.img-2.6.21-1-multimedia-amd64 title 64 Studio, memtest86+ root (hd0,0) kernel /memtest86+.bin quiet