Problems after changing partition size

LOL500

New Member
Messages
32
Okay, I have a 930GB Samsung Harddrive (ST1000LM024 HN-M101MBB)

My problem is after using aomei partition assistant to resize my partition, there has been a delay (like 15-25 seconds) between the part where it displays the Lenovo screen with the loading circle and the login screen.

So by any chance someone knows what is happening?
 

My Computer

System One

  • OS
    8
What partition did you change? Did you increase the size or decrease it? We'll also need a screenshot of your Disk Management view. Please update with as much detail as possible and include your system specs as well.
 

My Computer

System One

  • OS
    Windows 8.1
    Computer type
    PC/Desktop
    CPU
    Intel G2020
    Motherboard
    ASRock B75M-DGS R2.0
    Memory
    8GBs @ 1333 MHz
    Hard Drives
    Samsung 840 EVO
    PSU
    400w
    Internet Speed
    57/11
Untitled_zps340e2f7d.png
As you can see above, I moved 300GB of space from D: to C: . I also added 1GB or so of unallocated space that was floating around into :C

I'm using Windows 8 single language, i7, 4GB ram, Nvidia Geforce GT 645M
I'm also using Norton AV, ASC Pro 6.4 and Start8 if it helps.
 

My Computer

System One

  • OS
    8
OK, thanks for that. Now I can see the "after" but where was that 300GBs of space "before"? Was it in an adjacent partition that was before or after the destination partition? If before, did AOEMI give you the option to move the C data up to the front of the newly merged partiton? Or did it come from somewhere else entirely? Please be more clear about the original location of that 300GBs. And did you add that 1GB of unallocated space before or after the big move?
 

My Computer

System One

  • OS
    Windows 8.1
    Computer type
    PC/Desktop
    CPU
    Intel G2020
    Motherboard
    ASRock B75M-DGS R2.0
    Memory
    8GBs @ 1333 MHz
    Hard Drives
    Samsung 840 EVO
    PSU
    400w
    Internet Speed
    57/11
That 300GB was from D:, the Lenovo, I moved it to C: the boot drive.

When I try to use Disk Manager to move this 300GB, I can't because the unallocated space generated was on the right of D: and not next to C: . So I use Aomei to move it.

Aomei also says there was a 1GB of unallocated space, I forgot where it was and don't know how it got there but it was there so I move it into C:, the boot drive too.

Aomei moved that 1GB last, after it was done moving the 300GB into C:
 

My Computer

System One

  • OS
    8
OK, thanks for clearing that up. However, based on all of your clarifications, and not being familiar with AOMEI's capabilities, I cannot say that it should have done that gracefully but it would appear that the AOEMI move would also have to take into consideration the need to "move/push back/rearrange" the Lenovo D and the recovery partitions as well. My advice would be to wait for a followup from someone who is familiar with AOEMI and/or wait for some input from Thoeg on this issue. In any event, I hope you have your factory restore discs created and ready just in case they are needed. Good luck.
 

My Computer

System One

  • OS
    Windows 8.1
    Computer type
    PC/Desktop
    CPU
    Intel G2020
    Motherboard
    ASRock B75M-DGS R2.0
    Memory
    8GBs @ 1333 MHz
    Hard Drives
    Samsung 840 EVO
    PSU
    400w
    Internet Speed
    57/11
It might be a good idea to use Diskpart to list the partitions currently on the drive, since all do not show in Disk Management.

Open an Administrative command prompt and type the following, assuming you only have one hard drive.

Diskpart
lis dis
sel dis 0 <-- number of correct disk from prior listing
lis par

Then use the snipping tool to take a picture and attach, or Mark and copy the listing to you next post.

If you want to leave Diskpart and close the command prompt window, use

exit
exit
 

My Computer

System One

  • OS
    Windows 8.1 x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Home Grown
    CPU
    i7 3770K
    Motherboard
    ASUS P8Z77 -v Pro, Z87-Expert
    Memory
    16 G
    Graphics Card(s)
    EVGA GTX 680 Classified (2)
    Hard Drives
    Kingston SSD 240 GB
The partitions look OK. I suppose the unallocated 1 GB of space you mention is a little bit of a mystery and might be involved. OEMs don't normally leave empty space just laying around, but I have no information to make me think it would be anything but empty space.

If the system is taking longer to boot, it may be looking for something. Maybe it will work itself out after a few boot operations, but I can't think of anything you could do now.

I don't think changing a partition's size would change its identity, but I have not tested that situation to make sure. If a partition's identifier was changed, it could create problems.

You might run the reagentc /info command to see if the recovery options are still intact.
 

My Computer

System One

  • OS
    Windows 8.1 x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Home Grown
    CPU
    i7 3770K
    Motherboard
    ASUS P8Z77 -v Pro, Z87-Expert
    Memory
    16 G
    Graphics Card(s)
    EVGA GTX 680 Classified (2)
    Hard Drives
    Kingston SSD 240 GB
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.


C:\windows\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
information:


    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition1\Recove
ry\WindowsRE
    Boot Configuration Data (BCD) identifier: 320191f5-b041-11e2-be77-2016d8d3e2
c6
    Recovery image location:   \\?\GLOBALROOT\device\harddisk0\partition7\OKRbac
kup\factory
    Recovery image index:      1
    Custom image location:
    Custom image index:        0


REAGENTC.EXE: Operation Successful.




C:\windows\system32>

This is what I got.

Maybe there is some sort of diagnostic tool that can check for start up problems?

Oh and I just remember something:

After I boot up my computer after the partition size change, windows said something about needing to restart to avoid data loss.
When I restart, the part where it shows Lenovo + loading circle, below it was a text that says n% complete.
 

My Computer

System One

  • OS
    8
The readout looks OK also, so I have no idea what you might need to do, if anything.

One thought would be to disable the Windows 8 Fast Startup for a while to see if that helps. It is in the Power Options under Define what the power buttons do.
 

My Computer

System One

  • OS
    Windows 8.1 x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Home Grown
    CPU
    i7 3770K
    Motherboard
    ASUS P8Z77 -v Pro, Z87-Expert
    Memory
    16 G
    Graphics Card(s)
    EVGA GTX 680 Classified (2)
    Hard Drives
    Kingston SSD 240 GB
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.


C:\windows\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
information:


    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition1\Recove
ry\WindowsRE
    Boot Configuration Data (BCD) identifier: 320191f5-b041-11e2-be77-2016d8d3e2
c6
    Recovery image location:   \\?\GLOBALROOT\device\harddisk0\partition7\OKRbac
kup\factory
    Recovery image index:      1
    Custom image location:
    Custom image index:        0


REAGENTC.EXE: Operation Successful.




C:\windows\system32>

This is what I got.

Maybe there is some sort of diagnostic tool that can check for start up problems?

Oh and I just remember something:

After I boot up my computer after the partition size change, windows said something about needing to restart to avoid data loss.
When I restart, the part where it shows Lenovo + loading circle, below it was a text that says n% complete.

So basically it shows BSOD after you resize the partition, then there's a progress number below the boot screen loading circle?
I think there was a system file corruption, that may cause the BSOD earlier, and being fixed by Windows, that's why it shows a number below the loading circle. And i also think that because the clusters is so fragmented (partition resize may cause extreme cluster fragmentations), it causes the delay from boot to login.
 

My Computer

System One

  • OS
    Windows 10 Pro x64
    Computer type
    Laptop
    System Manufacturer/Model
    Lenovo Y520
    CPU
    Intel Core i5 7300HQ
    Motherboard
    OEM Lenovo
    Memory
    4GB DDR4-2400
    Graphics Card(s)
    NVIDIA GeForce GTX 1050
    Sound Card
    Realtek HD
    Monitor(s) Displays
    1 (2)
    Screen Resolution
    1920x1080
    Hard Drives
    Seagate 1TB 5400 RPM
    Keyboard
    OEM Lenovo
    Mouse
    Logitech G502 Proteus Core
    Internet Speed
    100 Mbps
    Browser
    Google Chrome
    Other Info
    PC:

    AMD Athlon X4 760K
    8GB DDR3-1866
    AMD Radeon RX 460
    Seagate 500 GB 7200 RPM
Windows hates 3rd party partitioning tools. It's usually much safer to use Windows Disk Management when dealing with a Windows partition.
I suspect you'll need to run a chkdsk on the Windows partition. If necessary run it more than once - until no errors are reported.
 

My Computer

System One

  • OS
    OS X / Windows 8.1 Pro / Ubuntu 13.10
    Computer type
    Laptop
    System Manufacturer/Model
    15" MacBook Pro retina 10,1
    CPU
    2.3GHz
    Memory
    8GB 1600MHz
    Graphics Card(s)
    Intel HD400 / Nvidia GT650M
    Screen Resolution
    2880 x 1800
    Hard Drives
    256GB SSD
Windows hates 3rd party partitioning tools. It's usually much safer to use Windows Disk Management when dealing with a Windows partition.
I suspect you'll need to run a chkdsk on the Windows partition. If necessary run it more than once - until no errors are reported.

Yep, i agree with you Duckface.
3rd party partitioning tool tend to resize partitions beyond the point where unmovable files are located. Sometimes the files are critical to Windows itself, so basically it was *almost* a suicide mission.

However, the partition management of Disk Management is quite difficult to use due to lack of GUI/sliders (you have to deal with the numbers itself).
 

My Computer

System One

  • OS
    Windows 10 Pro x64
    Computer type
    Laptop
    System Manufacturer/Model
    Lenovo Y520
    CPU
    Intel Core i5 7300HQ
    Motherboard
    OEM Lenovo
    Memory
    4GB DDR4-2400
    Graphics Card(s)
    NVIDIA GeForce GTX 1050
    Sound Card
    Realtek HD
    Monitor(s) Displays
    1 (2)
    Screen Resolution
    1920x1080
    Hard Drives
    Seagate 1TB 5400 RPM
    Keyboard
    OEM Lenovo
    Mouse
    Logitech G502 Proteus Core
    Internet Speed
    100 Mbps
    Browser
    Google Chrome
    Other Info
    PC:

    AMD Athlon X4 760K
    8GB DDR3-1866
    AMD Radeon RX 460
    Seagate 500 GB 7200 RPM
Back
Top