Unable to Start GParted












2















I've been doing some work with various USB drives and have been using Gparted to do so. However, for no apparent reason, gparted no longer starts.



If I open the graphical application, I authenticate with my password and then nothing happens.



If I run sudo gparted. I get:




mount: wrong fs type, bad option, bad superblock on /run/udisks2/inhibit-polkit, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so




When I run dmesg I get:



[ 1225.545050] usb 2-1: new high-speed USB device number 23 using xhci_hcd
[ 1225.568016] usb 2-1: New USB device found, idVendor=0781, idProduct=5583
[ 1225.568027] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1225.568033] usb 2-1: Product: Ultra Fit
[ 1225.568038] usb 2-1: Manufacturer: SanDisk
[ 1225.568042] usb 2-1: SerialNumber: 4C531001390502102383
[ 1225.570640] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 1225.572092] scsi8 : usb-storage 2-1:1.0
[ 1226.571712] scsi 8:0:0:0: Direct-Access SanDisk Ultra Fit 1.00 PQ: 0 ANSI: 6
[ 1226.572353] sd 8:0:0:0: Attached scsi generic sg1 type 0
[ 1226.574166] sd 8:0:0:0: [sdb] 242614272 512-byte logical blocks: (124 GB/115 GiB)
[ 1226.577102] sd 8:0:0:0: [sdb] Write Protect is off
[ 1226.577115] sd 8:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 1226.578691] sd 8:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 1226.596148] sdb: sdb1
[ 1226.600044] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[ 1226.886103] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 1237.359985] sdb: detected capacity change from 124218507264 to 0
[ 1251.998948] usb 2-1: USB disconnect, device number 23


I left out the top part because it doesn't contain much, or so I think. What I find curious is that the SanDisk Ultrafit listed here is not actually inserted into any usb drive and hasn't been for a few hours. This was one of the drives I was formatting.



Why is it still showing up here and does this have something to do with this? Should I somehow explicitly unmount it? I've read where Gparted does this in some instances where some part of the file system of a drive is not understood.



How should I proceed to be able to run gparted again?



Thanks!










share|improve this question

























  • You should use gksudo.

    – jasonwryan
    Oct 22 '17 at 21:35











  • Using gksudo offers the same issue.

    – chronic788
    Oct 22 '17 at 22:45
















2















I've been doing some work with various USB drives and have been using Gparted to do so. However, for no apparent reason, gparted no longer starts.



If I open the graphical application, I authenticate with my password and then nothing happens.



If I run sudo gparted. I get:




mount: wrong fs type, bad option, bad superblock on /run/udisks2/inhibit-polkit, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so




When I run dmesg I get:



[ 1225.545050] usb 2-1: new high-speed USB device number 23 using xhci_hcd
[ 1225.568016] usb 2-1: New USB device found, idVendor=0781, idProduct=5583
[ 1225.568027] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1225.568033] usb 2-1: Product: Ultra Fit
[ 1225.568038] usb 2-1: Manufacturer: SanDisk
[ 1225.568042] usb 2-1: SerialNumber: 4C531001390502102383
[ 1225.570640] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 1225.572092] scsi8 : usb-storage 2-1:1.0
[ 1226.571712] scsi 8:0:0:0: Direct-Access SanDisk Ultra Fit 1.00 PQ: 0 ANSI: 6
[ 1226.572353] sd 8:0:0:0: Attached scsi generic sg1 type 0
[ 1226.574166] sd 8:0:0:0: [sdb] 242614272 512-byte logical blocks: (124 GB/115 GiB)
[ 1226.577102] sd 8:0:0:0: [sdb] Write Protect is off
[ 1226.577115] sd 8:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 1226.578691] sd 8:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 1226.596148] sdb: sdb1
[ 1226.600044] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[ 1226.886103] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 1237.359985] sdb: detected capacity change from 124218507264 to 0
[ 1251.998948] usb 2-1: USB disconnect, device number 23


I left out the top part because it doesn't contain much, or so I think. What I find curious is that the SanDisk Ultrafit listed here is not actually inserted into any usb drive and hasn't been for a few hours. This was one of the drives I was formatting.



Why is it still showing up here and does this have something to do with this? Should I somehow explicitly unmount it? I've read where Gparted does this in some instances where some part of the file system of a drive is not understood.



How should I proceed to be able to run gparted again?



Thanks!










share|improve this question

























  • You should use gksudo.

    – jasonwryan
    Oct 22 '17 at 21:35











  • Using gksudo offers the same issue.

    – chronic788
    Oct 22 '17 at 22:45














2












2








2








I've been doing some work with various USB drives and have been using Gparted to do so. However, for no apparent reason, gparted no longer starts.



If I open the graphical application, I authenticate with my password and then nothing happens.



If I run sudo gparted. I get:




mount: wrong fs type, bad option, bad superblock on /run/udisks2/inhibit-polkit, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so




When I run dmesg I get:



[ 1225.545050] usb 2-1: new high-speed USB device number 23 using xhci_hcd
[ 1225.568016] usb 2-1: New USB device found, idVendor=0781, idProduct=5583
[ 1225.568027] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1225.568033] usb 2-1: Product: Ultra Fit
[ 1225.568038] usb 2-1: Manufacturer: SanDisk
[ 1225.568042] usb 2-1: SerialNumber: 4C531001390502102383
[ 1225.570640] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 1225.572092] scsi8 : usb-storage 2-1:1.0
[ 1226.571712] scsi 8:0:0:0: Direct-Access SanDisk Ultra Fit 1.00 PQ: 0 ANSI: 6
[ 1226.572353] sd 8:0:0:0: Attached scsi generic sg1 type 0
[ 1226.574166] sd 8:0:0:0: [sdb] 242614272 512-byte logical blocks: (124 GB/115 GiB)
[ 1226.577102] sd 8:0:0:0: [sdb] Write Protect is off
[ 1226.577115] sd 8:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 1226.578691] sd 8:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 1226.596148] sdb: sdb1
[ 1226.600044] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[ 1226.886103] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 1237.359985] sdb: detected capacity change from 124218507264 to 0
[ 1251.998948] usb 2-1: USB disconnect, device number 23


I left out the top part because it doesn't contain much, or so I think. What I find curious is that the SanDisk Ultrafit listed here is not actually inserted into any usb drive and hasn't been for a few hours. This was one of the drives I was formatting.



Why is it still showing up here and does this have something to do with this? Should I somehow explicitly unmount it? I've read where Gparted does this in some instances where some part of the file system of a drive is not understood.



How should I proceed to be able to run gparted again?



Thanks!










share|improve this question
















I've been doing some work with various USB drives and have been using Gparted to do so. However, for no apparent reason, gparted no longer starts.



If I open the graphical application, I authenticate with my password and then nothing happens.



If I run sudo gparted. I get:




mount: wrong fs type, bad option, bad superblock on /run/udisks2/inhibit-polkit, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so




When I run dmesg I get:



[ 1225.545050] usb 2-1: new high-speed USB device number 23 using xhci_hcd
[ 1225.568016] usb 2-1: New USB device found, idVendor=0781, idProduct=5583
[ 1225.568027] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1225.568033] usb 2-1: Product: Ultra Fit
[ 1225.568038] usb 2-1: Manufacturer: SanDisk
[ 1225.568042] usb 2-1: SerialNumber: 4C531001390502102383
[ 1225.570640] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 1225.572092] scsi8 : usb-storage 2-1:1.0
[ 1226.571712] scsi 8:0:0:0: Direct-Access SanDisk Ultra Fit 1.00 PQ: 0 ANSI: 6
[ 1226.572353] sd 8:0:0:0: Attached scsi generic sg1 type 0
[ 1226.574166] sd 8:0:0:0: [sdb] 242614272 512-byte logical blocks: (124 GB/115 GiB)
[ 1226.577102] sd 8:0:0:0: [sdb] Write Protect is off
[ 1226.577115] sd 8:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 1226.578691] sd 8:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 1226.596148] sdb: sdb1
[ 1226.600044] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[ 1226.886103] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 1237.359985] sdb: detected capacity change from 124218507264 to 0
[ 1251.998948] usb 2-1: USB disconnect, device number 23


I left out the top part because it doesn't contain much, or so I think. What I find curious is that the SanDisk Ultrafit listed here is not actually inserted into any usb drive and hasn't been for a few hours. This was one of the drives I was formatting.



Why is it still showing up here and does this have something to do with this? Should I somehow explicitly unmount it? I've read where Gparted does this in some instances where some part of the file system of a drive is not understood.



How should I proceed to be able to run gparted again?



Thanks!







filesystems usb-drive gparted






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 22 '17 at 22:47









agc

4,57811036




4,57811036










asked Oct 22 '17 at 21:23









chronic788chronic788

111




111













  • You should use gksudo.

    – jasonwryan
    Oct 22 '17 at 21:35











  • Using gksudo offers the same issue.

    – chronic788
    Oct 22 '17 at 22:45



















  • You should use gksudo.

    – jasonwryan
    Oct 22 '17 at 21:35











  • Using gksudo offers the same issue.

    – chronic788
    Oct 22 '17 at 22:45

















You should use gksudo.

– jasonwryan
Oct 22 '17 at 21:35





You should use gksudo.

– jasonwryan
Oct 22 '17 at 21:35













Using gksudo offers the same issue.

– chronic788
Oct 22 '17 at 22:45





Using gksudo offers the same issue.

– chronic788
Oct 22 '17 at 22:45










2 Answers
2






active

oldest

votes


















2














To troubleshoot, carefully run gparted on a disk known to be working, for example gparted /dev/sda -- just to see if the GUI starts correctly. If that works, close gparted without changing anything.



If the problem is the gparted software, reboot from your favorite Linux bootCD, (or live USB), one that does have a working gparted, and test any questionable drives from there.



But if gparted started correctly on /dev/sda, then the fault is in the USB drive(s). Then, maybe:




  1. the USB drive's partition table is corrupt. If the data is important, back it up with gddrescue, then see if gpart can guess where the partitions should be, and proceed accordingly.


  2. the table is in some newer format that gparted doesn't know about,


  3. there might be no partition table at all, the whole disk might be one file system. In which case try mounting it. The dmesg output seems to suggest that it is mounted.






share|improve this answer


























  • Thanks for your post! I just tried to run gparted on a usb drive that I know works using gparted /dev/sdX but get the same error message. I am concerned because even if no USB drives are inserted I can't start the gparted GUI in any way. Any other thoughts?

    – chronic788
    Oct 22 '17 at 23:14





















0














If U are using VMWorkstation:
I once used Gparted to enlarge my /dev/sda1(Ubuntu 14.04 64),here is what I have done:



1.I download Gparted iso source(SOURCEFORGE)



2.Go to Settings,find CD/DVD(SATA),click on using ISO file and add the iso which U just downloaded;



3.Start the system and KEEP CLICKING F2(check it,mybe different,this one is difficult,U have to do this fast),or click on the green arrow,choose the POWER ON TO BIOS(Recommend);



4.Choose BOOT,and move the CD-ROM drive to the first one,press F10 save and exit;



5.Now wait for a second and U are in Gparted live.(Be careful changing memory:))






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    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: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2funix.stackexchange.com%2fquestions%2f399784%2funable-to-start-gparted%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2














    To troubleshoot, carefully run gparted on a disk known to be working, for example gparted /dev/sda -- just to see if the GUI starts correctly. If that works, close gparted without changing anything.



    If the problem is the gparted software, reboot from your favorite Linux bootCD, (or live USB), one that does have a working gparted, and test any questionable drives from there.



    But if gparted started correctly on /dev/sda, then the fault is in the USB drive(s). Then, maybe:




    1. the USB drive's partition table is corrupt. If the data is important, back it up with gddrescue, then see if gpart can guess where the partitions should be, and proceed accordingly.


    2. the table is in some newer format that gparted doesn't know about,


    3. there might be no partition table at all, the whole disk might be one file system. In which case try mounting it. The dmesg output seems to suggest that it is mounted.






    share|improve this answer


























    • Thanks for your post! I just tried to run gparted on a usb drive that I know works using gparted /dev/sdX but get the same error message. I am concerned because even if no USB drives are inserted I can't start the gparted GUI in any way. Any other thoughts?

      – chronic788
      Oct 22 '17 at 23:14


















    2














    To troubleshoot, carefully run gparted on a disk known to be working, for example gparted /dev/sda -- just to see if the GUI starts correctly. If that works, close gparted without changing anything.



    If the problem is the gparted software, reboot from your favorite Linux bootCD, (or live USB), one that does have a working gparted, and test any questionable drives from there.



    But if gparted started correctly on /dev/sda, then the fault is in the USB drive(s). Then, maybe:




    1. the USB drive's partition table is corrupt. If the data is important, back it up with gddrescue, then see if gpart can guess where the partitions should be, and proceed accordingly.


    2. the table is in some newer format that gparted doesn't know about,


    3. there might be no partition table at all, the whole disk might be one file system. In which case try mounting it. The dmesg output seems to suggest that it is mounted.






    share|improve this answer


























    • Thanks for your post! I just tried to run gparted on a usb drive that I know works using gparted /dev/sdX but get the same error message. I am concerned because even if no USB drives are inserted I can't start the gparted GUI in any way. Any other thoughts?

      – chronic788
      Oct 22 '17 at 23:14
















    2












    2








    2







    To troubleshoot, carefully run gparted on a disk known to be working, for example gparted /dev/sda -- just to see if the GUI starts correctly. If that works, close gparted without changing anything.



    If the problem is the gparted software, reboot from your favorite Linux bootCD, (or live USB), one that does have a working gparted, and test any questionable drives from there.



    But if gparted started correctly on /dev/sda, then the fault is in the USB drive(s). Then, maybe:




    1. the USB drive's partition table is corrupt. If the data is important, back it up with gddrescue, then see if gpart can guess where the partitions should be, and proceed accordingly.


    2. the table is in some newer format that gparted doesn't know about,


    3. there might be no partition table at all, the whole disk might be one file system. In which case try mounting it. The dmesg output seems to suggest that it is mounted.






    share|improve this answer















    To troubleshoot, carefully run gparted on a disk known to be working, for example gparted /dev/sda -- just to see if the GUI starts correctly. If that works, close gparted without changing anything.



    If the problem is the gparted software, reboot from your favorite Linux bootCD, (or live USB), one that does have a working gparted, and test any questionable drives from there.



    But if gparted started correctly on /dev/sda, then the fault is in the USB drive(s). Then, maybe:




    1. the USB drive's partition table is corrupt. If the data is important, back it up with gddrescue, then see if gpart can guess where the partitions should be, and proceed accordingly.


    2. the table is in some newer format that gparted doesn't know about,


    3. there might be no partition table at all, the whole disk might be one file system. In which case try mounting it. The dmesg output seems to suggest that it is mounted.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Oct 22 '17 at 23:18

























    answered Oct 22 '17 at 23:05









    agcagc

    4,57811036




    4,57811036













    • Thanks for your post! I just tried to run gparted on a usb drive that I know works using gparted /dev/sdX but get the same error message. I am concerned because even if no USB drives are inserted I can't start the gparted GUI in any way. Any other thoughts?

      – chronic788
      Oct 22 '17 at 23:14





















    • Thanks for your post! I just tried to run gparted on a usb drive that I know works using gparted /dev/sdX but get the same error message. I am concerned because even if no USB drives are inserted I can't start the gparted GUI in any way. Any other thoughts?

      – chronic788
      Oct 22 '17 at 23:14



















    Thanks for your post! I just tried to run gparted on a usb drive that I know works using gparted /dev/sdX but get the same error message. I am concerned because even if no USB drives are inserted I can't start the gparted GUI in any way. Any other thoughts?

    – chronic788
    Oct 22 '17 at 23:14







    Thanks for your post! I just tried to run gparted on a usb drive that I know works using gparted /dev/sdX but get the same error message. I am concerned because even if no USB drives are inserted I can't start the gparted GUI in any way. Any other thoughts?

    – chronic788
    Oct 22 '17 at 23:14















    0














    If U are using VMWorkstation:
    I once used Gparted to enlarge my /dev/sda1(Ubuntu 14.04 64),here is what I have done:



    1.I download Gparted iso source(SOURCEFORGE)



    2.Go to Settings,find CD/DVD(SATA),click on using ISO file and add the iso which U just downloaded;



    3.Start the system and KEEP CLICKING F2(check it,mybe different,this one is difficult,U have to do this fast),or click on the green arrow,choose the POWER ON TO BIOS(Recommend);



    4.Choose BOOT,and move the CD-ROM drive to the first one,press F10 save and exit;



    5.Now wait for a second and U are in Gparted live.(Be careful changing memory:))






    share|improve this answer




























      0














      If U are using VMWorkstation:
      I once used Gparted to enlarge my /dev/sda1(Ubuntu 14.04 64),here is what I have done:



      1.I download Gparted iso source(SOURCEFORGE)



      2.Go to Settings,find CD/DVD(SATA),click on using ISO file and add the iso which U just downloaded;



      3.Start the system and KEEP CLICKING F2(check it,mybe different,this one is difficult,U have to do this fast),or click on the green arrow,choose the POWER ON TO BIOS(Recommend);



      4.Choose BOOT,and move the CD-ROM drive to the first one,press F10 save and exit;



      5.Now wait for a second and U are in Gparted live.(Be careful changing memory:))






      share|improve this answer


























        0












        0








        0







        If U are using VMWorkstation:
        I once used Gparted to enlarge my /dev/sda1(Ubuntu 14.04 64),here is what I have done:



        1.I download Gparted iso source(SOURCEFORGE)



        2.Go to Settings,find CD/DVD(SATA),click on using ISO file and add the iso which U just downloaded;



        3.Start the system and KEEP CLICKING F2(check it,mybe different,this one is difficult,U have to do this fast),or click on the green arrow,choose the POWER ON TO BIOS(Recommend);



        4.Choose BOOT,and move the CD-ROM drive to the first one,press F10 save and exit;



        5.Now wait for a second and U are in Gparted live.(Be careful changing memory:))






        share|improve this answer













        If U are using VMWorkstation:
        I once used Gparted to enlarge my /dev/sda1(Ubuntu 14.04 64),here is what I have done:



        1.I download Gparted iso source(SOURCEFORGE)



        2.Go to Settings,find CD/DVD(SATA),click on using ISO file and add the iso which U just downloaded;



        3.Start the system and KEEP CLICKING F2(check it,mybe different,this one is difficult,U have to do this fast),or click on the green arrow,choose the POWER ON TO BIOS(Recommend);



        4.Choose BOOT,and move the CD-ROM drive to the first one,press F10 save and exit;



        5.Now wait for a second and U are in Gparted live.(Be careful changing memory:))







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 6 at 2:11









        wjrforcyberwjrforcyber

        16




        16






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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%2funix.stackexchange.com%2fquestions%2f399784%2funable-to-start-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

            Morgemoulin

            Scott Moir

            Souastre