Re: F38 install issues

2023-09-10 Thread Matt Morgan
On Thu, Jul 13, 2023 at 2:33 PM Matt Morgan  wrote:

>
> I have a new laptop, set up with Windows, that I'm trying to install F38
> on. I used the media writer to make a USB boot/install drive. It booted
> fine, and I clicked to install to hard drive.
>
> I took about half of the 1TB SSD for Fedora, and told it to continue. Then
> I left for a few minutes. When I came back, the computer had booted to the
> USB drive again (it appeared). I removed the USB drive and rebooted again.
>
> The system booted to Windows with no indication of a grub boot menu. The
> drive was missing the space I'd reclaimed, so clearly that worked, at least
> partly. But nothing I do seems to get it to boot linux or drop me at a grub
> menu.
>
> When I boot off the usb drive, it works, but I don't see any linux-related
> files on the SSD. So basically it looks like the drive got partitioned, at
> least partly, and the install didn't run. So I'm trying to run the install
> again, but no combination of clicks is getting me what I want.
>
> 1) For "Installation Destination," I see "Error checking storage
> configuration." I click on that, and it has the one device for me to
> install to. At the bottom, it says "Error checking storage configuration."
> When I "click for details," I get
>
> ---
> The following erros were encountered when checking your storage
> configuration. You can modify your storage layout or quit the installer.
>
> Failed to find a suitable stage 1 device: EFI System Partition must be
> mounted on one of /boot/efi.; EFI System Partition cannot be of type None.;
> EFI System Partition cannot be of type ntfs.; EFI System Partition must be
> mounted on one of /boot/efi.; EFI System Partition cannot be of type ext4.;
> EFI System Partition must e mounted on one of /boot/efi.; EFI System
> Partition cannot be of type btrfs,; EFI System Partition must e mounted on
> one of /boot/efi.
> 
>
>
etc.

I thought I'd follow up here and add that this computer had a bad
motherboard. I got the computer replaced and the F38 install worked fine on
the new one.

Best,
Matt
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: F38 install issues

2023-07-15 Thread José María Terry Jiménez via users

El 15/7/23 a las 12:02, José María Terry Jiménez via users escribió:


It seems you burned the Fedora Live image in your NVMe 0 Namespace 1 
Partition 5 as seen in


nvme0n1p5  partition ext4    1024MiB fedora_localhost-live

You must burn it to an external USB drive (ej /dev/sdx) and boot for it.

If you reserved half disk (eg 500Gb) but later burn the image in I 
think is normal whats is seen in this partition list.


Hope helps


I mean boot FROM it, where FOR it (typo) sorry
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: F38 install issues

2023-07-15 Thread José María Terry Jiménez via users

El 13/7/23 a las 20:33, Matt Morgan escribió:
Hi. I haven't been here for a long time, which I guess is a testament 
to how well Fedora works these days.


I have a new laptop, set up with Windows, that I'm trying to install 
F38 on. I used the media writer to make a USB boot/install drive. It 
booted fine, and I clicked to install to hard drive.


I took about half of the 1TB SSD for Fedora, and told it to continue. 
Then I left for a few minutes. When I came back, the computer had 
booted to the USB drive again (it appeared). I removed the USB drive 
and rebooted again.


The system booted to Windows with no indication of a grub boot menu. 
The drive was missing the space I'd reclaimed, so clearly that worked, 
at least partly. But nothing I do seems to get it to boot linux or 
drop me at a grub menu.


When I boot off the usb drive, it works, but I don't see any 
linux-related files on the SSD. So basically it looks like the drive 
got partitioned, at least partly, and the install didn't run. So I'm 
trying to run the install again, but no combination of clicks is 
getting me what I want.


1) For "Installation Destination," I see "Error checking storage 
configuration." I click on that, and it has the one device for me to 
install to. At the bottom, it says "Error checking storage 
configuration." When I "click for details," I get


---
The following erros were encountered when checking your storage 
configuration. You can modify your storage layout or quit the installer.


Failed to find a suitable stage 1 device: EFI System Partition must be 
mounted on one of /boot/efi.; EFI System Partition cannot be of type 
None.; EFI System Partition cannot be of type ntfs.; EFI System 
Partition must be mounted on one of /boot/efi.; EFI System Partition 
cannot be of type ext4.; EFI System Partition must e mounted on one of 
/boot/efi.; EFI System Partition cannot be of type btrfs,; EFI System 
Partition must e mounted on one of /boot/efi.



If I then go into "BLIVET GUI PARTITIONING" I do see a Btrfs volume, 
labeled "fedora_locahost-live," of 460GB. It has "home" and "root" 
subvolumes. It has no mountpoints for / and /home, but I can add them. 
Still, I guess it wants me to tell it where to put /boot? What do I do?


For reference, when I look at the drive in BLIVET I see

device type  format size  label mountpoint
nvme0n1p1  partition efi 100MiB
nvme0n1p2  partition 16MiB
nvme0n1p3  partition ntfs 491.34GiB
nvme0n1p5  partition ext4 1024MiB   fedora_localhost-live
nvme0n1p4  partition ntfs    662MiB

So the overall picture I'm getting is that the first install didn't 
finish partitioning the drive (since I don't see anywhere for /boot) 
and didn't do any of the install. But a) I'm not really confident in 
that assessment b) I don't know what to do next, in any case. Is it 
nvwe0n1p2 where /boot was meant to go?


Thanks,
Matt



It seems you burned the Fedora Live image in your NVMe 0 Namespace 1 
Partition 5 as seen in


nvme0n1p5  partition ext4    1024MiB fedora_localhost-live

You must burn it to an external USB drive (ej /dev/sdx) and boot for it.

If you reserved half disk (eg 500Gb) but later burn the image in I think 
is normal whats is seen in this partition list.


Hope helps

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: F38 install issues

2023-07-14 Thread stan via users
On Thu, 13 Jul 2023 14:33:04 -0400
Matt Morgan  wrote:

> Hi. I haven't been here for a long time, which I guess is a testament
> to how well Fedora works these days.

True.

> I have a new laptop, set up with Windows, that I'm trying to install
> F38 on. I used the media writer to make a USB boot/install drive. It
> booted fine, and I clicked to install to hard drive.

Is this a live image?  I thought that when they were installed, they
just were copied directly onto the drive.  I always use netinstall.
But, wouldn't you still have to tell it which partitions or space to
use, or does it automatically divine that the efi partition should be
/boot/efi?

> I took about half of the 1TB SSD for Fedora, and told it to continue.
> Then I left for a few minutes. When I came back, the computer had
> booted to the USB drive again (it appeared). I removed the USB drive
> and rebooted again.

I think something critical happened in those few minutes.  :-)

> The system booted to Windows with no indication of a grub boot menu.
> The drive was missing the space I'd reclaimed, so clearly that
> worked, at least partly. But nothing I do seems to get it to boot
> linux or drop me at a grub menu.

If it was installed while secure boot (UEFI) was active, it will only
boot in UEFI mode.  If the system doesn't know where /boot/efi is, it
can't boot in UEFI mode.

> When I boot off the usb drive, it works, but I don't see any
> linux-related files on the SSD. So basically it looks like the drive
> got partitioned, at least partly, and the install didn't run. So I'm
> trying to run the install again, but no combination of clicks is
> getting me what I want.
> 
> 1) For "Installation Destination," I see "Error checking storage
> configuration." I click on that, and it has the one device for me to
> install to. At the bottom, it says "Error checking storage
> configuration." When I "click for details," I get
> 
> ---
> The following erros were encountered when checking your storage
> configuration. You can modify your storage layout or quit the
> installer.
> 
> Failed to find a suitable stage 1 device: EFI System Partition must be
> mounted on one of /boot/efi.; EFI System Partition cannot be of type
> None.; EFI System Partition cannot be of type ntfs.; EFI System
> Partition must be mounted on one of /boot/efi.; EFI System Partition
> cannot be of type ext4.; EFI System Partition must e mounted on one
> of /boot/efi.; EFI System Partition cannot be of type btrfs,; EFI
> System Partition must e mounted on one of /boot/efi.
> 

This is because it can't find /boot/efi to boot in UEFI mode.

> If I then go into "BLIVET GUI PARTITIONING" I do see a Btrfs volume,
> labeled "fedora_locahost-live," of 460GB. It has "home" and "root"
> subvolumes. It has no mountpoints for / and /home, but I can add them.
> Still, I guess it wants me to tell it where to put /boot? What do I
> do?
> 
> For reference, when I look at the drive in BLIVET I see
> 
> device type  format  size  label
> mountpoint nvme0n1p1  partition efi 100MiB
> nvme0n1p2  partition 16MiB
> nvme0n1p3  partition ntfs491.34GiB
> nvme0n1p5  partition ext41024MiB   fedora_localhost-live
> nvme0n1p4  partition ntfs662MiB
> 
> So the overall picture I'm getting is that the first install didn't
> finish partitioning the drive (since I don't see anywhere for /boot)
> and didn't do any of the install. But a) I'm not really confident in
> that assessment b) I don't know what to do next, in any case. Is it
> nvwe0n1p2 where /boot was meant to go?

I don't know windows, but I have heard that there is sometimes
a recovery partition that you wouldn't want to clobber, could that be
p4?  Or maybe that is p2?  If it is p4, maybe that is the reason that
it wasn't allocated as btrfs, and so the fs type was left as ntfs.
If p4 is actually the install space for / in Fedora, you could boot the
live image, and use gdisk (or fdisk) to remove the above partitions in
the space you want to use for Fedora. I think that would be p5 and p4
(if it isn't windows recovery). Then, try to install from the live image
again, but be sure to assign /boot/efi to the existing efi partition
for windows so both fedora and windows can boot from it.

An alternative if the above doesn't work.  I haven't used the netinstall
for a while, and it isn't live, but it allows for custom partitioning,
which seems to be what you need. I think it is still hub and spoke;
there are discussions of some kind of html anaconda interface, but I
don't think it is default yet. If it is still hub and spoke, you would
select the custom partitioning spoke and tell it to use the existing
efi partition as /boot/efi, and then allocate the rest for /boot and /.
 On the scheme above it looks like, as Samuel said, /boot would be
assigned to p5 and / would be assigned to p4, if it isn't the windows
recovery partition.  

Then, because a netinstall is minimal (runlevel multiuser), you could
ask it to install 

Re: F38 install issues

2023-07-13 Thread Samuel Sieb

On 7/13/23 11:33, Matt Morgan wrote:
If I then go into "BLIVET GUI PARTITIONING" I do see a Btrfs volume, 
labeled "fedora_locahost-live," of 460GB. It has "home" and "root" 
subvolumes. It has no mountpoints for / and /home, but I can add them. 
Still, I guess it wants me to tell it where to put /boot? What do I do?


For reference, when I look at the drive in BLIVET I see

device type  format  size  label mountpoint
nvme0n1p1  partition efi 100MiB
nvme0n1p2  partition 16MiB
nvme0n1p3  partition ntfs    491.34GiB
nvme0n1p5  partition ext4    1024MiB   fedora_localhost-live
nvme0n1p4  partition ntfs    662MiB


Did something get mixed up there?  I don't see any 460GB partition other 
than the windows one that is close to that.  The p5 partition is what I 
would have expected to be /boot and it's even marked as ext4 which is 
correct for that.  I don't know why btrfs label is on that one.  The one 
marked "efi" is the one that should be at /boot/efi.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


F38 install issues

2023-07-13 Thread Matt Morgan
Hi. I haven't been here for a long time, which I guess is a testament to
how well Fedora works these days.

I have a new laptop, set up with Windows, that I'm trying to install F38
on. I used the media writer to make a USB boot/install drive. It booted
fine, and I clicked to install to hard drive.

I took about half of the 1TB SSD for Fedora, and told it to continue. Then
I left for a few minutes. When I came back, the computer had booted to the
USB drive again (it appeared). I removed the USB drive and rebooted again.

The system booted to Windows with no indication of a grub boot menu. The
drive was missing the space I'd reclaimed, so clearly that worked, at least
partly. But nothing I do seems to get it to boot linux or drop me at a grub
menu.

When I boot off the usb drive, it works, but I don't see any linux-related
files on the SSD. So basically it looks like the drive got partitioned, at
least partly, and the install didn't run. So I'm trying to run the install
again, but no combination of clicks is getting me what I want.

1) For "Installation Destination," I see "Error checking storage
configuration." I click on that, and it has the one device for me to
install to. At the bottom, it says "Error checking storage configuration."
When I "click for details," I get

---
The following erros were encountered when checking your storage
configuration. You can modify your storage layout or quit the installer.

Failed to find a suitable stage 1 device: EFI System Partition must be
mounted on one of /boot/efi.; EFI System Partition cannot be of type None.;
EFI System Partition cannot be of type ntfs.; EFI System Partition must be
mounted on one of /boot/efi.; EFI System Partition cannot be of type ext4.;
EFI System Partition must e mounted on one of /boot/efi.; EFI System
Partition cannot be of type btrfs,; EFI System Partition must e mounted on
one of /boot/efi.


If I then go into "BLIVET GUI PARTITIONING" I do see a Btrfs volume,
labeled "fedora_locahost-live," of 460GB. It has "home" and "root"
subvolumes. It has no mountpoints for / and /home, but I can add them.
Still, I guess it wants me to tell it where to put /boot? What do I do?

For reference, when I look at the drive in BLIVET I see

device type  format  size  label mountpoint
nvme0n1p1  partition efi 100MiB
nvme0n1p2  partition 16MiB
nvme0n1p3  partition ntfs491.34GiB
nvme0n1p5  partition ext41024MiB   fedora_localhost-live
nvme0n1p4  partition ntfs662MiB

So the overall picture I'm getting is that the first install didn't finish
partitioning the drive (since I don't see anywhere for /boot) and didn't do
any of the install. But a) I'm not really confident in that assessment b) I
don't know what to do next, in any case. Is it nvwe0n1p2 where /boot was
meant to go?

Thanks,
Matt
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue