Disk Director will no longer resize a partition now that Linux is installed
Hi all,
I have sucessfully loaded Debian and am using the Debian boot loader to select between operating systems.
I have noticed now that when I run Disk Director (in WIn7 of course) and try to resize a partition, which I used to be able to do, I now get an error, or rather several errors.
---------------------------------------------------------------------
Error
---------------------------------------------------------------------
Error details
---------------------------------------------------------------------
Details
Code: 9,764,884(0x950014)
Module: C:\Program Files (x86)\Acronis\DiskDirector\mmsBundle.dll
Message: Applying has failed.
Code: 3,539,346(0x360192)
Message: Fdisk operation has failed.
Code: 1,060,886(0x103016)
Message: Failed to resize the volume.
Code: 1,051,655(0x100C07)
Message: The operation is not supported.
---------------------------------------------------------------------
The type of partition that I am trying to resize is the primary C partition (Win7). It is of type "basic". This used to work before I did my Debian install.
I did reinstall the software and hit "repair" as the option.
What other options do I have?
Thank You
Tom
Anton,
thank you for your reply.
I did as you suggested and rebooted the system. Then I attempted to resize a partition and to my delight it worked.
However, I have uncovered another problem that I have suspected for a few days. In order to finish the resize process, Acronis needs to reboot and finish the resize before Win7 really gets going. That is when I discovered that GRUB, my bootloader, was completely trashed. This has happened before when I was trying to use Acronis OS Selector. The OS Selector is completely deactivated so that is not the problem.
Evidently, Acronis Disk Director needs to write the partition table in the MBR. It does not properly write the MBR so that GRUB can read it.
In order to get my windows 7 primary partition to boot again, I had to load the Win7 rescue disk, open a command line terminal and type
"bootsect /nt60 E: /mbr" Not sure why "E:" was the proper dive letter because I thought that the win7 primary was "C:", but anyway , it worked.
Grub is still broken as all that comes up is "Grub-rescue" which I can find very little documentation on. I suppose that i can load the Debian rescue disk and do a reinstall of grub but I don't know if that will work.
Anyway, I am getting somewhat frustrated with the problems of the Acronis Disk Director. Is there a fix for the problem of interfering witih Grub?
BTW I also tried getting rid of Grub and using the Acronis OS selector but it did not recognize that there was a linux partition so I abandoned it.
Thank You
Tom Cipollone
TI does not always play nice with boot managers (including OSS). In my experience with OSS and GRUB, it's best to keep GRUB out of the MBR -- install it to the Linux partition. The current versions of Linux make this more difficult because GRUB2 resists doing this.
Without GRUB installed (or with it in a corrupted state), OSS wouldn't find it and then wouldn't find the Linux installation. This is another reason I prefer having GRUB installed to the partition (it's less likely to be disturbed).
In cases where a TI/DD "reboot" procedure doesn't work correctly, it's recommended to try using the TI CD instead. I usually just abort in those cases and boot to the CD instead of even trying the "reboot" method -- I've seen too many cases where the auto-run script gets things wrong and screws things up. Much better to use the CD and be able to see and control the procedure.
When booted to WinPE the drive letters are often different than in Windows. This is completely normal. You would just use the currently assigned letter.
Hello Tom and MudCrab,
Thank you for your reply and thank you very much for helping MudCrab.
Tom, we have a set of instructions in this KB article for reactivating different loaders, please let us know if you need any help with it.
Thank you.