no such device

Hello!

Please provide information using terminal commands from this thread: https://answers.launchpad.net/ubuntu/+question/107998

Can you do a "sudo fdisk -l" and "grub --version" ?
When you switch disk on BIOS, for old grub you have to update the file /boot/grub/menu.lst.

--- On Mon, 4/26/10, HX_unbanned <email address hidden> wrote:

From: HX_unbanned <email address hidden>
Subject: Re: [Question #108407]: no such device
To: <email address hidden>
Date: Monday, April 26, 2010, 1:10 AM

Your question #108407 on Ubuntu changed:
https://answers.launchpad.net/ubuntu/+question/108407

    Status: Open => Needs information

HX_unbanned requested for more information:
Hello!

Please provide information using terminal commands from this thread:
https://answers.launchpad.net/ubuntu/+question/107998

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/ubuntu/+question/1084I have no idea what is going on here. Is this a fix for my problem of
"no such device" at bootup from grub. I am new to the workings of
Ubuntu and at times the answers assume that we know more about the
system then we do. I have been having problems with dual boot from
Ubuntu. For some reason the system never shows my two sata drives in
grub. If i use the live cd they do not show up there. One has two Xp
pro systems and the other has Fedora 12 OS and it will not bootup. The
other two drives have Ubuntu on them. The 40gb drive had older version
on it that was updated to 9.10 and is the one i am using now. The 200gb
drive has 9.10 on it. I was able boot from grub on both drives for a
short time then the no such device came up. The only way i can use the
40gb drive is to have it the first drive in BIOS. If the 200gb drive is
first the grub that comes up gives me the choice of the 40gb and 200gb
drive but i get the no such device bootup. At no time has the two Sata
drives shown up in grub to boot from.

--- On Mon, 4/26/10, delance <email address hidden> wrote:

From: delance <email address hidden>
Subject: Re: [Question #108407]: no such device
To: <email address hidden>
Date: Monday, April 26, 2010, 1:01 PM

Your question #108407 on Ubuntu changed:
https://answers.launchpad.net/ubuntu/+question/108407

delance requested for more information:
Can you do a  "sudo fdisk -l"  and "grub --version" ?
When you switch disk on BIOS, for old grub you have to update the file /boot/grub/menu.lst.

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/ubuntu/+question/108407
ron@ron-desktop:~$ sudo fdisk -l
[sudo] password for ron:

Disk /dev/sda: 41.1 GB, 41110142976 bytes
255 heads, 63 sectors/track, 4998 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x140f140f

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        4787    38451546   83  Linux
/dev/sda2            4788        4998     1694857+   5  Extended
/dev/sda5            4788        4998     1694826   82  Linux swap / Solaris

Disk /dev/sdb: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xdad0dad0

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       23330   187398193+  83  Linux
/dev/sdb2           23331       24321     7960207+   5  Extended
/dev/sdb5           23331       24321     7960176   82  Linux swap / Solaris
ron@ron-desktop:~$ grub --version
grub (GNU GRUB 0.97)

--- On Mon, 4/26/10, delance <email address hidden> wrote:

From: delance <email address hidden>
Subject: Re: [Question #108407]: no such device
To: <email address hidden>
Date: Monday, April 26, 2010, 1:01 PM

Your question #108407 on Ubuntu changed:
https://answers.launchpad.net/ubuntu/+question/108407

delance requested for more information:
Can you do a  "sudo fdisk -l"  and "grub --version" ?
When you switch disk on BIOS, for old grub you have to update the file /boot/grub/menu.lst.

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/ubuntu/+question/108407
 I am new to the workings of
Ubuntu and at times the answers assume that we know more about the
system then we do. I have been having problems with dual boot from
Ubuntu. For some reason the system never shows my two sata drives in
grub. If i use the live cd they do not show up there. One has two Xp
pro systems and the other has Fedora 12 OS and it will not bootup. The
other two drives have Ubuntu on them. The 40gb drive had older version
on it that was updated to 9.10 and is the one i am using now. The 200gb
drive has 9.10 on it. I was able boot from grub on both drives for a
short time then the no such device came up. The only way i can use the
40gb drive is to have it the first drive in BIOS. If the 200gb drive is
first the grub that comes up gives me the choice of the 40gb and 200gb
drive but i get the no such device bootup. At no time has the two Sata
drives shown up in grub to boot from. I think others would have given up by now but i think i'm to stubborn :). But i'm learning more about the system all the time. I have been working with computers for years. Way before windows every thing was in dos.

--- On Mon, 4/26/10, Ronald <email address hidden> wrote:

From: Ronald <email address hidden>
Subject: Re: [Question #108407]: no such device
To: <email address hidden>
Date: Monday, April 26, 2010, 1:27 PM

Your question #108407 on Ubuntu changed:
https://answers.launchpad.net/ubuntu/+question/108407

You gave more information on the question:

--- On Mon, 4/26/10, delance <email address hidden>
wrote:

From: delance <email address hidden>
Subject: Re: [Question #108407]: no such device
To: <email address hidden>
Date: Monday, April 26, 2010, 1:01 PM

Your question #108407 on Ubuntu changed:
https://answers.launchpad.net/ubuntu/+question/108407

delance requested for more information:
Can you do a  "sudo fdisk -l"  and "grub --version" ?
When you switch disk on BIOS, for old grub you have to update the file /boot/grub/menu.lst.

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/ubuntu/+question/108407
 I am new to the workings of
Ubuntu and at times the answers assume that we know more about the
system then we do. I have been having problems with dual boot from
Ubuntu. For some reason the system never shows my two sata drives in
grub. If i use the live cd they do not show up there. One has two Xp
pro systems and the other has Fedora 12 OS and it will not bootup. The
other two drives have Ubuntu on them. The 40gb drive had older version
on it that was updated to 9.10 and is the one i am using now. The 200gb
drive has 9.10 on it. I was able boot from grub on both drives for a
short time then the no such device came up. The only way i can use the
40gb drive is to have it the first drive in BIOS. If the 200gb drive is
first the grub that comes up gives me the choice of the 40gb and 200gb
drive but i get the no such device bootup. At no time has the two Sata
drives shown up in grub to boot from. I think others would have given up by now but i think i'm to stubborn :). But i'm learning more about the system all the time. I have been working with computers for years. Way before windows every thing was in dos.

You received this question notification because you are a direct
subscriber of the question.on@ron-desktop:~$ /boot/grub/menu.lst.
bash: /boot/grub/menu.lst.: No such file or directory
ron@ron-desktop:~$

Could you answer via Launchpad instead of producing tons of posts ?
It becomes unreadable.

Summary:

grub (GNU GRUB 0.97) i.e. old version of Grub

Disk /dev/sda: 41.1 GB

     Device Boot Start End Blocks Id System
     /dev/sda1 * 1 4787 38451546 83 Linux
     /dev/sda2 4788 4998 1694857+ 5 Extended
     /dev/sda5 4788 4998 1694826 82 Linux swap / Solaris

Disk /dev/sdb: 200.0 GB

     Device Boot Start End Blocks Id System
     /dev/sdb1 1 23330 187398193+ 83 Linux
     /dev/sdb2 23331 24321 7960207+ 5 Extended
     /dev/sdb5 23331 24321 7960176 82 Linux swap / Solaris

Following previous configuration, you are supposed to boot on /dev/sda1 which must contains:
     /boot/grub/menu.lst

1) Now, can you boot with this configuration ?
2) What do you want to do (boot on 200GB disk, have a grub menu to choose boot between 40GB and 200GB disk) ?
3) You have two swap partitions, one of 1.7 GB, second one of 8GB. I presume first one is useless.

N.B. I will be back in two hours.

The 40gb drive is what i'm using at this time and it is first in BIOS. Would like to have menu to boot from 40 or 200gb drive. I have a new question also to add to problem. I also have two 500gb sata drives in system that never show up to install Ubuntu onto. I called the MB manufacture and the tech. said that  pci=nomsi had to be added to OS to let it see my two sata drives. At some point was to install Ubuntu on one and the other has Fedora 12 on it but it will not boot. If i can get those two drives to show up in the grub menu that may help.

--- On Mon, 4/26/10, delance <email address hidden> wrote:

From: delance <email address hidden>
Subject: Re: [Question #108407]: no such device
To: <email address hidden>
Date: Monday, April 26, 2010, 2:05 PM

Your question #108407 on Ubuntu changed:
https://answers.launchpad.net/ubuntu/+question/108407

    Status: Open => Needs information

delance requested for more information:
Could you answer via Launchpad instead of producing tons of posts ?
It becomes unreadable.

Summary:

grub (GNU GRUB 0.97) i.e. old version of Grub

Disk /dev/sda: 41.1 GB

     Device Boot        Start         End      Blocks       Id   System
     /dev/sda1   *              1        4787    38451546   83  Linux
     /dev/sda2            4788        4998     1694857+    5  Extended
     /dev/sda5            4788        4998     1694826    82  Linux swap / Solaris

Disk /dev/sdb: 200.0 GB

     Device Boot         Start         End      Blocks           Id  System
     /dev/sdb1                   1       23330   187398193+  83  Linux
     /dev/sdb2           23331       24321       7960207+    5  Extended
     /dev/sdb5           23331       24321       7960176    82  Linux swap / Solaris

Following previous configuration, you are supposed to boot on /dev/sda1 which must contains:
     /boot/grub/menu.lst

1) Now, can you boot with this configuration ?
2) What do you want to do (boot on 200GB disk, have a grub menu to choose boot between 40GB and 200GB disk) ?
3) You have two swap partitions, one of 1.7 GB, second one of 8GB. I presume first one is useless.

N.B. I will be back in two hours.

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/ubuntu/+question/108407

You received this question notification because you are a direct
subscriber of the question.

Please, if you reply by mail, remove previous message!

In /boot/grub/menu.lst in "1st partition 40GB disk", i.e. sda1, you should have something like:

title Ubuntu 9.10, kernel 2.6.31-20-generic
uuid ef3449fc-7813-48fe-a458-1c611b17fce4
kernel /boot/vmlinuz-2.6.31-20-generic root=UUID=ef3449fc-7813-48fe-a458-1c611b17fce4 ro xforcevesa quiet splash
initrd /boot/initrd.img-2.6.31-20-generic
quiet

1) 2.6.31-20 is kernel version. You have to identify the /boot/vmlinuz-2.6.31-?????-generic in the "1st partition of 200GB disk" i.e. sdb1
2) uuid is the partition identifier of sda1. With GParted, which is on LiveCD (or you can install via Synaptic), you must identify the UUID of partition SDB1
3) Do a copy/paste of the bloc of text in menu.lst.
   -) Do a backup of menu.lst (Allways to do a BACKUP)
   a) Then replace the three occurences of kernel version by sdb1's one.
   b) Replace the two occurences of UUID by sdb1's one.
   c) Reboot
You should have a menu with both partitions.

----------------------------------------------------------------------------------------------------

For the two 500GB, I presume it is another computer. Or there are on a PCI card with SATA controler ?
In first case, please open a new question (you can send me the link to this one with a mail, by clicking on my name).
In second case, I have to look if Grub knows how to manage disk on a PCI card.
Can you clarify ?

----------------------------------------------------------------------------------------------------

Please, if you reply by mail, remove previous message!

This is what comes up for menu.lst.                                                             ron@ron-desktop:~$ /boot/grub/menu.lst
bash: /boot/grub/menu.lst: No such file or directory. I'm using Ubuntu on the 40gb hard drive. The above is what comes up if i type it into the terminal.

The two sata drives are in the same computer. There are 4 total drives.

The two sata drives are not on a pci card the other two drives. The motherboard is newer and only had one plug to MB for the two older drives. I use MB connection for my two DVD drives. And i use the pci card for the two ata hard drives. :

1) menu.lst
I'm surprised. You should have /boot/grub/menu.lst if you have Grub.
Can you type "ll /boot/grub/" and "ll /boot" ?

2) hardware configuration
Sorry, English is not my native language. And don't know what is a MB connection.
Configuration is:
    two 500GB SATA disks connected to motherboard
    one 40GB and one 200GB PATA disk connected to a PCI card
Am I right ?

I'll be back this evening late (22h English time).

When type  ll /boot/grub/ or ll/boot  it comes up no command found.
Sorry MB is motherboard. Configuration is:
    two 500GB SATA disks connected to motherboard
    one 40GB and one 200GB PATA disk connected to a PCI card
The only drive i can boot from is the 40gb and it is not grub2. It is the one i'm using to e-mail  you. When i built this system i was going to install 9.10 on one of the 500gb drives but Ubuntu did not show those drives to install too. Any time i try to install to a drive the 40gb and 200gb are the only ones shown in partition list. I did notice that when i turn computer on that just before BIOS comes up the screen shows the 40gb drive as 0 and 200gb drive as 1. It never changes even if i change boot order in BIOS. I keep thinking it is a BIOS problem with sata drives. All 4 drives show up in BIOS. If i change to one of the sata drives to boot first it will go to XP pro that is on them. Ubuntu does not see them. The motherboard tech. said to add "pci-nomsi" to kernel line before "quiet splash". I do want to thank you for your time.

Sorry, replace "ll" commands by "ls -l /boot/grub/" and "ls -l /boot".

Can you do use GParted (from LiveCD ou you can install from Synaptic) to check if it sees the four disks, and can you provide the partitions for both 500GB disks? BE CAREFULL: don't play with GParted command except if you know what you do. It's powerfull...and dangerous.

I'll have a look tomorrow morning.

ron@ron-desktop:~$ ls -l /boot/grub/
total 2724
-rw-r--r-- 1 root root    8320 2010-04-18 15:52 915resolution.mod
-rw-r--r-- 1 root root   10632 2010-04-18 15:52 acpi.mod
-rw-r--r-- 1 root root    4684 2010-04-18 15:52 affs.mod
-rw-r--r-- 1 root root    5144 2010-04-18 15:52 afs_be.mod
-rw-r--r-- 1 root root    4916 2010-04-18 15:52 afs.mod
-rw-r--r-- 1 root root    1136 2010-04-18 15:52 aout.mod
-rw-r--r-- 1 root root    7952 2010-04-18 15:52 ata.mod
-rw-r--r-- 1 root root    2352 2010-04-18 15:52 ata_pthru.mod
-rw-r--r-- 1 root root    2324 2010-04-18 15:52 at_keyboard.mod
-rw-r--r-- 1 root root    5036 2010-04-18 15:52 befs_be.mod
-rw-r--r-- 1 root root    4808 2010-04-18 15:52 befs.mod
-rw-r--r-- 1 root root    4264 2010-04-18 15:52 biosdisk.mod
-rw-r--r-- 1 root root    2528 2010-04-18 15:52 bitmap.mod
-rw-r--r-- 1 root root    2116 2010-04-18 15:52 blocklist.mod
-rw-r--r-- 1 root root     512 2010-04-18 15:52 boot.img
-rw-r--r-- 1 root root    2652 2010-04-18 15:52 boot.mod
-rw-r--r-- 1 root root   19384 2010-04-18 15:52 bsd.mod
-rw-r--r-- 1 root root    2048 2010-04-18 15:52 bufio.mod
-rw-r--r-- 1 root root    2036 2010-04-18 15:52 cat.mod
-rw-r--r-- 1 root root     512 2010-04-18 15:52 cdboot.img
-rw-r--r-- 1 root root    2420 2010-04-18 15:52 chain.mod
-rw-r--r-- 1 root root    2212 2010-04-18 15:52 cmp.mod
-rw-r--r-- 1 root root    1558 2010-04-18 15:52 command.lst
-rw-r--r-- 1 root root    1904 2010-04-18 15:52 configfile.mod
-rw-r--r-- 1 root root   25105 2010-04-18 15:52 core.img
-rw-r--r-- 1 root root    2872 2010-04-18 15:52 cpio.mod
-rw-r--r-- 1 root root    1660 2010-04-18 15:52 cpuid.mod
-rw-r--r-- 1 root root    1824 2010-04-18 15:52 crc.mod
-rw-r--r-- 1 root root    1912 2010-04-18 15:52 datehook.mod
-rw-r--r-- 1 root root    2360 2010-04-18 15:52 date.mod
-rw-r--r-- 1 root root    1333 2010-04-18 15:52 datetime.mod
-rw-r--r-- 1 root root     191 2010-04-27 12:57 default
-rw-r--r-- 1 root root      30 2010-04-18 14:40 device.map
-rw-r--r-- 1 root root     512 2010-04-18 15:52 diskboot.img
-rw-r--r-- 1 root root    1932 2010-04-18 15:52 dm_nv.mod
-rw-r--r-- 1 root root    5620 2010-04-18 15:52 drivemap.mod
-rw-r--r-- 1 root root    2008 2010-04-18 15:52 echo.mod
-rw-r--r-- 1 root root    6436 2010-04-18 15:52 efiemu32.o
-rw-r--r-- 1 root root   11003 2010-04-18 15:52 efiemu64.o
-rw-r--r-- 1 root root   25024 2010-04-18 15:52 efiemu.mod
-rw-r--r-- 1 root root    4476 2010-04-18 15:52 elf.mod
-rw-r--r-- 1 root root    5544 2010-04-18 15:52 ext2.mod
-rw-r--r-- 1 root root    3916 2010-04-18 15:52 extcmd.mod
-rw-r--r-- 1 root root    5812 2010-04-18 15:52 fat.mod
-rw-r--r-- 1 root root    7296 2010-04-18 15:52 font.mod
-rw-r--r-- 1 root root    2284 2010-04-18 15:52 fs_file.mod
-rw-r--r-- 1 root root    2852 2010-04-18 15:52 fshelp.mod
-rw-r--r-- 1 root root     121 2010-04-18 15:52 fs.lst
-rw-r--r-- 1 root root    2220 2010-04-18 15:52 fs_uuid.mod
-rw-r--r-- 1 root root    8624 2010-04-18 15:52 gfxterm.mod
-rw-r--r-- 1 root root    3816 2010-04-18 15:52 gptsync.mod
-r--r--r-- 1 root root    3209 2010-04-18 15:53 grub.cfg
-rw-r--r-- 1 root root    1024 2010-04-27 14:44 grubenv
-rw-r--r-- 1 root root    7816 2010-04-18 15:52 gzio.mod
-rw-r--r-- 1 root root    1552 2010-04-18 15:52 halt.mod
-rw-r--r-- 1 root root     272 2010-04-18 15:52 handler.lst
-rw-r--r-- 1 root root    2144 2010-04-18 15:52 handler.mod
-rw-r--r-- 1 root root    7400 2010-04-18 15:52 hdparm.mod
-rw-r--r-- 1 root root    1308 2010-04-18 15:52 hello.mod
-rw-r--r-- 1 root root    2200 2010-04-18 15:52 help.mod
-rw-r--r-- 1 root root    3196 2010-04-18 15:52 hexdump.mod
-rw-r--r-- 1 root root    5996 2010-04-18 15:52 hfs.mod
-rw-r--r-- 1 root root    5876 2010-04-18 15:52 hfsplus.mod
-rw-r--r-- 1 root root    6080 2010-04-18 15:52 iso9660.mod
-rw-r--r-- 1 root root    5676 2010-04-18 15:52 jfs.mod
-rw-r--r-- 1 root root    5988 2010-04-18 15:52 jpeg.mod
-rw-r--r-- 1 root root   31004 2010-04-18 15:52 kernel.img
-rw-r--r-- 1 root root    2092 2010-04-18 15:52 keystatus.mod
-rw-r--r-- 1 root root    4952 2010-04-18 15:52 linux16.mod
-rw-r--r-- 1 root root    8716 2010-04-18 15:52 linux.mod
-rw-r--r-- 1 root root    1024 2010-04-18 15:52 lnxboot.img
-rw-r--r-- 1 root root    5664 2010-04-18 15:52 loadenv.mod
-rw-r--r-- 1 root root    3172 2010-04-18 15:52 loopback.mod
-rw-r--r-- 1 root root    1388 2010-04-18 15:52 lsmmap.mod
-rw-r--r-- 1 root root    4196 2010-04-18 15:52 ls.mod
-rw-r--r-- 1 root root    4272 2010-04-18 15:52 lspci.mod
-rw-r--r-- 1 root root    5580 2010-04-18 15:52 lvm.mod
-rw-r--r-- 1 root root    1856 2010-04-18 15:52 mdraid.mod
-rw-r--r-- 1 root root    2176 2010-04-18 15:52 memdisk.mod
-rw-r--r-- 1 root root    2272 2010-04-18 15:52 memrw.mod
-rw-r--r-- 1 root root    4656 2010-04-27 13:05 menu.lst
-rw-r--r-- 1 root root    4656 2010-04-27 13:05 menu.lst~
-rw-r--r-- 1 root root    4116 2010-04-18 15:52 minicmd.mod
-rw-r--r-- 1 root root    4456 2010-04-18 15:52 minix.mod
-rw-r--r-- 1 root root    8656 2010-04-18 15:52 mmap.mod
-rw-r--r-- 1 root root    1657 2010-04-18 15:52 moddep.lst
-rw-r--r-- 1 root root    2468 2010-04-18 15:52 msdospart.mod
-rw-r--r-- 1 root root   15112 2010-04-18 15:52 multiboot.mod
-rw-r--r-- 1 root root   34764 2010-04-18 15:52 normal.mod
-rw-r--r-- 1 root root    3352 2010-04-18 15:52 ntfscomp.mod
-rw-r--r-- 1 root root    8584 2010-04-18 15:52 ntfs.mod
-rw-r--r-- 1 root root    4576 2010-04-18 15:52 ohci.mod
-rw-r--r-- 1 root root    2196 2010-04-18 15:52 part_acorn.mod
-rw-r--r-- 1 root root    2400 2010-04-18 15:52 part_amiga.mod
-rw-r--r-- 1 root root    2776 2010-04-18 15:52 part_apple.mod
-rw-r--r-- 1 root root    2840 2010-04-18 15:52 part_gpt.mod
-rw-r--r-- 1 root root      62 2010-04-18 15:52 partmap.lst
-rw-r--r-- 1 root root    3552 2010-04-18 15:52 part_msdos.mod
-rw-r--r-- 1 root root    2376 2010-04-18 15:52 part_sun.mod
-rw-r--r-- 1 root root      22 2010-04-18 15:52 parttool.lst
-rw-r--r-- 1 root root    4608 2010-04-18 15:52 parttool.mod
-rw-r--r-- 1 root root    2052 2010-04-18 15:52 password.mod
-rw-r--r-- 1 root root     928 2010-04-18 15:52 pci.mod
-rw-r--r-- 1 root root    2144 2010-04-18 15:52 play.mod
-rw-r--r-- 1 root root    6580 2010-04-18 15:52 png.mod
-rw-r--r-- 1 root root    2752 2010-04-18 15:52 probe.mod
-rw-r--r-- 1 root root    1024 2010-04-18 15:52 pxeboot.img
-rw-r--r-- 1 root root    2512 2010-04-18 15:52 pxecmd.mod
-rw-r--r-- 1 root root    3620 2010-04-18 15:52 pxe.mod
-rw-r--r-- 1 root root    1472 2010-04-18 15:52 raid5rec.mod
-rw-r--r-- 1 root root    2920 2010-04-18 15:52 raid6rec.mod
-rw-r--r-- 1 root root    5960 2010-04-18 15:52 raid.mod
-rw-r--r-- 1 root root    1632 2010-04-18 15:52 read.mod
-rw-r--r-- 1 root root    1212 2010-04-18 15:52 reboot.mod
-rw-r--r-- 1 root root    9948 2010-04-18 15:52 reiserfs.mod
-rw-r--r-- 1 root root    3340 2010-04-18 15:52 scsi.mod
-rw-r--r-- 1 root root    3604 2010-04-18 15:52 search.mod
-rw-r--r-- 1 root root    5692 2010-04-18 15:52 serial.mod
-rw-r--r-- 1 root root     778 2010-04-18 15:52 setjmp.mod
-rw-r--r-- 1 root root    4228 2010-04-18 15:52 sfs.mod
-rw-r--r-- 1 root root   12132 2010-04-18 15:52 sh.mod
-rw-r--r-- 1 root root    2296 2010-04-18 15:52 sleep.mod
-rw-r--r-- 1 root root    2904 2010-04-18 15:52 tar.mod
-rw-r--r-- 1 root root    9624 2010-04-18 15:52 terminfo.mod
-rw-r--r-- 1 root root    5248 2010-04-18 15:52 test.mod
-rw-r--r-- 1 root root    2976 2010-04-18 15:52 tga.mod
-rw-r--r-- 1 root root    1356 2010-04-18 15:52 true.mod
-rw-r--r-- 1 root root    5156 2010-04-18 15:52 udf.mod
-rw-r--r-- 1 root root    4796 2010-04-18 15:52 ufs1.mod
-rw-r--r-- 1 root root    5116 2010-04-18 15:52 ufs2.mod
-rw-r--r-- 1 root root    4972 2010-04-18 15:52 uhci.mod
-rw-r--r-- 1 root root 1716019 2010-04-18 15:52 unicode.pf2
-rw-r--r-- 1 root root    3356 2010-04-18 15:52 usb_keyboard.mod
-rw-r--r-- 1 root root    4268 2010-04-18 15:52 usb.mod
-rw-r--r-- 1 root root    3876 2010-04-18 15:52 usbms.mod
-rw-r--r-- 1 root root    3052 2010-04-18 15:52 usbtest.mod
-rw-r--r-- 1 root root    2824 2010-04-18 15:52 vbeinfo.mod
-rw-r--r-- 1 root root    6236 2010-04-18 15:52 vbe.mod
-rw-r--r-- 1 root root    3136 2010-04-18 15:52 vbetest.mod
-rw-r--r-- 1 root root    3756 2010-04-18 15:52 vga.mod
-rw-r--r-- 1 root root    2780 2010-04-18 15:52 vga_text.mod
-rw-r--r-- 1 root root   16316 2010-04-18 15:52 video_fb.mod
-rw-r--r-- 1 root root    5352 2010-04-18 15:52 video.mod
-rw-r--r-- 1 root root    3912 2010-04-18 15:52 videotest.mod
-rw-r--r-- 1 root root    6168 2010-04-18 15:52 xfs.mod
-rw-r--r-- 1 root root   24792 2010-04-18 15:52 xnu.mod
-rw-r--r-- 1 root root    4312 2010-04-18 15:52 xnu_uuid.mod
-rw-r--r-- 1 root root    6416 2010-04-18 15:52 zfsinfo.mod
-rw-r--r-- 1 root root   24360 2010-04-18 15:52 zfs.mod

ron@ron-desktop:~$ ls -l /boot
total 14048
-rw-r--r-- 1 root root  629693 2010-03-12 03:51 abi-2.6.31-20-generic-pae
-rw-r--r-- 1 root root  111417 2010-03-12 03:51 config-2.6.31-20-generic-pae
drwxr-xr-x 2 root root    4096 2010-04-27 13:05 grub
-rw-r--r-- 1 root root 7912578 2010-04-27 12:18 initrd.img-2.6.31-20-generic-pae
-rw-r--r-- 1 root root  128796 2009-10-23 12:11 memtest86+.bin
-rw-r--r-- 1 root root 1667668 2010-03-12 03:51 System.map-2.6.31-20-generic-pae
-rw-r--r-- 1 root root    1200 2010-03-12 03:53 vmcoreinfo-2.6.31-20-generic-pae
-rw-r--r-- 1 root root 3914176 2010-03-12 03:51 vmlinuz-2.6.31-20-generic-pae

I got the four drives show up the places drop down box.
I used edit when the grub menu opened at boot up by adding "pci=nomsi" before "quiet splash" in the kernel. This is just temporary basis. To edit /etc/default/grub by adding gksu gedit in front of it. This is what happens when i try that.

ron@ron-desktop:~$ /etc/default/grub
bash: /etc/default/grub: Permission denied
ron@ron-desktop:~$ sudo /etc/default/grub
[sudo] password for ron:
sudo: /etc/default/grub: command not found

Also how do you make that change when trying to install Ubuntu9.10 to a different drive.

Also this is what came up when i checked grub version   grub (GNU GRUB 0.97) It is not grub2

What you have to edit is /boot/grub/menu.lst.
But before doing anything, can you send me this file at <email address hidden>.
I'm more optimistic for 200GB disk.

I need your investigation with GParted for the 500GB disks (but don't push the green button!).

# 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 use 'savedefault' 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        3

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu

# 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 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# 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=UUID=f029d9e9-024f-4bb5-a3d7-6677872a5bd5 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=f029d9e9-024f-4bb5-a3d7-6677872a5bd5

## 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=quiet splash

## 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=(recovery) single
# altoptions=(recovery 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

## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
##      indomU=true
##      indomU=false
# indomU=detect

## 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        Ubuntu 9.10, kernel 2.6.31-20-generic-pae
uuid        f029d9e9-024f-4bb5-a3d7-6677872a5bd5
kernel        /boot/vmlinuz-2.6.31-20-generic-pae root=UUID=f029d9e9-024f-4bb5-a3d7-6677872a5bd5 ro quiet splash
initrd        /boot/initrd.img-2.6.31-20-generic-pae

title        Ubuntu 9.10, kernel 2.6.31-20-generic-pae (recovery mode)
uuid        f029d9e9-024f-4bb5-a3d7-6677872a5bd5
kernel        /boot/vmlinuz-2.6.31-20-generic-pae root=UUID=f029d9e9-024f-4bb5-a3d7-6677872a5bd5 ro  single
initrd        /boot/initrd.img-2.6.31-20-generic-pae

title        Chainload into GRUB 2
root        f029d9e9-024f-4bb5-a3d7-6677872a5bd5
kernel        /boot/grub/core.img

title        Ubuntu 9.10, memtest86+
uuid        f029d9e9-024f-4bb5-a3d7-6677872a5bd5
kernel        /boot/memtest86+.bin

# 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 use 'savedefault' 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        3

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu

# 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 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# 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=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=a93aef37-ce17-43ec-b14f-de66c904c16e

## 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=quiet splash

## 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=(recovery) single
# altoptions=(recovery 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

## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
##      indomU=true
##      indomU=false
# indomU=detect

## 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        Ubuntu 9.10, kernel 2.6.31-21-generic-pae
uuid        a93aef37-ce17-43ec-b14f-de66c904c16e
kernel        /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro quiet splash
initrd        /boot/initrd.img-2.6.31-21-generic-pae

title        Ubuntu 9.10, kernel 2.6.31-21-generic-pae (recovery mode)
uuid        a93aef37-ce17-43ec-b14f-de66c904c16e
kernel        /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro  single
initrd        /boot/initrd.img-2.6.31-21-generic-pae

title        Ubuntu 9.10, kernel 2.6.31-20-generic-pae
uuid        a93aef37-ce17-43ec-b14f-de66c904c16e
kernel        /boot/vmlinuz-2.6.31-20-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro quiet splash
initrd        /boot/initrd.img-2.6.31-20-generic-pae

title        Ubuntu 9.10, kernel 2.6.31-20-generic-pae (recovery mode)
uuid        a93aef37-ce17-43ec-b14f-de66c904c16e
kernel        /boot/vmlinuz-2.6.31-20-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro  single
initrd        /boot/initrd.img-2.6.31-20-generic-pae

title        Chainload into GRUB 2
root        a93aef37-ce17-43ec-b14f-de66c904c16e
kernel        /boot/grub/core.img

title        Ubuntu 9.10, memtest86+
uuid        a93aef37-ce17-43ec-b14f-de66c904c16e
kernel        /boot/memtest86+.bin

### END DEBIAN AUTOMAGIC KERNELS LIST
### END DEBIAN AUTOMAGIC KERNELS LIST

The First list is from the 200gb drive and the second list is from the 40gb drive

In menu.lst of 40GB, add after :

title Ubuntu 9.10, kernel 2.6.31-20-generic-pae (recovery mode)
uuid f029d9e9-024f-4bb5-a3d7-6677872a5bd5
kernel /boot/vmlinuz-2.6.31-20-generic-pae root=UUID=f029d9e9-024f-4bb5-a3d7-6677872a5bd5 ro single
initrd /boot/initrd.img-2.6.31-20-generic-pae

the bloc:

title 200GB - Ubuntu 9.10, kernel 2.6.31-21-generic-pae
uuid a93aef37-ce17-43ec-b14f-de66c904c16e
kernel /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro quiet splash
initrd /boot/initrd.img-2.6.31-21-generic-pae

title 200GB - Ubuntu 9.10, kernel 2.6.31-21-generic-pae (recovery mode)
uuid a93aef37-ce17-43ec-b14f-de66c904c16e
kernel /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro single
initrd /boot/initrd.img-2.6.31-21-generic-pae

You should be able to boot on 200GB from 40GB.

--------------------------------------------------------------------------------------------------------------------------------------------
In menu.lst of 200 GB, add after :

title Ubuntu 9.10, kernel 2.6.31-21-generic-pae
uuid a93aef37-ce17-43ec-b14f-de66c904c16e
kernel /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro quiet splash
initrd /boot/initrd.img-2.6.31-21-generic-pae

the bloc :

title 40GB - Ubuntu 9.10, kernel 2.6.31-20-generic-pae
uuid f029d9e9-024f-4bb5-a3d7-6677872a5bd5
kernel /boot/vmlinuz-2.6.31-20-generic-pae root=UUID=f029d9e9-024f-4bb5-a3d7-6677872a5bd5 ro quiet splash
initrd /boot/initrd.img-2.6.31-20-generic-pae

title 40GB - Ubuntu 9.10, kernel 2.6.31-20-generic-pae (recovery mode)
uuid f029d9e9-024f-4bb5-a3d7-6677872a5bd5
kernel /boot/vmlinuz-2.6.31-20-generic-pae root=UUID=f029d9e9-024f-4bb5-a3d7-6677872a5bd5 ro single
initrd /boot/initrd.img-2.6.31-20-generic-pae

If you make 200GB disk bootable and first in BIOS setup, you could boot on 200GB, or on 200GB from 40GB.

------------------------------------------------------------------------------------------------------------------------------------------------------

But now, what do you want of these two disks (500GB disk will be seen later).

I made a change in my system since we talked last. I installed 10.04 on the 200gb drive and it will not boot. It always ends up back at the 40gb drive. When i boot from the 40gb drive now it lists 4 drives that i can mount. The 200gb drive has no menu.lst that shows up in boot. Could that be because it has 10.04 on it now. The bloc that you wanted me to add to the 40gb menu.lst looks like it is for the 200gb drive. The lines that the bloc was to go after is not on the 40gb drive but the 200gb drive and i did not make a change yet. This is the first line from the 40gb drive.    title        Ubuntu 9.10, kernel 2.6.31-21-generic-pae
uuid        a93aef37-ce17-43ec-b14f-de66c904c16e
kernel        /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro quiet splash
initrd        /boot/initrd.img-2.6.31-21-generic-pae

I don't know if you need change what i need to do or not. I will wait till i hear from you again. Did not want to make things worst
--- On Sun, 5/2/10, delance <email address hidden> wrote:

From: delance <email address hidden>
Subject: Re: [Question #108407]: no such device
To: <email address hidden>
Date: Sunday, May 2, 2010, 4:14 PM

Your question #108407 on Ubuntu changed:
https://answers.launchpad.net/ubuntu/+question/108407

    Status: Open => Answered

delance proposed the following answer:
In menu.lst of 40GB, add after :

title        Ubuntu 9.10, kernel 2.6.31-20-generic-pae (recovery mode)
uuid        f029d9e9-024f-4bb5-a3d7-6677872a5bd5
kernel        /boot/vmlinuz-2.6.31-20-generic-pae root=UUID=f029d9e9-024f-4bb5-a3d7-6677872a5bd5 ro  single
initrd        /boot/initrd.img-2.6.31-20-generic-pae

the bloc:

title        200GB - Ubuntu 9.10, kernel 2.6.31-21-generic-pae
uuid        a93aef37-ce17-43ec-b14f-de66c904c16e
kernel        /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro quiet splash
initrd        /boot/initrd.img-2.6.31-21-generic-pae

title        200GB - Ubuntu 9.10, kernel 2.6.31-21-generic-pae (recovery mode)
uuid        a93aef37-ce17-43ec-b14f-de66c904c16e
kernel        /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro  single
initrd        /boot/initrd.img-2.6.31-21-generic-pae

You should be able to boot on 200GB from 40GB.

--------------------------------------------------------------------------------------------------------------------------------------------
In menu.lst of 200 GB, add after :

title        Ubuntu 9.10, kernel 2.6.31-21-generic-pae
uuid        a93aef37-ce17-43ec-b14f-de66c904c16e
kernel        /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro quiet splash
initrd        /boot/initrd.img-2.6.31-21-generic-pae

the bloc :

title        40GB - Ubuntu 9.10, kernel 2.6.31-20-generic-pae
uuid        f029d9e9-024f-4bb5-a3d7-6677872a5bd5
kernel        /boot/vmlinuz-2.6.31-20-generic-pae root=UUID=f029d9e9-024f-4bb5-a3d7-6677872a5bd5 ro quiet splash
initrd        /boot/initrd.img-2.6.31-20-generic-pae

title        40GB - Ubuntu 9.10, kernel 2.6.31-20-generic-pae (recovery mode)
uuid        f029d9e9-024f-4bb5-a3d7-6677872a5bd5
kernel        /boot/vmlinuz-2.6.31-20-generic-pae root=UUID=f029d9e9-024f-4bb5-a3d7-6677872a5bd5 ro  single
initrd        /boot/initrd.img-2.6.31-20-generic-pae

If you make 200GB disk bootable and first in BIOS setup, you could boot on 200GB, or on 200GB from 40GB.

------------------------------------------------------------------------------------------------------------------------------------------------------

But now, what do you want of these two disks (500GB disk will be seen
later).

--
If this answers your question, please go to the following page to let us
know that it is solved:
https://answers.launchpad.net/ubuntu/+question/108407/+confirm?answer_id=17

If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https://answers.launchpad.net/ubuntu/+question/108407

You received this question notification because you are a direct
subscriber of the question.

Please, stop to reply with previous message.
I work under launchpad, and the thread is unreadable.
If it continues, you will solve the problem by yourself.
-----------------------------------------------------------------------------------------------------
Touch anything. I don't know what is your configuration.

Type
     sudo fdisk -l
     sudo parted -l
     ls -l /dev/disk/by-uuid/

for each disk, provide me again the contents of file /boot/grub/menu.lst AFTER line "## ## End Default Options ##".
for each disk, check existence of file /usr/sbin/grub (for the disk not used for boot, it should be preceded by something like /media/diskXXGB).

Please insert separator between each piece of data, or post each piece of data in a distinct message.
If I can't read, I can't understand (and can't help).

                             I'm using the 40gb drive and opening terminal for the following information.
___________________________________________________________________________________________________ THIS IS WHAT COMES UP FOR /boot/grub/menu.lst
ron@ron-desktop:~$ /boot/grub/menu.lst
bash: /boot/grub/menu.lst: Permission denied
ron@ron-desktop:~$ sudo /boot/grub/menu.lst
[sudo] password for ron:
sudo: /boot/grub/menu.lst: command not found

If i go to Places-Computer-File Systems then click on boot,then grub, then look for menu.lst. If i open it this is what comes up after ## ## End Default Options ##title Ubuntu 9.10, kernel 2.6.31-21-generic-pae
uuid a93aef37-ce17-43ec-b14f-de66c904c16e
kernel /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro quiet splash
initrd /boot/initrd.img-2.6.31-21-generic-pae

title Ubuntu 9.10, kernel 2.6.31-21-generic-pae (recovery mode)
uuid a93aef37-ce17-43ec-b14f-de66c904c16e
kernel /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro single
initrd /boot/initrd.img-2.6.31-21-generic-pae

title Ubuntu 9.10, kernel 2.6.31-20-generic-pae
uuid a93aef37-ce17-43ec-b14f-de66c904c16e
kernel /boot/vmlinuz-2.6.31-20-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro quiet splash
initrd /boot/initrd.img-2.6.31-20-generic-pae

title Ubuntu 9.10, kernel 2.6.31-20-generic-pae (recovery mode)
uuid a93aef37-ce17-43ec-b14f-de66c904c16e
kernel /boot/vmlinuz-2.6.31-20-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro single
initrd /boot/initrd.img-2.6.31-20-generic-pae

title Chainload into GRUB 2
root a93aef37-ce17-43ec-b14f-de66c904c16e
kernel /boot/grub/core.img

title Ubuntu 9.10, memtest86+
uuid a93aef37-ce17-43ec-b14f-de66c904c16e
kernel /boot/memtest86+.bin
___________________________________________________________________________________________________ THE 200GB DRIVE HAS NO /boot/grub/menu.lst. COULD THAT BE BECAUSE IT IS grub2. BECAUSE I INSTALLED ubuntu 10.04 ON IT. NOW THERE IS NO /boot/grub/menu.lst THAT I CAN FIND. IT WAS THERE BEFORE I INSTALLED 10.04 ON IT.
___________________________________________________________________________________________________ THIS IS WHAT COMES UP FOR sudo fdisk -l
ron@ron-desktop:~$ sudo fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0b1d0b1c

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 31871 256003776 7 HPFS/NTFS

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x586e586e

   Device Boot Start End Blocks Id System
/dev/sdb1 * 1 38245 307202931 7 HPFS/NTFS
/dev/sdb2 38246 60800 181173037+ f W95 Ext'd (LBA)
/dev/sdb5 38246 60800 181173006 7 HPFS/NTFS

Disk /dev/sdc: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0002276c

   Device Boot Start End Blocks Id System
/dev/sdc1 1 23330 187395072 83 Linux
/dev/sdc2 23330 24322 7963649 5 Extended
/dev/sdc5 23330 24322 7963648 82 Linux swap / Solaris

Disk /dev/sdd: 41.1 GB, 41110142976 bytes
255 heads, 63 sectors/track, 4998 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x140f140f

   Device Boot Start End Blocks Id System
/dev/sdd1 * 1 4787 38451546 83 Linux
/dev/sdd2 4788 4998 1694857+ 5 Extended
/dev/sdd5 4788 4998 1694826 82 Linux swap / Solaris
___________________________________________________________________________________________________ THIS IS WHAT COMES UP FOR sudo parted -l
ron@ron-desktop:~$ sudo parted -l
[sudo] password for ron:
Model: ATA WDC WD5001AALS-0 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
 1 32.3kB 262GB 262GB primary ntfs boot

Model: ATA Hitachi HDP72505 (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
 1 32.3kB 315GB 315GB primary ntfs boot
 2 315GB 500GB 186GB extended lba
 5 315GB 500GB 186GB logical ntfs

Model: ATA MAXTOR STM320082 (scsi)
Disk /dev/sdc: 200GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
 1 1049kB 192GB 192GB primary ext4
 2 192GB 200GB 8155MB extended
 5 192GB 200GB 8155MB logical linux-swap(v1)

Model: ATA Maxtor 6E040L0 (scsi)
Disk /dev/sdd: 41.1GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
 1 32.3kB 39.4GB 39.4GB primary ext4 boot
 2 39.4GB 41.1GB 1736MB extended
 5 39.4GB 41.1GB 1736MB logical linux-swap(v1)

___________________________________________________________________________________________________ THIS IS WHAT COMES UP FOR ls -l /dev/disk/by-uuid/
ron@ron-desktop:~$ ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 2010-05-03 16:07 0d9c3989-2f0f-4bf2-a5a6-f7a0e2229cf6 -> ../../sdc5
lrwxrwxrwx 1 root root 10 2010-05-03 16:07 265C5C635C5C3033 -> ../../sdb1
lrwxrwxrwx 1 root root 10 2010-05-03 16:07 2CF90030F8FFF644 -> ../../sda1
lrwxrwxrwx 1 root root 10 2010-05-03 16:07 39dfb629-3604-416c-856b-673e13d084ae -> ../../sdd5
lrwxrwxrwx 1 root root 10 2010-05-03 16:07 7A2CF9672CF91EB7 -> ../../sdb5
lrwxrwxrwx 1 root root 10 2010-05-03 16:07 8e625ac8-88c7-47e1-b609-d794370d0eb5 -> ../../sdc1
lrwxrwxrwx 1 root root 10 2010-05-03 16:07 a93aef37-ce17-43ec-b14f-de66c904c16e -> ../../sdd1
___________________________________________________________________________________________________ SORRY FOR THE CONFUSING INFORMATION. I HOPE THIS HELPS YOU BETTER.

Too late for today evening!
I printed last post and I will analyze it tomorrow evening, before evening german lesson.
I will answer tomorrow evening at 22:00 UK time or wednesday evening.

Are you interested by keeping Ubuntu 9.10 on 40GB or use it as a Data disk ?

KEEP IT WITH 9.10

As I have solved issues for other users, I will have more time than planned.

The situation at Boot Sector is:
      one windows Boot Sector for each 500GB
      one Boot Sector Grub1 on 40GB disk
and none on 200GB, which is perfect!

In a first step, you could check you are able able to boot on both 500GB, and if it is not the case repair the MBR (Windows Boot Sector) with Windows DVD-ROM.

After, you must make 200GB first disk (in the BIOS or by changing wiring).
You need to reinstall 10.4 on 200GB.
200GB must appear as /dev/sda.
During installation, Ubuntu will install Boot Sector of Grub2 on 200GB, and, in theory, it will detect the three others Boot Sectors, and chain them.
There are supposed to appear in boot menu.
But in practice, it doesn't work for all users.

Both 500gb drives boot to windows.

Reinstalled 10.04 to 200gb drive with it first in BIOS

At reboot it came up error: file not found
grub rescue>

Reboot with 40gb drive first in BIOS it came up
No such device 8eb625ac8-8807-47e1-b609-d79437d0eb5
grub rescue>

Your problem seems very complex!

Will will stay with 40GB for the moment:

For your 40GB disk, in previous messages,
 menu.lst a93aef37-ce17-43ec-b14f-de66c904c16e
 /dev/disk/by-uuid/ sdd a93aef37-ce17-43ec-b14f-de66c904c16e

Grub from 40GB looks to search another disk than 40GB disk.
With LiveCD, mount 40GB, and check that in /media/disk40GB/boot/grub/menu.lst, in first text boot block, you have UUID
a93aef37-ce17-43ec-b14f-de66c904c16e.
Do also "sudo blkid" to check again UUID of disks.
If UUID in /media/disk40GB/boot/grub/menu.lst doesn't match UUID of first partition on 40GB disk, you have to update UUID of this file.

We need to fix 40GB issue before looking at 200GB issue.

This is the first block of menu.lst. for 40gb drive

## ## End Default Options ##

title Ubuntu 9.10, kernel 2.6.31-21-generic-pae
uuid a93aef37-ce17-43ec-b14f-de66c904c16e
kernel /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro quiet splash
initrd /boot/initrd.img-2.6.31-21-generic-pae
______________________________________________________________________________

This what comes up for "sudo blkid"

ubuntu@ubuntu:~$ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/sda1: UUID="db318bec-8552-4384-aebc-d569e644a95b" TYPE="ext4"
/dev/sda5: UUID="0d9c3989-2f0f-4bf2-a5a6-f7a0e2229cf6" TYPE="swap"
/dev/sdb1: UUID="a93aef37-ce17-43ec-b14f-de66c904c16e" TYPE="ext4"
/dev/sdb5: UUID="39dfb629-3604-416c-856b-673e13d084ae" TYPE="swap"
____________________________________________________________________________
  The line"/dev/sda1: UUID="db318bec-8552-4384-aebc-d569e644a95b" TYPE="ext4" from sudo blkid should read /dev/sda1: uuid="a93aef37-ce17-43ec-b14f-de66c904c16e" Type="ext4" if i understand you correctly. Or do i have it backwards. If so how do you change it.

The UUID of the first text block of menu.lst match UUID of your second disk /dev/sdb1.
    a93aef37-ce17-43ec-b14f-de66c904c16e
    a93aef37-ce17-43ec-b14f-de66c904c16e
so it should work, which is not the case!

Can you look if you have this following UUID in menu.lst (for both 40GB and 200GB)?
8eb625ac8-8807-47e1-b609-d79437d0eb5

I understand nothing for the moment.

The only UUID in 40gb drive menu.lst is a93aef37-ce17-43ec-b14f-de66c904c16e

____________________________________________________________________________________________________

There is no menu.lst in the 200gb drive. It has 10.04 on it and uses grub 2. Grub2 uses /boot/grub/grub.cfg in place of it.

______________________________________________________________________________________________________ This is what is in /boot/grub/grub.cfg .

 #
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
  set saved_entry=${prev_saved_entry}
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z ${boot_once} ]; then
    saved_entry=${chosen}
    save_env saved_entry
  fi
}

function recordfail {
  set recordfail=1
  if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
}
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set db318bec-8552-4384-aebc-d569e644a95b
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
  fi
fi
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set db318bec-8552-4384-aebc-d569e644a95b
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
  set timeout=-1
else
  set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-22-generic-pae' --class ubuntu --class gnu-linux --class gnu --class os {
 recordfail
 insmod ext2
 set root='(hd0,1)'
 search --no-floppy --fs-uuid --set db318bec-8552-4384-aebc-d569e644a95b
 linux /boot/vmlinuz-2.6.32-22-generic-pae root=UUID=db318bec-8552-4384-aebc-d569e644a95b ro quiet splash
 initrd /boot/initrd.img-2.6.32-22-generic-pae
}
menuentry 'Ubuntu, with Linux 2.6.32-22-generic-pae (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
 recordfail
 insmod ext2
 set root='(hd0,1)'
 search --no-floppy --fs-uuid --set db318bec-8552-4384-aebc-d569e644a95b
 echo 'Loading Linux 2.6.32-22-generic-pae ...'
 linux /boot/vmlinuz-2.6.32-22-generic-pae root=UUID=db318bec-8552-4384-aebc-d569e644a95b ro single
 echo 'Loading initial ramdisk ...'
 initrd /boot/initrd.img-2.6.32-22-generic-pae
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
 insmod ext2
 set root='(hd0,1)'
 search --no-floppy --fs-uuid --set db318bec-8552-4384-aebc-d569e644a95b
 linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
 insmod ext2
 set root='(hd0,1)'
 search --no-floppy --fs-uuid --set db318bec-8552-4384-aebc-d569e644a95b
 linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Ubuntu, Linux 2.6.31-20-generic-pae (on /dev/sdb1)" {
 insmod ext2
 set root='(hd1,1)'
 search --no-floppy --fs-uuid --set a93aef37-ce17-43ec-b14f-de66c904c16e
 linux /boot/vmlinuz-2.6.31-20-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro pci=nomsi quiet splash
 initrd /boot/initrd.img-2.6.31-20-generic-pae
}
menuentry "Ubuntu, Linux 2.6.31-20-generic-pae (recovery mode) (on /dev/sdb1)" {
 insmod ext2
 set root='(hd1,1)'
 search --no-floppy --fs-uuid --set a93aef37-ce17-43ec-b14f-de66c904c16e
 linux /boot/vmlinuz-2.6.31-20-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro single
 initrd /boot/initrd.img-2.6.31-20-generic-pae
}
menuentry "Ubuntu, Linux 2.6.31-21-generic-pae (on /dev/sdb1)" {
 insmod ext2
 set root='(hd1,1)'
 search --no-floppy --fs-uuid --set a93aef37-ce17-43ec-b14f-de66c904c16e
 linux /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro pci=nomsi quiet splash
 initrd /boot/initrd.img-2.6.31-21-generic-pae
}
menuentry "Ubuntu, Linux 2.6.31-21-generic-pae (recovery mode) (on /dev/sdb1)" {
 insmod ext2
 set root='(hd1,1)'
 search --no-floppy --fs-uuid --set a93aef37-ce17-43ec-b14f-de66c904c16e
 linux /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro single
 initrd /boot/initrd.img-2.6.31-21-generic-pae
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

Reboot with 40gb drive first in BIOS it came up
No such device 8eb625ac8-8807-47e1-b609-d79437d0eb5
grub rescue>

040GB 1st part f029d9e9-024f-4bb5-a3d7-6677872a5bd5 (cf menu.lst)
200GB 1st part a93aef37-ce17-43ec-b14f-de66c904c16e (cf menu.lst)
500GB disk 8eb625ac8-8807-47e1-b609-d79437d0eb5

ls -l /dev/disk/by-uuid/

2CF90030F8FFF644 -> ../../sda1 (disk 500GB) UUID Windows
265C5C635C5C3033 -> ../../sdb1 (disk 500GB) UUID Windows
7A2CF9672CF91EB7 -> ../../sdb5 (disk 500GB) UUID Windows
8e625ac8-88c7-47e1-b609-d794370d0eb5 -> ../../sdc1 (disk 040GB) Linux
0d9c3989-2f0f-4bf2-a5a6-f7a0e2229cf6 -> ../../sdc5 (disk 040GB) Swap
a93aef37-ce17-43ec-b14f-de66c904c16e -> ../../sdd1 (disk 200GB) Linux
39dfb629-3604-416c-856b-673e13d084ae -> ../../sdd5 (disk 200GB) Swap
------------------------------------------------------------------------------------------------------------------------------
I have an inconsistency between UUID provide by "ls -l /dev/disk/by-uuid/", menu.lst on 40GB disk and error message.

Can you do:
     sudo blkid && sudo parted -l && sudo find / -name menu.lst | xargs fgrep UUID

Perhaps I'll finish to understand where is the problem.

             sudo blkid && sudo parted -l && sudo find / -name menu.lst | xargs fgrep UUID
____________________________________________________________________________
ubuntu@ubuntu:~$ sudo blkid && sudo parted -l && sudo find / -name menu.lst | xargs fgrep UUID
/dev/loop0: TYPE="squashfs"
/dev/sda1: UUID="db318bec-8552-4384-aebc-d569e644a95b" TYPE="ext4"
/dev/sda5: UUID="0d9c3989-2f0f-4bf2-a5a6-f7a0e2229cf6" TYPE="swap"
/dev/sdb1: UUID="a93aef37-ce17-43ec-b14f-de66c904c16e" TYPE="ext4"
/dev/sdb5: UUID="39dfb629-3604-416c-856b-673e13d084ae" TYPE="swap"
Model: ATA MAXTOR STM320082 (scsi)
Disk /dev/sda: 200GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
 1 1049kB 192GB 192GB primary ext4 boot
 2 192GB 200GB 8155MB extended
 5 192GB 200GB 8155MB logical linux-swap(v1)

Model: ATA Maxtor 6E040L0 (scsi)
Disk /dev/sdb: 41.1GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number Start End Size Type File system Flags
 1 32.3kB 39.4GB 39.4GB primary ext4 boot
 2 39.4GB 41.1GB 1736MB extended
 5 39.4GB 41.1GB 1736MB logical linux-swap(v1)

Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0
has been opened read-only.
Error: /dev/sr0: unrecognised disk label

(NB: it's a summary for myself)
UUID of both Ubuntu disks
/dev/sda1: UUID="db318bec-8552-4384-aebc-d569e644a95b" TYPE="ext4" 200GB
/dev/sda5: UUID="0d9c3989-2f0f-4bf2-a5a6-f7a0e2229cf6" TYPE="swap" 200GB
/dev/sdb1: UUID="a93aef37-ce17-43ec-b14f-de66c904c16e" TYPE="ext4" 41.1GB
/dev/sdb5: UUID="39dfb629-3604-416c-856b-673e13d084ae" TYPE="swap " 41.1GB

Reboot with 40gb drive first in BIOS it came up
No such device 8eb625ac8-8807-47e1-b609-d79437d0eb5
grub rescue>

You should have an error in menu.lst of 41.1GB.
Can you post to <email address hidden> the file menu.lst in /FileSystem41.1GB/boot/grub ?
(I prefer you send me an e-mail with this file because this "question" is becoming too big)

Can you explain me (in a separate post) why you have such a configuration, and what is your goals ?
Perhaps there is a way to reach them with a simpler configuration.

At first i was going to use one of the 500gb drives for Ubuntu and Windows. The other 500gb drive i was going to load Fedora 12 on it. The one 500gb drive already has Fedora on it but it would not boot up. It also has Windows on it. If i put  the one with Windows on it it will boot to Windows. It has two  Windows OS on it.The other has Windows and Fedora on it. But they don't show up in grub to boot from. The 40gb drive i was going to use in another computer.

--- On Wed, 5/12/10, delance <email address hidden> wrote:

From: delance <email address hidden>
Subject: Re: [Question #108407]: no such device
To: <email address hidden>
Date: Wednesday, May 12, 2010, 1:17 PM

Your question #108407 on Ubuntu changed:
https://answers.launchpad.net/ubuntu/+question/108407

delance requested for more information:
Can you explain me (in a separate post) why you have such a configuration, and what is your goals ?
Perhaps there is a way to reach them with a simpler configuration.

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/ubuntu/+question/108407

You received this question notification because you are a direct
subscriber of the question.

Please don't answer with previous message.

I presume that you do not use daily all these software distributions!
If you want simply to check them for evaluation, it could more easy to use virtual machines (like VirtualBox that I use daily).
You could have one virtual machine by distribution, and so avoid tricky multi-boot, with many XP, Ubuntu and Fedora systems.
It's what I use to help people in Ubuntu 9.10 or 10.04, and to use simultaneously for myself XP and Seven.
The only real limit is RAM, because each machine needs around 512MB of REAL memory (which means 5 machines on a 3.2GB computer). For IO or CPU, I see no real difference with a multi-boot software. It is sometimes a little more slowly (specially for XP, but I don't know why).
If you want to discover the "pleasure" of multi-boot, you can also do it on a virtual machine. It's how I debug for Launchpad users XP/Ubuntu multi-boot issues.

Trying to manage so many OSes is very ambitious!

Menu.lst:

title Ubuntu 9.10, kernel 2.6.31-21-generic-pae
uuid a93aef37-ce17-43ec-b14f-de66c904c16e
kernel /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro quiet splash
initrd /boot/initrd.img-2.6.31-21-generic-pae
Error message:

Reboot with 40gb drive first in BIOS it came up
No such device 8eb625ac8-8807-47e1-b609-d79437d0eb5
grub rescue>

Sorry, I have any explanation. I don't see why grub try to access "8eb625ac8-8807-47e1-b609-d79437d0eb5" instead of "a93aef37-ce17-43ec-b14f-de66c904c16e".

I will check into VirtualBox thank you for your help. I appreciate it very much.

--- On Wed, 5/12/10, delance <email address hidden> wrote:

From: delance <email address hidden>
Subject: Re: [Question #108407]: no such device
To: <email address hidden>
Date: Wednesday, May 12, 2010, 5:53 PM

Your question #108407 on Ubuntu changed:
https://answers.launchpad.net/ubuntu/+question/108407

    Status: Open => Answered

delance proposed the following answer:
Please don't answer with previous message.

I presume that you do not use daily all these software distributions!
If you want simply to check them for evaluation, it could more easy to use virtual machines (like VirtualBox that I use daily).
You could have one virtual machine by distribution, and so avoid tricky multi-boot, with many XP, Ubuntu and Fedora systems.
It's what I use to help people in Ubuntu 9.10 or 10.04, and to use simultaneously for myself XP and Seven.
The only real limit is RAM, because each machine needs around 512MB of REAL memory (which means 5 machines on a 3.2GB computer). For IO or CPU, I see no real difference with a multi-boot software. It is sometimes a little more slowly (specially for XP, but I don't know why).
If you want to discover the "pleasure" of multi-boot, you can also do it on a virtual machine. It's how I debug for Launchpad users XP/Ubuntu multi-boot issues.

Trying to manage so many OSes is very ambitious!

--
If this answers your question, please go to the following page to let us
know that it is solved:
https://answers.launchpad.net/ubuntu/+question/108407/+confirm?answer_id=35

If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https://answers.launchpad.net/ubuntu/+question/108407

You received this question notification because you are a direct
subscriber of the question.

I'm not sure what device 8eb625ac8-8807-47e1-b609-d79437d0eb5 is. Unless it is one of the 500gb drives. If i can get one of the Ubuntu drives to work i my start all over. Again i want to thank you very much for all your help.

--- On Wed, 5/12/10, delance <email address hidden> wrote:

From: delance <email address hidden>
Subject: Re: [Question #108407]: no such device
To: <email address hidden>
Date: Wednesday, May 12, 2010, 5:55 PM

Your question #108407 on Ubuntu changed:
https://answers.launchpad.net/ubuntu/+question/108407

delance proposed the following answer:
Menu.lst:

title        Ubuntu 9.10, kernel 2.6.31-21-generic-pae
uuid        a93aef37-ce17-43ec-b14f-de66c904c16e
kernel        /boot/vmlinuz-2.6.31-21-generic-pae root=UUID=a93aef37-ce17-43ec-b14f-de66c904c16e ro quiet splash
initrd        /boot/initrd.img-2.6.31-21-generic-pae
Error message:

Reboot with 40gb drive first in BIOS it came up
No such device 8eb625ac8-8807-47e1-b609-d79437d0eb5
grub rescue>

Sorry, I have any explanation. I don't see why grub try to access
"8eb625ac8-8807-47e1-b609-d79437d0eb5" instead of "a93aef37-ce17-43ec-
b14f-de66c904c16e".

--
If this answers your question, please go to the following page to let us
know that it is solved:
https://answers.launchpad.net/ubuntu/+question/108407/+confirm?answer_id=36

If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https://answers.launchpad.net/ubuntu/+question/108407

You received this question notification because you are a direct
subscriber of the question.

Hello, I will have some time tomorrow to follow your problem.
What is your status ?

I reinstalled 10.04 onto the 200gb drive. When i was in the partition window i used advanced and used ext4 instead of ext3. And for some reason made the 40gb drive work. When i rebooted after install i got a grub menu. I could pick the 40gb or 200gb drive. When i pick the 200gb drive it comes up Busy Box. Booting with 40gb drive it works ok. When i click on -places-on the task bar it shows the other 4 hard drives listed. I have done differant things to get the 200gb drive to work but no luck.

(NB: it's a summary for myself)
UUID of both Ubuntu disks
/dev/sda1: UUID="db318bec-8552-4384-aebc-d569e644a95b" TYPE="ext4" 200GB
/dev/sda5: UUID="0d9c3989-2f0f-4bf2-a5a6-f7a0e2229cf6" TYPE="swap" 200GB
/dev/sdb1: UUID="a93aef37-ce17-43ec-b14f-de66c904c16e" TYPE="ext4" 41.1GB
/dev/sdb5: UUID="39dfb629-3604-416c-856b-673e13d084ae" TYPE="swap " 41.1GB
+ two 500GB disks with XP
------------------------------------------------------------------------------------------------------------------
Perhaps now you don't have a Grub problem in 200GB, as you can access from it to 40GB disks, but a booting issue inside Lucid.
For 200GB, you should have two options, the first one is standard, the second one is "recovery".
Could you try this second option ?
And can you boot also on your two XP disks ?

It looks like it is going to boot from the 200gb drive. I went into recovery mode. It started listing a long list of line and then went into BusyBox again. This time i typed in exit and it then it opened a recovery menu. I picked update grub loader and it ran. Then i picked repair broken packages. Then i picked normal boot. It asked for my login and password. It then booted into desktop of 200gb drive. I don't know why i picked the word exit to use but it put it into recovery menu. It still will not give me the option to boot from the drives with XP Pro on them.

The thread became huge, so I have difficulties to retrieve data.

You have 4 disks, one 9.10, one 10.4 and two XPs.
Are you supposed to be able to boot on both XP disks ?
When you put bootable XP disk in first position in BIOS boot order, can you boot on it ?

Both XP disks will boot if first in BIOS boot order. One of the sata drives has two XP Pro systems on it and they were both in the menu list of the 40gb drive when it had an older Ubuntu OS on it. Only had one sata drive at that time.

In theory, you should be able to see these three "!!" XP boots, with 200GB/Ubuntu 10.4.
You should put 200GB disk at first in BIOS, boot on it and then:
     sudo grub-install /dev/sda

But a configuration with Ubuntu 9.10, 10.04 and many XPs looks for me very complex.
I advise you strongly to explore virtual machines, like Virtual Box, to experiment such situation, and perhaps also to avoid it.