On 5/11/26 12:11 AM, Tim via users wrote:
Robert McBroom:
F44 server netinstall fails to complete. Tried letting the automatic
drive allocation on a sufficiently large partition. A /boot and /root
partitions were created and 16G copied to the /root. Errored. Would not
report the error. The files in /boot seem to be complete but will not load.
Tim:
"/root" is the homespace for the root user (when you "su" to the super
user usually known as "root"). It'll contain few things like the bash
config file for root, and any files created as root (I put some post-
install notes in there as reminders). ...[snip]...
"/" is the very top of the directory tree, it's where everything on the
system goes inside. It maybe referred to as the sysroot or system root
by various people, but it's name is just "/" (the slash by itself).
Robert McBroomL
exactly
/root is usually just a directory inside "/". I've never seen it
created as a partition, though I don't see why it can't be a partition
mounted there.
Was the partition big enough?
Does it have a quota?
How close to filling it with your 16G file were you?
Was it mounted at the time?
In theory, you should be able to have a /root directory in / and mount
a /root partition on top of it (likewise with various other commo
directories). Then, when you look at /root you'll either see the
directory's contents if the partition is not mounted, or the
partition's contents if it is. I wonder if there's something that
disallows that? There could be some security consideration that's not
immediately obvious to me.
SELinux is the first thing that springs to mind when something doesn't
work without giving the usual failure messages we expect to see.
Though I get the impression that a non-functioning /boot is your big
problem at the moment. That *used* to require a bootable flag in the
partition info, /boot near the start of the drive, and it being
unencrypted. Some of those requirements have changed over time.
Another issue *used* to be that when you installed from media, the
drive allocations often put the install disc first and your installed-
to disc was numbered second. Then when you tried to boot off your
installation, drive numbering didn't match. I thought that problem
died long ago with a different way of IDing each partition.
Communication is a problem. Trying to indicate that I understand about
"/" being the root of the tree. Could look at what had been written to
the partition from another installation. The partition has 300G so space
is not a problem. It is a /boot/efi system. Tried the full server
install iso and the workstation install. They all fail in setting up the
boot. There is an nvme drive, two ssd's and a hdd on the system. Trying
to install f44 on the first ssd which shows as sda. There is an f43
installation on sda3 and sda4. sda2 is the first gpt partition and is
/boot/efi.
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
