So calamares and gparted disagree with regards to the size and distribution of partitions.

zack3g · 08-13-2020, 04:34 AM

OK so I'm having a weird issue while trying to install from a live image. I don't know that it matters, but the operating system is Parrot.

See screenshot below, on the left is the (correct, actually) output from gparted. On the right is what calamares sees.

Why?

https://i.imgur.com/whKPQAs.png

You might be able to guess from the gparted side of the image but I'm trying to stick the linux install into that 20gb unallocated spot, leaving the windows partitions etc untouched. This used to be simple, done it many many many times. Never seen this happen before.

What is causing this and how can I fix it? Try as I might I can't get the two to reconcile and agree on anything. I am worried that if I allow calamares to do what it wants it might nuke my whole drive. This would be very, very bad.

beachboy2 · 08-13-2020, 06:54 AM

zack3g,

All the sizes quoted by Calamares for partitions p1 to p4 appear to be incorrect.

I would be more inclined to believe GParted's figures.

Before proceeding further, I suggest that you make an image of your existing drive with Macrium Reflect Free to an external hard drive.

Also create Macrium Rescue Media.

https://www.macrium.com/reflectfree

syg00 · 08-13-2020, 07:08 AM

Not acceptable - open a bug against Parrot. They have almost certainly customised calamares. Maybe they'll push it up-stream given the following from the calamares site

Quote:

Calamares includes an advanced partitioning feature, with support for both manual and automated partitioning operations.

zack3g · 08-13-2020, 07:31 AM

Quote:

Originally Posted by syg00

Not acceptable - open a bug against Parrot. They have almost certainly customised calamares. Maybe they'll push it up-stream given the following from the calamares site

I have a post on their support forum as well though it's still waiting for moderator approval. I can't for the life of me figure out why calamares is so wrong about the partitions.

zack3g · 08-13-2020, 07:35 AM

Quote:

Originally Posted by beachboy2

zack3g,

All the sizes quoted by Calamares for partitions p1 to p4 appear to be incorrect.

I would be more inclined to believe GParted's figures.

Yep, which is why I said that gparted was correct in my initial post. They agree on how big the total drive is, but disagree as to how the partitions are sized and distributed. Very, very strange.

boughtonp · 08-13-2020, 07:44 AM

Quote:

Originally Posted by zack3g

I have a post on their support forum as well though it's still waiting for moderator approval.

And when it gets approved they'll tell you it's a bug and to go raise it was one, so you might as well do that bit now, and maybe it'll get fixed that bit sooner.

The relevant issue tracker for Parrot's Calamares changes seems to be https://nest.parrotsec.org/packages/...arrot/-/issues

zack3g · 08-13-2020, 07:58 AM

Quote:

Originally Posted by boughtonp

And when it gets approved they'll tell you it's a bug and to go raise it was one, so you might as well do that bit now, and maybe it'll get fixed that bit sooner.

The relevant issue tracker for Parrot's Calamares changes seems to be https://nest.parrotsec.org/packages/...arrot/-/issues

Signed up there and threw up a report. It may or may not be calamares related, we will have to see. It might just be some silly glitch elsewhere that calamares is picking up on. Only time will tell I suppose.

zack3g · 08-13-2020, 06:57 PM

Still no news, my post has shown up now!, no activity on bug report. Gah.