[Paragon Migrate to 3TB] Operation failed and The parameter is incorrect

Discussion in 'Paragon Early Adopter Program' started by certainty, Feb 12, 2011.

Thread Status:
Not open for further replies.
  1. certainty

    certainty Registered Member

    Joined:
    Feb 12, 2011
    Posts:
    1
    I've been trying out Paragon Migrate to 3TB and was unsuccessful.

    I'm using 3x1 TB drives at RAID0 on NVIDIA :thumbd: MediaShield and wanted to copy a 64GB Windows 7 x64 partition from another 400 GB drive.

    First of all I'm not sure "Migrate to 3TB" is a good name. What if I'd like to migrate to 4TB? And what's really the difference between Paragon Migrate to 3TB and Paragon Drive Copy Express? They both copy partitions so why not merge them? :)

    Paragon1.png

    When migrating to the 3 TB drive I'd like to keep the Windows partition at 64 GB so I uncheck "Copy data and resize partitions proportionally". After clicking Next I get and error message saying I'm out of disk space which of course is ridiculous since I got 3 TB free :rolleyes:

    Paragon2.png Paragon3.png

    I would prefer a textbox to the slider when selecting destination disk partitions size (or perhaps both?). With the slider it's impossible to configure a partition like 64 GB.

    "Time remaining" at the "Copying the hard disk" window is not accurate but what's worse is that "Time elapsed" also stalled for long periods which would drive impatient users to drastic measures.

    Paragon4.png

    The worst part was that after booting up the new 3 TB drive I'm not allowed to create any partition on the unallocated 2.7 TB space. I tried creating a 2.7 TB and 100 MB partition but always get "The parameter is incorrect" error message.

    Paragon5.png

    In the event log I get two different errors several times. One "Port driver for disk 0 failed ATA IDENTIFY command." and one "Unexpected failure. Error code: 1@01010003".

    Code:
    Log Name:      System
    Source:        gpt_loader
    Date:          2011-02-12 22:28:12
    Event ID:      11
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      Rajasthan
    Description:
    Port driver for disk 0 failed ATA IDENTIFY command.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="gpt_loader" />
        <EventID Qualifiers="32773">11</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-02-12T21:28:12.171200000Z" />
        <EventRecordID>1071</EventRecordID>
        <Channel>System</Channel>
        <Computer>Rajasthan</Computer>
        <Security />
      </System>
      <EventData>
        <Data>
        </Data>
        <Data>0</Data>
        <Binary>00001A0002004600000000000B0005800000000000000000000000000000000000000000000000005A4174614770744C6F616465723A3A6765744469736B53697A65</Binary>
      </EventData>
    </Event>
    Code:
    Log Name:      System
    Source:        VDS Basic Provider
    Date:          2011-02-12 22:37:11
    Event ID:      1
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Rajasthan
    Description:
    Unexpected failure. Error code: 1@01010003
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="VDS Basic Provider" />
        <EventID Qualifiers="49664">1</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-02-12T21:37:11.000000000Z" />
        <EventRecordID>1134</EventRecordID>
        <Channel>System</Channel>
        <Computer>Rajasthan</Computer>
        <Security />
      </System>
      <EventData>
        <Data>1@01010003</Data>
      </EventData>
    </Event>
     
  2. Mech_An

    Mech_An Registered Member

    Joined:
    Mar 29, 2010
    Posts:
    855
    1) It would be great to get LOGs of migration.
    By the way, what version of Migrate to 3TB did you use? Update was released recently and should contacin some bugfixing. Build number is 10.0.16.12621

    Logs: "PWLOG.TXT", "STUBACT.LOG", "BioNTlog.TXT" in "C:\Program Files\Paragon Software\[Program Name]\Program"

    2) GPT Loader driver which is installed together with Migrate to 3TB doesn't support RAIDS.
    http://www.paragon-software.com/technologies/components/gpt-loader/win7.html

    This warning should be added for Migrate to 3TB also.

    So you will not be able to create new partition beyond the 2.2TB limit.
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.