grub error 22
Hello, I powered on my lenny amd64 box this morning and I get GRUB loading, Error 22, and hangs. However! If I put in a live cd, for instance the ubuntu amd64 live cd, and then choose Boot from first hard drive from the list, then grub boots no problem and the computer runs as usual. So grub must be configured wrong and it doesn't find the right partition or device. Or the devices are named differently or something. So I thought this might have something to do with Lennart Sorensen's email on this list, with the subject SCSI Device Addresses. However, I go to this page http://people.debian.org/~terpstra/list/debian-amd64.en.html click on Lennart's email, and a blank page appears. I am using firefox, but I tried with galeon and konqueror. Blank page. So even though this issue might have been resolved, I can't read the mailing list. So is this related to a SCSI device naming bug or something? What's the fix? Thank you for your assistance. -- Alexandru I. Cabuz Tel: +44 (0)753.471.8031 --- Please no Word or Powerpoint attachments. Send plain text, rich text format, html, or pdf instead. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub error 22
On Sat, 17 May 2008 12:40:11 +0200, Alexandru Cabuz wrote: So is this related to a SCSI device naming bug or something? What's the fix? If you provide: # fdisk -l $ cat /boot/grub/device.map it will be much easier to help you. Try reinstalling grub, also, with # grub-install /dev/XXX where /dev/XXX is your boot device. -- Best Regards, Jack Linux User #264449 Powered by Debian GNU/Linux on AMD64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fwd: grub error 22
fdisk -l gives Disk /dev/sda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x Device Boot Start End Blocks Id System /dev/sda1 * 1 49 393561 83 Linux /dev/sda2 50 30401 2438024405 Extended /dev/sda5 501265 9767488+ 83 Linux /dev/sda612661751 3903763+ 83 Linux /dev/sda717522237 3903763+ 82 Linux swap / Solaris /dev/sda822382359 979933+ 83 Linux /dev/sda92360 30401 225247333+ 83 Linux Disk /dev/sdb: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xd03fd03f Device Boot Start End Blocks Id System /dev/sdb1 1 19457 156288321 83 Linux device.map contains (hd0) /dev/sda I tried reinstalling grub. grub-install /dev/sda It reinstalls without error, but same result. Error 22. -- Alexandru I. Cabuz Tel: +44 (0)753.471.8031 --- Please no Word or Powerpoint attachments. Send plain text, rich text format, html, or pdf instead. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub error 22
On Sat, May 17, 2008 at 4:30 PM, Alexandru Cabuz [EMAIL PROTECTED] wrote: device.map contains (hd0) /dev/sda I tried reinstalling grub. grub-install /dev/sda It reinstalls without error, but same result. Error 22. Did you search for error 22? After 2 minutes on google I've found this: Quoted from the GNU/GRUB manual 22 : No such partition This error is returned if a partition is requested in the device part of a device- or full file name which isn't on the selected disk. You should post your menu.lst file if you want more help. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub error 22
Yes, I did search for error 22. That's why I thought it might be a problem with the names of the partitions because the partition *is* there, it's not corrupted, it's readable and, like I said above, the system *does* boot just fine, but only if I put in a live cd (ubuntu in this case) and when the little menu comes up(choose to boot ubuntu live, install ubuntu, or boot from first hard drive) choose to boot from the first hard drive. I am actually writing this email from the running system so clearly there is no problem with the partitions. menu.lst is this: # menu.lst - See: grub(8), info grub, update-grub(8) #grub-install(8), grub-floppy(8), #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'. # WARNING: If you are using dmraid do not change this entry to 'saved' or your # array will desync and will not let you boot your system. default 0 ## timeout sec # Set a timeout, in SEC seconds, before automatically booting the default entry # (normally the first entry defined). timeout 5 # 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 # 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 specific 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_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=/dev/sda1 ro quiet ## default grub root device ## e.g. groot=(hd0,0) # groot=(hd0,0) ## 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 ## additional options to use with the default boot option, but not with the ## alternatives ## e.g. defoptions=vga=791 resume=/dev/hda5 # defoptions= ## should update-grub lock old automagic boot options ## e.g. lockold=false ## lockold=true # lockold=false ## Xen hypervisor options to use with the default Xen boot option # xenhopt= ## Xen Linux kernel options to use with the default Xen boot option # xenkopt=console=tty0 ## altoption boot targets option ## multiple altoptions lines are allowed ## e.g. altoptions=(extra menu suffix) extra boot options ## altoptions=(single-user) single # altoptions=(single-user mode) single ## 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 ## should update-grub adjust the value of the default booted system ## can be true or false # updatedefaultentry=false ## should update-grub add savedefault to the default options ## can be true or false # savedefault=false ## ## End Default Options ## title Debian GNU/Linux, kernel 2.6.24-1-amd64 root(hd0,0) kernel /boot/vmlinuz-2.6.24-1-amd64 root=/dev/sda1 ro quiet initrd /boot/initrd.img-2.6.24-1-amd64 title Debian GNU/Linux, kernel 2.6.24-1-amd64 (single-user mode) root(hd0,0) kernel /boot/vmlinuz-2.6.24-1-amd64 root=/dev/sda1 ro quiet single initrd /boot/initrd.img-2.6.24-1-amd64 ### END DEBIAN AUTOMAGIC KERNELS LIST -- Alexandru I. Cabuz Tel: +44 (0)753.471.8031 --- Please no Word or Powerpoint attachments. Send plain text, rich text format, html, or pdf instead. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub error 22
Alexandru, On Sat 17 May 2008 13:21, Alexandru Cabuz wrote: Yes, I did search for error 22. That's why I thought it might be a problem with the names of the partitions because the partition *is* there, it's not corrupted, it's readable and, like I said above, the system *does* boot just fine, but only if I put in a live cd (ubuntu in this case) and when the little menu comes up(choose to boot ubuntu live, install ubuntu, or boot from first hard drive) choose to boot from the first hard drive. I am actually writing this email from the running system so clearly there is no problem with the partitions. Two more questions: 1) Have you changed anything recently? Installed or deleted any programs or upgraded the BIOS? Have you made any physical changes to your system, e.g. installed a new hard drive or recabled your hard drives? Is it possible that your hard drive is failing? 2) According to your menu.lst file, both your kernel image and your root directory are in your first partition (sda1). Is this correct, or do you have /boot in your first partition and root in another (or some variation of this)? HTH! cmr menu.lst is this: # menu.lst - See: grub(8), info grub, update-grub(8) #grub-install(8), grub-floppy(8), #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'. # WARNING: If you are using dmraid do not change this entry to 'saved' or your # array will desync and will not let you boot your system. default 0 ## timeout sec # Set a timeout, in SEC seconds, before automatically booting the default entry # (normally the first entry defined). timeout 5 # 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 # 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 specific 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_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=/dev/sda1 ro quiet ## default grub root device ## e.g. groot=(hd0,0) # groot=(hd0,0) ## 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 ## additional options to use with the default boot option, but not with the ## alternatives ## e.g. defoptions=vga=791 resume=/dev/hda5 # defoptions= ## should update-grub lock old automagic boot options ## e.g. lockold=false ## lockold=true # lockold=false ## Xen hypervisor options to use with the default Xen boot option # xenhopt= ## Xen Linux kernel options to use with the default Xen boot option # xenkopt=console=tty0 ## altoption boot targets option ## multiple altoptions lines are allowed ## e.g. altoptions=(extra menu suffix) extra boot options ## altoptions=(single-user) single # altoptions=(single-user mode) single ## 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 ## should update-grub adjust the value of the default booted system ## can be true or false # updatedefaultentry=false ## should update-grub add savedefault to the default options ## can be true or false # savedefault=false ## ## End Default Options ## title Debian GNU/Linux, kernel 2.6.24-1-amd64 root (hd0,0) kernel
Re: grub error 22
I guess the one major thing I modified recently is to change the default runlevel in /etc/inittab from 2 to 5. For some reason gdm was not starting automatically when booting up. I would always get dropped to a terminal login, and then I would become root and run gdm and it would start without a problem. Changing the default runlevel fixed that and for about a week things went fine, until I got this error 22 this morning. Other than that I have changed nothing other than apt-get update apt-get dist-upgrade There is a possibility the hard drive might be failing. But there is no other sign of it. I'm going to run a fsck on the root partition to see if anything is wrong with it. And yes, / and /boot are on the same partition, the /dev/sda1. Thank you. -- Alexandru I. Cabuz Tel: +44 (0)753.471.8031 --- Please no Word or Powerpoint attachments. Send plain text, rich text format, html, or pdf instead. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian and cuda....
I read about GPUs nvidia and CUDA etc a bit on the web. I found out that CUDA is supposed to work in Linux and nosed around and saw that there is some sort of implementation of it for Ubuntu http://www.nvidia.com/object/cuda_get.html Unless you are developing an application that needs full access to the nvidia instruction set there is no need to worry about the very platform specific CUDA. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub error 22
Alexandru, On Sat 17 May 2008 14:05, Alexandru Cabuz wrote: I guess the one major thing I modified recently is to change the default runlevel in /etc/inittab from 2 to 5. For some reason gdm was not starting automatically when booting up. I would always get dropped to a terminal login, and then I would become root and run gdm and it would start without a problem. Changing the default runlevel fixed that and for about a week things went fine, until I got this error 22 this morning. Other than that I have changed nothing other than apt-get update apt-get dist-upgrade By any chance, did you do a dist-upgrade from Lenny to Sid? If so, then this GRUB bug might be the problem: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475958 In any case, it's beginning to sound like a GRUB bug. You might want to check the rest of the bug reports listed. HTH! cmr There is a possibility the hard drive might be failing. But there is no other sign of it. I'm going to run a fsck on the root partition to see if anything is wrong with it. And yes, / and /boot are on the same partition, the /dev/sda1. Thank you. -- Alexandru I. Cabuz Tel: +44 (0)753.471.8031 --- Please no Word or Powerpoint attachments. Send plain text, rich text format, html, or pdf instead. See http://www.gnu.org/philosophy/no-word-attachments.html -- Debian 'Etch' - Registered Linux User #241964 More laws, less justice. -- Marcus Tullius Ciceroca, 42 BC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: debian and cuda....
Date: Sat, 17 May 2008 15:06:38 -0400 From: [EMAIL PROTECTED] To: debian-amd64@lists.debian.org Subject: Re: debian and cuda I read about GPUs nvidia and CUDA etc a bit on the web. I found out that CUDA is supposed to work in Linux and nosed around and saw that there is some sort of implementation of it for Ubuntu http://www.nvidia.com/object/cuda_get.html Unless you are developing an application that needs full access to the nvidia instruction set there is no need to worry about the very platform specific CUDA. Thanks, I take that to mean that I could take e.g. either the Ubuntu code or the Red Hat code and both ought to work fine in Debian if I am interested e.g. to play around with CUDA a bit to learn about it MF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] _ Great deals on almost anything at eBay.co.uk. Search, bid, find and win on eBay today! http://clk.atdmt.com/UKM/go/msnnkmgl001004ukm/direct/01/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub error 22
On Sat, May 17, 2008 at 10:26 PM, C M Reinehr [EMAIL PROTECTED] wrote: GRUB bug might be the problem: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475958 That report is for another problem. Alex, in your case I would try to remove the second HDD (sdb) and first see if the system boots. If not, then I would inspect the grub parameters to make sure that root=/dev/sda1 and initrd too. Other ideeas at http://users.bigpond.net.au/hermanzone/p15.htm#22 Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub error 22
On Sat, May 17, 2008 at 11:39:05PM +0300, Teodor wrote: On Sat, May 17, 2008 at 10:26 PM, C M Reinehr [EMAIL PROTECTED] wrote: GRUB bug might be the problem: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475958 That report is for another problem. Alex, in your case I would try to remove the second HDD (sdb) and first see if the system boots. If not, then I would inspect the grub parameters to make sure that root=/dev/sda1 and initrd too. another path to test is to press any key at the grub boot prompt (do you get that prompt or does it crash before then and press e for edit to test out the lines, for example to test that it sees vmlinux at (hd0,0), you can type (hd0,0)/vmtab and it should expand out for your or even (hd0,0)/tab Other ideeas at http://users.bigpond.net.au/hermanzone/p15.htm#22 Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Scully: This seat taken? Mulder: No, but i should warn you i'm experiencing violent impulses. Scully: Well I'm armed so I'll take my chances. The X-Files: The Host signature.asc Description: Digital signature
