Author Topic: Grub Loader Issue  (Read 3312 times)

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11591
  • ----IOFLU----
Re: Grub Loader Issue
« Reply #15 on: April 25, 2012, 01:08:18 PM »
op, i did have 2 hd hooked when I ran that. I am working off of the one with the issue. I unpluged and ran it again. so it should only show what I have on here. It shows the ntfs for windows and it shows the linux. but what am i entering wrong. when i get so far it suggest -p but it will not let it go.

Code: [Select]
[guest@localhost guest]$ su root
Password:
[root@localhost ~]# fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x61777466

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63    93321584    46660761    7  HPFS/NTFS
/dev/sda2        93321585   976768064   441723240    5  Extended
/dev/sda5        93321648   339100019   122889186    7  HPFS/NTFS
/dev/sda6       339100083   492520769    76710343+   7  HPFS/NTFS
/dev/sda7       492520833   703068659   105273913+  83  Linux
/dev/sda8       703068723   719278244     8104761   82  Linux swap / Solaris
/dev/sda9       719278308   976768064   128744878+  83  Linux

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x974e974e

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63   510288659   255144298+   7  HPFS/NTFS
/dev/sdb2       510288660  1953520064   721615702+   5  Extended
/dev/sdb5       510288723  1024368659   257039968+   7  HPFS/NTFS
/dev/sdb6      1024368723  1414169819   194900548+  83  Linux
/dev/sdb7      1414169883  1422346904     4088511   82  Linux swap / Solaris
/dev/sdb8      1422346968  1953520064   265586548+  83  Linux
[root@localhost ~]# fsck -fy /dev/sbdc6
fsck from util-linux-ng 2.18
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext2: No such file or directory while trying to open /dev/sbdc6
Possibly non-existent device?
[root@localhost ~]# fsck -l /dev/sdc6
fsck from util-linux-ng 2.18
Usage: fsck.ext2 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
                [-I inode_buffer_blocks] [-P process_inode_size]
                [-l|-L bad_blocks_file] [-C fd] [-j external_journal]
                [-E extended-options] device

Emergency help:
 -p                   Automatic repair (no questions)
 -n                   Make no changes to the filesystem
 -y                   Assume "yes" to all questions
 -c                   Check for bad blocks and add them to the badblock list
 -f                   Force checking even if filesystem is marked clean
 -v                   Be verbose
 -b superblock        Use alternative superblock
 -B blocksize         Force blocksize when looking for superblock
 -j external_journal  Set location of the external journal
 -l bad_blocks_file   Add to badblocks list
 -L bad_blocks_file   Set badblocks list
[root@localhost ~]# -p
-bash: -p: command not found
[root@localhost ~]# p
-bash: cd: OLDPWD not set
[root@localhost ~]#

Don't be unplugging anything when we're troubleshooting a problem, unless specifically asked to! That's about the surest way there is to screw things up even worse.

With both drives attached, working from a liveCD, enter the commands using copy/paste from the above post by marcin82.

We can't help you if you refuse to follow the instructions, exactly as given!
« Last Edit: April 25, 2012, 01:11:34 PM by Old-Polack »
Old-Polack

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



Lest we forget...

Offline marcin82

  • Full Member
  • ***
  • Posts: 129
  • Jest wirek - jest impreza ;]
Re: Grub Loader Issue
« Reply #16 on: April 25, 2012, 01:09:03 PM »
Before you will run FSCK command - type in a console:
Code: [Select]
umount -aand tell us what is the result of this command?
marcin'82

Offline david1958

  • PCLinuxOS Tester
  • Full Member
  • *******
  • Posts: 212
  • Lovin Linux
    • Ed's Cuckoo Uhren
Re: Grub Loader Issue
« Reply #17 on: April 25, 2012, 01:30:20 PM »
Ok here is what I am going to do. I am going to shutdown, rehook the hd i unpluged. Now remember the 1t hd i have duel boot win xp/full monty and I have no problem with that one.

The 500 gig hd is the one I cannot boot. So I will set the hd that does not boot for the error and mount the live cd and get back with you in a few. I didnt realize unhooking the good hd might cause a conflict
david
To all Windows Users, Quit being Lazy and learn Linux. You'll Love it after you get the hang of it!
FullMonty Release:            2013.04
Kernel-version:    3.2.18-pclos2.pae.bfs
KDE4-version:                        4.10.1
Biostar mother Board A55MH,  CPU chip A8-3807K

8 gig ram

Offline david1958

  • PCLinuxOS Tester
  • Full Member
  • *******
  • Posts: 212
  • Lovin Linux
    • Ed's Cuckoo Uhren
Re: Grub Loader LEts Try again
« Reply #18 on: April 25, 2012, 05:28:10 PM »
Ok gents, I have both hd's hook. the second hd is the  one i have a problem with so I did the fsdisk and here is what I get

Code: [Select]
[guest@localhost guest]$ su root
Password:
[root@localhost ~]# fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x61777466

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63    93321584    46660761    7  HPFS/NTFS
/dev/sda2        93321585   976768064   441723240    5  Extended
/dev/sda5        93321648   339100019   122889186    7  HPFS/NTFS
/dev/sda6       339100083   492520769    76710343+   7  HPFS/NTFS
/dev/sda7       492520833   703068659   105273913+  83  Linux
/dev/sda8       703068723   719278244     8104761   82  Linux swap / Solaris
/dev/sda9       719278308   976768064   128744878+  83  Linux

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x974e974e

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63   510288659   255144298+   7  HPFS/NTFS
/dev/sdb2       510288660  1953520064   721615702+   5  Extended
/dev/sdb5       510288723  1024368659   257039968+   7  HPFS/NTFS
/dev/sdb6      1024368723  1414169819   194900548+  83  Linux
/dev/sdb7      1414169883  1422346904     4088511   82  Linux swap / Solaris
/dev/sdb8      1422346968  1953520064   265586548+  83  Linux
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# umount -a
umount: /: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
[root@localhost ~]#


so there is the answer to the last 2 post via both of ya.
To all Windows Users, Quit being Lazy and learn Linux. You'll Love it after you get the hang of it!
FullMonty Release:            2013.04
Kernel-version:    3.2.18-pclos2.pae.bfs
KDE4-version:                        4.10.1
Biostar mother Board A55MH,  CPU chip A8-3807K

8 gig ram

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11591
  • ----IOFLU----
Re: Grub Loader LEts Try again
« Reply #19 on: April 25, 2012, 05:34:30 PM »
Ok gents, I have both hd's hook. the second hd is the  one i have a problem with so I did the fsdisk and here is what I get

Code: [Select]
[guest@localhost guest]$ su root
Password:
[root@localhost ~]# fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x61777466

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63    93321584    46660761    7  HPFS/NTFS
/dev/sda2        93321585   976768064   441723240    5  Extended
/dev/sda5        93321648   339100019   122889186    7  HPFS/NTFS
/dev/sda6       339100083   492520769    76710343+   7  HPFS/NTFS
/dev/sda7       492520833   703068659   105273913+  83  Linux
/dev/sda8       703068723   719278244     8104761   82  Linux swap / Solaris
/dev/sda9       719278308   976768064   128744878+  83  Linux

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x974e974e

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63   510288659   255144298+   7  HPFS/NTFS
/dev/sdb2       510288660  1953520064   721615702+   5  Extended
/dev/sdb5       510288723  1024368659   257039968+   7  HPFS/NTFS
/dev/sdb6      1024368723  1414169819   194900548+  83  Linux
/dev/sdb7      1414169883  1422346904     4088511   82  Linux swap / Solaris
/dev/sdb8      1422346968  1953520064   265586548+  83  Linux
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# umount -a
umount: /: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
[root@localhost ~]#


so there is the answer to the last 2 post via both of ya.

Now enter;

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

When that check is done;

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

Post your results.
Old-Polack

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



Lest we forget...

Offline david1958

  • PCLinuxOS Tester
  • Full Member
  • *******
  • Posts: 212
  • Lovin Linux
    • Ed's Cuckoo Uhren
Re: Grub Loader Issue
« Reply #20 on: April 25, 2012, 06:25:24 PM »
 OP, here is the results of what you ask me

Code: [Select]
root@localhost ~]#
[root@localhost ~]# fsck -fy /dev/sdb6
fsck from util-linux-ng 2.18
e2fsck 1.41.14 (22-Dec-2010)
/dev/sdb6: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdb6: 420163/12181504 files (0.1% non-contiguous), 3961584/48725137 blocks
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# fsck -fy /dev/sdb8
fsck from util-linux-ng 2.18
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdb8: 13628/16605184 files (0.5% non-contiguous), 2387387/66396637 blocks
[root@localhost ~]#

I wait to see what you suggest next.
david
To all Windows Users, Quit being Lazy and learn Linux. You'll Love it after you get the hang of it!
FullMonty Release:            2013.04
Kernel-version:    3.2.18-pclos2.pae.bfs
KDE4-version:                        4.10.1
Biostar mother Board A55MH,  CPU chip A8-3807K

8 gig ram

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11591
  • ----IOFLU----
Re: Grub Loader Issue
« Reply #21 on: April 25, 2012, 07:40:56 PM »
OP, here is the results of what you ask me

Code: [Select]
root@localhost ~]#
[root@localhost ~]# fsck -fy /dev/sdb6
fsck from util-linux-ng 2.18
e2fsck 1.41.14 (22-Dec-2010)
/dev/sdb6: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdb6: 420163/12181504 files (0.1% non-contiguous), 3961584/48725137 blocks
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# fsck -fy /dev/sdb8
fsck from util-linux-ng 2.18
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdb8: 13628/16605184 files (0.5% non-contiguous), 2387387/66396637 blocks
[root@localhost ~]#

I wait to see what you suggest next.
david

Try to boot the installed system.

Post your results.
Old-Polack

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



Lest we forget...

Offline david1958

  • PCLinuxOS Tester
  • Full Member
  • *******
  • Posts: 212
  • Lovin Linux
    • Ed's Cuckoo Uhren
Re: Grub Loader Issue
« Reply #22 on: April 25, 2012, 09:02:24 PM »
OP, back to the same msg as the first post 
Code: [Select]
I get a error here of "Grub Loading 1.5"

hangs for a second, then

Error 17

as for the other hd, i booted that one just to see if it had any problems now and it does not. but the orginal is still there my friend. I will ck back around 7am.  I got cows to milk at 4am so u know what else I do too. tks for the help man and let me know the next move.
david
To all Windows Users, Quit being Lazy and learn Linux. You'll Love it after you get the hang of it!
FullMonty Release:            2013.04
Kernel-version:    3.2.18-pclos2.pae.bfs
KDE4-version:                        4.10.1
Biostar mother Board A55MH,  CPU chip A8-3807K

8 gig ram

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11591
  • ----IOFLU----
Re: Grub Loader Issue
« Reply #23 on: April 25, 2012, 09:25:52 PM »
OP, back to the same msg as the first post 
Code: [Select]
I get a error here of "Grub Loading 1.5"

hangs for a second, then

Error 17

as for the other hd, i booted that one just to see if it had any problems now and it does not. but the orginal is still there my friend. I will ck back around 7am.  I got cows to milk at 4am so u know what else I do too. tks for the help man and let me know the next move.
david

From info:grub/Stage2 errors

17 : Cannot mount selected partition
      This error is returned if the partition requested exists, but the
      filesystem type cannot be recognized by GRUB.


We just ran fsck -fy on your / partition so we know its filesystem can be read. That leaves your master /boot/grub/menu.lst as the prime suspect. 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.
Old-Polack

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



Lest we forget...

Offline david1958

  • PCLinuxOS Tester
  • Full Member
  • *******
  • Posts: 212
  • Lovin Linux
    • Ed's Cuckoo Uhren
Re: Grub Loader Issue
« Reply #24 on: April 26, 2012, 06:37:14 AM »
ok op. So per your post 
Code: [Select]
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.
how do u want me to get this info or do i just need to reload the system?
david
To all Windows Users, Quit being Lazy and learn Linux. You'll Love it after you get the hang of it!
FullMonty Release:            2013.04
Kernel-version:    3.2.18-pclos2.pae.bfs
KDE4-version:                        4.10.1
Biostar mother Board A55MH,  CPU chip A8-3807K

8 gig ram

Offline marcin82

  • Full Member
  • ***
  • Posts: 129
  • Jest wirek - jest impreza ;]
Re: Grub Loader Issue
« Reply #25 on: April 26, 2012, 08:56:49 AM »
Quote from: Old-Polack
]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.
Quote
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
marcin'82

Offline david1958

  • PCLinuxOS Tester
  • Full Member
  • *******
  • Posts: 212
  • Lovin Linux
    • Ed's Cuckoo Uhren
Re: Grub Loader Issue
« Reply #26 on: April 26, 2012, 09:06:20 AM »
I can do what you say, but rite now I am booted into another hd that does not have a problem. I think you mean to reboot under the hd that has the problem, run the live cd and then do what you 2 guys taught me on the terminal. Sorry I was such a bonehead yesterday on the terminal, but i'v only been into linux for 6 months but you got me confused with the su root and got me straight  on some other codes. I will await ur reply and then reboot the live cd.
tks again
david
To all Windows Users, Quit being Lazy and learn Linux. You'll Love it after you get the hang of it!
FullMonty Release:            2013.04
Kernel-version:    3.2.18-pclos2.pae.bfs
KDE4-version:                        4.10.1
Biostar mother Board A55MH,  CPU chip A8-3807K

8 gig ram

Online Bald Brick

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 6381
  • I'm going South
Re: Grub Loader Issue
« Reply #27 on: April 26, 2012, 10:05:32 AM »
I can do what you say, but rite now I am booted into another hd that does not have a problem. I think you mean to reboot under the hd that has the problem, run the live cd and then do what you 2 guys taught me on the terminal.

No, that's not what marcin82 wants you to do. He just wants you to 1) boot with the live CD, 2) become root (to get administrative privileges), 3) create mountpoints for all your normal Linux partitions, 4) mount the partitions at the newly created mountpoints while still running from the CD, and 5) list what's on the partitions. (It's possible to do all of this from the GUI, but using the command line is faster.)

The point is that O-P suspects your main /boot/grub/menu.lst of corruption, but as we can't be quite sure were it is, marcin82 wants to have a look at all your Linux partitions.

Quote
Sorry I was such a bonehead yesterday on the terminal, but i'v only been into linux for 6 months but you got me confused with the su root and got me straight  on some other codes. I will await ur reply and then reboot the live cd.
tks again
david

Being inexperienced is not being a bonehead.
« Last Edit: April 26, 2012, 10:14:08 AM by Bald Brick »
Feed the trolls!
They need it!

AMD Athlon 7450 Dual-Core Processor, 7.80 GiB RAM, Nvidia GeForce GT 120/PCIe/SSE2, OpenGL/ES-version: 3.3 0 NVIDIA 295.40, SBx00 Azalia (Intel HDA) soundcard, ‎Logitech B500 webcam, SAA7146 DVB card, HDDs: Seagate 250824AS, Western Digital WD10EAVS-00D

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11591
  • ----IOFLU----
Re: Grub Loader Issue
« Reply #28 on: April 26, 2012, 11:07:24 AM »
ok op. So per your post  
Code: [Select]
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.
how do u want me to get this info or do i just need to reload the system?
david

I'm assuming you are running the second Linux OS at the moment, the one on /dev/sda7, with the /home partition on /dev/sda9. That's what I'd be doing in your situation.

What distro OS is installed there? It is necessary to know, so we know what version boot loader it uses, grub or grub2. Next we need to know which of the two Linux OS installed its boot loader into the MBR of the current boot drive? Also, if you recall, did each Linux OS install its version of grub on the MBR of the hard drive it is installed on?

From your running system, not a liveCD, open a terminal, su to root, then enter;

[root@localhost ~]# ls -l /boot/grub                       <Enter>

This should tell us what version of grub this OS uses. If there is a menu.lst file present, it is legacy grub, if not then grub2.

Post your results.

If there is a menu.lst file, then enter;

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

and finally;

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

Post both of those results also.
« Last Edit: April 26, 2012, 11:16:44 AM by Old-Polack »
Old-Polack

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



Lest we forget...

Offline david1958

  • PCLinuxOS Tester
  • Full Member
  • *******
  • Posts: 212
  • Lovin Linux
    • Ed's Cuckoo Uhren
Re: Grub Loader Issue
« Reply #29 on: April 26, 2012, 06:44:29 PM »
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 ~]#
To all Windows Users, Quit being Lazy and learn Linux. You'll Love it after you get the hang of it!
FullMonty Release:            2013.04
Kernel-version:    3.2.18-pclos2.pae.bfs
KDE4-version:                        4.10.1
Biostar mother Board A55MH,  CPU chip A8-3807K

8 gig ram