Partition on an SATA harddisk not recognized after it was formatted using an USB adapter












0














I have five 500GB SATA harddisk. For all of these I used an USB 2.0 (and later an USB 3.0) adapter to connect to the PC. They all work good, no bad sectors and each one could be recognized over USB. I formatted all of them over USB using MBR as the type of the partition table.



For some days ago i bought an internal harddisk rack, like this one.
After i put the harddisk into the rack, and started Windows 7, the partition didn't show up, only a drive letter. If i clicked on the letter, a question appeared: "Do you want to format the disk?". The rack is ok, because other harddisk works great. The rack has no chip at all; it's simply connecting the SATA cable to the harddisk and therefore no driver was installed upon the first start.



I started Linux. I realized, that all of the 5 harddisk have NO partiton table at all (I mean the old school MBR-type partition table with entries for 4 primary partitions), because fdisk /dev/sdb shows an empty list.



This means: under Linux I can mount the harddisk using mount /dev/sdb and NOT mount /dev/sdb1. It seems, the entire disk is a one large partition; therefore sdb1 didn't work.



I used Testdisk to recover the partition, but not worked.



Is my only option, to copy the data from all of the 5 disks to another disk, that has really an MBR-type partition table?










share|improve this question
























  • How you going to copy the data if there is no partition table?
    – Moab
    Dec 16 at 17:24










  • Luckily I can copy it, because the partition is recognized, BUT ONLY if i use the USB adapter. If put the disk into the rack, the partition isn't showing :-) I can confirm: if i create the MBR partition table under Linux using fdisk and create an NTFS filesystem on the first partition (with mkntfs), everything works fine (rack, USB2, USB3, everything is ok).
    – awgold90
    Dec 16 at 18:17










  • If I dump the first few hundred sectors with dd, would it be difficult to fix the problem manually ? (creating the MBR, and writing the starting sector of the partition into it)
    – awgold90
    Dec 16 at 18:21








  • 1




    Some USB enclosures and adapters have weird problems and incompatibilities. It sounds like your adapter is one. You might want to just replace it. In the meantime, use it to offload anything you've stored on the drives, then reformat the drives either internally, or using a USB device that doesn't have problems.
    – fixer1234
    Dec 16 at 23:40










  • The funny thing is, under Linux I can mount the disk using the same USB adapter, that makes the problem under Windows :-)
    – awgold90
    Dec 17 at 8:47
















0














I have five 500GB SATA harddisk. For all of these I used an USB 2.0 (and later an USB 3.0) adapter to connect to the PC. They all work good, no bad sectors and each one could be recognized over USB. I formatted all of them over USB using MBR as the type of the partition table.



For some days ago i bought an internal harddisk rack, like this one.
After i put the harddisk into the rack, and started Windows 7, the partition didn't show up, only a drive letter. If i clicked on the letter, a question appeared: "Do you want to format the disk?". The rack is ok, because other harddisk works great. The rack has no chip at all; it's simply connecting the SATA cable to the harddisk and therefore no driver was installed upon the first start.



I started Linux. I realized, that all of the 5 harddisk have NO partiton table at all (I mean the old school MBR-type partition table with entries for 4 primary partitions), because fdisk /dev/sdb shows an empty list.



This means: under Linux I can mount the harddisk using mount /dev/sdb and NOT mount /dev/sdb1. It seems, the entire disk is a one large partition; therefore sdb1 didn't work.



I used Testdisk to recover the partition, but not worked.



Is my only option, to copy the data from all of the 5 disks to another disk, that has really an MBR-type partition table?










share|improve this question
























  • How you going to copy the data if there is no partition table?
    – Moab
    Dec 16 at 17:24










  • Luckily I can copy it, because the partition is recognized, BUT ONLY if i use the USB adapter. If put the disk into the rack, the partition isn't showing :-) I can confirm: if i create the MBR partition table under Linux using fdisk and create an NTFS filesystem on the first partition (with mkntfs), everything works fine (rack, USB2, USB3, everything is ok).
    – awgold90
    Dec 16 at 18:17










  • If I dump the first few hundred sectors with dd, would it be difficult to fix the problem manually ? (creating the MBR, and writing the starting sector of the partition into it)
    – awgold90
    Dec 16 at 18:21








  • 1




    Some USB enclosures and adapters have weird problems and incompatibilities. It sounds like your adapter is one. You might want to just replace it. In the meantime, use it to offload anything you've stored on the drives, then reformat the drives either internally, or using a USB device that doesn't have problems.
    – fixer1234
    Dec 16 at 23:40










  • The funny thing is, under Linux I can mount the disk using the same USB adapter, that makes the problem under Windows :-)
    – awgold90
    Dec 17 at 8:47














0












0








0







I have five 500GB SATA harddisk. For all of these I used an USB 2.0 (and later an USB 3.0) adapter to connect to the PC. They all work good, no bad sectors and each one could be recognized over USB. I formatted all of them over USB using MBR as the type of the partition table.



For some days ago i bought an internal harddisk rack, like this one.
After i put the harddisk into the rack, and started Windows 7, the partition didn't show up, only a drive letter. If i clicked on the letter, a question appeared: "Do you want to format the disk?". The rack is ok, because other harddisk works great. The rack has no chip at all; it's simply connecting the SATA cable to the harddisk and therefore no driver was installed upon the first start.



I started Linux. I realized, that all of the 5 harddisk have NO partiton table at all (I mean the old school MBR-type partition table with entries for 4 primary partitions), because fdisk /dev/sdb shows an empty list.



This means: under Linux I can mount the harddisk using mount /dev/sdb and NOT mount /dev/sdb1. It seems, the entire disk is a one large partition; therefore sdb1 didn't work.



I used Testdisk to recover the partition, but not worked.



Is my only option, to copy the data from all of the 5 disks to another disk, that has really an MBR-type partition table?










share|improve this question















I have five 500GB SATA harddisk. For all of these I used an USB 2.0 (and later an USB 3.0) adapter to connect to the PC. They all work good, no bad sectors and each one could be recognized over USB. I formatted all of them over USB using MBR as the type of the partition table.



For some days ago i bought an internal harddisk rack, like this one.
After i put the harddisk into the rack, and started Windows 7, the partition didn't show up, only a drive letter. If i clicked on the letter, a question appeared: "Do you want to format the disk?". The rack is ok, because other harddisk works great. The rack has no chip at all; it's simply connecting the SATA cable to the harddisk and therefore no driver was installed upon the first start.



I started Linux. I realized, that all of the 5 harddisk have NO partiton table at all (I mean the old school MBR-type partition table with entries for 4 primary partitions), because fdisk /dev/sdb shows an empty list.



This means: under Linux I can mount the harddisk using mount /dev/sdb and NOT mount /dev/sdb1. It seems, the entire disk is a one large partition; therefore sdb1 didn't work.



I used Testdisk to recover the partition, but not worked.



Is my only option, to copy the data from all of the 5 disks to another disk, that has really an MBR-type partition table?







windows-7 hard-drive partitioning






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 17 at 14:19

























asked Dec 16 at 16:43









awgold90

11




11












  • How you going to copy the data if there is no partition table?
    – Moab
    Dec 16 at 17:24










  • Luckily I can copy it, because the partition is recognized, BUT ONLY if i use the USB adapter. If put the disk into the rack, the partition isn't showing :-) I can confirm: if i create the MBR partition table under Linux using fdisk and create an NTFS filesystem on the first partition (with mkntfs), everything works fine (rack, USB2, USB3, everything is ok).
    – awgold90
    Dec 16 at 18:17










  • If I dump the first few hundred sectors with dd, would it be difficult to fix the problem manually ? (creating the MBR, and writing the starting sector of the partition into it)
    – awgold90
    Dec 16 at 18:21








  • 1




    Some USB enclosures and adapters have weird problems and incompatibilities. It sounds like your adapter is one. You might want to just replace it. In the meantime, use it to offload anything you've stored on the drives, then reformat the drives either internally, or using a USB device that doesn't have problems.
    – fixer1234
    Dec 16 at 23:40










  • The funny thing is, under Linux I can mount the disk using the same USB adapter, that makes the problem under Windows :-)
    – awgold90
    Dec 17 at 8:47


















  • How you going to copy the data if there is no partition table?
    – Moab
    Dec 16 at 17:24










  • Luckily I can copy it, because the partition is recognized, BUT ONLY if i use the USB adapter. If put the disk into the rack, the partition isn't showing :-) I can confirm: if i create the MBR partition table under Linux using fdisk and create an NTFS filesystem on the first partition (with mkntfs), everything works fine (rack, USB2, USB3, everything is ok).
    – awgold90
    Dec 16 at 18:17










  • If I dump the first few hundred sectors with dd, would it be difficult to fix the problem manually ? (creating the MBR, and writing the starting sector of the partition into it)
    – awgold90
    Dec 16 at 18:21








  • 1




    Some USB enclosures and adapters have weird problems and incompatibilities. It sounds like your adapter is one. You might want to just replace it. In the meantime, use it to offload anything you've stored on the drives, then reformat the drives either internally, or using a USB device that doesn't have problems.
    – fixer1234
    Dec 16 at 23:40










  • The funny thing is, under Linux I can mount the disk using the same USB adapter, that makes the problem under Windows :-)
    – awgold90
    Dec 17 at 8:47
















How you going to copy the data if there is no partition table?
– Moab
Dec 16 at 17:24




How you going to copy the data if there is no partition table?
– Moab
Dec 16 at 17:24












Luckily I can copy it, because the partition is recognized, BUT ONLY if i use the USB adapter. If put the disk into the rack, the partition isn't showing :-) I can confirm: if i create the MBR partition table under Linux using fdisk and create an NTFS filesystem on the first partition (with mkntfs), everything works fine (rack, USB2, USB3, everything is ok).
– awgold90
Dec 16 at 18:17




Luckily I can copy it, because the partition is recognized, BUT ONLY if i use the USB adapter. If put the disk into the rack, the partition isn't showing :-) I can confirm: if i create the MBR partition table under Linux using fdisk and create an NTFS filesystem on the first partition (with mkntfs), everything works fine (rack, USB2, USB3, everything is ok).
– awgold90
Dec 16 at 18:17












If I dump the first few hundred sectors with dd, would it be difficult to fix the problem manually ? (creating the MBR, and writing the starting sector of the partition into it)
– awgold90
Dec 16 at 18:21






If I dump the first few hundred sectors with dd, would it be difficult to fix the problem manually ? (creating the MBR, and writing the starting sector of the partition into it)
– awgold90
Dec 16 at 18:21






1




1




Some USB enclosures and adapters have weird problems and incompatibilities. It sounds like your adapter is one. You might want to just replace it. In the meantime, use it to offload anything you've stored on the drives, then reformat the drives either internally, or using a USB device that doesn't have problems.
– fixer1234
Dec 16 at 23:40




Some USB enclosures and adapters have weird problems and incompatibilities. It sounds like your adapter is one. You might want to just replace it. In the meantime, use it to offload anything you've stored on the drives, then reformat the drives either internally, or using a USB device that doesn't have problems.
– fixer1234
Dec 16 at 23:40












The funny thing is, under Linux I can mount the disk using the same USB adapter, that makes the problem under Windows :-)
– awgold90
Dec 17 at 8:47




The funny thing is, under Linux I can mount the disk using the same USB adapter, that makes the problem under Windows :-)
– awgold90
Dec 17 at 8:47










1 Answer
1






active

oldest

votes


















0














I made some investigations with an 500GB Seagate ST500DM002 disk, that made some problems.






Formatting with blocksize "standard" under Windows



Using an USB3 adapter: the disk was not recognized !





  • HxD Hex Editor reports a sector size of 512 bytes

  • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

  • fdisk: Sector size (logical/physical): 512 bytes / 4096 bytes

  • Mounting the partition was successful under Linux


Using an USB2 adapter: the disk was recognized under Windows, but the partition was not shown. The popup says: it has to be formatted.




  • HxD reports a sector size of 4096 bytes

  • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

  • fdisk: Sector size (logical/physical): 4096 bytes / 4096 bytes

  • Mounting the partition failed under Linux


Using the SATA port: under Windows the disk was recognized, but the partition was not shown.




  • HxD reports a sector size of 512 bytes

  • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

  • fdisk: Sector size (logical/physical): 512 bytes / 4096 bytes

  • Mounting the partition was successful under Linux.





The first 20971520 sectors were dumped with:



dd bs=10485760 count=2 if=/dev/sdc of=/tmp/hdd_main/test/blocksize_standard/file



Sector dumps (using USB2, USB3, SATA) for the option blocksize=standard are located in: blocksize_standard/ --> all files are identical.
Using blocksize=512bytes, they are under blocksize_512bytes/ --> all files are identical.
The filesystem contains a README file with the content "Hello World".







Formatting with blocksize "512bytes" under Windows



Under Windows I was not able to do this. Only Linux



mkntfs -f -v -s 512 /dev/sdc1



could format it with 512 bytes.
Using this option i was able to access the disk using USB3, and SATA under Windows and under Linux!
USB2 has not worked (on both Linux and Windows) !
It seems the problem is with the adapter (and somehow with the OS). The adapter doesn't insert extra data into the stream.
It has to do with the blocksize read by the adapter (as fdisk shows).







The solution:



formatting with blocksize 512bytes under Linux, the disk can be used intern and extern as well (as mentioned here).
If the disk was used under Windows, the data must be backed up (e.g under Linux), the disk must be formatted again, and the data have to copied back to it.






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%2f1385041%2fpartition-on-an-sata-harddisk-not-recognized-after-it-was-formatted-using-an-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














    I made some investigations with an 500GB Seagate ST500DM002 disk, that made some problems.






    Formatting with blocksize "standard" under Windows



    Using an USB3 adapter: the disk was not recognized !





    • HxD Hex Editor reports a sector size of 512 bytes

    • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

    • fdisk: Sector size (logical/physical): 512 bytes / 4096 bytes

    • Mounting the partition was successful under Linux


    Using an USB2 adapter: the disk was recognized under Windows, but the partition was not shown. The popup says: it has to be formatted.




    • HxD reports a sector size of 4096 bytes

    • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

    • fdisk: Sector size (logical/physical): 4096 bytes / 4096 bytes

    • Mounting the partition failed under Linux


    Using the SATA port: under Windows the disk was recognized, but the partition was not shown.




    • HxD reports a sector size of 512 bytes

    • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

    • fdisk: Sector size (logical/physical): 512 bytes / 4096 bytes

    • Mounting the partition was successful under Linux.





    The first 20971520 sectors were dumped with:



    dd bs=10485760 count=2 if=/dev/sdc of=/tmp/hdd_main/test/blocksize_standard/file



    Sector dumps (using USB2, USB3, SATA) for the option blocksize=standard are located in: blocksize_standard/ --> all files are identical.
    Using blocksize=512bytes, they are under blocksize_512bytes/ --> all files are identical.
    The filesystem contains a README file with the content "Hello World".







    Formatting with blocksize "512bytes" under Windows



    Under Windows I was not able to do this. Only Linux



    mkntfs -f -v -s 512 /dev/sdc1



    could format it with 512 bytes.
    Using this option i was able to access the disk using USB3, and SATA under Windows and under Linux!
    USB2 has not worked (on both Linux and Windows) !
    It seems the problem is with the adapter (and somehow with the OS). The adapter doesn't insert extra data into the stream.
    It has to do with the blocksize read by the adapter (as fdisk shows).







    The solution:



    formatting with blocksize 512bytes under Linux, the disk can be used intern and extern as well (as mentioned here).
    If the disk was used under Windows, the data must be backed up (e.g under Linux), the disk must be formatted again, and the data have to copied back to it.






    share|improve this answer


























      0














      I made some investigations with an 500GB Seagate ST500DM002 disk, that made some problems.






      Formatting with blocksize "standard" under Windows



      Using an USB3 adapter: the disk was not recognized !





      • HxD Hex Editor reports a sector size of 512 bytes

      • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

      • fdisk: Sector size (logical/physical): 512 bytes / 4096 bytes

      • Mounting the partition was successful under Linux


      Using an USB2 adapter: the disk was recognized under Windows, but the partition was not shown. The popup says: it has to be formatted.




      • HxD reports a sector size of 4096 bytes

      • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

      • fdisk: Sector size (logical/physical): 4096 bytes / 4096 bytes

      • Mounting the partition failed under Linux


      Using the SATA port: under Windows the disk was recognized, but the partition was not shown.




      • HxD reports a sector size of 512 bytes

      • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

      • fdisk: Sector size (logical/physical): 512 bytes / 4096 bytes

      • Mounting the partition was successful under Linux.





      The first 20971520 sectors were dumped with:



      dd bs=10485760 count=2 if=/dev/sdc of=/tmp/hdd_main/test/blocksize_standard/file



      Sector dumps (using USB2, USB3, SATA) for the option blocksize=standard are located in: blocksize_standard/ --> all files are identical.
      Using blocksize=512bytes, they are under blocksize_512bytes/ --> all files are identical.
      The filesystem contains a README file with the content "Hello World".







      Formatting with blocksize "512bytes" under Windows



      Under Windows I was not able to do this. Only Linux



      mkntfs -f -v -s 512 /dev/sdc1



      could format it with 512 bytes.
      Using this option i was able to access the disk using USB3, and SATA under Windows and under Linux!
      USB2 has not worked (on both Linux and Windows) !
      It seems the problem is with the adapter (and somehow with the OS). The adapter doesn't insert extra data into the stream.
      It has to do with the blocksize read by the adapter (as fdisk shows).







      The solution:



      formatting with blocksize 512bytes under Linux, the disk can be used intern and extern as well (as mentioned here).
      If the disk was used under Windows, the data must be backed up (e.g under Linux), the disk must be formatted again, and the data have to copied back to it.






      share|improve this answer
























        0












        0








        0






        I made some investigations with an 500GB Seagate ST500DM002 disk, that made some problems.






        Formatting with blocksize "standard" under Windows



        Using an USB3 adapter: the disk was not recognized !





        • HxD Hex Editor reports a sector size of 512 bytes

        • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

        • fdisk: Sector size (logical/physical): 512 bytes / 4096 bytes

        • Mounting the partition was successful under Linux


        Using an USB2 adapter: the disk was recognized under Windows, but the partition was not shown. The popup says: it has to be formatted.




        • HxD reports a sector size of 4096 bytes

        • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

        • fdisk: Sector size (logical/physical): 4096 bytes / 4096 bytes

        • Mounting the partition failed under Linux


        Using the SATA port: under Windows the disk was recognized, but the partition was not shown.




        • HxD reports a sector size of 512 bytes

        • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

        • fdisk: Sector size (logical/physical): 512 bytes / 4096 bytes

        • Mounting the partition was successful under Linux.





        The first 20971520 sectors were dumped with:



        dd bs=10485760 count=2 if=/dev/sdc of=/tmp/hdd_main/test/blocksize_standard/file



        Sector dumps (using USB2, USB3, SATA) for the option blocksize=standard are located in: blocksize_standard/ --> all files are identical.
        Using blocksize=512bytes, they are under blocksize_512bytes/ --> all files are identical.
        The filesystem contains a README file with the content "Hello World".







        Formatting with blocksize "512bytes" under Windows



        Under Windows I was not able to do this. Only Linux



        mkntfs -f -v -s 512 /dev/sdc1



        could format it with 512 bytes.
        Using this option i was able to access the disk using USB3, and SATA under Windows and under Linux!
        USB2 has not worked (on both Linux and Windows) !
        It seems the problem is with the adapter (and somehow with the OS). The adapter doesn't insert extra data into the stream.
        It has to do with the blocksize read by the adapter (as fdisk shows).







        The solution:



        formatting with blocksize 512bytes under Linux, the disk can be used intern and extern as well (as mentioned here).
        If the disk was used under Windows, the data must be backed up (e.g under Linux), the disk must be formatted again, and the data have to copied back to it.






        share|improve this answer












        I made some investigations with an 500GB Seagate ST500DM002 disk, that made some problems.






        Formatting with blocksize "standard" under Windows



        Using an USB3 adapter: the disk was not recognized !





        • HxD Hex Editor reports a sector size of 512 bytes

        • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

        • fdisk: Sector size (logical/physical): 512 bytes / 4096 bytes

        • Mounting the partition was successful under Linux


        Using an USB2 adapter: the disk was recognized under Windows, but the partition was not shown. The popup says: it has to be formatted.




        • HxD reports a sector size of 4096 bytes

        • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

        • fdisk: Sector size (logical/physical): 4096 bytes / 4096 bytes

        • Mounting the partition failed under Linux


        Using the SATA port: under Windows the disk was recognized, but the partition was not shown.




        • HxD reports a sector size of 512 bytes

        • hdparm: Logical Sector size: 512 bytes / Physical Sector size: 4096 bytes

        • fdisk: Sector size (logical/physical): 512 bytes / 4096 bytes

        • Mounting the partition was successful under Linux.





        The first 20971520 sectors were dumped with:



        dd bs=10485760 count=2 if=/dev/sdc of=/tmp/hdd_main/test/blocksize_standard/file



        Sector dumps (using USB2, USB3, SATA) for the option blocksize=standard are located in: blocksize_standard/ --> all files are identical.
        Using blocksize=512bytes, they are under blocksize_512bytes/ --> all files are identical.
        The filesystem contains a README file with the content "Hello World".







        Formatting with blocksize "512bytes" under Windows



        Under Windows I was not able to do this. Only Linux



        mkntfs -f -v -s 512 /dev/sdc1



        could format it with 512 bytes.
        Using this option i was able to access the disk using USB3, and SATA under Windows and under Linux!
        USB2 has not worked (on both Linux and Windows) !
        It seems the problem is with the adapter (and somehow with the OS). The adapter doesn't insert extra data into the stream.
        It has to do with the blocksize read by the adapter (as fdisk shows).







        The solution:



        formatting with blocksize 512bytes under Linux, the disk can be used intern and extern as well (as mentioned here).
        If the disk was used under Windows, the data must be backed up (e.g under Linux), the disk must be formatted again, and the data have to copied back to it.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered yesterday









        awgold90

        11




        11






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f1385041%2fpartition-on-an-sata-harddisk-not-recognized-after-it-was-formatted-using-an-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

            flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

            Mangá

            Eduardo VII do Reino Unido