Grub Loader Issue

[Old-Polack]

Here we go guys, Here is the output op told me to post. there is no catalog file

Code: [Select]

[guest@localhost guest]$ su root
Password:
su: incorrect password
[guest@localhost guest]$ su root
Password:
[root@localhost ~]# ls -l /boot/grub
total 313
-rw-r--r-- 1 root root     30 Jul  9  2011 device.map
-rw-r--r-- 1 root root     30 Mar 16  2010 device.map.backup
-rw-r--r-- 1 root root     30 Jul  9  2011 device.map.old
-rw-r--r-- 1 root root   8604 Jun 11  2011 e2fs_stage1_5
-rw-r--r-- 1 root root   7924 Jun 11  2011 fat_stage1_5
-rw-r--r-- 1 root root   7184 Jun 11  2011 ffs_stage1_5
-rwxr-xr-x 1 root root    115 Jul  9  2011 install.sh*
-rwxr-xr-x 1 root root    115 Jul  9  2011 install.sh.old*
-rw-r--r-- 1 root root   8760 Jun 11  2011 iso9660_stage1_5
-rw-r--r-- 1 root root   8592 Jun 11  2011 jfs_stage1_5
-rw-r--r-- 1 root root   7364 Jun 11  2011 minix_stage1_5
-rw-r--r-- 1 root root   9616 Jun 11  2011 reiserfs_stage1_5
-rw-r--r-- 1 root root   3576 Feb 17  2010 splash.xpm.gz
-rw-r--r-- 1 root root    512 Jun 11  2011 stage1
-rw-r--r-- 1 root root 113276 Jun 11  2011 stage2
-rw-r--r-- 1 root root 114812 Jun  9  2011 stage2_eltorito
-rw-r--r-- 1 root root   7448 Jun 11  2011 ufs2_stage1_5
-rw-r--r-- 1 root root   6808 Jun 11  2011 vstafs_stage1_5
-rw-r--r-- 1 root root   9268 Jun 11  2011 xfs_stage1_5
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# cat /boot/grub/menu.lst
cat: /boot/grub/menu.lst: No such file or directory
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# cat /etc/fstab
/dev/root / rootfs defaults 0 0
none /proc proc defaults 0 0
none /dev/pts devpts defaults 0 0
[root@localhost ~]#


You are posting that from a liveCD, which I asked you not to do. The commands I asked you to run only give the information we need when executed from the installed running system.

You can't follow instructions from two or more people, mixing parts of each set of instructions with others from someone else. Instructions pertaining to running from a liveCD will always be different from running an installed system. You said you were running from your second installed system, so I gave you instructions for getting the information needed while in that specific environment.

Pick a single reply. Follow all the instructions on that one reply and post the results that were asked for, and direct those answers to the person that wrote the reply you are answering. Pick the next reply and do the same. It's easier if you click the Quote link on the reply you are answering, as I have done here. Scroll down to the last end quote tag, place your cursor after the tag, left click, then press the Enter key twice, to start two new lines, then post the information requested in the quoted text above. Click the Preview button to see what your reply will look like when it's posted. It will appear above the Post reply window, so you may need to scroll up to see it. Scroll back down to the Post reply window to make any changes you want. When the preview meets your approval, click on the Post button.

[david1958]

sorry op. I went back and reread. I will take care of this in the morning sir. We will get it.

[david1958]

Here we go guys, Here is the output op told me to post. there is no catalog file

Code: [Select]

[guest@localhost guest]$ su root
Password:
su: incorrect password
[guest@localhost guest]$ su root
Password:
[root@localhost ~]# ls -l /boot/grub
total 313
-rw-r--r-- 1 root root     30 Jul  9  2011 device.map
-rw-r--r-- 1 root root     30 Mar 16  2010 device.map.backup
-rw-r--r-- 1 root root     30 Jul  9  2011 device.map.old
-rw-r--r-- 1 root root   8604 Jun 11  2011 e2fs_stage1_5
-rw-r--r-- 1 root root   7924 Jun 11  2011 fat_stage1_5
-rw-r--r-- 1 root root   7184 Jun 11  2011 ffs_stage1_5
-rwxr-xr-x 1 root root    115 Jul  9  2011 install.sh*
-rwxr-xr-x 1 root root    115 Jul  9  2011 install.sh.old*
-rw-r--r-- 1 root root   8760 Jun 11  2011 iso9660_stage1_5
-rw-r--r-- 1 root root   8592 Jun 11  2011 jfs_stage1_5
-rw-r--r-- 1 root root   7364 Jun 11  2011 minix_stage1_5
-rw-r--r-- 1 root root   9616 Jun 11  2011 reiserfs_stage1_5
-rw-r--r-- 1 root root   3576 Feb 17  2010 splash.xpm.gz
-rw-r--r-- 1 root root    512 Jun 11  2011 stage1
-rw-r--r-- 1 root root 113276 Jun 11  2011 stage2
-rw-r--r-- 1 root root 114812 Jun  9  2011 stage2_eltorito
-rw-r--r-- 1 root root   7448 Jun 11  2011 ufs2_stage1_5
-rw-r--r-- 1 root root   6808 Jun 11  2011 vstafs_stage1_5
-rw-r--r-- 1 root root   9268 Jun 11  2011 xfs_stage1_5
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# cat /boot/grub/menu.lst
cat: /boot/grub/menu.lst: No such file or directory
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# cat /etc/fstab
/dev/root / rootfs defaults 0 0
none /proc proc defaults 0 0
none /dev/pts devpts defaults 0 0
[root@localhost ~]#


You are posting that from a liveCD, which I asked you not to do. The commands I asked you to run only give the information we need when executed from the installed running system.

You can't follow instructions from two or more people, mixing parts of each set of instructions with others from someone else. Instructions pertaining to running from a liveCD will always be different from running an installed system. You said you were running from your second installed system, so I gave you instructions for getting the information needed while in that specific environment.

Pick a single reply. Follow all the instructions on that one reply and post the results that were asked for, and direct those answers to the person that wrote the reply you are answering. Pick the next reply and do the same. It's easier if you click the Quote link on the reply you are answering, as I have done here. Scroll down to the last end quote tag, place your cursor after the tag, left click, then press the Enter key twice, to start two new lines, then post the information requested in the quoted text above. Click the Preview button to see what your reply will look like when it's posted. It will appear above the Post reply window, so you may need to scroll up to see it. Scroll back down to the Post reply window to make any changes you want. When the preview meets your approval, click on the Post button.

Here is what you want  op

Code: [Select]

[david@localhost ~]$ su root
Password:
[root@localhost ~]# ls -l /boot/grub
total 364
-rw-r--r-- 1 root root     30 Apr 24 12:47 device.map
-rw-r--r-- 1 root root     30 Mar 15  2010 device.map.backup
-rw-r--r-- 1 root root     15 Jan  5 18:50 device.map.old
-rw-r--r-- 1 root root   8604 Jan  5 18:48 e2fs_stage1_5
-rw-r--r-- 1 root root   7924 Jan  5 18:48 fat_stage1_5
-rw-r--r-- 1 root root   7184 Jan  5 18:48 ffs_stage1_5
-rwxr-xr-x 1 root root    115 Apr 24 12:47 install.sh*
-rwxr-xr-x 1 root root    115 Jan  5 18:50 install.sh.old*
-rw-r--r-- 1 root root   8760 Jan  5 18:48 iso9660_stage1_5
-rw-r--r-- 1 root root   8592 Jan  5 18:48 jfs_stage1_5
-rw------- 1 root root    971 Apr 24 12:47 menu.lst
-rw------- 1 root root    931 Jan  5 18:50 menu.lst.old
-rw-r--r-- 1 root root   7364 Jan  5 18:48 minix_stage1_5
-rw-r--r-- 1 root root   9616 Jan  5 18:48 reiserfs_stage1_5
-rw-r--r-- 1 root root   3576 Feb 16  2010 splash.xpm.gz
-rw-r--r-- 1 root root    512 Jan  5 18:48 stage1
-rw-r--r-- 1 root root 113276 Jan  5 18:48 stage2
-rw-r--r-- 1 root root 114812 Jun  9  2011 stage2_eltorito
-rw-r--r-- 1 root root   7448 Jan  5 18:48 ufs2_stage1_5
-rw-r--r-- 1 root root   6808 Jan  5 18:48 vstafs_stage1_5
-rw-r--r-- 1 root root   9268 Jan  5 18:48 xfs_stage1_5
[root@localhost ~]#
[root@localhost ~]# cat /boot/grub/menu.lst 
timeout 20
color black/cyan yellow/cyan
gfxmenu (hd0,5)/boot/gfxmenu
default 0

title PCLinuxOS_FullMonty
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4 splash=silent vga=788
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty-nonfb
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty(failsafe)
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b failsafe nokmsboot vmalloc=256M
initrd (hd0,5)/boot/initrd.img

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

title memtest-4.20
kernel (hd0,5)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20  nokmsboot
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# cat /etc/fstab
# Entry for /dev/sda6 :
UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b / ext4 defaults 1 1
# Entry for /dev/sda8 :
UUID=eecf80ed-3d62-4410-9f0c-1e356694e936 /home ext4 defaults 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda7 :
UUID=43745e83-85f1-435a-9d20-805001c885a4 swap swap defaults 0 0
none /dev/pts devpts defaults 0 0
[root@localhost ~]#


[david1958]

]We need to see the contents thereof. The boot stanza for this installation appears to be trying to find the kernel on the wrong partition, most likely the swap partition.

david1958

Follow these steps to let us know what is the content of linux partition you have.
1. Run your livcd.
2. Log into root account in console:

Code: [Select]

su root [Enter][Passwd][Enter]3. Umount all automatically mounted partitions:

Code: [Select]

umount -a4. Make the proper directories to mount all of your linux partitions:

Code: [Select]

mkdir /mnt/sda7

Code: [Select]

mkdir /mnt/sda9

Code: [Select]

mkdir /mnt/sdb6

Code: [Select]

mkdir /mnt/sdb85. Mount linux partition at already created mount-points:

Code: [Select]

mount /dev/sda7 /mnt/sda7

Code: [Select]

mount /dev/sda9 /mnt/sda9

Code: [Select]

mount /dev/sdb6 /mnt/sdb6

Code: [Select]

mount /dev/sdb8 /mnt/sdb86. Now it's the FINNISH - show result of commands:

Code: [Select]

ls -al /mnt/sda7

Code: [Select]

ls -al /mnt/sda9

Code: [Select]

ls -al /mnt/sdb6

Code: [Select]

ls -al /mnt/sdb8

I did not do this one. I did the one op spoke of. Let me know if you need me to do all of this. I believe you will find my results to op on page 3

[Old-Polack]

sorry op. I went back and reread. I will take care of this in the morning sir. We will get it.

Trust me, I know this all seems to want to spin your head around, when it's all new to you. We've all been there and done that too. 

Hang in there, and don't get too frustrated. Basically try to stay calm, and look at this as a puzzle to solve. We have to work as a team, because only you can see your monitor, but don't necessarily understand what it's trying to tell you. Many of us do know what it's trying to tall you, but again, we can't see what you see. The trick to this whole thing is to have you do the looking, and command entering, then report to us in a manner that does allow us to see what you see.

Sometimes a single post can give all the information we need, to give you instructions for a quick fix. Other times it takes a series of posts, from us and from you, to get to the source of the problem at hand. Once we finally get there, we can then offer the best advise we know. Sometimes that is an easy fix, sometimes a harder but still correct fix, and sometimes we know the fix will be far more difficult and time consuming than simply reinstalling the system. If it comes to that, the good news is PCLinuxOS is very easy to reinstall. Always the choice is yours as to whether you wish to continue and learn something in the process, or decide the time involved is of greater value than the knowledge to be gained

Sometimes we ( I ) type a lot of information in a single reply in a manner that may be interpreted as being a bit harsh or abrupt, but it's not intended as such. It's just a matter of trying to get the information down and posted as quickly as possible, to prevent the person we're addressing from doing further damage to his/her system, if it looks like they may be heading that way.

Another thing, if you don't fully understand what's being asked of you, rather than guess and possibly make a mess of things, just ask for clarification. We do this all the time, and sometimes assume we're being very clear in our replies, and questions, and the person receiving the information, looks at it and thinks we must be from the far side of Mars, and speaking a totally alien language, different from any known on Earth. If you don't understand the language used, part of our job is helping you learn the language, as well as fix your system.

If you can have a bit of patience with us, and we you, we will figure out how to communicate effectively and get the job done. 

[Old-Polack]

Here is what you want  op

Code: [Select]

[david@localhost ~]$ su root
Password:
[root@localhost ~]# ls -l /boot/grub
total 364
-rw-r--r-- 1 root root     30 Apr 24 12:47 device.map
-rw-r--r-- 1 root root     30 Mar 15  2010 device.map.backup
-rw-r--r-- 1 root root     15 Jan  5 18:50 device.map.old
-rw-r--r-- 1 root root   8604 Jan  5 18:48 e2fs_stage1_5
-rw-r--r-- 1 root root   7924 Jan  5 18:48 fat_stage1_5
-rw-r--r-- 1 root root   7184 Jan  5 18:48 ffs_stage1_5
-rwxr-xr-x 1 root root    115 Apr 24 12:47 install.sh*
-rwxr-xr-x 1 root root    115 Jan  5 18:50 install.sh.old*
-rw-r--r-- 1 root root   8760 Jan  5 18:48 iso9660_stage1_5
-rw-r--r-- 1 root root   8592 Jan  5 18:48 jfs_stage1_5
-rw------- 1 root root    971 Apr 24 12:47 menu.lst
-rw------- 1 root root    931 Jan  5 18:50 menu.lst.old
-rw-r--r-- 1 root root   7364 Jan  5 18:48 minix_stage1_5
-rw-r--r-- 1 root root   9616 Jan  5 18:48 reiserfs_stage1_5
-rw-r--r-- 1 root root   3576 Feb 16  2010 splash.xpm.gz
-rw-r--r-- 1 root root    512 Jan  5 18:48 stage1
-rw-r--r-- 1 root root 113276 Jan  5 18:48 stage2
-rw-r--r-- 1 root root 114812 Jun  9  2011 stage2_eltorito
-rw-r--r-- 1 root root   7448 Jan  5 18:48 ufs2_stage1_5
-rw-r--r-- 1 root root   6808 Jan  5 18:48 vstafs_stage1_5
-rw-r--r-- 1 root root   9268 Jan  5 18:48 xfs_stage1_5
[root@localhost ~]#
[root@localhost ~]# cat /boot/grub/menu.lst 
timeout 20
color black/cyan yellow/cyan
gfxmenu (hd0,5)/boot/gfxmenu
default 0

title PCLinuxOS_FullMonty
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4 splash=silent vga=788
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty-nonfb
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty(failsafe)
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b failsafe nokmsboot vmalloc=256M
initrd (hd0,5)/boot/initrd.img

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

title memtest-4.20
kernel (hd0,5)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20  nokmsboot
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# cat /etc/fstab
# Entry for /dev/sda6 :
UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b / ext4 defaults 1 1
# Entry for /dev/sda8 :
UUID=eecf80ed-3d62-4410-9f0c-1e356694e936 /home ext4 defaults 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda7 :
UUID=43745e83-85f1-435a-9d20-805001c885a4 swap swap defaults 0 0
none /dev/pts devpts defaults 0 0
[root@localhost ~]#


Excellent!

In your menu.lst stanzas there is no mention of the second installation, ie no means to boot to it from this menu.lst.

That would indicate that the other installation contains the master menu.lst that allows you to boot all your OS, or it contains only the information to boot whatever is on that hard drive alone, and you choose which hard drive to boot from, each time you start the computer. The question is, "Which is it?"

You don't need to tell me because that information can be gotten with the next set of commands;

From a terminal on this OS, su to root, then enter;

[root@localhost ~]# mkdir -p /mnt/here                      <Enter>

[root@localhost ~]# mount /dev/sdb6 /mnt/here                         <Enter>

[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst                            <Enter>

That last command is to see if there is a menu.lst file present on the second hard drive installation. If it is there, we then want to see what it contains.

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

We also want to see what that installation's fstab looks like;

[root@localhost ~]# cat /mnt/here/etc/fstab                          <Enter>

Assuming all has worked as planned, post your results from the last two commands.

If you get error messages anywhere along the way, stop what you are doing, and post the prompt, command and error message, exactly as you see them.

[david1958]

Here is what you want  op

Code: [Select]

[david@localhost ~]$ su root
Password:
[root@localhost ~]# ls -l /boot/grub
total 364
-rw-r--r-- 1 root root     30 Apr 24 12:47 device.map
-rw-r--r-- 1 root root     30 Mar 15  2010 device.map.backup
-rw-r--r-- 1 root root     15 Jan  5 18:50 device.map.old
-rw-r--r-- 1 root root   8604 Jan  5 18:48 e2fs_stage1_5
-rw-r--r-- 1 root root   7924 Jan  5 18:48 fat_stage1_5
-rw-r--r-- 1 root root   7184 Jan  5 18:48 ffs_stage1_5
-rwxr-xr-x 1 root root    115 Apr 24 12:47 install.sh*
-rwxr-xr-x 1 root root    115 Jan  5 18:50 install.sh.old*
-rw-r--r-- 1 root root   8760 Jan  5 18:48 iso9660_stage1_5
-rw-r--r-- 1 root root   8592 Jan  5 18:48 jfs_stage1_5
-rw------- 1 root root    971 Apr 24 12:47 menu.lst
-rw------- 1 root root    931 Jan  5 18:50 menu.lst.old
-rw-r--r-- 1 root root   7364 Jan  5 18:48 minix_stage1_5
-rw-r--r-- 1 root root   9616 Jan  5 18:48 reiserfs_stage1_5
-rw-r--r-- 1 root root   3576 Feb 16  2010 splash.xpm.gz
-rw-r--r-- 1 root root    512 Jan  5 18:48 stage1
-rw-r--r-- 1 root root 113276 Jan  5 18:48 stage2
-rw-r--r-- 1 root root 114812 Jun  9  2011 stage2_eltorito
-rw-r--r-- 1 root root   7448 Jan  5 18:48 ufs2_stage1_5
-rw-r--r-- 1 root root   6808 Jan  5 18:48 vstafs_stage1_5
-rw-r--r-- 1 root root   9268 Jan  5 18:48 xfs_stage1_5
[root@localhost ~]#
[root@localhost ~]# cat /boot/grub/menu.lst 
timeout 20
color black/cyan yellow/cyan
gfxmenu (hd0,5)/boot/gfxmenu
default 0

title PCLinuxOS_FullMonty
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4 splash=silent vga=788
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty-nonfb
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty(failsafe)
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b failsafe nokmsboot vmalloc=256M
initrd (hd0,5)/boot/initrd.img

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

title memtest-4.20
kernel (hd0,5)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20  nokmsboot
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# cat /etc/fstab
# Entry for /dev/sda6 :
UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b / ext4 defaults 1 1
# Entry for /dev/sda8 :
UUID=eecf80ed-3d62-4410-9f0c-1e356694e936 /home ext4 defaults 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda7 :
UUID=43745e83-85f1-435a-9d20-805001c885a4 swap swap defaults 0 0
none /dev/pts devpts defaults 0 0
[root@localhost ~]#


Excellent!

In your menu.lst stanzas there is no mention of the second installation, ie no means to boot to it from this menu.lst.

That would indicate that the other installation contains the master menu.lst that allows you to boot all your OS, or it contains only the information to boot whatever is on that hard drive alone, and you choose which hard drive to boot from, each time you start the computer. The question is, "Which is it?"

You don't need to tell me because that information can be gotten with the next set of commands;

From a terminal on this OS, su to root, then enter;

[root@localhost ~]# mkdir -p /mnt/here                      <Enter>

[root@localhost ~]# mount /dev/sdb6 /mnt/here                         <Enter>

[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst                            <Enter>

That last command is to see if there is a menu.lst file present on the second hard drive installation. If it is there, we then want to see what it contains.

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

We also want to see what that installation's fstab looks like;

[root@localhost ~]# cat /mnt/here/etc/fstab                          <Enter>

Assuming all has worked as planned, post your results from the last two commands.

If you get error messages anywhere along the way, stop what you are doing, and post the prompt, command and error message, exactly as you see them.

OP here is the info you requsted. Just to let you know that on both hd's, the good one I have working rite now has xp/full monty and when I loaded them both good and the 1 with the issue, At the end of the load, when it came to choose bootloader, I chose the first radio button which i dont have to explain but I set both to use the linux boot loader to start.
Appricate you working with me. I got no errors on the terminal also
David

[david@localhost ~]$ su root
Password:
[root@localhost ~]# mkdir -p /mnt/here
[root@localhost ~]# mount /dev/sdb6 /mnt/here
[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst
-rw------- 1 root root    971 Apr 24 12:47 menu.lst
-rw------- 1 root root    931 Jan  5 18:50 menu.lst.old
[root@localhost ~]#
[root@localhost ~]# cat /mnt/here/boot/grub/menu.lst     
timeout 20
color black/cyan yellow/cyan
gfxmenu (hd0,5)/boot/gfxmenu
default 0

title PCLinuxOS_FullMonty
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4 splash=silent vga=788
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty-nonfb
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty(failsafe)
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b failsafe nokmsboot vmalloc=256M
initrd (hd0,5)/boot/initrd.img

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

title memtest-4.20
kernel (hd0,5)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20  nokmsboot
[root@localhost ~]#
[root@localhost ~]# cat /mnt/here/etc/fstab
# Entry for /dev/sda6 :
UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b / ext4 defaults 1 1
# Entry for /dev/sda8 :
UUID=eecf80ed-3d62-4410-9f0c-1e356694e936 /home ext4 defaults 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda7 :
UUID=43745e83-85f1-435a-9d20-805001c885a4 swap swap defaults 0 0
none /dev/pts devpts defaults 0 0
[root@localhost ~]#
 

[Old-Polack]

Here is what you want  op

Code: [Select]

[david@localhost ~]$ su root
Password:
[root@localhost ~]# ls -l /boot/grub
total 364
-rw-r--r-- 1 root root     30 Apr 24 12:47 device.map
-rw-r--r-- 1 root root     30 Mar 15  2010 device.map.backup
-rw-r--r-- 1 root root     15 Jan  5 18:50 device.map.old
-rw-r--r-- 1 root root   8604 Jan  5 18:48 e2fs_stage1_5
-rw-r--r-- 1 root root   7924 Jan  5 18:48 fat_stage1_5
-rw-r--r-- 1 root root   7184 Jan  5 18:48 ffs_stage1_5
-rwxr-xr-x 1 root root    115 Apr 24 12:47 install.sh*
-rwxr-xr-x 1 root root    115 Jan  5 18:50 install.sh.old*
-rw-r--r-- 1 root root   8760 Jan  5 18:48 iso9660_stage1_5
-rw-r--r-- 1 root root   8592 Jan  5 18:48 jfs_stage1_5
-rw------- 1 root root    971 Apr 24 12:47 menu.lst
-rw------- 1 root root    931 Jan  5 18:50 menu.lst.old
-rw-r--r-- 1 root root   7364 Jan  5 18:48 minix_stage1_5
-rw-r--r-- 1 root root   9616 Jan  5 18:48 reiserfs_stage1_5
-rw-r--r-- 1 root root   3576 Feb 16  2010 splash.xpm.gz
-rw-r--r-- 1 root root    512 Jan  5 18:48 stage1
-rw-r--r-- 1 root root 113276 Jan  5 18:48 stage2
-rw-r--r-- 1 root root 114812 Jun  9  2011 stage2_eltorito
-rw-r--r-- 1 root root   7448 Jan  5 18:48 ufs2_stage1_5
-rw-r--r-- 1 root root   6808 Jan  5 18:48 vstafs_stage1_5
-rw-r--r-- 1 root root   9268 Jan  5 18:48 xfs_stage1_5
[root@localhost ~]#
[root@localhost ~]# cat /boot/grub/menu.lst 
timeout 20
color black/cyan yellow/cyan
gfxmenu (hd0,5)/boot/gfxmenu
default 0

title PCLinuxOS_FullMonty
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4 splash=silent vga=788
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty-nonfb
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty(failsafe)
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b failsafe nokmsboot vmalloc=256M
initrd (hd0,5)/boot/initrd.img

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

title memtest-4.20
kernel (hd0,5)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20  nokmsboot
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# cat /etc/fstab
# Entry for /dev/sda6 :
UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b / ext4 defaults 1 1
# Entry for /dev/sda8 :
UUID=eecf80ed-3d62-4410-9f0c-1e356694e936 /home ext4 defaults 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda7 :
UUID=43745e83-85f1-435a-9d20-805001c885a4 swap swap defaults 0 0
none /dev/pts devpts defaults 0 0
[root@localhost ~]#


Excellent!

In your menu.lst stanzas there is no mention of the second installation, ie no means to boot to it from this menu.lst.

That would indicate that the other installation contains the master menu.lst that allows you to boot all your OS, or it contains only the information to boot whatever is on that hard drive alone, and you choose which hard drive to boot from, each time you start the computer. The question is, "Which is it?"

You don't need to tell me because that information can be gotten with the next set of commands;

From a terminal on this OS, su to root, then enter;

[root@localhost ~]# mkdir -p /mnt/here                      <Enter>

[root@localhost ~]# mount /dev/sdb6 /mnt/here                         <Enter>

[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst                            <Enter>

That last command is to see if there is a menu.lst file present on the second hard drive installation. If it is there, we then want to see what it contains.

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

We also want to see what that installation's fstab looks like;

[root@localhost ~]# cat /mnt/here/etc/fstab                          <Enter>

Assuming all has worked as planned, post your results from the last two commands.

If you get error messages anywhere along the way, stop what you are doing, and post the prompt, command and error message, exactly as you see them.

OP here is the info you requsted. Just to let you know that on both hd's, the good one I have working rite now has xp/full monty and when I loaded them both good and the 1 with the issue, At the end of the load, when it came to choose bootloader, I chose the first radio button which i dont have to explain but I set both to use the linux boot loader to start.
Appricate you working with me. I got no errors on the terminal also
David

[david@localhost ~]$ su root
Password:
[root@localhost ~]# mkdir -p /mnt/here
[root@localhost ~]# mount /dev/sdb6 /mnt/here
[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst
-rw------- 1 root root    971 Apr 24 12:47 menu.lst
-rw------- 1 root root    931 Jan  5 18:50 menu.lst.old
[root@localhost ~]#
[root@localhost ~]# cat /mnt/here/boot/grub/menu.lst     
timeout 20
color black/cyan yellow/cyan
gfxmenu (hd0,5)/boot/gfxmenu
default 0

title PCLinuxOS_FullMonty
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4 splash=silent vga=788
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty-nonfb
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty(failsafe)
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b failsafe nokmsboot vmalloc=256M
initrd (hd0,5)/boot/initrd.img

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

title memtest-4.20
kernel (hd0,5)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20  nokmsboot
[root@localhost ~]#
[root@localhost ~]# cat /mnt/here/etc/fstab
# Entry for /dev/sda6 :
UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b / ext4 defaults 1 1
# Entry for /dev/sda8 :
UUID=eecf80ed-3d62-4410-9f0c-1e356694e936 /home ext4 defaults 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda7 :
UUID=43745e83-85f1-435a-9d20-805001c885a4 swap swap defaults 0 0
none /dev/pts devpts defaults 0 0
[root@localhost ~]#
 

OK ... You are, in fact, booted to /dev/sdb6 but your fstab thinks it's /dev/sda6. Confusing to say the least. Next set of commands;

[root@localhost ~]# umount /mnt/here                         <Enter>

To check that the partition did get unmounted;

[root@localhost ~]# ls -l /mnt/here                            <Enter>

The result should be total 0 if the partition was successfully unmounted. Now we mount /dev/sda7 and request the same information as we did from /dev/sdb6.

[root@localhost ~]# mount /dev/sda7 /mnt/here                         <Enter>

[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst                            <Enter>

Again, if it is there, we then want to see what it contains.

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

...and the contents of its fstab;

[root@localhost ~]# cat /mnt/here/etc/fstab                          <Enter>

Post your results from the last two commands.

And again, if you get error messages anywhere along the way, stop what you are doing, and post the prompt, command and error message, exactly as you see them.

[david1958]

Here is what you want  op

Code: [Select]

[david@localhost ~]$ su root
Password:
[root@localhost ~]# ls -l /boot/grub
total 364
-rw-r--r-- 1 root root     30 Apr 24 12:47 device.map
-rw-r--r-- 1 root root     30 Mar 15  2010 device.map.backup
-rw-r--r-- 1 root root     15 Jan  5 18:50 device.map.old
-rw-r--r-- 1 root root   8604 Jan  5 18:48 e2fs_stage1_5
-rw-r--r-- 1 root root   7924 Jan  5 18:48 fat_stage1_5
-rw-r--r-- 1 root root   7184 Jan  5 18:48 ffs_stage1_5
-rwxr-xr-x 1 root root    115 Apr 24 12:47 install.sh*
-rwxr-xr-x 1 root root    115 Jan  5 18:50 install.sh.old*
-rw-r--r-- 1 root root   8760 Jan  5 18:48 iso9660_stage1_5
-rw-r--r-- 1 root root   8592 Jan  5 18:48 jfs_stage1_5
-rw------- 1 root root    971 Apr 24 12:47 menu.lst
-rw------- 1 root root    931 Jan  5 18:50 menu.lst.old
-rw-r--r-- 1 root root   7364 Jan  5 18:48 minix_stage1_5
-rw-r--r-- 1 root root   9616 Jan  5 18:48 reiserfs_stage1_5
-rw-r--r-- 1 root root   3576 Feb 16  2010 splash.xpm.gz
-rw-r--r-- 1 root root    512 Jan  5 18:48 stage1
-rw-r--r-- 1 root root 113276 Jan  5 18:48 stage2
-rw-r--r-- 1 root root 114812 Jun  9  2011 stage2_eltorito
-rw-r--r-- 1 root root   7448 Jan  5 18:48 ufs2_stage1_5
-rw-r--r-- 1 root root   6808 Jan  5 18:48 vstafs_stage1_5
-rw-r--r-- 1 root root   9268 Jan  5 18:48 xfs_stage1_5
[root@localhost ~]#
[root@localhost ~]# cat /boot/grub/menu.lst 
timeout 20
color black/cyan yellow/cyan
gfxmenu (hd0,5)/boot/gfxmenu
default 0

title PCLinuxOS_FullMonty
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4 splash=silent vga=788
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty-nonfb
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty(failsafe)
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b failsafe nokmsboot vmalloc=256M
initrd (hd0,5)/boot/initrd.img

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

title memtest-4.20
kernel (hd0,5)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20  nokmsboot
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# cat /etc/fstab
# Entry for /dev/sda6 :
UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b / ext4 defaults 1 1
# Entry for /dev/sda8 :
UUID=eecf80ed-3d62-4410-9f0c-1e356694e936 /home ext4 defaults 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda7 :
UUID=43745e83-85f1-435a-9d20-805001c885a4 swap swap defaults 0 0
none /dev/pts devpts defaults 0 0
[root@localhost ~]#


Excellent!

In your menu.lst stanzas there is no mention of the second installation, ie no means to boot to it from this menu.lst.

That would indicate that the other installation contains the master menu.lst that allows you to boot all your OS, or it contains only the information to boot whatever is on that hard drive alone, and you choose which hard drive to boot from, each time you start the computer. The question is, "Which is it?"

You don't need to tell me because that information can be gotten with the next set of commands;

From a terminal on this OS, su to root, then enter;

[root@localhost ~]# mkdir -p /mnt/here                      <Enter>

[root@localhost ~]# mount /dev/sdb6 /mnt/here                         <Enter>

[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst                            <Enter>

That last command is to see if there is a menu.lst file present on the second hard drive installation. If it is there, we then want to see what it contains.

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

We also want to see what that installation's fstab looks like;

[root@localhost ~]# cat /mnt/here/etc/fstab                          <Enter>

Assuming all has worked as planned, post your results from the last two commands.

If you get error messages anywhere along the way, stop what you are doing, and post the prompt, command and error message, exactly as you see them.

OP here is the info you requsted. Just to let you know that on both hd's, the good one I have working rite now has xp/full monty and when I loaded them both good and the 1 with the issue, At the end of the load, when it came to choose bootloader, I chose the first radio button which i dont have to explain but I set both to use the linux boot loader to start.
Appricate you working with me. I got no errors on the terminal also
David

[david@localhost ~]$ su root
Password:
[root@localhost ~]# mkdir -p /mnt/here
[root@localhost ~]# mount /dev/sdb6 /mnt/here
[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst
-rw------- 1 root root    971 Apr 24 12:47 menu.lst
-rw------- 1 root root    931 Jan  5 18:50 menu.lst.old
[root@localhost ~]#
[root@localhost ~]# cat /mnt/here/boot/grub/menu.lst     
timeout 20
color black/cyan yellow/cyan
gfxmenu (hd0,5)/boot/gfxmenu
default 0

title PCLinuxOS_FullMonty
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4 splash=silent vga=788
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty-nonfb
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty-nonfb root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b quiet nokmsboot vmalloc=256M acpi=on resume=UUID=43745e83-85f1-435a-9d20-805001c885a4
initrd (hd0,5)/boot/initrd.img

title PCLinuxOS_FullMonty(failsafe)
kernel (hd0,5)/boot/vmlinuz BOOT_IMAGE=PCLinuxOS_FullMonty(failsafe) root=UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b failsafe nokmsboot vmalloc=256M
initrd (hd0,5)/boot/initrd.img

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

title memtest-4.20
kernel (hd0,5)/boot/memtest-4.20 BOOT_IMAGE=memtest-4.20  nokmsboot
[root@localhost ~]#
[root@localhost ~]# cat /mnt/here/etc/fstab
# Entry for /dev/sda6 :
UUID=01091d57-3be9-4fe3-9b0d-5e99da5dd52b / ext4 defaults 1 1
# Entry for /dev/sda8 :
UUID=eecf80ed-3d62-4410-9f0c-1e356694e936 /home ext4 defaults 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda7 :
UUID=43745e83-85f1-435a-9d20-805001c885a4 swap swap defaults 0 0
none /dev/pts devpts defaults 0 0
[root@localhost ~]#
 

OK ... You are, in fact, booted to /dev/sdb6 but your fstab thinks it's /dev/sda6. Confusing to say the least. Next set of commands;

[root@localhost ~]# umount /mnt/here                         <Enter>

To check that the partition did get unmounted;

[root@localhost ~]# ls -l /mnt/here                            <Enter>

The result should be total 0 if the partition was successfully unmounted. Now we mount /dev/sda7 and request the same information as we did from /dev/sdb6.

[root@localhost ~]# mount /dev/sda7 /mnt/here                         <Enter>

[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst                            <Enter>

Again, if it is there, we then want to see what it contains.

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

...and the contents of its fstab;

[root@localhost ~]# cat /mnt/here/etc/fstab                          <Enter>

Post your results from the last two commands.

And again, if you get error messages anywhere along the way, stop what you are doing, and post the prompt, command and error message, exactly as you see them.

op i did not run it all for "it cannot find directory" so i think this is where you want me to stop. I will resubmit if I am wrong and you want me to run the rest of the commands I will do so.
David 1958

[david@localhost ~]$ su root
Password:
[root@localhost ~]# umount /mnt/here
umount: /mnt/here: not mounted
[root@localhost ~]# ls -l /mnt/here
total 0
[root@localhost ~]# mount /dev/sda7 /mnt/here
mount: you must specify the filesystem type
[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst
ls: cannot access /mnt/here/boot/grub: No such file or directory
[root@localhost ~]#

[Old-Polack]

OK ... You are, in fact, booted to /dev/sdb6 but your fstab thinks it's /dev/sda6. Confusing to say the least. Next set of commands;

[root@localhost ~]# umount /mnt/here                         <Enter>

To check that the partition did get unmounted;

[root@localhost ~]# ls -l /mnt/here                            <Enter>

The result should be total 0 if the partition was successfully unmounted. Now we mount /dev/sda7 and request the same information as we did from /dev/sdb6.

[root@localhost ~]# mount /dev/sda7 /mnt/here                         <Enter>

[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst                            <Enter>

Again, if it is there, we then want to see what it contains.

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

...and the contents of its fstab;

[root@localhost ~]# cat /mnt/here/etc/fstab                          <Enter>

Post your results from the last two commands.

And again, if you get error messages anywhere along the way, stop what you are doing, and post the prompt, command and error message, exactly as you see them.

op i did not run it all for "it cannot find directory" so i think this is where you want me to stop. I will resubmit if I am wrong and you want me to run the rest of the commands I will do so.
David 1958

[david@localhost ~]$ su root
Password:
[root@localhost ~]# umount /mnt/here
umount: /mnt/here: not mounted
[root@localhost ~]# ls -l /mnt/here
total 0
[root@localhost ~]# mount /dev/sda7 /mnt/here
mount: you must specify the filesystem type
[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst
ls: cannot access /mnt/here/boot/grub: No such file or directory
[root@localhost ~]#

Yup, good call. This is exactly what I wanted you to do in case of an error.

The error message, in blue above, indicates the partition format type can't be read. This is usually caused by corruption of the superblock on that partition. We can tell for sure by running a filesystem check (fsck -fy) on that partition. On the first run, you will most likely get another error message with reference to the superblock. Not to panic. There are backup superblocks available, and if even one is uncorrupted the filesystem can be saved. We'll start with a regular fsck command, and plan our next move when we see the actual results.

[root@localhost ~]# fsck -fy /dev/sda7               <Enter>

Post your results.

[david1958]

OK ... You are, in fact, booted to /dev/sdb6 but your fstab thinks it's /dev/sda6. Confusing to say the least. Next set of commands;

[root@localhost ~]# umount /mnt/here                         <Enter>

To check that the partition did get unmounted;

[root@localhost ~]# ls -l /mnt/here                            <Enter>

The result should be total 0 if the partition was successfully unmounted. Now we mount /dev/sda7 and request the same information as we did from /dev/sdb6.

[root@localhost ~]# mount /dev/sda7 /mnt/here                         <Enter>

[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst                            <Enter>

Again, if it is there, we then want to see what it contains.

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

...and the contents of its fstab;

[root@localhost ~]# cat /mnt/here/etc/fstab                          <Enter>

Post your results from the last two commands.

And again, if you get error messages anywhere along the way, stop what you are doing, and post the prompt, command and error message, exactly as you see them.

op i did not run it all for "it cannot find directory" so i think this is where you want me to stop. I will resubmit if I am wrong and you want me to run the rest of the commands I will do so.
David 1958

[david@localhost ~]$ su root
Password:
[root@localhost ~]# umount /mnt/here
umount: /mnt/here: not mounted
[root@localhost ~]# ls -l /mnt/here
total 0
[root@localhost ~]# mount /dev/sda7 /mnt/here
mount: you must specify the filesystem type
[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst
ls: cannot access /mnt/here/boot/grub: No such file or directory
[root@localhost ~]#

Yup, good call. This is exactly what I wanted you to do in case of an error.

The error message, in blue above, indicates the partition format type can't be read. This is usually caused by corruption of the superblock on that partition. We can tell for sure by running a filesystem check (fsck -fy) on that partition. On the first run, you will most likely get another error message with reference to the superblock. Not to panic. There are backup superblocks available, and if even one is uncorrupted the filesystem can be saved. We'll start with a regular fsck command, and plan our next move when we see the actual results.

[root@localhost ~]# fsck -fy /dev/sda7               <Enter>

Post your results.

No data received
Unable to load the webpage because the server sent no data.
Here are some suggestions:
Reload this webpage later.
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.

[david1958]

OK ... You are, in fact, booted to /dev/sdb6 but your fstab thinks it's /dev/sda6. Confusing to say the least. Next set of commands;

[root@localhost ~]# umount /mnt/here                         <Enter>

To check that the partition did get unmounted;

[root@localhost ~]# ls -l /mnt/here                            <Enter>

The result should be total 0 if the partition was successfully unmounted. Now we mount /dev/sda7 and request the same information as we did from /dev/sdb6.

[root@localhost ~]# mount /dev/sda7 /mnt/here                         <Enter>

[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst                            <Enter>

Again, if it is there, we then want to see what it contains.

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

...and the contents of its fstab;

[root@localhost ~]# cat /mnt/here/etc/fstab                          <Enter>

Post your results from the last two commands.

And again, if you get error messages anywhere along the way, stop what you are doing, and post the prompt, command and error message, exactly as you see them.

op i did not run it all for "it cannot find directory" so i think this is where you want me to stop. I will resubmit if I am wrong and you want me to run the rest of the commands I will do so.
David 1958

[david@localhost ~]$ su root
Password:
[root@localhost ~]# umount /mnt/here
umount: /mnt/here: not mounted
[root@localhost ~]# ls -l /mnt/here
total 0
[root@localhost ~]# mount /dev/sda7 /mnt/here
mount: you must specify the filesystem type
[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst
ls: cannot access /mnt/here/boot/grub: No such file or directory
[root@localhost ~]#

Yup, good call. This is exactly what I wanted you to do in case of an error.

The error message, in blue above, indicates the partition format type can't be read. This is usually caused by corruption of the superblock on that partition. We can tell for sure by running a filesystem check (fsck -fy) on that partition. On the first run, you will most likely get another error message with reference to the superblock. Not to panic. There are backup superblocks available, and if even one is uncorrupted the filesystem can be saved. We'll start with a regular fsck command, and plan our next move when we see the actual results.

[root@localhost ~]# fsck -fy /dev/sda7               <Enter>

Post your results.

No data received
Unable to load the webpage because the server sent no data.
Here are some suggestions:
Reload this webpage later.
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.

Op, i sent you a pm on the pastebin page.

[Old-Polack]

For others reading along, the above mentioned pastebin link is here.

 http://pastebin.com/mSFVt7ze

david1958:

With that out of the way, extensive repairs were made, but some files were sent to lost+found as unrecoverable. They may be critical, or they may have been unsaved copies from memory that didn't get properly saved because of a bad shut down. If the latter, the OS itself may still be completely intact. First thing to do now is again try to mount the partition. If that now works, we can again try to view the contents of the files we were originally trying to access.

Start with the command;

[root@localhost ~]# mount /dev/sda7 /mnt/here                         <Enter>

If it again returns... mount: you must specify the filesystem type... try this command;

[root@localhost ~]# mount -t ext4 /dev/sda7 /mnt/here                  <Enter>

That assumes that you used the default ext4 filesystem. If you chose ext3 you'll get a "wrong fs type" error and will need to substitute ext3 when you re-run the command.

If the mount goes smoothly, with no errors, then continue with;

[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst                            <Enter>

Again, if it is there, we then want to see what it contains.

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

...and the contents of its fstab;

[root@localhost ~]# cat /mnt/here/etc/fstab                          <Enter>

Post your results from the last two commands.

And again, if you get error messages anywhere along the way, stop what you are doing, and post the prompt, command and error message, exactly as you see them.

[david1958]

For others reading along, the above mentioned pastebin link is here.

 http://pastebin.com/mSFVt7ze

david1958:

With that out of the way, extensive repairs were made, but some files were sent to lost+found as unrecoverable. They may be critical, or they may have been unsaved copies from memory that didn't get properly saved because of a bad shut down. If the latter, the OS itself may still be completely intact. First thing to do now is again try to mount the partition. If that now works, we can again try to view the contents of the files we were originally trying to access.

Start with the command;

[root@localhost ~]# mount /dev/sda7 /mnt/here                         <Enter>

If it again returns... mount: you must specify the filesystem type... try this command;

[root@localhost ~]# mount -t ext4 /dev/sda7 /mnt/here                  <Enter>

That assumes that you used the default ext4 filesystem. If you chose ext3 you'll get a "wrong fs type" error and will need to substitute ext3 when you re-run the command.

If the mount goes smoothly, with no errors, then continue with;

[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst                            <Enter>

Again, if it is there, we then want to see what it contains.

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

...and the contents of its fstab;

[root@localhost ~]# cat /mnt/here/etc/fstab                          <Enter>

Post your results from the last two commands.

And again, if you get error messages anywhere along the way, stop what you are doing, and post the prompt, command and error message, exactly as you see them.

OP i am going to stop till you check  this. I ran the first commands like you told me to try and this is what I get. As for repair yesterday, yes I think on the one command it did do some repairs, but I could not send you that first list of commands for the program would not take it. Let me know what to do on this. I would rather check with you than congtinue. Let me know. I will check back at noon

Code: [Select]

[david@localhost ~]$ su root
Password:
[root@localhost ~]# mount /dev/sda7 /mnt/here
mount: /dev/sda7 already mounted or /mnt/here busy
mount: according to mtab, /dev/sda7 is already mounted on /mnt/here
[root@localhost ~]# mount -t ext4 /dev/sda7 /mnt/here
mount: /dev/sda7 already mounted or /mnt/here busy
mount: according to mtab, /dev/sda7 is already mounted on /mnt/here
[root@localhost ~]#


[Old-Polack]

For others reading along, the above mentioned pastebin link is here.

 http://pastebin.com/mSFVt7ze

david1958:

With that out of the way, extensive repairs were made, but some files were sent to lost+found as unrecoverable. They may be critical, or they may have been unsaved copies from memory that didn't get properly saved because of a bad shut down. If the latter, the OS itself may still be completely intact. First thing to do now is again try to mount the partition. If that now works, we can again try to view the contents of the files we were originally trying to access.

Start with the command;

[root@localhost ~]# mount /dev/sda7 /mnt/here                         <Enter>

If it again returns... mount: you must specify the filesystem type... try this command;

[root@localhost ~]# mount -t ext4 /dev/sda7 /mnt/here                  <Enter>

That assumes that you used the default ext4 filesystem. If you chose ext3 you'll get a "wrong fs type" error and will need to substitute ext3 when you re-run the command.

If the mount goes smoothly, with no errors, then continue with;

[root@localhost ~]# ls -l /mnt/here/boot/grub |grep menu.lst                            <Enter>

Again, if it is there, we then want to see what it contains.

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

...and the contents of its fstab;

[root@localhost ~]# cat /mnt/here/etc/fstab                          <Enter>

Post your results from the last two commands.

And again, if you get error messages anywhere along the way, stop what you are doing, and post the prompt, command and error message, exactly as you see them.

OP i am going to stop till you check  this. I ran the first commands like you told me to try and this is what I get. As for repair yesterday, yes I think on the one command it did do some repairs, but I could not send you that first list of commands for the program would not take it. Let me know what to do on this. I would rather check with you than congtinue. Let me know. I will check back at noon

Code: [Select]

[david@localhost ~]$ su root
Password:
[root@localhost ~]# mount /dev/sda7 /mnt/here
mount: /dev/sda7 already mounted or /mnt/here busy
mount: according to mtab, /dev/sda7 is already mounted on /mnt/here
[root@localhost ~]# mount -t ext4 /dev/sda7 /mnt/here
mount: /dev/sda7 already mounted or /mnt/here busy
mount: according to mtab, /dev/sda7 is already mounted on /mnt/here
[root@localhost ~]#


It says the mount was successful, and /dev/sda7 should now be accessible on /mnt/here. This is what we want. Now it's time to try the last three commands from the quoted text above. If the first reveals that there is a /boot/grub/menu.lst present, then you need to post the results of the last two commands.