inaccessible_boot_device after resizing system partition

Archived from groups: microsoft.public.windowsnt.misc (More info?)

I used ServerMagic 4.0 for NT to resize my system partition from 17GB to 7.8GB on a system running Small Business Server 4.5. Now I get a stop message inaccessible_boot_device when I reboot. Any suggestions?
3 answers Last reply
More about inaccessible_boot_device resizing system partition
  1. Archived from groups: microsoft.public.windowsnt.misc (More info?)

    Hi,

    does this machine have a single combined system/boot partition? (ie: does the
    root of the drive contain ntldr. ntdetect.com etc.. and it also has a folder
    \winnt)

    Officially the correct terms are:

    system partition is the one that contain the system loader files (ntdetect.com
    etc..)
    boot partition is the one that contains the \winnt folder tree and is where NT
    actually 'boots' from

    There are problems with NT4 dealing with HDDs exceeding 7.8GB in size. It is
    solvable, but must be arranged correctly. Have a read of
    http://nt4ref.zcm.com.au/bigdisk.htm

    My suspicion is that when you resized your partition one or more files needed in
    the NT4 boot process have been moved beyond the 7.8GB limit imposed by CHS
    addressing, making the system unstartable :-(

    Perhaps you could describe the current arrangement in a bit more detail, and I
    and others may be able to offer more precise advice.

    Calvin.
  2. Archived from groups: microsoft.public.windowsnt.misc (More info?)

    My system has 1 35gb physical disk. There are 2 partitions C: and E: each 17.5gb. The system and boot partition are on partition C: Originally the system and boot partition were on a 7.8gb drive but I used ServerImage from Powerquest to restore the image to a larger 17.5gb partition on a new disk. The new larger partition worked fine and I had no problem with it booting up. The first time I noticed a problem was when I tried to download and install security updates. I was told by Microsoft that it my system partition being over 7.8gb that was the problem. So that is why I was trying to use ServerMagic to resize the system partition from 17.5gb to 7.8gb. That's when I get the Inaccessible_boot_device BSOD. Is there a way to resize the system partition down to 7.8gb?

    "Calvin" wrote:

    > Hi,
    >
    > does this machine have a single combined system/boot partition? (ie: does the
    > root of the drive contain ntldr. ntdetect.com etc.. and it also has a folder
    > \winnt)
    >
    > Officially the correct terms are:
    >
    > system partition is the one that contain the system loader files (ntdetect.com
    > etc..)
    > boot partition is the one that contains the \winnt folder tree and is where NT
    > actually 'boots' from
    >
    > There are problems with NT4 dealing with HDDs exceeding 7.8GB in size. It is
    > solvable, but must be arranged correctly. Have a read of
    > http://nt4ref.zcm.com.au/bigdisk.htm
    >
    > My suspicion is that when you resized your partition one or more files needed in
    > the NT4 boot process have been moved beyond the 7.8GB limit imposed by CHS
    > addressing, making the system unstartable :-(
    >
    > Perhaps you could describe the current arrangement in a bit more detail, and I
    > and others may be able to offer more precise advice.
    >
    > Calvin.
    >
    >
  3. Archived from groups: microsoft.public.windowsnt.misc (More info?)

    Hi,

    Resizing the system/boot partition down to below the 7.8GB barrier could prove
    difficult now that the system has been rendered inoperable. Somebody else here
    may have other ideas on how to proceed, but the only option I see open to you
    now is below:

    The best suggestion I could make at this stage is (assuming you have backups of
    everything on the machine) is to wipe the HDD clean, repartition in a manner
    that will satisfy NT and prevent a re-occurance of your problems.

    Suggested layout (have a read of http://nt4ref.zcm.com.au/bigdisk.htm for details):

    a primary partition of max 2GB formatted FAT16 - system partition C: (the spot
    for NTloader, ntdetect etc...)

    AN extended partition using the remainder of the HDD space

    the first logical drive in the extended partition of a size that in total with
    the system partition above does NOT cross the 7.8GB barrier - boot partition D:
    (the partition to put the /WinNt folder in)

    a logical drive arrangement using the remainder of the extended partition on the
    disk that suits your needs (maybe just one partition E: ?)

    Temporarily install a copy NT into drive C: (hence why I suggested making it
    about 2GB in size, you may be able to get away with smaller, if other partition
    sizes being maximised is important) Don't forget to apply SP6a to this 'parallel
    install' after you complete it's intiial installation, otherwise it won't be
    able to see and recognise the rest of your HDD correctly.

    Once it is operational, you can then restore all your content from backups to
    partitions D: and E:

    You'll have to modify boot.ini to point to the correct locations for system
    startup of your original NT4 installation (now re-instated) You may also have
    problems with hardcoded paths in the registry refering to (now wrong) drive
    letters, since you tell me your NT4 installation used to be on drive E: - these
    can be corrected with registry editor.

    A typical symptom of this 'hardcoded paths' problem is a warning on startup that
    the 'Protected Storage' service failed to start - reason being is that the
    idiots at Microsoft botched the registry entry for this service, and it is in
    the form letter:\winnt\system32\pstores.exe, instead of the correct syntax of
    %systemroot%\system32\pstores.exe !

    I have successfully recovered a system using this technique, and managed to
    'teach it' about the fact that it now resides on a different drive letter than
    it was installed to originally - even though Microsoft say this can't be done.

    I hasten to add that the only reason that it officially 'can't be done' is
    because of their EXTREMELY BAD coding practises and lack of discipline when it
    comes to registry entries. If everything was correctly entered in the form
    %systemroot%, instead of the 4 different syntaxes that I have seen, it wouldn't
    have been an issue!

    As I said at the beggining however - this whole approach is contingent on you
    having current backups of everything on the machine before it fell over - if
    not, you can follow this installation procedure in
    http://nt4ref.zcm.com.au/bigdisk.htm and everything will have to be reloaded
    from scratch. Hopefully you do have backups of all the user data somewhere, so
    it can be re-instated once NT4 and the apps are all back and working.

    Hope this helps.

    Calvin.
Ask a new question

Read More

Partition Boot Devices Windows