[SOLVED] GParted seems to confuse the Disks tool ???

Questions about applications and software
Forum rules
Before you post please read how to get help
Post Reply
sanmig
Level 3
Level 3
Posts: 139
Joined: Tue Dec 04, 2018 8:27 am

[SOLVED] GParted seems to confuse the Disks tool ???

Post by sanmig »

Caution, n00b here!

On my system I see a strange malfunction of the graphical "Disks" tool.
Or is it GParted?

With Mint19, the Accessories - Disks tool displays all details of both of my drives, including secondary partition and the free space of sda.
Good.

But after staring GParted (in live system or installed afterwards) the Disks tool shows wrong information: Unknown partition and wrong free space.
Even after closing GParted, Disks tool will not work properly until a reboot.

Virgin Disks tool:
Image

Disks tool with GParted:
Image

The tainted Disks tool will remain until reboot.
It seems GParted doesn't vanish completely when closing it?

Is this a known issue or how to find out the reason on my system (don't want to try to re-install because it's the same with my USB live system and I'd like to know the cause of the confusion)?
Last edited by sanmig on Tue Feb 05, 2019 7:01 pm, edited 1 time in total.

User avatar
Pierre
Level 19
Level 19
Posts: 9858
Joined: Fri Sep 05, 2008 5:33 am
Location: Perth, AU.

Re: GParted seems to confuse the Disks tool ???

Post by Pierre »

it is known that Gparted does display a different disk size, to what is displayed by the Disks tool.

can you redo those two images ? as that have not displayed correctly.
Image
Please edit your original post title to include [SOLVED] - when your problem is solved!
and DO LOOK at those Unanswered Topics - - you may be able to answer some!.

rbmorse
Level 3
Level 3
Posts: 186
Joined: Mon Mar 07, 2011 11:56 pm
Location: Albuquerque, New Mexico USA

Re: GParted seems to confuse the Disks tool ???

Post by rbmorse »

The size disparity between the two is because gParted expresses in terms of GiB (gigabyte = 1024 mb) and the disk utility uses GB (gigabyte = 1000 mb).

I have no idea why the disk utility goes wacky after running gParted. The problem does not manifest on my system.
Hope is not a plan

gm10
Level 20
Level 20
Posts: 11000
Joined: Thu Jun 21, 2018 5:11 pm

Re: GParted seems to confuse the Disks tool ???

Post by gm10 »

I had linked you to https://github.com/storaged-project/udisks/issues/425 in your other thread as the likely cause for what you are seeing.

sanmig
Level 3
Level 3
Posts: 139
Joined: Tue Dec 04, 2018 8:27 am

Re: GParted seems to confuse the Disks tool ???

Post by sanmig »

Pierre wrote:
Thu Dec 20, 2018 3:02 am
can you redo those two images ?
Unfortunately I don't know why they don't show up, but clicking the "?" will take you to the linked image.
rbmorse wrote:
Thu Dec 20, 2018 10:46 am
The size disparity between the two is because ...
Nah, I'd not mind some MBs, the difference is about 216 GB!
It's completely wrong, and worse, it does not show any clue of an underlying error to the unexperienced eye (partition 2 is an extended partition, but it is shown as primary, that's the only hint).
I don't want to try to change anything on that drive using Disks, it must fail badly.
gm10 wrote:
Thu Dec 20, 2018 11:07 am
I had linked you to ...
Thanks, but, as I said, I don't understand what they are talking about - let alone if there is a solution in the pipeline?
The only point I may grasp is that the problem goes together with an extended partition, which I have on sda, but that's very common, isn't it?
Many will have that.

Re your "likely the cause":
As @rbmorse does not have that issue, where could be seen that GParted changes some "properties" in the system which will remain changed when GParted is closed?
Could I change these "properties" without GParted, to see if that would confuse Disks?
Or is that too much an effort for a known problem?

As I wrote in the other thread, the Disks tool is showing wrong information, but is it only GParted to trigger that?
What if there are other causes?

gm10
Level 20
Level 20
Posts: 11000
Joined: Thu Jun 21, 2018 5:11 pm

Re: GParted seems to confuse the Disks tool ???

Post by gm10 »

I'm sorry I'm no expert on this issue, that bug report I linked just seems to match your error description exactly. There's a reproducer that doesn't require GParted in there.

That's about all I can tell you. The issue is limited to extended partitions and I don't have any setup that uses one so I'm not affected.

sanmig
Level 3
Level 3
Posts: 139
Joined: Tue Dec 04, 2018 8:27 am

Re: GParted seems to confuse the Disks tool ???

Post by sanmig »

gm10 wrote:
Thu Dec 20, 2018 8:01 pm
... That's about all I can tell you. The issue is limited to extended partitions and I don't have any setup that uses one so I'm not affected.
Thanks anyway, so at the moment there is a small trace of a probable error, and a very strong indicator not to trust the Disks tool.

Do you know of a bug report re Disks tool?

gm10
Level 20
Level 20
Posts: 11000
Joined: Thu Jun 21, 2018 5:11 pm

Re: GParted seems to confuse the Disks tool ???

Post by gm10 »

sanmig wrote:
Thu Dec 20, 2018 8:15 pm
Do you know of a bug report re Disks tool?
Yes, the one I linked, with further links to another bug report on Ubuntu's launchpad.net.

rickNS
Level 5
Level 5
Posts: 693
Joined: Tue Jan 25, 2011 11:59 pm

Re: GParted seems to confuse the Disks tool ???

Post by rickNS »

Thanks for this post. I had noticed myself that "sometimes" that the disks tool, did not display my extended partition properly, said 0.0 KB, and alloted that space some 70 GB to the free space. I wasn't too concerned as it "normally" did report correctly.

So the error occurs after gparted has been launched, and lasts till next reboot, correct ?
Attachments
xshot-03.jpg
Mint 19.0 mate on 2 identical Thinkpad T420's

sanmig
Level 3
Level 3
Posts: 139
Joined: Tue Dec 04, 2018 8:27 am

Re: GParted seems to confuse the Disks tool ???

Post by sanmig »

rickNS wrote:
Sat Dec 22, 2018 10:04 am
So the error occurs after gparted has been launched, and lasts till next reboot, correct ?
Yes, you can watch data corruption in Disks when you start GParted, it will not recover after closing GParted.
But other events may trigger the issue, too (?).

sanmig
Level 3
Level 3
Posts: 139
Joined: Tue Dec 04, 2018 8:27 am

Re: GParted seems to confuse the Disks tool ???

Post by sanmig »

gm10 wrote:
Thu Dec 20, 2018 8:29 pm
Yes, the one I linked, with further links to another bug report on Ubuntu's launchpad.net.
I've searched a little bit, way over my head :(

OK, after some reading I understand Disks is "only" a GUI for Udisks. Further reading brought up udisksctl dump to probably "see" what Udisks "knows" of the drives.
Now I wanted to compare the dump before and after using GParted.

But: I'm a n00b.
Open a terminal. That's what I know from DOS times back then, no prob.
Type the command udsksctl dump.
The output is expected to be quite long.
The window has a scroll bar to the right - but no pointer?
Scrolling by scrollwheel works, but still no pointer.
Ctrl+a doesn't mark all,
marking by mouse doesn't scroll.

But Menu Edit has Select All - good,
but it selects only the visible part as I see when pasting into xed :x

Back at the terminal I'm going to read the Help pages - great, there is "Save Terminal output to a file", exactly what I want:
1. Go to File - OK,
2. Select Save Contents ... ?
But that command is not there. New Tab/Window and Close Tab/Window, that's all :evil:
Is this the standard terminal for Linux?
I don't like it.
DOS was yesterday, today we have WinWin!

- Yes, there is a difference in the extended partition sda2 after using GParted (e.g. the partition size is 0). Obviously the graphical tool can not display the correct partition info.

- Does it mean GParted is at fault?

Just to start / close GParted will change permanently data in the system?
- Which data will be changed?
- Why can Nemo still mount and access data there?

sanmig
Level 3
Level 3
Posts: 139
Joined: Tue Dec 04, 2018 8:27 am

Re: GParted seems to confuse the Disks tool ???

Post by sanmig »

As "Disks" is just a GUI of Udisks, if Udisks's data is wrong so Disks must be wrong.

GParted is a GUI for Parted (v3.2),
but running

Code: Select all

parted /dev/sda print unit s print unit chs print
e.g. does not trigger wrong data in Udisks / Disks.
It's only GParted that persistently changes "something" in the system.

I also don't understand why one has to authenticate when opening GParted, this seems to be dangerous, and it is not needed just to see partitions. Disks doesn't need it, too.

So GParted seems to persistently write to the system if opened / closed, until next reboot, this is unacceptable (esp. if it's an old problem).
I've added an issue at
https://gitlab.gnome.org/GNOME/gparted/issues/33

sanmig
Level 3
Level 3
Posts: 139
Joined: Tue Dec 04, 2018 8:27 am

Re: GParted seems to confuse the Disks tool ???

Post by sanmig »

gm10 wrote:
Thu Dec 20, 2018 8:29 pm
sanmig wrote:
Thu Dec 20, 2018 8:15 pm
Do you know of a bug report re Disks tool?
Yes, the one I linked, with further links to another bug report on Ubuntu's launchpad.net.
There seems to be another bug report and solution (again, I don't know what they are talking about):

My GParted issue 33 got a reply by Curtis Gedak:
Note that I have been unable to reproduce this issue in either Ubuntu 18.04 or Ubuntu 18.10 running in VMs.
(EDIT:) From more research it appears there was a problem in udisks that was fixed with
https://github.com/storaged-project/udisks/pull/571. The patch was merged into the master branch on Sep. 24, 2018.
Perhaps this patch has not made it into your distro yet? (my emphasis)
***Could you please answer the question from @gedakc, or do you know whom to ask?***

How is that related to opening a program? Just asking because I'm curious how that would justify to write persistently to the system?

gm10
Level 20
Level 20
Posts: 11000
Joined: Thu Jun 21, 2018 5:11 pm

Re: GParted seems to confuse the Disks tool ???

Post by gm10 »

sanmig wrote:
Fri Jan 25, 2019 6:33 pm
My GParted issue 33 got a reply by Curtis Gedak:
Note that I have been unable to reproduce this issue in either Ubuntu 18.04 or Ubuntu 18.10 running in VMs.
(EDIT:) From more research it appears there was a problem in udisks that was fixed with
https://github.com/storaged-project/udisks/pull/571. The patch was merged into the master branch on Sep. 24, 2018.
Perhaps this patch has not made it into your distro yet? (my emphasis)
***Could you please answer the question from @gedakc, or do you know whom to ask?***
The udisks patch will be included in upcoming Ubuntu 19.04, but it has not been released for Ubuntu 18.04 or 18.10 (and thus not for Mint 19.x). I don't know why he cannot reproduce it in a VM, maybe it does not affect VMs. Either way, it's an udisks issue, it's not for gparted to fix. If anything, create an issue with Ubuntu requesting to implement the fix for 18.04 (or rather, bump the existing bug report on launchpad.net that I already mentioned).

sanmig
Level 3
Level 3
Posts: 139
Joined: Tue Dec 04, 2018 8:27 am

Re: GParted seems to confuse the Disks tool ???

Post by sanmig »

Thanks, I'll quote your answer for @gedakc.
I'll try to bump that as you recommended earlier, only my problem is that I don't understand and it's hard for me to do something I don't understand.
But OK, my personal problem :(

gm10
Level 20
Level 20
Posts: 11000
Joined: Thu Jun 21, 2018 5:11 pm

Re: GParted seems to confuse the Disks tool ???

Post by gm10 »

Well, it's a high importance flagged bug report older than 2 years. Maybe they'll be happy to hear it's fixed upstream in udisks v2.81+ / commit https://github.com/storaged-project/udi ... f35d4b94b7 or maybe the won't care. ¯\_(ツ)_/¯

sanmig
Level 3
Level 3
Posts: 139
Joined: Tue Dec 04, 2018 8:27 am

Re: GParted seems to confuse the Disks tool ???

Post by sanmig »

gm10 wrote:
Fri Jan 25, 2019 6:52 pm
... (or rather, bump the existing bug report on launchpad.net that I already mentioned).
There I got also a reply directing me "upstream".
Seems to be part of the "Who moves first?" jackstraws game 8)

But sorry, I'm not going github, Mi$o sucks.
Thanks anyway.

PS: Instead I'll now have a look at the (GRUB2) os-prober issue!

gm10
Level 20
Level 20
Posts: 11000
Joined: Thu Jun 21, 2018 5:11 pm

Re: GParted seems to confuse the Disks tool ???

Post by gm10 »

sanmig wrote:
Tue Jan 29, 2019 7:54 pm
gm10 wrote:
Fri Jan 25, 2019 6:52 pm
... (or rather, bump the existing bug report on launchpad.net that I already mentioned).
There I got also a reply directing me "upstream".
Seems to be part of the "Who moves first?" jackstraws game 8)

But sorry, I'm not going github, Mi$o sucks.
Thanks anyway.
Haha, classic. Pretty sure with upstream he meant Debian, not github. Ubuntu gets most of their stuff from Debian.

Also interesting, apparently it's not fixed in Ubuntu 19.04 according to one guy in that bug report. I guess the fix didn't work after all. I don't know. ;)

sanmig
Level 3
Level 3
Posts: 139
Joined: Tue Dec 04, 2018 8:27 am

Re: GParted seems to confuse the Disks tool ???

Post by sanmig »

gm10 wrote:
Tue Jan 29, 2019 8:09 pm
... with upstream he meant Debian, not github.
OK, but where is "Debian"?
On their https://www.debian.org/Bugs/ page, at "Searching bug reports", the link to the HyperEstraier search engine seems broken:
https://bugs.debian.org/cgi-bin/search.cgi
Oh man.

- I'd guess it's not fixed as they are talking about some "events" (change, add, ...#570, #571) but that's not needed to trigger the issue.

sanmig
Level 3
Level 3
Posts: 139
Joined: Tue Dec 04, 2018 8:27 am

Re: GParted seems to confuse the Disks tool ???

Post by sanmig »

When I was back at my PCLOS (tinkering with GRUB) I decided to try the Disks / GParted issue there.

PCLOS doesn't have Disks installed but as the problem was already visible in udisksctl dump I've compared that before and after GParted:
In PCLOS the extended partition sda2 didn't change a bit. Size, type and UUID are still correctly reported after using GParted:

Code: Select all

PCLOS dump before opening GParted,
sda2 (extended) partition still has valid data:

###/org/freedesktop/UDisks2/Manager:
###  org.freedesktop.UDisks2.Manager:
###    Version:            2.1.6
...

/org/freedesktop/UDisks2/block_devices/sda2:
  org.freedesktop.UDisks2.Block:
    Configuration:              []
    CryptoBackingDevice:        '/'
    Device:                     /dev/sda2
    DeviceNumber:               2050
    Drive:                      '/org/freedesktop/UDisks2/drives/Samsung_SSD_850_EVO_500GB_S21JNXAG697664V'
    HintAuto:                   false
    HintIconName:               
    HintIgnore:                 false
    HintName:                   
    HintPartitionable:          true
    HintSymbolicIconName:       
    HintSystem:                 true
    Id:                         by-id-ata-Samsung_SSD_850_EVO_500GB_S21JNXAG697664V-part2
    IdLabel:                    
    IdType:                     
    IdUUID:                     
    IdUsage:                    
    IdVersion:                  
    MDRaid:                     '/'
    MDRaidMember:               '/'
    PreferredDevice:            /dev/sda2
    ReadOnly:                   false
    Size:                       1024
    Symlinks:                   /dev/block/8:2
                                /dev/disk/by-id/ata-Samsung_SSD_850_EVO_500GB_S21JNXAG697664V-part2
                                /dev/disk/by-id/scsi-SATA_Samsung_SSD_850S21JNXAG697664V-part2
                                /dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part2
                                /dev/disk/by-id/wwn-0x5002538d4027c57d-part2
  org.freedesktop.UDisks2.Partition:
    Flags:              0
    IsContained:        false
    IsContainer:        true
    Name:               
    Number:             2
    Offset:             167104216064
    Size:               216003511296
    Table:              '/org/freedesktop/UDisks2/block_devices/sda'
    Type:               0x05
    UUID:               12240f8d-02

Code: Select all

PCLOS dump after closing GParted 0.32.0 (no action):

/org/freedesktop/UDisks2/block_devices/sda2:
  org.freedesktop.UDisks2.Block:
    Configuration:              []
    CryptoBackingDevice:        '/'
    Device:                     /dev/sda2
    DeviceNumber:               2050
    Drive:                      '/org/freedesktop/UDisks2/drives/Samsung_SSD_850_EVO_500GB_S21JNXAG697664V'
    HintAuto:                   false
    HintIconName:               
    HintIgnore:                 false
    HintName:                   
    HintPartitionable:          true
    HintSymbolicIconName:       
    HintSystem:                 true
    Id:                         by-id-ata-Samsung_SSD_850_EVO_500GB_S21JNXAG697664V-part2
    IdLabel:                    
    IdType:                     
    IdUUID:                     
    IdUsage:                    
    IdVersion:                  
    MDRaid:                     '/'
    MDRaidMember:               '/'
    PreferredDevice:            /dev/sda2
    ReadOnly:                   false
    Size:                       1024
    Symlinks:                   /dev/block/8:2
                                /dev/disk/by-id/ata-Samsung_SSD_850_EVO_500GB_S21JNXAG697664V-part2
                                /dev/disk/by-id/scsi-SATA_Samsung_SSD_850S21JNXAG697664V-part2
                                /dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part2
                                /dev/disk/by-id/wwn-0x5002538d4027c57d-part2
  org.freedesktop.UDisks2.Partition:
    Flags:              0
    IsContained:        false
    IsContainer:        true
    Name:               
    Number:             2
    Offset:             167104216064
    Size:               216003511296
    Table:              '/org/freedesktop/UDisks2/block_devices/sda'
    Type:               0x05
    UUID:               12240f8d-02

BUT:
a)
The udisks2.Manager reports different versions in udisksctl:
PCLOS has 2.1.6, the Mint version is 2.7.6.

GParted: Both have 0.32.0, only in Mint the start takes several seconds more (spinning wheel) when the interface is already displayed, PCLOS is extremely fast (<0.5") after authentication.

b)
Comparing the sda2 section in udisksctl dump, there is a difference in the Symlinks.
Generally in PCLOS there are 5 lines reported, but in Mint we have 4 before and only 3 after starting GParted: The line "/dev/disk/by-partuuid/12240f8d-02" is lost.

PCLOS doesn't have this line, but has ...by-id/scsi-... instead, and additionally the line /dev/block/8:2.

However:
This test seems to prove the problem is not simply in GParted,
- so my nose was wrong once again :evil:

As the fix may take years (if ever) I think I'll file that under "nice collection of deep system bugs".

-> Edit: xxxxx I set this thread to solved anyway.
-> GParted is not the cause, it's only the trigger of a deeper issue.

Post Reply

Return to “Software & Applications”