eSata+USB2 enclosure and compatibility/weirdness?

User discussion forum for items related to technology in general.
ohaya
Posts: 229
Joined: Fri Jan 06, 2012 11:40 pm

Re: eSata+USB2 enclosure and compatibility/weirdness?

Post by ohaya »

esata:

C:\>fsutil fsinfo ntfsinfo j:
NTFS Volume Serial Number : 0xb0525dc6525d9248
Version : 3.1
Number Sectors : 0x0000000057544fff
Total Clusters : 0x000000000aea89ff
Free Clusters : 0x00000000037fa917
Total Reserved : 0x00000000000004b0
Bytes Per Sector : 512
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x0000000000100000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x00000000000c0100
Mft Zone End : 0x00000000000cc840
RM Identifier: 454E4EC7-6A94-11E2-A307-008CFA2A5E8E



USB:

C:\>fsutil fsinfo volumeinfo k:
Error: The volume does not contain a recognized file system.
Please make sure that all required file system drivers are loaded and that the v
olume is not corrupted.
TeraByte Support
Posts: 3596
Joined: Thu May 05, 2011 10:37 pm

Re: eSata+USB2 enclosure and compatibility/weirdness?

Post by TeraByte Support »

but make it available so you can get the information...


"ohaya" wrote in message news:9034@public.tech.misc...

esata:

C:\>fsutil fsinfo ntfsinfo j:
NTFS Volume Serial Number : 0xb0525dc6525d9248
Version : 3.1
Number Sectors : 0x0000000057544fff
Total Clusters : 0x000000000aea89ff
Free Clusters : 0x00000000037fa917
Total Reserved : 0x00000000000004b0
Bytes Per Sector : 512
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 0x0000000000100000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x00000000000c0100
Mft Zone End : 0x00000000000cc840
RM Identifier: 454E4EC7-6A94-11E2-A307-008CFA2A5E8E



USB:

C:\>fsutil fsinfo volumeinfo k:
Error: The volume does not contain a recognized file system.
Please make sure that all required file system drivers are loaded and that
the v
olume is not corrupted.


ohaya
Posts: 229
Joined: Fri Jan 06, 2012 11:40 pm

Re: eSata+USB2 enclosure and compatibility/weirdness?

Post by ohaya »

Hi,

I don't understand your last post?

"but make it available so you can get the information... "
TeraByte Support(PP)
Posts: 1643
Joined: Fri Aug 12, 2011 12:51 am

Re: eSata+USB2 enclosure and compatibility/weirdness?

Post by TeraByte Support(PP) »

You would need to have a formatted partition on the USB drive to get the details. For example, initialize the drive, create a partition, format it NTFS, assign a letter (K:), then run fsutil on it. This would, of course, delete any data on the drive. I assume that isn't a problem since it sounds like you're just testing with the drive. If it is a problem maybe you could use one of the other drives you know has the problem.
ohaya
Posts: 229
Joined: Fri Jan 06, 2012 11:40 pm

Re: eSata+USB2 enclosure and compatibility/weirdness?

Post by ohaya »

The following was with the drive/enclosure connected to the PC via USB. I formatted in Windows 7 (rt-click, format):

C:\>fsutil fsinfo ntfsinfo k:
NTFS Volume Serial Number : 0x10a06db1a06d9e4a
Version : 3.1
Number Sectors : 0x000000000aea8cdd
Total Clusters : 0x000000000aea8cdd
Free Clusters : 0x000000000aea208e
Total Reserved : 0x0000000000000000
Bytes Per Sector : 4096
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 4096
Clusters Per FileRecord Segment : 1
Mft Valid Data Length : 0x0000000000100000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x00000000000c0000
Mft Zone End : 0x00000000000cc820
RM Identifier: 545FB43A-7F65-11E4-BCD3-005056C00008
ohaya
Posts: 229
Joined: Fri Jan 06, 2012 11:40 pm

Re: eSata+USB2 enclosure and compatibility/weirdness?

Post by ohaya »

I can see that the formatting is different between the two situations above, but I'm not quite sure what the above is telling me/us?

Maybe I need to force the allocation size in the format to some size that would be acceptable both when connected using USB and when using eSATA, or something like that?
ohaya
Posts: 229
Joined: Fri Jan 06, 2012 11:40 pm

Re: eSata+USB2 enclosure and compatibility/weirdness?

Post by ohaya »

Is the problem I'm seeing because the two 750GB drives are advanced format drives?

And, if so, if I formatted the drive while it was plugged directly into a SATA port on the computer, would the drive then work (the partition be visible) both when using USB and eSATA connections?
TeraByte Support(PP)
Posts: 1643
Joined: Fri Aug 12, 2011 12:51 am

Re: eSata+USB2 enclosure and compatibility/weirdness?

Post by TeraByte Support(PP) »

I don't see the "Bytes Per Physical Sector" item in either of your outputs. Is your Windows 7 system updated (pre-SP1 looks like your output)? If not, updating may help resolve the issue (or at least improve it).

If this is the source of the original problem it would be because of the 4K sectors and not the size of the drive. Of course, larger drives would be more likely to use 4K sectors.
ohaya
Posts: 229
Joined: Fri Jan 06, 2012 11:40 pm

Re: eSata+USB2 enclosure and compatibility/weirdness?

Post by ohaya »

Paul,

This PC is already WIndows 7 SP1.

Were there any post-SP1 updates that might be helpful?
ohaya
Posts: 229
Joined: Fri Jan 06, 2012 11:40 pm

Re: eSata+USB2 enclosure and compatibility/weirdness?

Post by ohaya »

I found this:

http://support.microsoft.com/kb/982018

and installed it.

Here's the command now, on USB:

C:\>fsutil fsinfo ntfsinfo k:
NTFS Volume Serial Number : 0x10a06db1a06d9e4a
Version : 3.1
Number Sectors : 0x000000000aea8cdd
Total Clusters : 0x000000000aea8cdd
Free Clusters : 0x000000000aea2089
Total Reserved : 0x0000000000000a00
Bytes Per Sector : 4096
Bytes Per Physical Sector : <Not Supported>
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 4096
Clusters Per FileRecord Segment : 1
Mft Valid Data Length : 0x0000000000100000
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x00000000000c0100
Mft Zone End : 0x00000000000cc900
RM Identifier: 545FB43A-7F65-11E4-BCD3-005056C00008
Post Reply