sigh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059907
Title:
missing option to erase and use the whole drive
To manage notifications about this bug go to:
Since I've observed a successful install with a cleanly closed Calamares
leave the target partition mounted, I'm concerned there's a fundamental
bug in the umount module. I've also seen some suggestion upstream
(haven't checked the code to be fair) that unmounting is supposed to
happen before
Before starting Calamares I unmounted it (of course), and there was no
swap partition (only zram).
There was a live Lubuntu system on the target drive, and obviously this
was recognized by Calamares.
The running live system was booted from another drive, but Calamares
either 'assumed' that
Was it mounted?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059907
Title:
missing option to erase and use the whole drive
To manage notifications about this bug go to:
Well, today I found a case, where unmounting and swapping off does not
help. I had to wipe the first mibibyte.
In my Toshiba Satellite Pro c850-19w I connected a target SSD with a
current daily live Lubuntu system, and it was not identified as a target
device (until I wiped the partition table).
** Changed in: calamares (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059907
Title:
missing option to erase and use the whole drive
To manage
@ԜаӀtеr Ⅼарсһуnѕkі (wxl),
Yes, unmount what can be unmounted (unless when using the boot option
'toram', I think some partition(s) on the live drive should be left
mounted (not be forced to be unmounted)). And swapoff everything except
the zram.
I think that would squash this bug.
--
You
You're right that the automounting of the partition is irrelevant if
we're just going to go ahead an umount whatever, but it's still
perplexing not to know *why*.
Anyways, another good point about keeping zram on. We do have that for a
reason. Thus, the recommendation of `swapoff -a` is not a
Why struggle to understand why the partition on the target drive is
mounted? Maybe because the target SSD is connected via USB (and not via
SATA). During these tests there is no internal drive in my Toshiba, only
two SSDs, the live drive and the target drive.
In the case of these tests with my
That's weird to see the partition mounted. I struggle to understand why.
Try again, but this time don't worry about that and `swapoff`. It
certainly is known that swaps are automounted (this has something to do
with the core Ubuntu setup). It is also known that, at least when they
are related to
1. Fresh boot into iso in (UEFI mode).
2. The partition on the target drive is mounted automatically. I unmount
it now. This should be done automatically by Calamares.
3. I leave the zram swap on (I don't think it must be swapped off; I
want to check that.)
4. Fix for 2054795 and start the
I did nothing other than boot and run the installer.
If you can reproduce the behavior again, I would then do this:
1. A fresh boot into the ISO
2. Check to see if your drive is mounted (it shouldn't be under any
conditions) - `umount` if so and double check
3. Check to see if your swap is
I can try in another computer (not the Toshiba). But the zram swap
should not be linked to any SSD or HDD; it resides in RAM.
When trying to reproduce, did you manually unmount all partitions on the
target drive before starting Calamares?
I don't think that beginners will do that.
But when I
Well, that's weird. I did two installation tests and couldn't reproduce
*that* behavior:
1. With pre-existing BIOS install, fresh boot in UEFI mode
2. With pre-existing UEFI install, fresh boot in BIOS mode
In both cases, I got the erase disk option.
That said, I wonder if your issue isn't
No, I shut down the computer after installing in BIOS mode, cold boot
into the installed system, shut down again, boot in UEFI mode into the
Lubuntu Noble live. The problem is *not* caused by running the installer
twice in one session.
But I agree, that it would be a good idea to run the umount
To be clear, as I understand it, this is the situation caused by running
the installer twice in one session. The problem is caused because the
drive is still mounted at /tmp. This occurs regardless of whether or
not Calamares is interrupted in the middle of installation or if it is
allowed to
** Changed in: calamares (Ubuntu)
Status: New => Confirmed
** Changed in: calamares (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059907
Title:
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2059907
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
See also this link
https://discourse.lubuntu.me/t/report-about-iso-testing-and-two-
questions-about-reporting-or-not-reporting-bugs/4793
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059907
Title:
19 matches
Mail list logo
