JD wrote:
On 01/09/2019 10:04 AM, Jean-Pierre André wrote:
JD wrote:
Hi,
Running /usr/bin/ntfsck for partition 2 of a windows 7 drive, where
windows is installed,
I get about 10 or so $MFT's for which I/O failed - which, to me,
indicates head crash damage
in those locations.
If this is the ntfsck shipped with ntfs-3g, ignore it altogether.
This is a placeholder which does nothing useful.
Use chkdsk from Windows if you can.
/usr/bin/ntfsck turns out to be a symlink to /sbin/*fsck*.*ntfs*
Yes, and this is just a placeholder.
As I mentioned, a second machine with win7 does not detect
the attached damaged drive in question, so,
how can I run chkdsk ??
On http://jp-andre.pagesperso-orange.fr/runwin.zip
I have put runwin which is a tool able to run chkdsk.exe
with the source and binaries for several platforms.
Read the "readme" to get the list of executables and dlls
you need to get from Windows.
runwin is pretty safe (I use it a lot), but I warn you that
chkdsk on a dying drive can make damages if it cannot
read essential parameters.
I would like to be able to extract the full home dir of a user on
this drive.
I would appreciate info on best way to proceed.
If this is user data, a decent archiver (tar, zip, etc.) will do.
If you disk is dying and you can still mount it from Linux,
you may want to save the data before chkdsk make more
damage.
Jean-Pierre
_______________________________________________
ntfs-3g-devel mailing list
ntfs-3g-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
