1 Topic by scrutr

  • scrutr
  • New member
  • Offline
  • Registered: 2011-06-18
  • Posts: 2

Topic: BSOD after resizing partition

Hey guys, I've done a bad thing. I tried to shrink my Windows partition to make room for a F15 install. The process failed. Now I'm getting a horrid BSOD whenever I try to log back into Windows.

I tried using the startup repair functionality;  it keeps saying that it has fixed a boot record, but I still can't start Windows.

I tried following the tutorial here (http://gparted-forum.surf4.info/viewtopic.php?id=13937), but I stopped when I noticed that the result of my fdisk -l -u is a little different:

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 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: 0xd17b3a53

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048     2459647     1228800    7  HPFS/NTFS/exFAT
/dev/sda2         2459648   578652159   288096256    7  HPFS/NTFS/exFAT

Disk /dev/sdb: 4016 MB, 4016046080 bytes
90 heads, 25 sectors/track, 3486 cylinders, total 7843840 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: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        8192     7843839     3917824    b  W95 FAT32

Disk /dev/mapper/live-rw: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders, total 8388608 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: 0x00000000

Disk /dev/mapper/live-rw doesn't contain a valid partition table

Disk /dev/mapper/live-osimg-min: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders, total 8388608 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: 0x00000000

Disk /dev/mapper/live-osimg-min doesn't contain a valid partition table

See? There's two partitions on my /dev/sda rather than one. I'm not exactly sure how to proceed from here. I don't want to do anything stupid (further) and lose alll my data because of it. Can somebody help me out please?

2 Reply by gedakc

  • gedakc
  • Developer
  • Offline
  • Registered: 2007-11-30
  • Posts: 4,593

Re: BSOD after resizing partition

Which version of GParted, GParted Live, or other software did you use to resize the partition?

My assumption would be that you resized the second partition (sda2) to free up space at the end of the drive.  If this is the case then sda2 is the partition and file system that will require fixing.

Please feel free to follow the tutorial to fix sda2.  If you would like help then 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-scutr.mbr bs=512 count=1

where sda-scutr.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=sda2-scutr.pbr bs=512 count=1 skip=2459648

where sda2-scutr.pbr is the name of the file that will need to be uploaded.

Please note that your sda2 partition begins on sector 2459648, and not 63 as in the tutorial.

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 Reply by scrutr

  • scrutr
  • New member
  • Offline
  • Registered: 2011-06-18
  • Posts: 2

Re: BSOD after resizing partition

Thanks a lot man, you're the best. All is well now.

The program I used was the built-in partitioner on the Fedora 15 install ISO.

Do you know how I can safely resize my partition in order to use the installer?

4 Reply by gedakc

  • gedakc
  • Developer
  • Offline
  • Registered: 2007-11-30
  • Posts: 4,593

Re: BSOD after resizing partition

The Fedora 15 ISO should have worked.  You can always try the latest version of GParted Live since this is the Live image that we test GParted with.   smile