Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Tuesday, November 4, 2008

Problems repartitioning NTFS partition

CEB
After trying to repartition the C: drive (NTFS formatted with 40 GB)
After running n-times (in CMD line modus) the infamous command
C:\chkdsk /r               (/r not /f)
and waiting long time to repair errors and twice restarts...
It could not be able with Linux OS (Knoppix 5.1 and openSuSE 10.3 and Parted Magic 2.1) to repartitioning this (little) bad M$ file system.
The disk surface is in order (it has no bad clusters), confirmed after inspection (SMART utility)
The error output from Linux (gparted & visualparted) was:

#....error 2 while executing fsck.ntfs-3G


(When some blocks of the partition(s) could be damaged, I suggest to run "fdisk -l" to be 100% sure about sda* and then run "fsck" to
check these partitions)
#fdisk -l

I don' like to use the last instance linux command to clear certain journaling structures of ntfs and something in the FMT.
#ntfsfix /dev/sda1
but I didn't have another better choice... et voilá!
It was then possible to resize (partition of 20 GB)

Another case

Another sugestion
If you are using TestDisk 6.8 or later, in the
Advanced menu, select the NTFS partition, choose Boot and List.
Sometimes it can access files even if the filesystem is a "little"
damaged. RepairMFT can repair the MFT using the MFT mirror, it will ask
you confirmation before changing anything. If you have done a backup
with dd or GNU ddrescue, it's even better.
Another suggestion
If the recovery console can't see the drive, it can't repair, in this kind of situation, I would try using a bootcd like from www.ubcd4win.com
and use those utilities to do data recovery, after important data
recovered, delete the raid volumes, check the drives one by one if
having problem or not, if healthy, rebuilt the raid, this kind of hard
drive crash maybe caused by overheated drives. Be sure your hard drives are well ventilated.

No comments: