B
bidalah
Hello all,
I am simply trying to create a new 20 gig partition on my 160gb hard
drive. There is already a single 15 gig partition on the disk in which
I am running Windows 2000. I have tried creating both primary and
extended partitions ( I only need extended). Every time I get the same
error message:
"An internal error has occurred. The Logical Disk Manager service may
have become unstable. Please close the Disk Management snapin window
and restart the Logical Disk manager or reboot the machine".
To date I have:
--Edited the registry to support 48 LBA
--Stopped and restarted both the Logical Disk management service and
the whole computer several times
--Confirmed that my motherboard is set to use 48 LBA
--Updated the disk driver (with a minor update that should not have
mattered to this issue)
None of these have had any impact. I just don't know what else to try.
There doesn't seem to be any documentation on the microsoft site about
this issue (though it is hard to tell since there is no error code or
number to look up). There is no entry made in the system error log
either.
Has anyone seen this error before? Please let me know.
I am simply trying to create a new 20 gig partition on my 160gb hard
drive. There is already a single 15 gig partition on the disk in which
I am running Windows 2000. I have tried creating both primary and
extended partitions ( I only need extended). Every time I get the same
error message:
"An internal error has occurred. The Logical Disk Manager service may
have become unstable. Please close the Disk Management snapin window
and restart the Logical Disk manager or reboot the machine".
To date I have:
--Edited the registry to support 48 LBA
--Stopped and restarted both the Logical Disk management service and
the whole computer several times
--Confirmed that my motherboard is set to use 48 LBA
--Updated the disk driver (with a minor update that should not have
mattered to this issue)
None of these have had any impact. I just don't know what else to try.
There doesn't seem to be any documentation on the microsoft site about
this issue (though it is hard to tell since there is no error code or
number to look up). There is no entry made in the system error log
either.
Has anyone seen this error before? Please let me know.