Can I request you to list the contents of your current initramfs using following command and paste the contents?
sudo --login lsinitrd /boot/initramfs-$( name --kernel-release).img
I believe it is the emptyetc/fstab.empty file in your current sudo ls -i -l -h -F -Z /boot/initramfs-$( uname --kernel-release).img causing this issue.
The boot process is having challenges identifying your rootdevice and rootfilesystem
The option --login creates a login shell when executing the command following the sudo command. I want my .profile file to be read and apply my environment customizations if any I have when executing commands
Are you able to get at the bootloader prompt ( this is the grub2 prompt ) ?
grub>
This is done by pressing Esc or any other equivalent key specific to your system when the system powers up. You might want to determine the hard disk on which Fedora is installed. This can be done by typing the following sequence of command at the grub2 prompt
Determine the filesystem on each partition
for DISKNO in {1..10} ; do for PARTNO in {1..120} ; do ls (hd$DISKNO,gpt$PARTNO) ; ls (hd$DISKNO,gpt$PARTNO)/ ; done ; done
I am making few assumptions in the aforementioned command. You have atleast 1 hard-disk and you are using GUID partition scheme to partition your disks . Please help me with output from above command.
Once the root partition has been determined following sequence of commands can be typed at the grub prompt
grub>
to successfully boot and login to the installed system
# i assume your boot partition is on first hard-disk and first partition. Please make
# the appropriate changes
# I also assume your root mounted at / is on third partition /dev/sda3. This is obtained from
# aforementioned command
linuxefi (hd0,gpt1)/vmlinuz-6.4.10-200.fc38.x86_64 root=/dev/sda3 rootfstype=ext4 rootfsdelay=3600 rd.debug rd.udev.debug udev.log_level=debug systemd.log_level=debug systemd.hostname=youp-lamb
initrdefi (hd0,gpt1)/initramfs-6.4.10-200.fc38.x86_64.img
boot
Please let me know if you were able to recover your system
-i, --login
Run the shell specified by the target user's password database
entry as a login shell. This means that login-specific resource
files such as .profile, .bash_profile, or .login will be read by
the shell. If a command is specified, it is passed to the shell
as a simple command using the -c option. The command and any
args are concatenated, separated by spaces, after escaping each
character (including white space) with a backslash (‘\’) except
for alphanumerics, underscores, hyphens, and dollar signs. If no
command is specified, an interactive shell is executed. sudo at‐
tempts to change to that user's home directory before running the
shell. The command is run with an environment similar to the one
a user would receive at log in. Most shells behave differently
when a command is specified as compared to an interactive ses‐
sion; consult the shell's manual for details. The Command
environment section in the sudoers(5) manual documents how the -i
option affects the environment in which a command is run when the
sudoers policy is in use.
and also of note and related …
Since environment variables can influence program behavior, sudoers pro‐
vides a means to restrict which variables from the user's environment are
inherited by the command to be run. There are two distinct ways sudoers
can deal with environment variables.
By default, the env_reset flag is enabled. This causes commands to be
executed with a new, minimal environment. On AIX (and Linux systems
without PAM), the environment is initialized with the contents of the
/etc/environment file.
So how you use sudo determines what it will actually do with the command passed, and what environment it uses. Since Fedora uses PAM, it’s behaviour would be a bit different I would think, otherwise why note it in the manpage.
I’ve tripple checked it and I didn’t make a typing error. my drive is a nvme drive and it’s the only drive in my system. I used the default fedora btrfs partition layout with luks encryption if that’s helps
hey, the output of that command is memdisk) (proc) (hd0) (hd0, gpt5) (hd0, gpt4) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1
I assume its hd0 gpt3 because it is /dev/nvme0n1p3 in linux
Can I request you to try and help me with the listing on each of the disks and their associated partitions with the following commands at the grub prompt?
like you suggested, the system first kernel panicked but after a restart it just suddenly started working on the latest kernel version. I don’t know if the command solved the issue or if it just resolved itself. either way, thank you so much for your help!
@youpie ,
Great to hear you’re back up and running! Can you please mark what you feel was the solution so some other user can use your solution if they have a similar issue?
user can use your solution if they have a similar issue?