e-SATA formatted external HDD not recognized by USB












0















So I have an external HDD, I believe it's a Hitachi, 2tb, working fine EXCEPT: when I formatted this, it was via e-SATA, thru an Expresscard slot in my Mac Book Pro A1151, 2 partition, NTFS/Fat32. The enclosure I'm using is a Sabrent, e-sata/USB - solid.



It recognizes in SATA connection but not in USB - every time I connect via USB (in either OS X or Windows) it sees the drive but no file system/files and wants to be formatted.



Why?










share|improve this question























  • From your description and troubleshooting, sounds pretty much like bad hardware... Enclosure, USB cable, USB port, or possibly power (if USB powered).

    – acejavelin
    Feb 3 '16 at 0:18











  • hm - I suppose I never considered that. thanks for the insight, I guess the only solution is to remove it from the enclosure and test it via a dock or swiss army hook-up.

    – Jujube
    Feb 3 '16 at 0:25











  • If it always works via eSATA, you can pretty much say the drive itself is OK... My money is on the enclosure or cable. Are you trying to connect both eSATA and USB simultaneously? That would fail in most enclosures, some older ones required a power cycle between changing interfaces.

    – acejavelin
    Feb 3 '16 at 0:34











  • Maybe because of this. USB is trying to be smart while eSATA just relays data without any translation.

    – Kamil Maciorowski
    Dec 17 '18 at 9:08
















0















So I have an external HDD, I believe it's a Hitachi, 2tb, working fine EXCEPT: when I formatted this, it was via e-SATA, thru an Expresscard slot in my Mac Book Pro A1151, 2 partition, NTFS/Fat32. The enclosure I'm using is a Sabrent, e-sata/USB - solid.



It recognizes in SATA connection but not in USB - every time I connect via USB (in either OS X or Windows) it sees the drive but no file system/files and wants to be formatted.



Why?










share|improve this question























  • From your description and troubleshooting, sounds pretty much like bad hardware... Enclosure, USB cable, USB port, or possibly power (if USB powered).

    – acejavelin
    Feb 3 '16 at 0:18











  • hm - I suppose I never considered that. thanks for the insight, I guess the only solution is to remove it from the enclosure and test it via a dock or swiss army hook-up.

    – Jujube
    Feb 3 '16 at 0:25











  • If it always works via eSATA, you can pretty much say the drive itself is OK... My money is on the enclosure or cable. Are you trying to connect both eSATA and USB simultaneously? That would fail in most enclosures, some older ones required a power cycle between changing interfaces.

    – acejavelin
    Feb 3 '16 at 0:34











  • Maybe because of this. USB is trying to be smart while eSATA just relays data without any translation.

    – Kamil Maciorowski
    Dec 17 '18 at 9:08














0












0








0








So I have an external HDD, I believe it's a Hitachi, 2tb, working fine EXCEPT: when I formatted this, it was via e-SATA, thru an Expresscard slot in my Mac Book Pro A1151, 2 partition, NTFS/Fat32. The enclosure I'm using is a Sabrent, e-sata/USB - solid.



It recognizes in SATA connection but not in USB - every time I connect via USB (in either OS X or Windows) it sees the drive but no file system/files and wants to be formatted.



Why?










share|improve this question














So I have an external HDD, I believe it's a Hitachi, 2tb, working fine EXCEPT: when I formatted this, it was via e-SATA, thru an Expresscard slot in my Mac Book Pro A1151, 2 partition, NTFS/Fat32. The enclosure I'm using is a Sabrent, e-sata/USB - solid.



It recognizes in SATA connection but not in USB - every time I connect via USB (in either OS X or Windows) it sees the drive but no file system/files and wants to be formatted.



Why?







usb external-hard-drive connection esata expresscard






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 2 '16 at 21:28









JujubeJujube

1




1













  • From your description and troubleshooting, sounds pretty much like bad hardware... Enclosure, USB cable, USB port, or possibly power (if USB powered).

    – acejavelin
    Feb 3 '16 at 0:18











  • hm - I suppose I never considered that. thanks for the insight, I guess the only solution is to remove it from the enclosure and test it via a dock or swiss army hook-up.

    – Jujube
    Feb 3 '16 at 0:25











  • If it always works via eSATA, you can pretty much say the drive itself is OK... My money is on the enclosure or cable. Are you trying to connect both eSATA and USB simultaneously? That would fail in most enclosures, some older ones required a power cycle between changing interfaces.

    – acejavelin
    Feb 3 '16 at 0:34











  • Maybe because of this. USB is trying to be smart while eSATA just relays data without any translation.

    – Kamil Maciorowski
    Dec 17 '18 at 9:08



















  • From your description and troubleshooting, sounds pretty much like bad hardware... Enclosure, USB cable, USB port, or possibly power (if USB powered).

    – acejavelin
    Feb 3 '16 at 0:18











  • hm - I suppose I never considered that. thanks for the insight, I guess the only solution is to remove it from the enclosure and test it via a dock or swiss army hook-up.

    – Jujube
    Feb 3 '16 at 0:25











  • If it always works via eSATA, you can pretty much say the drive itself is OK... My money is on the enclosure or cable. Are you trying to connect both eSATA and USB simultaneously? That would fail in most enclosures, some older ones required a power cycle between changing interfaces.

    – acejavelin
    Feb 3 '16 at 0:34











  • Maybe because of this. USB is trying to be smart while eSATA just relays data without any translation.

    – Kamil Maciorowski
    Dec 17 '18 at 9:08

















From your description and troubleshooting, sounds pretty much like bad hardware... Enclosure, USB cable, USB port, or possibly power (if USB powered).

– acejavelin
Feb 3 '16 at 0:18





From your description and troubleshooting, sounds pretty much like bad hardware... Enclosure, USB cable, USB port, or possibly power (if USB powered).

– acejavelin
Feb 3 '16 at 0:18













hm - I suppose I never considered that. thanks for the insight, I guess the only solution is to remove it from the enclosure and test it via a dock or swiss army hook-up.

– Jujube
Feb 3 '16 at 0:25





hm - I suppose I never considered that. thanks for the insight, I guess the only solution is to remove it from the enclosure and test it via a dock or swiss army hook-up.

– Jujube
Feb 3 '16 at 0:25













If it always works via eSATA, you can pretty much say the drive itself is OK... My money is on the enclosure or cable. Are you trying to connect both eSATA and USB simultaneously? That would fail in most enclosures, some older ones required a power cycle between changing interfaces.

– acejavelin
Feb 3 '16 at 0:34





If it always works via eSATA, you can pretty much say the drive itself is OK... My money is on the enclosure or cable. Are you trying to connect both eSATA and USB simultaneously? That would fail in most enclosures, some older ones required a power cycle between changing interfaces.

– acejavelin
Feb 3 '16 at 0:34













Maybe because of this. USB is trying to be smart while eSATA just relays data without any translation.

– Kamil Maciorowski
Dec 17 '18 at 9:08





Maybe because of this. USB is trying to be smart while eSATA just relays data without any translation.

– Kamil Maciorowski
Dec 17 '18 at 9:08










1 Answer
1






active

oldest

votes


















0














It sounds to me, you have a very similar problem, what I have. My case is exactly reverse of yours :-) Your hardware is ok. Can you try to mount the disk and run fdisk under Linux (and post the output) ? In my case the problem was, Windows doesn't create an MBR-type partition table; it just creates a single large partition, and allocates the whole space of the harddisk for it. Maybe this is the problem in your case too.



USB sticks behave in this way under Windows. If you format a stick (even if it's 128GB or bigger), the entire space is allocated for one partition, wihtout creating the MBR.






share|improve this answer

























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1034821%2fe-sata-formatted-external-hdd-not-recognized-by-usb%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    It sounds to me, you have a very similar problem, what I have. My case is exactly reverse of yours :-) Your hardware is ok. Can you try to mount the disk and run fdisk under Linux (and post the output) ? In my case the problem was, Windows doesn't create an MBR-type partition table; it just creates a single large partition, and allocates the whole space of the harddisk for it. Maybe this is the problem in your case too.



    USB sticks behave in this way under Windows. If you format a stick (even if it's 128GB or bigger), the entire space is allocated for one partition, wihtout creating the MBR.






    share|improve this answer






























      0














      It sounds to me, you have a very similar problem, what I have. My case is exactly reverse of yours :-) Your hardware is ok. Can you try to mount the disk and run fdisk under Linux (and post the output) ? In my case the problem was, Windows doesn't create an MBR-type partition table; it just creates a single large partition, and allocates the whole space of the harddisk for it. Maybe this is the problem in your case too.



      USB sticks behave in this way under Windows. If you format a stick (even if it's 128GB or bigger), the entire space is allocated for one partition, wihtout creating the MBR.






      share|improve this answer




























        0












        0








        0







        It sounds to me, you have a very similar problem, what I have. My case is exactly reverse of yours :-) Your hardware is ok. Can you try to mount the disk and run fdisk under Linux (and post the output) ? In my case the problem was, Windows doesn't create an MBR-type partition table; it just creates a single large partition, and allocates the whole space of the harddisk for it. Maybe this is the problem in your case too.



        USB sticks behave in this way under Windows. If you format a stick (even if it's 128GB or bigger), the entire space is allocated for one partition, wihtout creating the MBR.






        share|improve this answer















        It sounds to me, you have a very similar problem, what I have. My case is exactly reverse of yours :-) Your hardware is ok. Can you try to mount the disk and run fdisk under Linux (and post the output) ? In my case the problem was, Windows doesn't create an MBR-type partition table; it just creates a single large partition, and allocates the whole space of the harddisk for it. Maybe this is the problem in your case too.



        USB sticks behave in this way under Windows. If you format a stick (even if it's 128GB or bigger), the entire space is allocated for one partition, wihtout creating the MBR.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Dec 17 '18 at 10:39

























        answered Dec 17 '18 at 8:42









        awgold90awgold90

        33




        33






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1034821%2fe-sata-formatted-external-hdd-not-recognized-by-usb%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Plaza Victoria

            Brian Clough

            Cáceres