On Mon, 20 Apr 2020 20:52:23 +0100
Paul Smith wrote:
> Thanks, Stan. After having run
>
> fsck /dev/mapper/fedora_localhost--live-home
>
> within emergency mode and rebooted, the problem seems to be resolved.
You're welcome. I saw the continuation from Roger where he guided you
to the issue.
Thank you very much indeed, Roger! Without your help, I would have not
fixed the problem.
I did remove both the nofail than the "0 0", and everything seems to
be working fine! I have already rebooted and no emergency mode
appeared.
Paul
On Mon, Apr 20, 2020 at 9:38 PM Roger Heflin wrote:
>
> re
remove the ,nofail and see if it goes to emergency mode still.
If it does then remove these from the grub file
rd.lvm.lv=fedora_localhost-live/root
rd.lvm.lv=fedora_localhost-live/swap
And add this in its place:
rd.lvm.vg=fedora_localhost-live
The above 2 options indicate that only those 2 lv ar
Thanks, Stan. After having run
fsck /dev/mapper/fedora_localhost--live-home
within emergency mode and rebooted, the problem seems to be resolved.
Paul
On Mon, Apr 20, 2020 at 7:28 PM stan via users
wrote:
>
> On Mon, 20 Apr 2020 12:23:35 +0100
> Paul Smith wrote:
>
> > Dear All,
> >
> > This
On Mon, 20 Apr 2020 12:23:35 +0100
Paul Smith wrote:
> Dear All,
>
> This morning, I tried to run VirtualBox, but it did not start. Then I
> tried to do a reboot and while booting, I got into emergency mode. I
> typed my root password and issued the command
>
> systemctl reboot
>
> It reboots,
Hi Roger,
By adding
"defaults,nofail" and "0 0"
to /home on fstab, my computer reboots fine.
What a mystery!
Paul
On Mon, Apr 20, 2020 at 4:51 PM Paul Smith wrote:
>
> Thanks, Roger. The result of the command was:
>
> ---
> cat /proc/cmdline
> BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.5.
Thanks, Roger. The result of the command was:
---
cat /proc/cmdline
BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.5.17-200.fc31.x86_64
root=/dev/mapper/fedora_localhost--live-root ro
resume=/dev/mapper/fedora_localhost--live-swap
rd.lvm.lv=fedora_localhost-live/root
rd.lvm.lv=fedora_localhost-live
Nothing really to see there.
cat /proc/cmdline and lets see what is on it.
On Mon, Apr 20, 2020 at 10:03 AM Paul Smith wrote:
>
> Thanks, Roger! You can find below the output of the two commands.
>
> Paul
> ---
> 13.843s dnf-makecache.service
> 4.961s NetworkMana
Thanks, Roger! You can find below the output of the two commands.
Paul
---
13.843s dnf-makecache.service
4.961s NetworkManager-wait-online.service
2.047s systemd-udev-settle.service
1.506s akmods.service
1.257s firewalld.service
996ms sssd.service
994ms init
So home mounted eventually.
Run these 2 commands and return the output:
systemd-analyze blame
systemd-analyze critical-chain home.mount
if the 2nd one returns nothing do this:
systemctl list-units | grep home
and use the name of the .mount unit it reports that home is using.
On Mon, Apr 20, 20
Thanks, Roger. After having edited fstab according to your guidelines,
I issued the command
# exit
on the root prompt and I was led to my usual graphical login panel.
I did the following after having logged in:
# mount /home
mount: /home: /dev/mapper/fedora_localhost--live-home already mounted
Edit your fstab and on the entry for /home were it says defaults
change it to "defaults,nofail" and where it says "1 2" at then end
change that to "0 0" I am not sure if the last 2 entries are still
used quite the same way but "0 0" will stop anything else looking for
/home.
That should get you
Thanks again, Roger. Got them! Please, see them at:
https://drive.google.com/drive/folders/158qtJIgB6WiEbnLu4oFShbSY1paWafj8?usp=sharing
Thanks,
Paul
On Mon, Apr 20, 2020 at 2:26 PM Roger Heflin wrote:
>
> Hit shift-pageup/pagedown it will scroll that screen, it should scroll
> back 100's of l
Hit shift-pageup/pagedown it will scroll that screen, it should scroll
back 100's of lines or more. Take pictures each pageup.
On Mon, Apr 20, 2020 at 8:20 AM Paul Smith wrote:
>
> Thanks, Roger. But how can I get the error messages?
>
> Paul
>
> On Mon, Apr 20, 2020 at 2:13 PM Roger Heflin wro
Thanks, Roger. But how can I get the error messages?
Paul
On Mon, Apr 20, 2020 at 2:13 PM Roger Heflin wrote:
>
> A screen shot of the fstab does not tell anyone anything as we have no
> way to know what is going on.
>
> Did you follow the instructions to use shift-pageup/down to page
> through
A screen shot of the fstab does not tell anyone anything as we have no
way to know what is going on.
Did you follow the instructions to use shift-pageup/down to page
through the error messages (above the emergency mode prompt) and and
see what it indicates is going wrong? It is probably going to
Please, see my fstab photo:
https://drive.google.com/file/d/1fWv2h-CLt2ecoE2m5aCpAOsUr2aEhuvh/view?usp=sharing
Paul
On Mon, Apr 20, 2020 at 1:22 PM Paul Smith wrote:
>
> Thanks, Roger and Ed. I did not touch fstab at all. It may have been
> VirtualBox by itself.
>
> I did enter my root passwor
Thanks, Roger and Ed. I did not touch fstab at all. It may have been
VirtualBox by itself.
I did enter my root password. And now, what should I do next?
Thanks, Paul
On Mon, Apr 20, 2020 at 1:09 PM Roger Heflin wrote:
>
> You have to type your password and then figure out what is going wrong.
You have to type your password and then figure out what is going wrong.
Any number of things can be messed up.Often if one adds a fstab
entry and does it wrong systemd will drop you to emergency mode.
Mountpoint mising, path to device wrong. If you did mess with fstab
recently then add ",nof
On 2020-04-20 19:23, Paul Smith wrote:
> Dear All,
>
> This morning, I tried to run VirtualBox, but it did not start. Then I
> tried to do a reboot and while booting, I got into emergency mode. I
> typed my root password and issued the command
>
> systemctl reboot
>
> It reboots, but again I got lo
Dear All,
This morning, I tried to run VirtualBox, but it did not start. Then I
tried to do a reboot and while booting, I got into emergency mode. I
typed my root password and issued the command
systemctl reboot
It reboots, but again I got locked into emergency mode.
How can I overcome this?
T
21 matches
Mail list logo
