Installation Not Showing. Resolved

[wavemaker]

OP,, I'm really sorry but this isn't working for me. Yes I am running the live CD and I'm unsure what it is you want me to  do  next.

[Old-Polack]

OP,, I'm really sorry but this isn't working for me. Yes I am running the live CD and I'm unsure what it is you want me to  do  next.

Open a terminal and execute the three commands given, in the order given. If you are logged in as guest you will first have to use the su command, and give the root password, which is root also. When the prompt is [root@localhost ~]# in red you are ready to type the commands. Use copy/paste to post the results of the last command.

[wavemaker]

Good morning OP. I can't remember where the / partition is. How do I find out. Starting to feel like a real dunce here. Should I start again and create a bigger partition on the external drive?

[Old-Polack]

[root@localhost root]# cat /boot/grub/menu.lst
cat: /boot/grub/menu.lst: No such file or directory
[root@localhost root]#

Are you posting from the liveCD? If so you need to mount the partition with your installation somewhere, then add the mount point to the path.

Example:

[root@localhost root]# mkdir /here          <Enter>

[root@localhost root]# mount /dev/<whatever> /here             <Enter>

[root@localhost root]# cat /here/boot/grub/menu.lst               <Enter>

Replace <whatever> with the proper designation for your installation's / partition. If you installed to /dev/sda5 <whatever> would be sda5

Good morning OP. I can't remember where the / partition is. How do I find out. Starting to feel like a real dunce here. Should I start again and create a bigger partition on the external drive?

I'm sorry, but at the moment I'm laughing at you, I hope you'll see the humor, and join me.

You have an installation on (hd0,4) which with current kernels would normally be /dev/sda5. That would be my best guess, and why I suggested that in my previous post, quoted above to get it on this page for easy reference. You can check by opening the root terminal and issuing the command;

[root@localhost ~]# fdisk -l          <Enter>  <-- That's a lower case letter L

Post the results.

[wavemaker]

Thanks OP. I laugh a lot at me too. I think it must be the autism.


[root@localhost root]# fdisk -l     

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00003285

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       27598   221680903+   7  HPFS/NTFS
/dev/sda2           27599       30401    22515097+   5  Extended
/dev/sda5           27599       29062    11759548+  83  Linux
/dev/sda6           29063       29221     1277136   82  Linux swap / Solaris
/dev/sda7           29222       30401     9478318+  83  Linux

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe8900690

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1        6374    51199123+   7  HPFS/NTFS
/dev/sdb2            6375      110465   836110957+   7  HPFS/NTFS
/dev/sdb3          110466      121601    89449920    5  Extended
/dev/sdb5          110466      112033    12594928+  83  Linux
/dev/sdb6          112034      112542     4088511   82  Linux swap / Solaris
/dev/sdb7          112543      121601    72766386   83  Linux
[root@localhost root]#

[wavemaker]

So, OP, I have done that and below are the results. I dont know what I did differently as I had done this half a dozen times and the rotten thing kept tellin me it was a bad command.


root@localhost root]# mkdir /here
mkdir: cannot create directory `/here': File exists
[root@localhost root]# mount /dev/sda5 /here
[root@localhost root]# cat /here/boot/grub/menu.lst   
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd1,4)/boot/gfxmenu
default 0

title linux
kernel (hd1,4)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  resume=UUID=bf0c64e6-bb73-4228-88a2-b6f3a4a7eb2a splash=silent vga=788
initrd (hd1,4)/boot/initrd.img

title linux-nonfb
kernel (hd1,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  resume=UUID=bf0c64e6-bb73-4228-88a2-b6f3a4a7eb2a
initrd (hd1,4)/boot/initrd.img

title failsafe
kernel (hd1,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  failsafe
initrd (hd1,4)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

title windows1
root (hd1,0)
map (0x81) (0x80)
map (0x80) (0x81)
makeactive
chainloader +1
[root@localhost root]#

[wavemaker]

Gooday again. Having done all that,hopefully correctly, I still don't get a GRUB at start up. Just launches straight into windows.

[Old-Polack]

So, OP, I have done that and below are the results. I dont know what I did differently as I had done this half a dozen times and the rotten thing kept tellin me it was a bad command.


root@localhost root]# mkdir /here
mkdir: cannot create directory `/here': File exists
[root@localhost root]# mount /dev/sda5 /here
[root@localhost root]# cat /here/boot/grub/menu.lst   
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd1,4)/boot/gfxmenu
default 0

title linux
kernel (hd1,4)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  resume=UUID=bf0c64e6-bb73-4228-88a2-b6f3a4a7eb2a splash=silent vga=788
initrd (hd1,4)/boot/initrd.img

title linux-nonfb
kernel (hd1,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  resume=UUID=bf0c64e6-bb73-4228-88a2-b6f3a4a7eb2a
initrd (hd1,4)/boot/initrd.img

title failsafe
kernel (hd1,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  failsafe
initrd (hd1,4)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

title windows1
root (hd1,0)
map (0x81) (0x80)
map (0x80) (0x81)
makeactive
chainloader +1
[root@localhost root]#

See all those blue 1s above. I do believe that's your problem. They should each be a 0 indicating to look on the same drive for the installation, not the external drive. You should be able to open the file with kwrite, as root, edit the file to change each (hd1,4) to (hd0,4) save the file and be able to boot to the installed system. The first problem is getting the file opened in kwrite. I use the following command.

[root@localhost root]# kwrite /here/boot/grub/menu.lst               <Enter>

If it does not work, try;

[root@localhost root]# dbus-launch kwrite /here/boot/grub/menu.lst       <Enter>

One should work. If not, pressing the Alt+F2 keys on your keyboard, (That's the Alt key, and the F2 key) at the same time, should bring up a run command box. Enter in that box;

kdesu kwrite /here/boot/grub/menu.lst

You will get a pop up box. Enter the root password

root

then press the Enter key, or click the OK button.

Kwrite should start with the open menu.lst file.

Once kwrite is open click the Edit menu item, and choose Replace towards the bottom of the drop down menu.



At the bottom of kwrite these boxes will appear;



Fill the two boxes as below;



Then click the Replace All button. Check to see that all went well, then save the file.

Try to reboot to the hard drive installation.

Post your results.

[wavemaker]

I believe I have done that correctly, below is the latest output. I rebooted and got a  failure error 21.


[root@localhost root]# mkdir /here
[root@localhost root]# mount /dev/sda5 /here
[root@localhost root]# cat /here/boot/grub/menu.lst     
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
default 0

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  resume=UUID=bf0c64e6-bb73-4228-88a2-b6f3a4a7eb2a splash=silent vga=788
initrd (hd0,4)/boot/initrd.img

title linux-nonfb
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  resume=UUID=bf0c64e6-bb73-4228-88a2-b6f3a4a7eb2a
initrd (hd0,4)/boot/initrd.img

title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  failsafe
initrd (hd0,4)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

title windows1
root (hd1,0)
map (0x81) (0x80)
map (0x80) (0x81)
makeactive
chainloader +1
[root@localhost root]#

[Old-Polack]

wavemaker:

From the Grub manual:

21 : Selected disk does not exist
      This error is returned if the device part of a device- or full
      file name refers to a disk or BIOS device that is not present or
      not recognized by the BIOS in the system.

The menu.lst looks good. The only other thing I can think of might be that the UUID number is incorrect, for either the resume or / partition, or both. You could try changing them in the first stanza.

From:

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  resume=UUID=bf0c64e6-bb73-4228-88a2-b6f3a4a7eb2a splash=silent vga=788
initrd (hd0,4)/boot/initrd.img

To:

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=/dev/sda5 resume=/dev/sda6 splash=silent vga=788
initrd (hd0,4)/boot/initrd.img

Again, use kwrite to do this, and as we are experimenting here, do just the one stanza for now. Do the edit, save the file. then try again to boot to the installed system.

Post your results.

[wavemaker]

Thanks again. I got the following trying to boot the hard disc.
Grub Loading Stage 1.5
Grub Loading Please Wait. Error 21.

Out put after edit.

[root@localhost root]# mkdir /here 
[root@localhost root]# mount /dev/sda5 /here
[root@localhost root]# cat /here/boot/grub/menu.lst
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
default 0

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root= /dev/sda5  resume= /dev/sda6  splash=silent vga=788
initrd (hd0,4)/boot/initrd.img

title linux-nonfb
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  resume=UUID=bf0c64e6-bb73-4228-88a2-b6f3a4a7eb2a
initrd (hd0,4)/boot/initrd.img

title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  failsafe
initrd (hd0,4)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

title windows1
root (hd1,0)
map (0x81) (0x80)
map (0x80) (0x81)
makeactive
chainloader +1
[root@localhost root]#

[Old-Polack]

Thanks again. I got the following trying to boot the hard disc.
Grub Loading Stage 1.5
Grub Loading Please Wait. Error 21.

Out put after edit.

[root@localhost root]# mkdir /here 
[root@localhost root]# mount /dev/sda5 /here
[root@localhost root]# cat /here/boot/grub/menu.lst
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
default 0

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root= /dev/sda5  resume= /dev/sda6  splash=silent vga=788
initrd (hd0,4)/boot/initrd.img

title linux-nonfb
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  resume=UUID=bf0c64e6-bb73-4228-88a2-b6f3a4a7eb2a
initrd (hd0,4)/boot/initrd.img

title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  failsafe
initrd (hd0,4)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

title windows1
root (hd1,0)
map (0x81) (0x80)
map (0x80) (0x81)
makeactive
chainloader +1
[root@localhost root]#

You left a space after root= and after resume=

There should be none. Linux Is very sensitive about what spaces mean, and the space, after each, breaks the line inappropriately. One more edit.

[wavemaker]

Sorry to report but same result. Error 21.


[root@localhost root]#  mkdir /here
[root@localhost root]# mount /dev/sda5 /here
[root@localhost root]# cat /here/boot/grub/menu.lst     
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
default 0

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=/dev/sda5  resume=/dev/sda6  splash=silent vga=788
initrd (hd0,4)/boot/initrd.img

title linux-nonfb
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  resume=UUID=bf0c64e6-bb73-4228-88a2-b6f3a4a7eb2a
initrd (hd0,4)/boot/initrd.img

title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=72a14156-c6de-48ae-a914-026d72a5a7b4  failsafe
initrd (hd0,4)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

title windows1
root (hd1,0)
map (0x81) (0x80)
map (0x80) (0x81)
makeactive
chainloader +1
[root@localhost root]#

[Old-Polack]

wavemaker:

For the sake of argument, what happens if you shut down, unplug the external drive, leave it unattached, then try to boot?

[wavemaker]

I will give that a try. In that last post where I had left a space in front of the edits, I just tried removing the space at the end of the edits, same result. I will replace those spaces for now.