Partition not accessibly in Windows 2003 server

Discussion in 'Paragon Partition Manager Product Line' started by debo, Feb 12, 2010.

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

    debo Registered Member

    Joined:
    Feb 12, 2010
    Posts:
    4
    Trying to resize the hard drive partitions.

    Bootable primary was increased in size
    another primary was decreased in size

    The system rebooted as instructed and upon logging back into Windows the bootable primary is the same size that it was the other primary is smaller in size and there is a large unallocated group now.

    Problem is, the primary that was decreased in size is not accesible in Windows. I can see the data on it from Partition Manager, and the drive is listed in Windows, but no statistics listed and error when trying to open.

    I have submitted a ticket with an immediate response for more information and I sent that information back. It's been 4 hours and I have not heard anything, not even a verification that they received the submission.

    This is a live server. I am reaching out here to try for some assistance.
     
  2. Paragon_MattK

    Paragon_MattK Paragon Moderator

    Joined:
    Jan 14, 2010
    Posts:
    176
    Location:
    Irvine, CA
    It sounds like the partition table information may be incorrect, you can try to rebuild it by resizing the decreased partition again very slightly (increase or decrease by the minimum amount).

    Does the partition appear formatted within paragon? and in windows disk management?

    What is the error you receive when you try to access the drive?
     
  3. Paragon_Tommy

    Paragon_Tommy Paragon Moderator

    Joined:
    Aug 10, 2009
    Posts:
    918
  4. debo

    debo Registered Member

    Joined:
    Feb 12, 2010
    Posts:
    4
    Thank you both, I am trying to resize a bit larger now. Will update as soon as it's finished.
     
  5. debo

    debo Registered Member

    Joined:
    Feb 12, 2010
    Posts:
    4
    File system has allocation errors due to cross-linked files.
    Run OS built-in tools for checking and correcting this kind of errors.

    Error source: Hard Disk Manager
    Error code: 0x10018
     
  6. Paragon_MattK

    Paragon_MattK Paragon Moderator

    Joined:
    Jan 14, 2010
    Posts:
    176
    Location:
    Irvine, CA
    Ok, you should run chkdsk /f if you still get errors after that use the chkdsk /r option, it will need to reboot to complete the operation because chkdsk /f requires exclusive access to the drive.
     
  7. debo

    debo Registered Member

    Joined:
    Feb 12, 2010
    Posts:
    4
    Yes, checkdisk worked. Thank you for the quick response. I will go close my ticket now.
     
  8. Paragon_MattK

    Paragon_MattK Paragon Moderator

    Joined:
    Jan 14, 2010
    Posts:
    176
    Location:
    Irvine, CA
    Glad to hear its working :thumb:
     
Loading...
Thread Status:
Not open for further replies.