On 5/28/19 7:36 PM, stan wrote:
On Tue, 28 May 2019 13:59:07 -0700 Samuel Sieb samuel@sieb.net wrote:
On 5/28/19 1:04 PM, stan wrote:
On Mon, 27 May 2019 22:27:16 -0600 Chris Murphy lists@colorremedies.com wrote:
On Mon, May 27, 2019 at 3:55 PM stan upaitag@zoho.com wrote:
And, if I install as UEFI, for some reason it doesn't accept the existing ext4 partitions on the gpt formatted drive.
What do you mean by it didn't accept them?
The installer gives an error message, and they are still marked as incomplete in the hub.
We would need the error message, but from what you mentioned in the other email, it's likely the lack of an EFI boot partition (ESP).
That's a separate bug report, also needs installer logs attached.
Same question. Where are they saved?
If the installation is nearly complete, they are probably in /var/log/anaconda on the installed system. Otherwise, they are in /tmp while the installer is running. You can switch to a console to see them or copy them off.
Weren't there, guess it didn't get far enough.
If it hasn't even set up the partitions then the logs will definitely not be on the hard drive.
The kernel will mount a partition regardless of what it's labelled as, but the installer might not accept it.
That's interesting. I suppose if it has incorrect data it will crash, and if it has the correct data the partition label doesn't matter.
Unless specifically told what to use, the kernel will auto-detect the filesystem. In any case, it doesn't use the partition type to determine what filesystem to choose.