Cannot get into BIOS after mini tool partition resize

Page 1 of 3 123 LastLast

  1. Posts : 37
    Windows 7 Ultimate x64, Win 8.1, Win 10 preview, ubuntu14
       #1

    Cannot get into BIOS after mini tool partition resize


    Resized a non-boot partition on my HDD which completed outside of windows and now the BIOS screen hangs right after detecting THAT HDD. If I disconnect the IDE cable, the BIOS comes up ok. I connected the same HDD to another PC and it boots up into win7 no problem and all the files are there. I ran a chkdsk on it and it found some index erros which it repaired but still hangs up the BIOS in the 1st PC.

    Any ideas?
      My Computer


  2. Posts : 2,752
    Windows 7 Pro x64 (1), Win7 Pro X64 (2)
       #2

    Can you post a screenshot from DISKMGMT.MSC on the other machine where this disk doesn't prevent that BIOS from booting to Windows? We need to see what the disk currently looks like. Full-screen from DISKMGMT please, and spread the columns so that all the text in the cells is visible in the screenshot and we can read it.

    You say all you did was resize a partition, and it wasn't even the Windows C-partition. So it's odd that you say the resize operation was completed outside of windows (i.e. a reboot was requested in order to complete). This would not be the way the program works when working with a non-C partition where you can perform any operation fully without needing to be outside of Windows. Only if the boot partitions are affected would a non-Windows environment be needed.

    In other words, I have a hunch you actually did something which DID affect the Windows partition (or "system reserved" where Boot Manager would normally be living), and thus somehow might have affected the use of the drive to actually boot from on its primary "home" machine.

    The screenshot or this drive from DISKMGMT.MSC (or Partition Wizard, actually) on the other machine to show us all its partitions, which one is "active", and whether it's MBR or GPT, is critical to providing further guidance.
      My Computer


  3. Posts : 13,576
    Windows 10 Pro x64
       #3

    And even if you did mess up when re sizing, it should have not affected the bios at all.

    How did you re size the partition, which partition, what program did you use ?

    Post the shot of DM, as suggested.
      My Computer


  4. Posts : 6,292
    Windows 7 64 Bit Home Premium SP1
       #4

    AddRAM said:
    And even if you did mess up when re sizing, it should have not affected the bios at all.
    There is nothing wrong with the BIOS. The BIOS boots fine, just confused wording.
    It just can't hand off to an OS so it stops there.

    I suspect a missing ACTIVE flag, as do you all. We could see that right away with a screenshot.
      My Computer


  5. Posts : 13,576
    Windows 10 Pro x64
       #5

    Mexman, we can`t help you if you don`t reply.
      My Computer


  6. Posts : 37
    Windows 7 Ultimate x64, Win 8.1, Win 10 preview, ubuntu14
    Thread Starter
       #6

    Hey,I just woke up! :)

    Here's the print screen (both diskmgmt and minitool):

    I agree, it was strange that mini tool requested a reboot to resize that partition. After 10-20 secs it said the drive was 'in use', but I could not find any process using it, so I opted the resize after a reboot. It was a resize of the non-root partition to use the remaining space on the HDD.
    Attached Thumbnails Attached Thumbnails Cannot get into BIOS after mini tool partition resize-badhdd1.jpg   Cannot get into BIOS after mini tool partition resize-badhdd2.jpg  
    Last edited by Mexman; 03 Mar 2015 at 15:23.
      My Computer


  7. Posts : 6,292
    Windows 7 64 Bit Home Premium SP1
       #7

    This is the problem hard drive installed on another computer - correct?

    And that other computer has it's own operating system on it's own hard drive - correct?

    If so, the problem hard drive is DISK 1 in Disk Management, and Disk 2 in Partition Wizard?
      My Computer


  8. Posts : 37
    Windows 7 Ultimate x64, Win 8.1, Win 10 preview, ubuntu14
    Thread Starter
       #8

    TVeblen said:
    This is the problem hard drive installed on another computer - correct? YES


    And that other computer has it's own operating system on it's own hard drive - correct? YES

    If so, the problem hard drive is DISK 1 in Disk Management, and Disk 2 in Partition Wizard?
    YES



    I also setup the problem HDD as the boot drive in the OTHER PC and it boots ok.

    Also ran WD's Data lifegaurd quick test with no errors.
      My Computer


  9. Posts : 6,292
    Windows 7 64 Bit Home Premium SP1
       #9

    Disk 1 in the screenshot shows:

    • A System Reserved partition (100MB), marked System and Active
    • Dive G: - (19.53GB), data
    • Drive H: - (57.06GB), data

    I don't see a C: drive or and operating system on that disk.

    I think your other computers are just starting their own windows installations.
      My Computer


  10. Posts : 2,752
    Windows 7 Pro x64 (1), Win7 Pro X64 (2)
       #10

    TVeblen said:
    Disk 1 in the screenshot shows:

    • A System Reserved partition (100MB), marked System and Active
    • Dive G: - (19.53GB), data
    • Drive H: - (57.06GB), data

    I don't see a C: drive or and operating system on that disk.

    I think your other computers are just starting their own windows installations.
    When the problem drive is a second drive in the other machine its partitions would not show up with the same letters as you might expect if it were the primary drive in the original machine.

    Obviously the C in this other machine setup is on its own primary drive (DISK0 in DISKMGMT). The partitions on what is now seen as the second disk simply get assigned next available letters on the other machine. That's even why "system reserved" is given a letter in this 2nd-drive setup, when in a true setup it would not get any letter.

    ==> No problem that I see. Everything looks perfectly fine. MBR, "active" partition is "system reserved", and nothing strange is apparent.

    Also, configuring the BIOS in the other machine to boot from this "problem drive" and having no problem whatsoever simply adds to the confusion. If Windows on the drive can be booted to successfully in this other machine, why it is a problem to the original machine... well, quite the mystery I agree.

    NOTE to Mexman: you didn't spread the columns in the upper part of the DISKMGMT screenshot, so the important text was not visible. Fortunately it is visible in the PW screenshot, so no harm.

    I will say that if G (as shown) is the Windows partition on what is currently the second drive on this other machine, it's really very very small for a Windows 7. Only a 20GB partition, with only 10GB used? That's unbelievably tiny. But I guess if it "works" as the system partition when booting to it on this other machine, then it must work. But it really does look very very tiny for "used". Never saw a Win7 with only 10GB used.
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:12.
Find Us