1 Topic by simontse

  • simontse
  • New member
  • Offline
  • Registered: 2012-05-17
  • Posts: 3

Topic: Resizing NTFS problems for Seagate GoFlex Desk 2TB External USB 2.0

I tried to resize the only NTFS partition that comes pre-formatted with my external 2TB Seagate GoFlex Desk harddrive. I attempted to reduce the formatted size from 1.82TB to 1.53TB to give space "on the right end of the drive". My intention for the space was to copy and paste partitions from another internal Samsung harddrive which SMART reports imminent failure.

I ran Linux Mint 11 from an SSD and use GParted 0.8.1. After a long wait, gparted reported doing everything successfully except the last part: the final NTFS consistency check. I tried to save the details but it hanged, but luckily the file was saved anyway.

After this I cannot mount it in Linux saying I/O error and that $MFT and $MFTMirr don't agree.  Neither can Windows 7 mount it and in Disk Management, the partition was wrongly identified as RAW though the drive letter is still here. Double clicking the drive letter says "disk structure corrupted and unreadable".

I was suspecting there's some proprietory magic in the enclosure base that causes trouble, and so I tried to unplug the base which provides the USB port and found there's SATA type power and data ports. I plugged it directly to my motherboard SATA ports and the BIOS wouldn't even detect the harddrive...

I'm clueless on what to do now... This external harddrive has been performing well and there's never sudden disconnection due to instability of USB power (there's a dedicated AC adapter and my motherboard is quite new). Since gparted basically went through everything normally I think my precious data are all there... I dare not force reconstruct the partition table and NTFS filesystem to the former state... Any suggestions?

As for the details dumped out from gparted, I can't find useful information from the details but I post here anyway:

GParted 0.8.1 --enable-libparted-dmraid

Libparted 2.3
Shrink /dev/sdd1 from 1.82 TB to 1.53 TB  02:39:02    ( ERROR )
         
calibrate /dev/sdd1  00:00:00    ( SUCCESS )
         
path: /dev/sdd1
start: 63
end: 3907024127
size: 3907024065 (1.82 TB)
check file system on /dev/sdd1 for errors and (if possible) fix them  00:01:25    ( SUCCESS )
         
ntfsresize -P -i -f -v /dev/sdd1
         
ntfsresize v2011.4.12AR.4 (libntfs-3g)
Device name : /dev/sdd1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 2000396321280 bytes (2000397 MB)
Current device size: 2000396321280 bytes (2000397 MB)
Checking for bad sectors ...
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 16 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 17 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 18 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 19 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 20 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 21 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 22 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 23 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 16 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 17 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 18 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 19 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 20 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 21 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 22 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 23 has no FILE magic (0x0)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 1145464 MB (57.3%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 1940908 MB 0
Multi-Record : 1997793 MB 941317
$MFTMirr : 1000199 MB 1
Compressed : 65407 MB 364643
Sparse : 1844328 MB 398787
Ordinary : 2000397 MB 1163205
You might resize at 1145463681024 bytes or 1145464 MB (freeing 854933 MB).
Please make a test run using both the -n and -s options before real resizing!
shrink file system  02:36:56    ( SUCCESS )
         
run simulation  00:10:22    ( SUCCESS )
         
ntfsresize -P --force /dev/sdd1 -s 1685827060223 --no-action
         
ntfsresize v2011.4.12AR.4 (libntfs-3g)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 16 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 17 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 18 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 19 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 20 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 21 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 22 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 23 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 16 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 17 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 18 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 19 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 20 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 21 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 22 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 23 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 16 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 17 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 18 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 19 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 20 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 21 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 22 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 23 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 23 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 22 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 21 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 20 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 19 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 18 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 17 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 16 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Non-positive free clusters (0)!
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Device name : /dev/sdd1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 2000396321280 bytes (2000397 MB)
Current device size: 2000396321280 bytes (2000397 MB)
New volume size : 1685827056128 bytes (1685828 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 1145464 MB (57.3%)
Collecting resizing constraints ...
Needed relocations : 22783962 (93324 MB)
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Relocating needed data ...
Updating $BadClust file ...
Updating $Bitmap file ...
Updating Boot record ...
The read-only test run ended successfully.
real resize  02:26:34    ( SUCCESS )
         
ntfsresize -P --force /dev/sdd1 -s 1685827060223
         
ntfsresize v2011.4.12AR.4 (libntfs-3g)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 16 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 17 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 18 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 19 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 20 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 21 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 22 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 23 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 16 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 17 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 18 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 19 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 20 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 21 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 22 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 23 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 16 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 17 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 18 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 19 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 20 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 21 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 22 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 23 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 23 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 22 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 21 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 20 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 19 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 18 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 17 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Record 16 has no FILE magic (0x0)
Non-positive free clusters (0)!
Device name : /dev/sdd1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 2000396321280 bytes (2000397 MB)
Current device size: 2000396321280 bytes (2000397 MB)
New volume size : 1685827056128 bytes (1685828 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 1145464 MB (57.3%)
Collecting resizing constraints ...
Needed relocations : 22783962 (93324 MB)
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Relocating needed data ...
Updating $BadClust file ...
Updating $Bitmap file ...
Updating Boot record ...
Syncing device ...
Successfully resized NTFS on device '/dev/sdd1'.
You can go on to shrink the device for example with Linux fdisk.
IMPORTANT: When recreating the partition, make sure that you
1) create it at the same disk sector (use sector as the unit!)
2) create it with the same partition type (usually 7, HPFS/NTFS)
3) do not make it smaller than the new NTFS filesystem size
4) set the bootable flag for the partition if it existed before
Otherwise you won't be able to access NTFS or can't boot from the disk!
If you make a mistake and don't have a partition table backup then you
can recover the partition table by TestDisk or Parted's rescue mode.
shrink partition from 1.82 TB to 1.53 TB  00:00:01    ( SUCCESS )
         
old start: 63
old end: 3907024127
old size: 3907024065 (1.82 TB)
new start: 63
new end: 3292631039
new size: 3292630977 (1.53 TB)
check file system on /dev/sdd1 for errors and (if possible) fix them  00:00:40    ( ERROR )
         
ntfsresize -P -i -f -v /dev/sdd1

2 Reply by gedakc

  • gedakc
  • Developer
  • Offline
  • Registered: 2007-11-30
  • Posts: 4,592

Re: Resizing NTFS problems for Seagate GoFlex Desk 2TB External USB 2.0

From the what I can see of the gparted_details.htm log file, it appears that all operations went well, except for the last step to check the file system for errors.

Unfortunately the log file seems to end at the point and does not contain the details of the file system check.  Can you provide the remaining lines of the log file?

Would you be able to use GParted Live 0.12.1-1, and then use GParted to see if any errors are reported for the partition?

Also, would you be able to provide the output from the following three commands?

sudo fdisk -l -u

where one of the options is a lower case "L" and not the number one.

sudo parted /path-to-your-device unit s print

where /path-to-your-device is something like /dev/sdd.

sudo ntfsresize --info --force --no-progress-bar /path-to-partition

where /path-to-partition is something like /dev/sdd1.

3 Reply by simontse

  • simontse
  • New member
  • Offline
  • Registered: 2012-05-17
  • Posts: 3

Re: Resizing NTFS problems for Seagate GoFlex Desk 2TB External USB 2.0

Yep, unfortunately the gparted_details.htm log file ends at exactly that line. When I boot GParted Live 0.12.1-1, the errors reported are the same which is the output of ntfsresize (the #3 output).

Output from commands (/dev/sdd1 is the problematic partition.):

1. sudo fdisk -l -u

Disk /dev/sda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c6434

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048    30722047    15360000   83  Linux
/dev/sda2   *    30722048   117225471    43251712    7  HPFS/NTFS/exFAT

Disk /dev/sdb: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00091f70

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        2048   117229567    58613760   83  Linux

Disk /dev/sdd: 2000.4 GB, 2000398933504 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029167 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00048733

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1              63  3292631039  1646315488+   7  HPFS/NTFS/exFAT

2. sudo parted /dev/sdd unit s print

Model: Seagate FA GoFlex Desk (scsi)
Disk /dev/sdd: 3907029167s
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start  End          Size         Type     File system  Flags
 1      63s    3292631039s  3292630977s  primary  ntfs

3. sudo ntfsresize --info --force --no-progress-bar /dev/sdd1

ntfsresize v2011.4.12AR.4 (libntfs-3g)
$MFTMirr does not match $MFT (record 0).
ERROR(5): Opening '/dev/sdd1' as NTFS failed: Input/output error
NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!
The usage of the /f parameter is very IMPORTANT! No modification was
and will be made to NTFS by this software until it gets repaired.

Thank you very much for your help.

4 Reply by gedakc

  • gedakc
  • Developer
  • Offline
  • Registered: 2007-11-30
  • Posts: 4,592

Re: Resizing NTFS problems for Seagate GoFlex Desk 2TB External USB 2.0

When the ntfsresize command finishes resizing an NTFS file system, it marks the file system as "inconsistent" so that Windows will know to run a file system check upon boot.

The problem in this case is that Windows does not recognize the file system on the partition.
Since your computer also does not recognize the hard drive when plugged in directly via SATA, it is possible that the drive uses 4,096 byte sectors.  These 4 kByte sector drives are new and it is possible that your motherboard and OS only support 512 byte sector drives.

Is there another newer computer that you can try attaching to using SATA?

Your data should still be on the drive.  Since you are trying to recover the data, I assume that you do not have a backup of your data.  If you did, then reformatting the drive and restoring your backup would be the obvious solution.

Before attempting to fix the file system, it is advisable to make an image backup of the drive.  That way if a data recovery step does not work then you can restore the image and try something different.

If you wish to try to extract files from the drive in it's current state, but without writing any data to the drive, then you might check out photorec.

5 Reply by simontse (edited by simontse 2012-05-19 11:06:32)

  • simontse
  • New member
  • Offline
  • Registered: 2012-05-17
  • Posts: 3

Re: Resizing NTFS problems for Seagate GoFlex Desk 2TB External USB 2.0

I don't have another newer computer to try attaching using SATA... but my computer is really recent... running Z68 chipset by Gigabytem assembled half a year ago. I tried toggling the controller mode from IDE to AHCI to Intel's Rapid Storage mode but still the BIOS can't detect the hard disk. Should I try some add-on card? I don't have one though, but the data is precious enough for me to buy one for it.

I did some googling to learn more about what's up with the seagate base. Curiously I found that

1. The newer GoFlex Desk 4TB USB 3.0 drive does not natively use the advanced format (4K sector), see http://www.everythingusb.com/seagate-go … 21441.html, even though it is required to break the 2TB limit. The base has logics to translate 512 bytes sector to pretend 4K to an OS. So I guess my drive should also be just the old 512 bytes.
2. Since it makes perfect sense of modders to use the drive internally, I searched and found from youtube videos how people are actually connecting the hard drive internally. It seems most people can just plug the SATA cable and things just work. Curiously, from a comment somebody reported that his 2TB drive also can't be detected from the BIOS...

Here comes the wackiest bit. I turn to use ntfsfix on the drive and it worked and I can mount the drive in linux and read some files! (Yay!) Even gparted does not say it's corrupted and show that it's mounted. Yet, when I rebooted to windows 7, it appears in "RAW" again. Back to linux, everything turned back to the previous state (i.e. cannot mount with the same error messages, gparted and ntfsresize reports same error message)

Now, I run ntfsfix again to fix the $MFT and $MFTMirr inconsistencies and run gparted WITHOUT the drive mounted, to see if things would come out differently (I use gparted live 0.12.1-1). As expected, the partition appear with a red exclamation sign in gparted and when I right click for information, it froze, just like what happened just after the resize operation.

The situation is reproducible by running ntfsfix then gparted. Then I ran

sudo ntfsresize --info --force --no-progress-bar /dev/sdd1

and the output is huge:

ntfsresize v2011.4.12AR.4 (libntfs-3g)
Device name        : /dev/sdd1
NTFS volume version: 3.1
Cluster size       : 4096 bytes
Current volume size: 1685827056128 bytes (1685828 MB)
Current device size: 1685827060224 bytes (1685828 MB)
Checking filesystem consistency ...
Outside of the volume reference for inode 0 at 450891832:4096
Outside of the volume reference for inode 0 at 449744962:4086
Outside of the volume reference for inode 0 at 473850372:4084
Outside of the volume reference for inode 0 at 434522931:3845
ntfs_mst_post_read_fixup: magic: 0x00000000  size: 1024  usa_ofs: 0  usa_count: 65535: Invalid argument
Record 16 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000  size: 1024  usa_ofs: 0  usa_count: 65535: Invalid argument
Record 17 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000  size: 1024  usa_ofs: 0  usa_count: 65535: Invalid argument
Record 18 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000  size: 1024  usa_ofs: 0  usa_count: 65535: Invalid argument
Record 19 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000  size: 1024  usa_ofs: 0  usa_count: 65535: Invalid argument
Record 20 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000  size: 1024  usa_ofs: 0  usa_count: 65535: Invalid argument
Record 21 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000  size: 1024  usa_ofs: 0  usa_count: 65535: Invalid argument
Record 22 has no FILE magic (0x0)
ntfs_mst_post_read_fixup: magic: 0x00000000  size: 1024  usa_ofs: 0  usa_count: 65535: Invalid argument
Record 23 has no FILE magic (0x0)
^C2.63 percent completed

I think resizing the partition back to the original size by running fdisk then ntfsresize -f should work but I will refrain from trying before I backup my stuff, which will take a long time... (because I have been using this largest drive of mine like a garbage dump... and things are not so well organized...)

6 Reply by gedakc

  • gedakc
  • Developer
  • Offline
  • Registered: 2007-11-30
  • Posts: 4,592

Re: Resizing NTFS problems for Seagate GoFlex Desk 2TB External USB 2.0

Good sleuth work simontse discovering a way to get access for your data.  :-)

I whole heartedly agree that now that you have access to the file system, the first step is to back up your data.

After the backup is complete, your idea to grow the file system to it's original size sounds like a good one.  Since the partition starts on sector 63, which indicates cylinder alignment, I suggest you use "Align to Cylinder" when you try to grow the partition.