After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 340439 - resizing NTFS makes mistakes in the MBR
resizing NTFS makes mistakes in the MBR
Status: RESOLVED OBSOLETE
Product: gparted
Classification: Other
Component: application
0.2.2
Other All
: Normal blocker
: ---
Assigned To: gparted maintainers alias
gparted maintainers alias
Depends on:
Blocks:
 
 
Reported: 2006-05-02 19:45 UTC by guiguionekenobi
Modified: 2007-11-05 05:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description guiguionekenobi 2006-05-02 19:45:43 UTC
Please describe the problem:
I think Gparted makes mistakes in the MBR because the hard drive I try to modify
has a number of head per cylinder of 16.

I want to resize partitions on a Packard Bell computer.
There is two partition : 4GB and 110GB.
The boot partition is the second.

After resizing my partitions with Gparted, I try to boot but It was impossible.
I used testdisk to correct the MBR and during this I have seen that there was a
probleme of LBA indexes (and not CHS)

Steps to reproduce:
1. Try to resize any partitions with Gparted on this hard drive
2. And then try to boot...
3. 


Actual results:
"error loading operatin system"

Expected results:
that the system start correctly

Does this happen every time?
Yes

Other information:
Symantec PartitionInfo 8.0 -- Windows NT/2000 Version
Date Generated:  05/02/06  21:43:52
Copyright (c)1994-2004, Symantec Corporation
Permission is granted for this utility to be freely copied so long
as it is not modified in any way.  All other rights are reserved.

===========================================================================================================
Disk Geometry Information for Disk 1:    238216 Cylinders,  16 Heads,  63
Sectors/Track
System              PartSect  # Boot BCyl Head Sect  FS    ECyl Head Sect   
StartSect     NumSects
===========================================================================================================
                           0  0  00     0    1    1  07    1023   15   63      
    63    8,386,497
Info: End C,H,S values were large drive placeholders.
  Actual values are:
        0  0  00      0    1    1  07   8319   15   63        63   8386497
                           0  1  80  1023   15   63  07    1023   15   63   
8,388,702  216,168,498
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
  Actual values are:
        0  1  80   8322    2    1  07  222774   15   63   8388702 216168498
Error #105: Partition didn't begin on head boundary.
  ucBeginHead expected to be 0 or 1, not 2.



===========================================================================================================
Partition Information for Disk 1:    117,246.9 Megabytes
Volume         PartType    Status    Size MB    PartSect  #   StartSect  TotalSects
===========================================================================================================
F:             NTFS        Pri       4,095.0           0  0          63   8,386,497
               Unallocated Pri           1.0        None --   8,386,560       2,016
C:             NTFS        Pri,Boot 105,551.0           0  1   8,388,702 216,168,498
               Unallocated Pri       7,599.9        None -- 224,557,200  15,564,528


===========================================================================================================
Boot Record for drive F:   (Drive: 1, Starting sector: 63, Type: NTFS)
===========================================================================================================
 1. Jump:                   EB 5B 90
 2. OEM Name:               NTFS    
 3. Bytes per Sector:       512
 4. Sectors per Cluster:    8
 5. Reserved Sectors:       0
 6. Number of FATs:         0
 7. Root Dir Entries:       0
 8. Total Sectors:          0
 9. Media Descriptor:       0xF8
10. Sectors per FAT:        0
11. Sectors per Track:      63  (0x3F)
12. Number of Heads:        16  (0x10)
13. Hidden Sectors:         63  (0x3F)
14. Total Sectors (>32MB):  0  (0x0)
15. Unused:                 0x00000000
16. Total NTFS Sectors:     8385866
17. MFT Start Cluster:      4
18. MFT Mirror Start Clust: 524116
19. Clusters per FRS:       246
20. Clusters per Index Blk: 1
21. Serial Number:          0x3C44C1E3066AE314
22. Checksum:               0  (0x0)
23. Boot Signature:         0xAA55

===========================================================================================================
Boot Record for drive C:   (Drive: 1, Starting sector: 8,388,702, Type: NTFS)
===========================================================================================================
 1. Jump:                   EB 52 90
 2. OEM Name:               NTFS    
 3. Bytes per Sector:       512
 4. Sectors per Cluster:    8
 5. Reserved Sectors:       0
 6. Number of FATs:         0
 7. Root Dir Entries:       0
 8. Total Sectors:          0
 9. Media Descriptor:       0xF8
10. Sectors per FAT:        0
11. Sectors per Track:      63  (0x3F)
12. Number of Heads:        255  (0xFF)
13. Hidden Sectors:         8388702  (0x80005E)
14. Total Sectors (>32MB):  0  (0x0)
15. Unused:                 0x80008000
16. Total NTFS Sectors:     216167856
17. MFT Start Cluster:      802815
18. MFT Mirror Start Clust: 3840365
19. Clusters per FRS:       246
20. Clusters per Index Blk: 1
21. Serial Number:          0x4280D08F80D08B35
22. Checksum:               0  (0x0)
23. Boot Signature:         0xAA55
Comment 1 Plors (Bart H) 2006-09-14 08:10:53 UTC
sorry for the late response.
Without reading your bug (don't have time now, but i'll do it later) i have 1 comment.
resizing ntfs doesn't touch the MBR, so the title seems to be inappropiate.

Anyway, i'll read the bug later in detail.
Comment 2 hugues larrive 2007-10-05 02:35:56 UTC
It seems that the geometry of the partition table was set to 255 heads before you use gparted as that appearing in ntfs boot record of the second partition.

At boot time, ntldr check the consistency of geometry between partition table and boot record... Under XP the result of this inconsistency is:
"A disk read error occurred
Press Ctrl+Alt+Del to restart"

Neither gparted nor ntfsresize modify the ntfs boot records.

The command line printf "\x10" | dd of=/dev/hda2 bs=1 seek=26 should solve this problem.
Comment 3 Laurent de Trogoff 2007-11-05 05:46:16 UTC
Please : switch to last gparted version !!!!!!!!!!!!!!!