1 (edited by C_Okyen 2010-11-17 04:31:28)

Topic: [SOLVED ]Logical Drive and Other Partition Error:

I have had to stop doing investigation myself on my corrupt /dev/sda5 partition due to time constraints. The /dev/sda1 partition has also has some flash warning 's in the logs you will se below.

      This image shot is the entire drives partitions from GParted Version 0.5.1.

    http://img521.imageshack.us/img521/2530/gpartedpartall.png

      Furthermore, the properties of /dev/sda5 showing the ERROR s as well:
      http://img521.imageshack.us/img521/6286/gpartednda5info.png

        Here is the log in order of when they were created ( since I never changed them AFIAK, the modified metadata should show it's in chronological order.

        Modified: Friday 29 Oct 2010 6:57:15 PM
        Accessed Sat 30 Oct 2010 3:31:42 PM
        
        GParted 0.5.1
        
        Libparted 2.2
        
        Move /dev/sda5 to the right and shrink it from 100.04 GiB to 97.23 GiB  00:00:08    ( ERROR )
                
        calibrate /dev/sda5  00:00:00    ( SUCCESS )
                
        path: /dev/sda5
        start: 20971503
        end: 230761439
        size: 209789937 (100.04 GiB)
        calculate new size and position of /dev/sda5  00:00:00    ( SUCCESS )
                
        requested start: 26844678
        requested end: 230757659
        requested size: 203912982 (97.23 GiB)
        new start: 26844615
        new end: 230757659
        new size: 203913045 (97.23 GiB)
        check file system on /dev/sda5 for ]ERRORs and (if possible) fix them  00:00:02    ( SUCCESS )
                
        ntfsresize -P -i -f -v /dev/sda5
                
        ntfsresize v2.0.0 (libntfs 10:0:0)
        Device name : /dev/sda5
        NTFS volume version: 3.1
        Cluster size : 4096 bytes
        Current volume size: 107412447744 bytes (107413 MB)
        Current device size: 107412447744 bytes (107413 MB)
        Checking for bad sectors ...
        Checking filesystem consistency ...
        Accounting clusters ...
        Space in use : 1685 MB (1.6%)
        Collecting resizing constraints ...
        Estimating smallest shrunken size supported ...
        File feature Last used at By inode
        $MFT : 3236 MB 0
        $MFTMirr : 53707 MB 1
        Sparse : 1865 MB 3020
        Ordinary : 53710 MB 10
        You might resize at 3235221504 bytes or 3236 MB (freeing 104177 MB).
        Please make a test run using both the -n and -s options before real resizing!
        shrink file system  00:00:04    ( SUCCESS )
                
        run simulation  00:00:03    ( SUCCESS )
                
        ntfsresize -P --force /dev/sda5 -s 104403479039 --no-action
                
        ntfsresize v2.0.0 (libntfs 10:0:0)
        Device name : /dev/sda5
        NTFS volume version: 3.1
        Cluster size : 4096 bytes
        Current volume size: 107412447744 bytes (107413 MB)
        Current device size: 107412447744 bytes (107413 MB)
        New volume size : 104403472896 bytes (104404 MB)
        Checking filesystem consistency ...
        Accounting clusters ...
        Space in use : 1685 MB (1.6%)
        Collecting resizing constraints ...
        Needed relocations : 0 (0 MB)
        Schedule chkdsk for NTFS consistency check at Windows boot time ...
        Resetting $LogFile ... (this might take a while)
        Updating $BadClust file ...
        Updating $Bitmap file ...
        Updating Boot record ...
        The read-only test run ended successfully.
        real resize  00:00:01    ( SUCCESS )
                
        ntfsresize -P --force /dev/sda5 -s 104403479039
                
        ntfsresize v2.0.0 (libntfs 10:0:0)
        Device name : /dev/sda5
        NTFS volume version: 3.1
        Cluster size : 4096 bytes
        Current volume size: 107412447744 bytes (107413 MB)
        Current device size: 107412447744 bytes (107413 MB)
        New volume size : 104403472896 bytes (104404 MB)
        Checking filesystem consistency ...
        Accounting clusters ...
        Space in use : 1685 MB (1.6%)
        Collecting resizing constraints ...
        Needed relocations : 0 (0 MB)
        Schedule chkdsk for NTFS consistency check at Windows boot time ...
        Resetting $LogFile ... (this might take a while)
        Updating $BadClust file ...
        Updating $Bitmap file ...
        Updating Boot record ...
        Syncing device ...
        Successfully resized NTFS on device '/dev/sda5'.
        You can go on to shrink the device for example with Linux fdisk.
        IMPORTANT: When recreating the partition, make sure that you
        1) create it at the same disk sector (use sector as the unit!)
        2) create it with the same partition type (usually 7, HPFS/NTFS)
        3) do not make it smaller than the new NTFS filesystem size
        4) set the bootable flag for the partition if it existed before
        Otherwise you won't be able to access NTFS or can't boot from the disk!
        If you make a mistake and don't have a partition table backup then you
        can recover the partition table by TestDisk or Parted's rescue mode.
        shrink partition from 100.04 GiB to 97.23 GiB  00:00:01    ( SUCCESS )
                
        old start: 20971503
        old end: 230761439
        old size: 209789937 (100.04 GiB)
        new start: 20971503
        new end: 224884547
        new size: 203913045 (97.23 GiB)
        check file system on /dev/sda5 for ERRORs and (if possible) fix them  00:00:00    ( ERROR )
                
        ntfsresize -P -i -f -v /dev/sda5
                
        ntfsresize v2.0.0 (libntfs 10:0:0)
        Device name : /dev/sda5
        NTFS volume version: 3.1
        Cluster size : 4096 bytes
        Current volume size: 107412447744 bytes (107413 MB)
        Current device size: 104403479040 bytes (104404 MB)
        ERROR: Current NTFS volume size is bigger than the device size!
        Corrupt partition table or incorrect device partitioning?
        grow file system to fill the partition  00:00:01    ( ERROR )
                
        run simulation  00:00:01    ( ERROR )
                
        ntfsresize -P --force /dev/sda5 --no-action
                
        ntfsresize v2.0.0 (libntfs 10:0:0)
        Device name : /dev/sda5
        NTFS volume version: 3.1
        Cluster size : 4096 bytes
        Current volume size: 107412447744 bytes (107413 MB)
        Current device size: 104403479040 bytes (104404 MB)
        ERROR: Current NTFS volume size is bigger than the device size!
        Corrupt partition table or incorrect device partitioning?
        ========================================
        Modified " 11::25::59 AM
        Accessed Sat 30 2010 2:55:27 PM
        
        GParted 0.5.1
        
        Libparted 2.2
        
        Check and repair file system (ntfs) on /dev/sda5  00:00:00    ( ERROR )
                
        calibrate /dev/sda5  00:00:00    ( SUCCESS )
                
        path: /dev/sda5
        start: 20971503
        end: 224884547
        size: 203913045 (97.23 GiB)
        check file system on /dev/sda5 for ERRORs and (if possible) fix them  00:00:00    ( ERROR )
                
        ntfsresize -P -i -f -v /dev/sda5
                
        ntfsresize v2.0.0 (libntfs 10:0:0)
        Device name : /dev/sda5
        NTFS volume version: 3.1
        Cluster size : 4096 bytes
        Current volume size: 107412447744 bytes (107413 MB)
        Current device size: 104403479040 bytes (104404 MB)
        ERROR: Current NTFS volume size is bigger than the device size!
        Corrupt partition table or incorrect device partitioning?
        ========================================

        gparted details.htm 
        
        Modified "                        " 4: 32:39 PM
        Accessed sat 30 10/20/10 3:32:40 PM
        
        GParted 0.5.1
        
        Libparted 2.2
        
        Move /dev/sda1 to the right and shrink it from 10.00 GiB to 9.82 GiB  00:00:17    ( ERROR )
                
        calibrate /dev/sda1  00:00:00    ( SUCCESS )
                
        path: /dev/sda1
        start: 63
        end: 20971439
        size: 20971377 (10.00 GiB)
        calculate new size and position of /dev/sda1  00:00:00    ( SUCCESS )
                
        requested start: 369495
        requested end: 20964824
        requested size: 20595330 (9.82 GiB)
        new start: 369495
        new end: 20964824
        new size: 20595330 (9.82 GiB)
        check file system on /dev/sda1 for ERRORs and (if possible) fix them  00:00:03    ( SUCCESS )
                
        ntfsresize -P -i -f -v /dev/sda1
                
        ntfsresize v2.0.0 (libntfs 10:0:0)
        Device name : /dev/sda1
        NTFS volume version: 3.1
        Cluster size : 4096 bytes
        Current volume size: 10737345024 bytes (10738 MB)
        Current device size: 10737345024 bytes (10738 MB)
        Checking for bad sectors ...
        Checking filesystem consistency ...
        Accounting clusters ...
        Space in use : 10142 MB (94.5%)
        Collecting resizing constraints ...
        Estimating smallest shrunken size supported ...
        File feature Last used at By inode
        $MFT : 10056 MB 0
        Multi-Record : 10738 MB 30115
        $MFTMirr : 5369 MB 1
        Compressed : 10734 MB 30578
        Ordinary : 10738 MB 6541
        You might resize at 10141523968 bytes or 10142 MB (freeing 596 MB).
        Please make a test run using both the -n and -s options before real resizing!
        shrink file system  00:00:11    ( ERROR )
                
        run simulation  00:00:11    ( ERROR )
                
        ntfsresize -P --force /dev/sda1 -s 10544808959 --no-action
                
        ntfsresize v2.0.0 (libntfs 10:0:0)
        Device name : /dev/sda1
        NTFS volume version: 3.1
        Cluster size : 4096 bytes
        Current volume size: 10737345024 bytes (10738 MB)
        Current device size: 10737345024 bytes (10738 MB)
        New volume size : 10544804352 bytes (10545 MB)
        Checking filesystem consistency ...
        Accounting clusters ...
        Space in use : 10142 MB (94.5%)
        Collecting resizing constraints ...
        Needed relocations : 45879 (188 MB)
        Schedule chkdsk for NTFS consistency check at Windows boot time ...
        Resetting $LogFile ... (this might take a while)
        Relocating needed data ...
        ERROR: Extended record needed (1032 > 1024), not yet supported!
        Please try to free less space.
        check file system on /dev/sda1 for ERRORs and (if possible) fix them  00:00:03    ( SUCCESS )
                
        ntfsresize -P -i -f -v /dev/sda1
                
        ntfsresize v2.0.0 (libntfs 10:0:0)
        Device name : /dev/sda1
        NTFS volume version: 3.1
        Cluster size : 4096 bytes
        Current volume size: 10737345024 bytes (10738 MB)
        Current device size: 10737345024 bytes (10738 MB)
        Checking for bad sectors ...
        Checking filesystem consistency ...
        Accounting clusters ...
        Space in use : 10142 MB (94.5%)
        Collecting resizing constraints ...
        Estimating smallest shrunken size supported ...
        File feature Last used at By inode
        $MFT : 10056 MB 0
        Multi-Record : 10738 MB 30115
        $MFTMirr : 5369 MB 1
        Compressed : 10734 MB 30578
        Ordinary : 10738 MB 6541
        You might resize at 10141523968 bytes or 10142 MB (freeing 596 MB).
        Please make a test run using both the -n and -s options before real resizing!
        grow file system to fill the partition  00:00:00    ( SUCCESS )
                
        run simulation  00:00:00    ( SUCCESS )
                
        ntfsresize -P --force /dev/sda1 --no-action
                
        ntfsresize v2.0.0 (libntfs 10:0:0)
        Device name : /dev/sda1
        NTFS volume version: 3.1
        Cluster size : 4096 bytes
        Current volume size: 10737345024 bytes (10738 MB)
        Current device size: 10737345024 bytes (10738 MB)
        New volume size : 10737340928 bytes (10738 MB)
        Nothing to do: NTFS volume size is already OK.
        real resize  00:00:00    ( SUCCESS )
                
        ntfsresize -P --force /dev/sda1
                
        ntfsresize v2.0.0 (libntfs 10:0:0)
        Device name : /dev/sda1
        NTFS volume version: 3.1
        Cluster size : 4096 bytes
        Current volume size: 10737345024 bytes (10738 MB)
        Current device size: 10737345024 bytes (10738 MB)
        New volume size : 10737340928 bytes (10738 MB)
        Nothing to do: NTFS volume size is already OK.
        ========================================

        Here is the last bit of requested command line code I add:

        root@###:~# parted /dev/sda unit s print
        Model: ATA WDC WD1600BB-22F (scsi)
        Disk /dev/sda: 312581808s
        Sector size (logical/physical): 512B/512B
        Partition Table: msdos
        
        Number  Start       End         Size                Type      File system     Flags
         1      63s         20971439s   20971377s   primary   ntfs                 boot
        
        [i][*][/*]So my real partion sda1 size is 20971377s -1 = 20971376s
        [/i]
         2      20971501s   312580095s  291608595s  extended                  lba
        
        [i][*][/*]So my real partion sda2 size is 291608595s -1 = 291608594s[/i]
        
         5      20971503s   224884547s  203913045s  logical   ntfs
        
        [i][*][/*]So my real partion sda5 size is 203913045s -1 = 203913044s[/i]
        
         6      230762496s  236761087s  5998592s    logical   linux-swap(v1)
         7      236763136s  250761215s  13998080s   logical   ext4
         8      250763264s  312580095s  61816832s   logical   ext4
        root@###:~# fdisk -l -u
        
        Disk /dev/sda: 160.0 GB, 160041885696 bytes
        255 heads, 63 sectors/track, 19457 cylinders, total 312581808 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: 0xdd5bdd5b
        
           Device Boot      Start         End      Blocks   Id  System
        /dev/sda1   *          63    20971439    10485688+   7  HPFS/NTFS
        Partition 1 does not end on cylinder boundary.
        /dev/sda2        20971501   312580095   145804297+   f  W95 Ext'd (LBA)
        
        
        /dev/sda5        20971503   224884547   101956522+   7  HPFS/NTFS
        /dev/sda6       230762496   236761087     2999296   82  Linux swap / Solaris
        /dev/sda7       236763136   250761215     6999040   83  Linux
        /dev/sda8       250763264   312580095    30908416   83  Linux

        To conclude, I am not sure if reversing what i  did would be the best option!

        Thanks

        -Chris O.

        2

        Re: [SOLVED ]Logical Drive and Other Partition Error:

        We can fix this problem.  Reversing the steps is very difficult because the ntfsprogs commands will fail because there is an error.  Hence it is best to fix this problem directly.


        To proceed we will need copies of the Master Boot Record and the NTFS Partition Boot Record.

        You can capture the Master Boot Record in a file with the following command:

        NOTE:  Be extra careful to type this command in properly, otherwise loss of data could result.

        dd if=/dev/sda of=sda-cokyen.mbr bs=512 count=1

        where sda-cokyen.mbr is the name of the file that will need to be uploaded.


        You can capture the NTFS Partition Boot Record in a file with the following command:

        NOTE:  Be extra careful to type this command in properly, otherwise loss of data could result.

        dd if=/dev/sda of=sda5-cokyen.pbr bs=512 count=1 skip=20971503

        where sda5-cokyen.pbr is the name of the file that will need to be uploaded.


        Then upload these files to a media sharing site, such as mediafire or filefactory, and post the link to these files in this forum post.

        3

        Re: [SOLVED ]Logical Drive and Other Partition Error:

        tried to backup the MBR and the NTFS Partition Boot Record as you can see in my history of commands but I think I messed up there or either when I did the command you gave me, i didnt realize exactly what dd did and that it essentially could be used as a backup image or actual partition. Note some of the commands are invalid and or didn't know the effects.

        root@:-# history

         
          642  if=/dev/sda of=sda5-cokyen.pbr
          643  dd if=/dev/sda of=sda5-cokyen.pbr

          644  sudo -s
          645  sudo -s
        I THINK this is where I tried to "backup" the MBR and NTFS Partition Boot Record




          646  /ded/hda1
          647  $dd if=/dev/sda1 of=MBR-backup bs=512 count=1
          648  if=/dev/sd1 of=MBR-backup bs=512 count=1
          649  if=/dev/sda of=MBR-backup bs=512 count=1
          650  if=/dev/hda of=MBR-backup bs=512 count=1
          651  if=/dev/sda1 of=MBR-backup bs=512 count=1
          652  if=/dev/sda  of=/dev/sda1 bs=512 count=1
          653  if=/dev/sd1  of=/dev/MBR-backup  bs=512 count=1
          654  if=/dev/sd1 of /dev/MBR-backup bs=512 count=1
          655  if=/dev/sd1 of=/dev/MBR-backup bs=512 count=1
          656  dd if=/dev/sd1 of /dev/MBR-backup bs=512 count=1

        I have recieved many many errors including these some when I open up sda5 ( im not sure if it would appear before when I got the other error for the log vol in gparted) :

        http://img820.imageshack.us/img820/4061/screenshot91.png

        And the terminal wont let me change the background settings ( it was black bg white font now it's reversed'; also, look at the greyed out area.) I dont know if other stuff on my nix root got messed up. :

        http://img703.imageshack.us/img703/8093/screenshot9g.png

        And a last screen shot of an error to help you gratefully play Sherlock Holmes- the backup partition ( IIRC ) /dev/sdb/ is having no luck finding a mounting point :

        http://img19.imageshack.us/img19/6765/screenshot432.png

        Lastly, can I trace a log of the dd command results I looked up the reference for the unix comand but all I see in the comprehensive doc is that you can add a argument that species a log files name to add. Will /var/log/ contain a log of this?

        Thank you so much and I hope I can just get some knowledge before I screw anything else up on the nix os ;P

        Cheers

        P.S. Would gparted like me to use clipping or for the matter, TGA files or something?
        -Chris Okyen

        4

        Re: [SOLVED ]Logical Drive and Other Partition Error:

        The commands must be entered EXACTLY as I stated in post #2.  These commands are dangerous if not entered correctly and can destroy your data.

        If you are not comfortable entering these commands, perhaps you might seek the help of someone who has a more in-depth understanding of computers and partition tables.

        5

        Re: [SOLVED ]Logical Drive and Other Partition Error:

        Sorry for such a late reply; here are the PBR an MBR files:

        PBR: http://www.mediafire.com/?1dndg0j4i1dfnzz
        MBR: http://www.mediafire.com/?quln308j2l3d87v

        Thanks So Much!

        -Chris

        6

        Re: [SOLVED ]Logical Drive and Other Partition Error:

        Since you were trying to shrink the partition, we will decrease the NTFS volume size to fit within the partition.

        The change I have made to the file is from a length of 209,789,936 sectors:
        00000020   00 00 00 00  80 00 80 00  F0 23 81 0C  00 00 00 00
        To a new length of 101,956,521 sectors:
        00000020   00 00 00 00  80 00 80 00  A9 BB 13 06  00 00 00 00

        Note:  The NTFS volume size is always 1 sector less than the total number of sectors in the partition table entry because the NTFS backup sector is not considered part of the NTFS volume.

        To apply this change:

        1) Download the new NTFS PBR: sda5-cokyen_new.pbr

        2) Load the new NTFS PBR on your hard disk.
        NOTE:  Be extra careful when entering the commands.  Data loss could result otherwise.

        dd if=sda5-cokyen_new.pbr of=/dev/sda bs=512 count=1 seek=20971503

        3) Reboot the computer

        4) Check that the file system is recognized in GParted

        5) If all seems fine then I would advise booting into Windows and running "chkdsk /f /r" multiple times, until there are no more faults.

        7 (edited by C_Okyen 2010-11-14 03:23:08)

        Re: [SOLVED ]Logical Drive and Other Partition Error:

        Hey I did as you said and ran chkdsk with the Fixes errors on the disk /f and/r ( Locates bad sectors and recovers readable information) parameters.

        I then verified the copying of the new pbr file worked by copying the pbr file to cokyen folder  and used a hex editor to verify A9.... string you changed was there but it was the old F0.... one sad...


        Heres my log of tampering with the command the bolded lines that did what I wanted ( correctly ): not sure if others messed it up.

        and say it was still the and the following errors are still shown in gparted for sda5 that were there before. and checked the latest event viewrs Applications -> WinLogon Log:

        NOTE: I did dd if= [ drag the file from jump drive to terminal ] of=/dev/sda bs=512 count=1 seek=209715033

          720  dd if=sda5-cokyen_new.pbr of=/dev/sda bs=512 count=1 seek=209715033
          721  dd if='/media/UDISK/boot records/fixed/sda5-cokyen_new.pbr'  of=/dev/sda bs=512 count=1 seek=209715033
          722  sudo -s
          723  SUDO -S
          724  sudo -s
          725  dd if='/media/UDISK/boot records/fixed/sda5-cokyen_new.pbr' of=/dev/sda bs=512 count=1 seek=209715033
          726  dd if=/dev/sda of=sda5-cokyen.pbr
          727  if=/dev/sda of=sda5-cokyen.pbr
          728  dd if=/dev/sda of=sda5-cokyen.pbr bs=512 count=1 skip=20971503
          729  dd if=/dev/sda of=sda-cokyen.mbr bs=512 count=1
          730  history
          731  dd if=/dev/sda of=sda5-cokyen.pbr




        11 13 2010 log application winlogon
        
        Checking file system on C:
        The type of the file system is NTFS.
        
        A disk check has been scheduled.
        Windows will now check the disk.                         
        Cleaning up minor inconsistencies on the drive.
        Cleaning up 131 unused index entries from index $SII of file 0x9.
        Cleaning up 131 unused index entries from index $SDH of file 0x9.
        Cleaning up 131 unused security descriptors.
        CHKDSK is verifying Usn Journal...
        Usn Journal verification completed.
        CHKDSK is verifying file data (stage 4 of 5)...
        File data verification completed.
        CHKDSK is verifying free space (stage 5 of 5)...
        Free space verification is complete.
        CHKDSK discovered free space marked as allocated in the
        master file table (MFT) bitmap.
        Windows has made corrections to the file system.
        
          10485688 KB total disk space.
          10001452 KB in 34424 files.
             12364 KB in 3272 indexes.
                 0 KB in bad sectors.
            105772 KB in use by the system.
             54480 KB occupied by the log file.
            366100 KB available on disk.
        
              4096 bytes in each allocation unit.
           2621422 total allocation units on disk.
             91525 allocation units available on disk.
        
        Internal Info:
        d0 9e 00 00 4c 93 00 00 8f c6 00 00 00 00 00 00  ....L...........
        84 0e 00 00 00 00 00 00 03 05 00 00 00 00 00 00  ................
        de 66 4b 01 00 00 00 00 70 08 4c 13 00 00 00 00  .fK.....p.L.....
        f2 e6 1f 07 00 00 00 00 e8 73 b9 5c 01 00 00 00  .........s.\....
        5e 19 32 10 00 00 00 00 a4 76 30 90 01 00 00 00  ^.2......v0.....
        99 9e 36 00 00 00 00 00 58 3f 07 00 78 86 00 00  ..6.....X?..x...
        00 00 00 00 00 b0 70 62 02 00 00 00 c8 0c 00 00  ......pb........
        
        Windows has finished checking your disk.
        Please wait while your computer restarts.

        it found free space marked allotted in the MFT bitmap for one.

        I probably need to run it several times but what will multiple runs do that the first did not do?

        NOTE: i tried the copy of the new pbr to my pbr and then copied that to a file in the cokyen file using the reverse order of input and output where the inputs the sda5 and the outputs the file named C_okyen_new_2 and it still had the old f0 Hex string sad
        Thanks!

        dd if='/media/UDISK/boot records/fixed/sda5-cokyen_new.pbr' of=/dev/sda bs=512 count=1 seek=209715033
        history
        root@Chris:~# dd if=/dev/sda of=sda5-cokyen_new2.pbr bs=512 count=1 skip=20971503
        1+0 records in
        1+0 records out
        512 bytes (512 B) copied, 0.000229453 s, 2.2 MB/s



        -Chris

        8

        Re: [SOLVED ]Logical Drive and Other Partition Error:

        You have to type in the command EXACTLY as I stated.  Otherwise data loss will result.

        In this quote from your message, you used seek=2097150331, not seek=20971503 as was stated.

        C_Okyen wrote:

          720  dd if=sda5-cokyen_new.pbr of=/dev/sda bs=512 count=1 seek=2097150331

        9

        Re: [SOLVED ]Logical Drive and Other Partition Error:

        i get a warning that gnome is not working properly now on the logon screen adn when I log onto ubuntu it takes a second and goes to a screen like right before the logon with black backgorund and white text and then goes again to the logon screen. xterm doesnt even work.

        10

        Re: [SOLVED ]Logical Drive and Other Partition Error:

        By the way, ubuntu doesnt give the logon error now. But would doing the dd if of command again correctly fix it

        11

        Re: [SOLVED ]Logical Drive and Other Partition Error:

        Thanks so much I fixed it by redoing what you said correctly using a backup .pbr file on my jumpdrive smile! However, this whole mess was caused by me messing with sda2 and sda5 moving and resizing the partitions; should I just try to resize the data partition? I am afraid it will get corrupted again since I am not sure if Version 0.5.1. handles windows ntfs resizinfg from ubuntu. The docs had a lot of references with uncapabilities doing so.  Ive seen .4 versions had trouble and all kinds of reasons having toruble!

        Thanks So Much; am glad it actuall works after it being so messed up I didnt think the pbr was recoverable smile

        12

        Re: [SOLVED ]Logical Drive and Other Partition Error:

        It is good to hear that your are up and running again.

        If you do decide to reorganize more partitions, then I highly recommend that you download and use the latest GParted version.