Author Topic: Grub Loader Issue  (Read 3298 times)

Offline david1958

  • PCLinuxOS Tester
  • Full Member
  • *******
  • Posts: 212
  • Lovin Linux
    • Ed's Cuckoo Uhren
Grub Loader Issue
« on: April 24, 2012, 01:21:40 PM »
Greetings, New to the forum, I have been running Pc Monty for the last 6 months as a duel boot with windows XP. Have had a few issues getting started, but I have a friend that was a good teacher so I know what i am doing. The other night everything was doing great as usual, Kaffiene tv viewer would not close out on Monty. 1st time it had ever done that. I rebooted, went into software developement and marked to uninstall and then reinstall Kaffiene. It did I rebooted Monty loaded just fine as duel boot, OPen Kaffiene tv viewer again, it works but still will not close or x out. Rebooted again, this time the hd will not boot,

I get a error here of "Grub Loading 1.5"

hangs for a second, then

Error 17

and that is it. So can I reload just the Grub Loader instead of reloading the full monty program is my question?


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: 11587
  • ----IOFLU----
Re: Grub Loader Issue
« Reply #1 on: April 24, 2012, 01:31:06 PM »
Greetings, New to the forum, I have been running Pc Monty for the last 6 months as a duel boot with windows XP. Have had a few issues getting started, but I have a friend that was a good teacher so I know what i am doing. The other night everything was doing great as usual, Kaffiene tv viewer would not close out on Monty. 1st time it had ever done that. I rebooted, went into software developement and marked to uninstall and then reinstall Kaffiene. It did I rebooted Monty loaded just fine as duel boot, OPen Kaffiene tv viewer again, it works but still will not close or x out. Rebooted again, this time the hd will not boot,

I get a error here of "Grub Loading 1.5"

hangs for a second, then

Error 17

and that is it. So can I reload just the Grub Loader instead of reloading the full monty program is my question?


From a liveCD, open a terminal, su to root, then enter;

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

Replace x with the drive letter, and n with the proper number of the installed / partition.

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 #2 on: April 25, 2012, 10:19:48 AM »
OP, I trust you but I am doing something wrong. I am logged in as route and I cannot get it to go. When I go into my pc control center and go to Manage Disk Partitions and here is what i got for info

Quote
Device: sda7
Type: Linux native (0x83)
Start: sector 492520833
Size: 100GB (21%), 210547827 sectors
Cylinder 30658 to 43763

NOw the partitions for windows xp are on the front, and linux is on the last 3 partitions. Never the less, I changed the code different ways and I still get the same results. Let me show you what I am entering

Quote
fsck -fy /dev/sdc7

where "c" should be how the hd is listed, the 7 as the partition. I had tried to add just the sd7 and sda7 and it still gives me this error

[root@localhost root]# fsck -fy /dev/sdc1
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/sdc1
Possibly non-existent device?
[root@localhost root]# fsck -fy /dev/sdc7
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/sdc7
Possibly non-existent device?
[root@localhost root]#

I know I am entering wrong. You or Mr. Brick will let me know.
tks
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: 128
  • Jest wirek - jest impreza ;]
Re: Grub Loader Issue
« Reply #3 on: April 25, 2012, 11:18:32 AM »
Run livecd, login in terminal to root:
Code: [Select]
su rootPost the result of command:
Code: [Select]
fdisk -lAfter "fdisk" is "little" L letter.
marcin'82

Offline david1958

  • PCLinuxOS Tester
  • Full Member
  • *******
  • Posts: 212
  • Lovin Linux
    • Ed's Cuckoo Uhren
Re: Grub Loader Issue
« Reply #4 on: April 25, 2012, 11:37:40 AM »
you mean fsck l  dont you? you put fdisk, itsn't that for windows.
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: 128
  • Jest wirek - jest impreza ;]
Re: Grub Loader Issue
« Reply #5 on: April 25, 2012, 11:41:28 AM »
Quote
[...]itsn't that for windows.
No, I know what I say :D Command fdisk -l will let you know what devices (e.g. /dev/sda1, /dev/sda2) are present on your HDD and what should be the proper name od device that you'll use in command fsck.

Post result as root from livecd:
Code: [Select]
fdisk -l
« Last Edit: April 25, 2012, 11:46:50 AM by marcin82 »
marcin'82

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11587
  • ----IOFLU----
Re: Grub Loader Issue
« Reply #6 on: April 25, 2012, 11:42:54 AM »
you mean fsck l  dont you? you put fdisk, itsn't that for windows.

No that is for Linux fdisk, and it will show all your partitions on all your disks like this;

[root@fatman boot]# fdisk -l
Code: [Select]
Disk /dev/sdb: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 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: 0x2db1883a

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63      208844      104391   83  Linux
/dev/sdb2          208845    12225464     6008310   82  Linux swap / Solaris
/dev/sdb3        12225465    72244304    30009420   83  Linux
/dev/sdb4        72244305  1465144064   696449880    5  Extended
/dev/sdb5        72244368   272253554   100004593+  83  Linux
/dev/sdb6       272253618   670713749   199230066   83  Linux
/dev/sdb7       670713813   731278799    30282493+  83  Linux
/dev/sdb8       731278863   811378889    40050013+  83  Linux
/dev/sdb9       811378953  1045767239   117194143+  83  Linux
/dev/sdb10     1045767303  1280155589   117194143+  83  Linux
/dev/sdb11     1280155653  1465144064    92494206   83  Linux

Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x18eee7ae

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1            2048     2099199     1048576   83  Linux
/dev/sdc2         2099200    18876415     8388608   82  Linux swap / Solaris
/dev/sdc3        18876416    81790975    31457280   83  Linux
/dev/sdc4        81790976  3907029167  1912619096    5  Extended
/dev/sdc5        81793024   176164863    47185920   83  Linux
/dev/sdc6       176166912   281024511    52428800   83  Linux
/dev/sdc7       281026560   385884159    52428800   83  Linux
/dev/sdc8       385886208   805316607   209715200   83  Linux
/dev/sdc9       805318656   857747455    26214400   83  Linux
/dev/sdc10      857749504   910178303    26214400   83  Linux

Disk /dev/sda: 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: 0x0000d21c

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63      626534      313236   83  Linux
/dev/sda2          626535    16820054     8096760   82  Linux swap / Solaris
/dev/sda3        16820055   114495254    48837600   83  Linux
/dev/sda4       114495255  1953520064   919512405    5  Extended
/dev/sda5       114495318   329332499   107418591   83  Linux
/dev/sda6       329332563   534434354   102550896   83  Linux
/dev/sda7       534434418   596943269    31254426   83  Linux
/dev/sda8       596943333   659452184    31254426   83  Linux
/dev/sda9       659452248   721961099    31254426   83  Linux
/dev/sda10      721961163   784470014    31254426   83  Linux
/dev/sda11      784470078   994198589   104864256   83  Linux
/dev/sda12      994198653  1623368249   314584798+  83  Linux
/dev/sda13     1623368313  1685893229    31262458+  83  Linux
/dev/sda14     1685893293  1749366044    31736376   83  Linux
/dev/sda15     1749366108  1816485614    33559753+  83  Linux
/dev/sda16     1816487663  1889887982    36700160   83  Linux
/dev/sda17     1889892080  1953520064    31813992+  83  Linux
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 #7 on: April 25, 2012, 12:10:07 PM »
Gents I have tried quite a few ways and as close as i can get is into the emergency it suggest -p which I tried to enter and then I get a msg about OLDPASW  check out what i got out of the terminal. sorry it is so long but I want to show both of you what i get whatever I try.

Code: [Select]
[root@localhost root]# fsck -fy /dev/sdg7
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/sdg7
Possibly non-existent device?
[root@localhost root]# fsck -fy /dev/sdg7
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/sdg7
Possibly non-existent device?
[root@localhost root]# fsck l /dev/sdg7 
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 root]# p
bash: cd: OLDPWD not set
[root@localhost root]# su
[root@localhost root]# root
bash: root: command not found
[root@localhost root]# p
bash: cd: OLDPWD not set
[root@localhost root]# -p
bash: -p: command not found
[root@localhost root]# fsck
fsck from util-linux-ng 2.18
[root@localhost root]# y
bash: y: command not found
[root@localhost root]# fsck l
fsck from util-linux-ng 2.18
[root@localhost root]# fsck g
fsck from util-linux-ng 2.18
[root@localhost root]# su to root
su: user to does not exist
[root@localhost root]# su
[root@localhost root]# guest
bash: guest: command not found
[root@localhost root]# logout
bash: logout: not login shell: use `exit'
[root@localhost root]# fsck l /dev/sdg7 
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 root]# fdsk-l
bash: fdsk-l: command not found
[root@localhost root]# fdsck l /dev/sdg7
bash: fdsck: command not found
[root@localhost root]# fdisk-l /dev/sdg7 
bash: fdisk-l: command not found
[root@localhost root]# fdisk-l
bash: fdisk-l: command not found
[root@localhost root]# fdisk l/dev/sdg7 

Unable to open l/dev/sdg7
[root@localhost root]# fdisk l/dev/sdG7 

Unable to open l/dev/sdG7
[root@localhost root]# p
bash: cd: OLDPWD not set
[root@localhost root]# password
bash: password: command not found
[root@localhost root]# OLDPWD
bash: OLDPWD: command not found
[root@localhost root]# root
bash: root: command not found
[root@localhost root]# agp-get update
bash: agp-get: command not found
[root@localhost root]# sudo
usage: sudo -h | -K | -k | -L | -V
usage: sudo -v [-AknS] [-p prompt]
usage: sudo -l[l] [-AknS] [-g groupname|#gid] [-p prompt] [-U username] [-u
            username|#uid] [-g groupname|#gid] [command]
usage: sudo [-AbEHknPS] [-C fd] [-g groupname|#gid] [-p prompt] [-u
            username|#uid] [-g groupname|#gid] [VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AknS] [-C fd] [-g groupname|#gid] [-p prompt] [-u
            username|#uid] file ...
[root@localhost root]# fdisk l/dev/sdG7 

Unable to open l/dev/sdG7
[root@localhost root]# fdisk l/dev/sdg7 

Unable to open l/dev/sdg7
[root@localhost root]# fdisk l/grub/sdg7 

Unable to open l/grub/sdg7
[root@localhost root]# fsck -fy /dev/sdf7
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/sdf7
Possibly non-existent device?
[root@localhost root]# fsck -l /dev/sdf7
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 root]# p
bash: cd: OLDPWD not set
[root@localhost root]# "p"
bash: p: command not found
[root@localhost root]# p/
bash: p/: No such file or directory
[root@localhost root]# -p
bash: -p: command not found
[root@localhost root]# -n
bash: -n: command not found
[root@localhost root]#
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: 128
  • Jest wirek - jest impreza ;]
Re: Grub Loader Issue
« Reply #8 on: April 25, 2012, 12:22:36 PM »
Root password on PCLinuxOS livecd is root.
All you should to do is:
1. Run your livecd
2. Open terminal and type:
Code: [Select]
su root [Enter]Then type in:
Code: [Select]
rootand press Enter.
3. Type in the console:
Code: [Select]
fdisk -lYou should see result like this:

marcin'82

Offline david1958

  • PCLinuxOS Tester
  • Full Member
  • *******
  • Posts: 212
  • Lovin Linux
    • Ed's Cuckoo Uhren
Re: Grub Loader Issue
« Reply #9 on: April 25, 2012, 12:24:57 PM »
ok guys, i got somthing going now. your rite fdisk -l shows me this

Code: [Select]
[root@localhost root]# 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]#
[root@localhost root]#

now mabe i am wrong. should i be puttting in /dev/sbd6?

Im not going to give up until i figure out this. that is the kind of guy i am.
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: 11587
  • ----IOFLU----
Re: Grub Loader Issue
« Reply #10 on: April 25, 2012, 12:34:56 PM »
ok guys, i got somthing going now. your rite fdisk -l shows me this

Code: [Select]
[root@localhost root]# 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]#
[root@localhost root]#

now mabe i am wrong. should i be puttting in /dev/sbd6?

Im not going to give up until i figure out this. that is the kind of guy i am.
David

That depends on which Linux installation you want to check. You seem to have two. It wouldn't hurt anything to run fsck on all four of your regular Linux partitions. Don't try running it on a swap partition... doesn't work there.
Old-Polack

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



Lest we forget...

Offline marcin82

  • Full Member
  • ***
  • Posts: 128
  • Jest wirek - jest impreza ;]
Re: Grub Loader Issue
« Reply #11 on: April 25, 2012, 12:38:16 PM »
Remember about one thing too - fsck command can't be performed on mounted filesystem. I don't remember if linux livecd mounts any partitions automatically.

For this reason, before you run FSCK type in a console command:
Code: [Select]
umount -aThen run commands:
Code: [Select]
fsck -fy /dev/sda7       
Code: [Select]
fsck -fy /dev/sda9
Code: [Select]
fsck -fy /dev/sdb6
Code: [Select]
fsck -fy /dev/sdb8
« Last Edit: April 25, 2012, 12:41:49 PM by marcin82 »
marcin'82

Offline david1958

  • PCLinuxOS Tester
  • Full Member
  • *******
  • Posts: 212
  • Lovin Linux
    • Ed's Cuckoo Uhren
Re: Grub Loader Issue
« Reply #12 on: April 25, 2012, 12:43:47 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 ~]#
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: 128
  • Jest wirek - jest impreza ;]
Re: Grub Loader Issue
« Reply #13 on: April 25, 2012, 12:47:35 PM »
Names of the block devices must be the same as they real are ... Just COPY and PASTE from this forum:

Quote
fsck -fy /dev/sda7
Quote
fsck -fy /dev/sda9
Quote
fsck -fy /dev/sdb6
Quote
fsck -fy /dev/sdb8
« Last Edit: April 25, 2012, 12:53:27 PM by marcin82 »
marcin'82

Offline david1958

  • PCLinuxOS Tester
  • Full Member
  • *******
  • Posts: 212
  • Lovin Linux
    • Ed's Cuckoo Uhren
Re: Grub Loader Issue
« Reply #14 on: April 25, 2012, 01:05:30 PM »
Ok, here is what I get in the terminal. should I or should not i for it gives the msg about the file system?

Code: [Select]
[guest@localhost guest]$ su root
Password:
[root@localhost ~]# fsck -fy /dev/sdb6
fsck from util-linux-ng 2.18
e2fsck 1.41.14 (22-Dec-2010)
/dev/sdb6 is mounted.

WARNING!!!  The filesystem is mounted.   If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.

Do you really want to continue (y/n)?


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