« previous next »
Pages: 1 [2] 3   Go Down

Author Topic: Fixing A Tri Boot  (Read 3671 times)

Offline Duvid

  • Sr. Member
  • ****
  • Posts: 270
Re: Fixing A Tri Boot
« Reply #15 on: October 05, 2009, 04:18:39 PM »
 Realized my syntax was wrong ( think that is the correct wording) so now the terminal reads as such

  grub> root (hd0,0)
 Filesystem type is ext2fs, partition type 0x83

grub> setup (hd0,0)
 Checking if "/boot/grub/stage1" exists... no
 Checking if "/grub/stage1" exists... no

Error 15: File not found


Nothing is after the above line
« Last Edit: October 05, 2009, 04:20:25 PM by Duvid »
Logged

Offline Gnarly

  • New Friend
  • *
  • Posts: 9
Re: Fixing A Tri Boot
« Reply #16 on: October 05, 2009, 04:40:53 PM »
Quote from: Duvid on October 05, 2009, 04:18:39 PM
Realized my syntax was wrong ( think that is the correct wording) so now the terminal reads as such

  grub> root (hd0,0)
 Filesystem type is ext2fs, partition type 0x83

grub> setup (hd0,0)
 Checking if "/boot/grub/stage1" exists... no
 Checking if "/grub/stage1" exists... no

Error 15: File not found






Nothing is after the above line


Try   

grub> setup (hd0)
Logged

Online Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11522
  • ----IOFLU----
Re: Fixing A Tri Boot
« Reply #17 on: October 05, 2009, 04:46:01 PM »
Quote from: Duvid on October 05, 2009, 04:18:39 PM
Realized my syntax was wrong ( think that is the correct wording) so now the terminal reads as such

  grub> root (hd0,0)
 Filesystem type is ext2fs, partition type 0x83

grub> setup (hd0,0)
 Checking if "/boot/grub/stage1" exists... no
 Checking if "/grub/stage1" exists... no

Error 15: File not found


Nothing is after the above line

Now, if you'll use the commands, as given, we might get some place. Windows is on (hd0,0). Your Linux is on (hd0,1). At least that's what your menu.lst tells me. You are installing grub to the MBR. MBR=(hd0)
« Last Edit: October 05, 2009, 04:51:26 PM by old-polack »
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Duvid

  • Sr. Member
  • ****
  • Posts: 270
Re: Fixing A Tri Boot
« Reply #18 on: October 05, 2009, 04:56:00 PM »
 That is correct.....awaiting your next suggestion :)
Logged

Online Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11522
  • ----IOFLU----
Re: Fixing A Tri Boot
« Reply #19 on: October 05, 2009, 05:03:48 PM »
Quote from: Duvid on October 05, 2009, 04:56:00 PM
That is correct.....awaiting your next suggestion :)

What suggestion? Other than use the commands as given? What you reported is not what was given.
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Duvid

  • Sr. Member
  • ****
  • Posts: 270
Re: Fixing A Tri Boot
« Reply #20 on: October 05, 2009, 05:35:07 PM »
I don't understand. I explained what I did, how I did it  with the end results showing  both menu.lst. I think I typed in the grub commands as you have suggested, but I cannot interpret the results to my benefit other than it seems that it isn't as it should be.I  think there must must be a grub some where, I haven't used a third party bootloader
 I would not be adverse to doing a clean install, but would welcome any suggestion how better to do it than I have approached it previously. The way I have it works, in that it gets me to where I need, but not the best road traveled.
  Regardless, having appreciated the feedback.
« Last Edit: October 05, 2009, 05:37:13 PM by Duvid »
Logged

Offline Duvid

  • Sr. Member
  • ****
  • Posts: 270
Re: Fixing A Tri Boot (SOLVED)
« Reply #21 on: October 05, 2009, 06:32:06 PM »
       O-P and Other Friends
 
I looked backed through the post and saw you were irked where I had two lines that showed up in two separate stanzas in my PCLOS K3 menu.lst which linked me to my menu.lst in PCLOS K4. Once I commented it out, the reason for this post was SOLVED. Below is the menu.lst with the changes made highlited in blue. This change linked me directly to the KDE4 login screen.
                                                                                                                                                                                                                                            
  timeout 5
color black/cyan yellow/cyan
gfxmenu (hd0,1)/boot/gfxmenu
default 0

title PCLinuxOS 2009.1 KDE3
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_2009.1_KDE3 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd.img

title linux-nonfb
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose
initrd (hd0,1)/boot/initrd.img

title failsafe
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c failsafe acpi=on
initrd (hd0,1)/boot/initrd.img

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

title 2.6.26.8.tex3
kernel (hd0,1)/boot/vmlinuz-2.6.26.8.tex3 BOOT_IMAGE=2.6.26.8.tex3 root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd (hd0,1)/boot/initrd-2.6.26.8.tex3.img
root      (hd0,6)
kernel      /boot/vmlinuz BOOT_IMAGE=linux root=UUID=e7ccc224-df95-4eed-9bfc-35a147f81bf5 acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd      (hd0,6)/boot/initrd.img
savedefault
boot


title      PCLinuxOS KDE4 (on /dev/sda8)
root      (hd0,7)
kernel      /boot/vmlinuz BOOT_IMAGE=linux root=UUID=338bfe6e-6e12-4096-ad54-7575eb8d506a acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=silent vga=788
initrd      (hd0,7)/boot/initrd.img
#savedefault
#boot


title linux
kernel (hd0,1)/boot/vmlinuz-2.6.27.31.tex5 BOOT_IMAGE=linux root=UUID=67712f42-4bae-49e8-8c93-4ea3415d4f9c acpi=on resume=UUID=f0016d67-3fac-49f1-b05f-1faf59720327 splash=verbose vga=788
initrd (hd0,1)/boot/initrd-2.6.27.31.tex5.img

                                               Thank you all for your help,and for jogging my brain cells
« Last Edit: October 05, 2009, 06:35:52 PM by Duvid »
Logged

Online Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11522
  • ----IOFLU----
Re: Fixing A Tri Boot
« Reply #22 on: October 05, 2009, 08:04:42 PM »
Quote from: Duvid on October 05, 2009, 05:35:07 PM
I don't understand. I explained what I did, how I did it  with the end results showing  both menu.lst. I think I typed in the grub commands as you have suggested, but I cannot interpret the results to my benefit other than it seems that it isn't as it should be.I  think there must must be a grub some where, I haven't used a third party bootloader
 I would not be adverse to doing a clean install, but would welcome any suggestion how better to do it than I have approached it previously. The way I have it works, in that it gets me to where I need, but not the best road traveled.
  Regardless, having appreciated the feedback.

I gave you a command;

grub> root (hd0,1)

You report back;

grub> root (hd0,0)

This is not the command given.

I gave you a command;

grub> setup (hd0)

You report back;

grub> setup (hd0,0)

This is not the command given.

Does this make it any clearer?

The commands I gave are based directly on your reported menu.lst for the KDE3 installation, and the other information you provided. If you don't follow the instructions exactly as given, and accurately report the results, how do you expect to make any progress?
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Duvid

  • Sr. Member
  • ****
  • Posts: 270
Re: Fixing A Tri Boot
« Reply #23 on: October 05, 2009, 08:58:55 PM »

 Although it appeared I didn't follow your instructions I had just tried other variables after doing what you had suggested. Below is the copy of what happened when entering as  you suggested.
                                        GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]

grub> root (hd0,1)
 Filesystem type is ext2fs, partition type 0x83

grub> setup (hd0)
 Checking if "/boot/grub/stage1" exists... no
 Checking if "/grub/stage1" exists... no

Error 15: File not found

grub>
Logged

Online Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11522
  • ----IOFLU----
Re: Fixing A Tri Boot
« Reply #24 on: October 05, 2009, 09:24:04 PM »
Quote from: Duvid on October 05, 2009, 08:58:55 PM

 Although it appeared I didn't follow your instructions I had just tried other variables after doing what you had suggested. Below is the copy of what happened when entering as  you suggested.
                                        GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]

grub> root (hd0,1)
 Filesystem type is ext2fs, partition type 0x83

grub> setup (hd0)
 Checking if "/boot/grub/stage1" exists... no
 Checking if "/grub/stage1" exists... no

Error 15: File not found

grub>


From a root terminal;

[root@localhost ~]# ls -l /boot/grub     <-- That's a lower case L not a number 1

Post your results.
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Duvid

  • Sr. Member
  • ****
  • Posts: 270
Re: Fixing A Tri Boot
« Reply #25 on: October 05, 2009, 10:06:44 PM »

Thanks again for hanging in there. I am really interested if there is a better way than I have been doing this.


[root@localhost duvid]# ls -l /boot/grub
total 376
-rw-rw-r-- 1 root root     30 Oct  5 19:54 device.map
-rw-r--r-- 1 root root     30 Jul 24 08:02 device.map.backup
-rw-rw-r-- 1 root root     30 Oct  3 13:51 device.map.old
-rw-r--r-- 1 root root   8512 Oct  4 19:43 e2fs_stage1_5
-rw-r--r-- 1 root root   7744 Oct  4 19:43 fat_stage1_5
-rw-r--r-- 1 root root   7040 Oct  4 19:43 ffs_stage1_5
-rwxr-xr-x 1 root root    115 Oct  5 19:54 install.sh*
-rwxr-xr-x 1 root root    115 Oct  3 13:51 install.sh.old*
-rw-r--r-- 1 root root   8576 Oct  4 19:43 iso9660_stage1_5
-rw-r--r-- 1 root root   8480 Oct  4 19:43 jfs_stage1_5
-rw-rw-r-- 1 root root   1776 Oct  5 20:51 menu.lst
-rw-rw-r-- 1 root root   1765 Oct  5 20:11 menu.lst~
-rw-r--r-- 1 root root    223 Sep 18 21:15 menu.lst.example
-rw-rw-r-- 1 root root   1998 Oct  3 13:52 menu.lst.old
-rw-r--r-- 1 root root   7168 Oct  4 19:43 minix_stage1_5
-rw-r--r-- 1 root root   9504 Oct  4 19:43 reiserfs_stage1_5
-rw-r--r-- 1 root root   3576 Oct  1 23:00 splash.xpm.gz
-rw-r--r-- 1 root root    512 Oct  4 19:43 stage1
-rw-r--r-- 1 root root 111792 Oct  5 23:41 stage2
-rw-r--r-- 1 root root 113328 Oct  4 19:43 stage2_eltorito
-rw-r--r-- 1 root root   7392 Oct  4 19:43 ufs2_stage1_5
-rw-r--r-- 1 root root   6592 Oct  4 19:43 vstafs_stage1_5
-rw-r--r-- 1 root root   9224 Oct  4 19:43 xfs_stage1_5
Logged

Online Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11522
  • ----IOFLU----
Re: Fixing A Tri Boot
« Reply #26 on: October 05, 2009, 10:36:00 PM »
Quote from: Duvid on October 05, 2009, 10:06:44 PM

Thanks again for hanging in there. I am really interested if there is a better way than I have been doing this.


[root@localhost duvid]# ls -l /boot/grub
total 376
-rw-rw-r-- 1 root root     30 Oct  5 19:54 device.map
-rw-r--r-- 1 root root     30 Jul 24 08:02 device.map.backup
-rw-rw-r-- 1 root root     30 Oct  3 13:51 device.map.old
-rw-r--r-- 1 root root   8512 Oct  4 19:43 e2fs_stage1_5
-rw-r--r-- 1 root root   7744 Oct  4 19:43 fat_stage1_5
-rw-r--r-- 1 root root   7040 Oct  4 19:43 ffs_stage1_5
-rwxr-xr-x 1 root root    115 Oct  5 19:54 install.sh*
-rwxr-xr-x 1 root root    115 Oct  3 13:51 install.sh.old*
-rw-r--r-- 1 root root   8576 Oct  4 19:43 iso9660_stage1_5
-rw-r--r-- 1 root root   8480 Oct  4 19:43 jfs_stage1_5
-rw-rw-r-- 1 root root   1776 Oct  5 20:51 menu.lst
-rw-rw-r-- 1 root root   1765 Oct  5 20:11 menu.lst~
-rw-r--r-- 1 root root    223 Sep 18 21:15 menu.lst.example
-rw-rw-r-- 1 root root   1998 Oct  3 13:52 menu.lst.old
-rw-r--r-- 1 root root   7168 Oct  4 19:43 minix_stage1_5
-rw-r--r-- 1 root root   9504 Oct  4 19:43 reiserfs_stage1_5
-rw-r--r-- 1 root root   3576 Oct  1 23:00 splash.xpm.gz
-rw-r--r-- 1 root root    512 Oct  4 19:43 stage1
-rw-r--r-- 1 root root 111792 Oct  5 23:41 stage2
-rw-r--r-- 1 root root 113328 Oct  4 19:43 stage2_eltorito
-rw-r--r-- 1 root root   7392 Oct  4 19:43 ufs2_stage1_5
-rw-r--r-- 1 root root   6592 Oct  4 19:43 vstafs_stage1_5
-rw-r--r-- 1 root root   9224 Oct  4 19:43 xfs_stage1_5


Those are all the files that you reported grub saying it can't find.

Try;

[root@localhost ~]# grub

    GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]

grub> find /boot/grub/stage2

Post your results.
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Duvid

  • Sr. Member
  • ****
  • Posts: 270
Re: Fixing A Tri Boot
« Reply #27 on: October 05, 2009, 10:44:17 PM »

 Here we go

GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]

grub> find /boot/grub/stage2
 (hd1,1)
 (hd1,7)
 
grub>



Logged

Online Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11522
  • ----IOFLU----
Re: Fixing A Tri Boot
« Reply #28 on: October 05, 2009, 11:01:07 PM »
Quote from: Duvid on October 05, 2009, 10:44:17 PM

 Here we go

GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]

grub> find /boot/grub/stage2
 (hd1,1)
 (hd1,7)
 
grub>





Open a second terminal and do this.


[root@localhost ~]# fdisk -l

Post your results.
Logged
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline Duvid

  • Sr. Member
  • ****
  • Posts: 270
Re: Fixing A Tri Boot
« Reply #29 on: October 05, 2009, 11:12:55 PM »
[root@localhost duvid]# 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: 0x00073da6

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        1958    15727603+  83  Linux
/dev/sda2            1959        5874    31455270   83  Linux
/dev/sda3           60541       60801     2096482+  82  Linux swap / Solaris
/dev/sda4            5875       60540   439104645   83  Linux

Partition table entries are not in disk order

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

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1        5222    41945683+   7  HPFS/NTFS
/dev/sdb2            5223        7180    15727635   83  Linux
/dev/sdb3            7181       20234   104856255   83  Linux
/dev/sdb4           20235      121601   814230427+   5  Extended
/dev/sdb5           20235      114029   753408306   83  Linux
/dev/sdb6          114030      117293    26218048+  83  Linux
/dev/sdb7          121341      121601     2096451   82  Linux swap / Solaris
/dev/sdb8          117294      118729    11534638+  83  Linux
/dev/sdb9          118730      121340    20972826   83  Linux

Partition table entries are not in disk order

 This past weekend I installed a 500gig HD for storage only which is why the drive with the operating systems is now called /dev/sdb instead of /dev/sda
The multiple Bootscreen was the same prior to the new hard drive
Logged
Pages: 1 [2] 3   Go Up
« previous next »