I have not had this issue in hirsute (or ever before using these steps).
I expect to do a number of installs in coming ~week looking for this issue (1914521) & even 1864787 using the hirsute release.
Replicating this setup is easy (standard QA-test install, then a second "install alongside") taking only time.. This system is old and has spinning-rust drive, thus time.
I've not had this issue before; only 1864787 which I assumed related to a complex partition scheme..
Installs using this exact procedure (and thus partition layout) are done maybe 100 times per cycle as easy to do and most efficient way to test for
- full disk install (any non-encrypted testcase)
- install alongside
at least that's how I do those two testcases...
I have not had this issue in hirsute (or ever before using these steps).
I expect to do a number of installs in coming ~week looking for this issue (1914521) & even 1864787 using the hirsute release.
Replicating this setup is easy (standard QA-test install, then a second "install alongside") taking only time.. This system is old and has spinning-rust drive, thus time.
I've not had this issue before; only 1864787 which I assumed related to a complex partition scheme..
Installs using this exact procedure (and thus partition layout) are done maybe 100 times per cycle as easy to do and most efficient way to test for
- full disk install (any non-encrypted testcase)
- install alongside
at least that's how I do those two testcases...