So calamares and gparted disagree with regards to the size and distribution of partitions.
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. |
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 |
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:
|
Quote:
|
Quote:
|
Quote:
The relevant issue tracker for Parrot's Calamares changes seems to be https://nest.parrotsec.org/packages/...arrot/-/issues |
Quote:
|
Still no news, my post has shown up now!, no activity on bug report. Gah.
|
All times are GMT -5. The time now is 05:18 PM. |