16.04 Live vs GParted












1















I have made a Live 16.04 pendrive using SDC, (no persistence option available), and also tried UNetbootin-windows 613, (persistent). The drive is 4GB.



When I look at the drive in GParted on a 14.04 computer I am given a Libparted warning about GPT signatures, no valid fake MSDOS...GParted then shows the drive as only having unallocated space.



When I look at the drive in GParted when booted from the Live 16.04 drive the Libparted warning tells me the driver descriptor says block size is 2048b but Linux says 512b.



If I click ignore, GParted then shows unknown first partition of 4KiB, unllocated second partition of 1.38GiB, 2.31 MiB fat16 third partition and 13.99 GiB unallocated forth partition. (which is a lot of free space for a 4GB drive).



I have also not been unable to edit grub.cfg, txt.cfg or syslinux.cfg (to use persistence).



I am wondering what is up? Is anyone else experiencing this?










share|improve this question

























  • Perhaps you have a hybrid GPT/MSDOS partition table on the drive? These are often seen with OS X, but are not normal for GNU/Linux or Windows. If you need both then be sure to keep these in sync with a tool like gptsync.

    – Curtis Gedak
    Apr 29 '16 at 17:30













  • Thanks, I've tried both GPT and MSDOS tables, I am wondering if this is a bug with Startup Disk Creator in 16.04, and If it is happening to others.

    – C.S.Cameron
    May 2 '16 at 23:43
















1















I have made a Live 16.04 pendrive using SDC, (no persistence option available), and also tried UNetbootin-windows 613, (persistent). The drive is 4GB.



When I look at the drive in GParted on a 14.04 computer I am given a Libparted warning about GPT signatures, no valid fake MSDOS...GParted then shows the drive as only having unallocated space.



When I look at the drive in GParted when booted from the Live 16.04 drive the Libparted warning tells me the driver descriptor says block size is 2048b but Linux says 512b.



If I click ignore, GParted then shows unknown first partition of 4KiB, unllocated second partition of 1.38GiB, 2.31 MiB fat16 third partition and 13.99 GiB unallocated forth partition. (which is a lot of free space for a 4GB drive).



I have also not been unable to edit grub.cfg, txt.cfg or syslinux.cfg (to use persistence).



I am wondering what is up? Is anyone else experiencing this?










share|improve this question

























  • Perhaps you have a hybrid GPT/MSDOS partition table on the drive? These are often seen with OS X, but are not normal for GNU/Linux or Windows. If you need both then be sure to keep these in sync with a tool like gptsync.

    – Curtis Gedak
    Apr 29 '16 at 17:30













  • Thanks, I've tried both GPT and MSDOS tables, I am wondering if this is a bug with Startup Disk Creator in 16.04, and If it is happening to others.

    – C.S.Cameron
    May 2 '16 at 23:43














1












1








1








I have made a Live 16.04 pendrive using SDC, (no persistence option available), and also tried UNetbootin-windows 613, (persistent). The drive is 4GB.



When I look at the drive in GParted on a 14.04 computer I am given a Libparted warning about GPT signatures, no valid fake MSDOS...GParted then shows the drive as only having unallocated space.



When I look at the drive in GParted when booted from the Live 16.04 drive the Libparted warning tells me the driver descriptor says block size is 2048b but Linux says 512b.



If I click ignore, GParted then shows unknown first partition of 4KiB, unllocated second partition of 1.38GiB, 2.31 MiB fat16 third partition and 13.99 GiB unallocated forth partition. (which is a lot of free space for a 4GB drive).



I have also not been unable to edit grub.cfg, txt.cfg or syslinux.cfg (to use persistence).



I am wondering what is up? Is anyone else experiencing this?










share|improve this question
















I have made a Live 16.04 pendrive using SDC, (no persistence option available), and also tried UNetbootin-windows 613, (persistent). The drive is 4GB.



When I look at the drive in GParted on a 14.04 computer I am given a Libparted warning about GPT signatures, no valid fake MSDOS...GParted then shows the drive as only having unallocated space.



When I look at the drive in GParted when booted from the Live 16.04 drive the Libparted warning tells me the driver descriptor says block size is 2048b but Linux says 512b.



If I click ignore, GParted then shows unknown first partition of 4KiB, unllocated second partition of 1.38GiB, 2.31 MiB fat16 third partition and 13.99 GiB unallocated forth partition. (which is a lot of free space for a 4GB drive).



I have also not been unable to edit grub.cfg, txt.cfg or syslinux.cfg (to use persistence).



I am wondering what is up? Is anyone else experiencing this?







gparted






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 12 at 3:22









Codito ergo sum

1,5023825




1,5023825










asked Apr 27 '16 at 18:24









C.S.CameronC.S.Cameron

4,4691928




4,4691928













  • Perhaps you have a hybrid GPT/MSDOS partition table on the drive? These are often seen with OS X, but are not normal for GNU/Linux or Windows. If you need both then be sure to keep these in sync with a tool like gptsync.

    – Curtis Gedak
    Apr 29 '16 at 17:30













  • Thanks, I've tried both GPT and MSDOS tables, I am wondering if this is a bug with Startup Disk Creator in 16.04, and If it is happening to others.

    – C.S.Cameron
    May 2 '16 at 23:43



















  • Perhaps you have a hybrid GPT/MSDOS partition table on the drive? These are often seen with OS X, but are not normal for GNU/Linux or Windows. If you need both then be sure to keep these in sync with a tool like gptsync.

    – Curtis Gedak
    Apr 29 '16 at 17:30













  • Thanks, I've tried both GPT and MSDOS tables, I am wondering if this is a bug with Startup Disk Creator in 16.04, and If it is happening to others.

    – C.S.Cameron
    May 2 '16 at 23:43

















Perhaps you have a hybrid GPT/MSDOS partition table on the drive? These are often seen with OS X, but are not normal for GNU/Linux or Windows. If you need both then be sure to keep these in sync with a tool like gptsync.

– Curtis Gedak
Apr 29 '16 at 17:30







Perhaps you have a hybrid GPT/MSDOS partition table on the drive? These are often seen with OS X, but are not normal for GNU/Linux or Windows. If you need both then be sure to keep these in sync with a tool like gptsync.

– Curtis Gedak
Apr 29 '16 at 17:30















Thanks, I've tried both GPT and MSDOS tables, I am wondering if this is a bug with Startup Disk Creator in 16.04, and If it is happening to others.

– C.S.Cameron
May 2 '16 at 23:43





Thanks, I've tried both GPT and MSDOS tables, I am wondering if this is a bug with Startup Disk Creator in 16.04, and If it is happening to others.

– C.S.Cameron
May 2 '16 at 23:43










1 Answer
1






active

oldest

votes


















0














You might try removing the broken GPT with the following steps.





  1. From a terminal window run:



    sudo gdisk /path-to-usb-drive


    Where /path-to-usb-drive is something like /dev/sdc.



  2. Use x to enter the expert menu.


  3. Use z to zap the GPT.


  4. Use w to write the partition table and exit.



The msdos partition table (aka MBR) will be the only partition table remaining.






share|improve this answer

























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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%2faskubuntu.com%2fquestions%2f763911%2f16-04-live-vs-gparted%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














    You might try removing the broken GPT with the following steps.





    1. From a terminal window run:



      sudo gdisk /path-to-usb-drive


      Where /path-to-usb-drive is something like /dev/sdc.



    2. Use x to enter the expert menu.


    3. Use z to zap the GPT.


    4. Use w to write the partition table and exit.



    The msdos partition table (aka MBR) will be the only partition table remaining.






    share|improve this answer






























      0














      You might try removing the broken GPT with the following steps.





      1. From a terminal window run:



        sudo gdisk /path-to-usb-drive


        Where /path-to-usb-drive is something like /dev/sdc.



      2. Use x to enter the expert menu.


      3. Use z to zap the GPT.


      4. Use w to write the partition table and exit.



      The msdos partition table (aka MBR) will be the only partition table remaining.






      share|improve this answer




























        0












        0








        0







        You might try removing the broken GPT with the following steps.





        1. From a terminal window run:



          sudo gdisk /path-to-usb-drive


          Where /path-to-usb-drive is something like /dev/sdc.



        2. Use x to enter the expert menu.


        3. Use z to zap the GPT.


        4. Use w to write the partition table and exit.



        The msdos partition table (aka MBR) will be the only partition table remaining.






        share|improve this answer















        You might try removing the broken GPT with the following steps.





        1. From a terminal window run:



          sudo gdisk /path-to-usb-drive


          Where /path-to-usb-drive is something like /dev/sdc.



        2. Use x to enter the expert menu.


        3. Use z to zap the GPT.


        4. Use w to write the partition table and exit.



        The msdos partition table (aka MBR) will be the only partition table remaining.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited May 26 '16 at 17:45

























        answered May 26 '16 at 17:31









        Curtis GedakCurtis Gedak

        88654




        88654






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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%2faskubuntu.com%2fquestions%2f763911%2f16-04-live-vs-gparted%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

            How to make a Squid Proxy server?

            Is this a new Fibonacci Identity?

            Touch on Surface Book