Link to home
Start Free TrialLog in
Avatar of MajSteel
MajSteelFlag for United States of America

asked on

cannot browse root of c drive after using GPARTED

I recently used GPARTED to extend my c drive due to lack of space on my Windows 2003 server. The server boots correctly and windows logs in just fine. However, I cannot browse the root of C drive now with My Computer. My explorer process will lock up and take forever to recover. However, I can browse all subdirectories via Windows Explorer tree and with command prompt. My backup device will not operate now and it is a big problem. Can anyone help lead me in the right direction? Thanks.
Avatar of noxcho
noxcho
Flag of Germany image

Did you perform CHKDSK /f on the server after resize?
Also, when you look the drives via Windows Disk Management, are there drive letters assigned to partitions?
Boot from Win2003 install CD and apply FIX MBR and FIX BOOT commands.
First command should be enough to repair backup problems.
Avatar of MajSteel

ASKER

I did run CHKDSK /f. I've attached the code. In disk management, it lists the C drive as a Healthy System partition with 22GB, which is the correct new size that I gave it with GPARTED.

I will try your other commands shortly, as this server has important data being used on other partitions.
Event Type:	Information
Event Source:	Winlogon
Event Category:	None
Event ID:	1001
Date:		7/7/2009
Time:		10:16:56 AM
User:		N/A
Computer:	LEVIATHON
Description:
Checking file system on C:
The type of the file system is NTFS.
 
 
One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.                         
Cleaning up minor inconsistencies on the drive.
Cleaning up 1316 unused index entries from index $SII of file 0x9.
Cleaning up 1316 unused index entries from index $SDH of file 0x9.
Cleaning up 1316 unused security descriptors.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Windows has made corrections to the file system.
 
  23272300 KB total disk space.
   9299648 KB in 623628 files.
    222584 KB in 2297 indexes.
         0 KB in bad sectors.
    653668 KB in use by the system.
     23040 KB occupied by the log file.
  13096400 KB available on disk.
 
      4096 bytes in each allocation unit.
   5818075 total allocation units on disk.
   3274100 allocation units available on disk.
 
Internal Info:
60 8e 09 00 10 8d 09 00 17 c1 12 00 00 00 00 00  `...............
2b 00 00 00 00 00 00 00 c9 0a 00 00 00 00 00 00  +...............
ea 04 47 2e 00 00 00 00 7c 44 63 3f 01 00 00 00  ..G.....|Dc?....
9c e9 99 44 00 00 00 00 00 00 00 00 00 00 00 00  ...D............
00 00 00 00 00 00 00 00 6c f0 e9 c6 01 00 00 00  ........l.......
00 91 be be 00 00 00 00 ff ff ff ff 05 00 00 00  ................
0c 84 09 00 00 00 00 00 00 00 9b 37 02 00 00 00  ...........7....
 
Windows has finished checking your disk.
Please wait while your computer restarts.
 
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

Did you run this check with /f key?
Before you run FIX MBR and FIX BOOT take backup of the drive.
Yes, I did use the /f switch
Ok, what are the results of FIX MBR & FIX BOOT?
Haven't had a chance to do it yet, as this server is running to much during business hours. I will try this as soon as we close for the day and post the results. Thanks for checking up.
Np. Don't hurry.
ASKER CERTIFIED SOLUTION
Avatar of MajSteel
MajSteel
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial