Two years later, I can say that this error might still be a thing.
I concluded that the most likely cause is my mother. Jokes aside, she unplugged
the power chord before the pc switches off completely. Through the years, she
managed to crash in the same way f33, f34, and now f35.
This time I had
On Tue, Sep 10, 2019 at 2:52 PM Roger Heflin wrote:
>
> Symbolic links missing on / (/bin->/usr/bin and such).
> /bin/bash missing or corrupted.
> /lib64/ libraries missing or corrupted.
> systemd itself missing, pivot root attempts to run systemd and that
> may be what is failing, but you don't r
On Tue, Sep 10, 2019 at 2:52 PM Roger Heflin wrote:
>
> Symbolic links missing on / (/bin->/usr/bin and such).
> /bin/bash missing or corrupted.
> /lib64/ libraries missing or corrupted.
> systemd itself missing, pivot root attempts to run systemd and that
> may be what is failing, but you don't r
Symbolic links missing on / (/bin->/usr/bin and such).
/bin/bash missing or corrupted.
/lib64/ libraries missing or corrupted.
systemd itself missing, pivot root attempts to run systemd and that
may be what is failing, but you don't really know what the underlying
cause is for it to fail.
What exa
On Mon, Sep 9, 2019 at 9:07 PM Tony Nelson wrote:
>
> Usually, when it all goes wrong just after pivot-root, there is a
> problem with the new (real) root. Exactly how it goes wrong is not
> useful. I would look hard at whatever is mounted at /sysroot. It
> should be what you expect / (root) to
On 19-09-09 14:10:24, murph nj wrote:
Tony:
Can you give me some insight as to what the boot process does next
AFTER that pivot point? The output I'm getting isn't enlightening me,
and I'm not quite sure where to look next.
...
Usually, when it all goes wrong just after pivot-root, there is
Tony:
Can you give me some insight as to what the boot process does next
AFTER that pivot point? The output I'm getting isn't enlightening me,
and I'm not quite sure where to look next.
I can just reinstall, but I'm trying to learn more about how to
recover from errors, instead of taking the eas
On Thu, Sep 5, 2019 at 11:08 AM sixpack13 wrote:
>
> e2fsck is for ext -partitions
> AFAIK /boot/efi is fat !
You are correct. I already checked, all the partitions are fine.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send
e2fsck is for ext -partitions
AFAIK /boot/efi is fat !
___
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-o
On Wed, 4 Sep 2019 17:42:40 -0400
murph nj wrote:
> I had not, but I edited from the grub menu, and eliminated them. I
> was then able to see the messages. (I was able to see them previously
> by hitting the escape key right after entering my password for the
> disks.)
>
> Everything left on th
On Wed, Sep 4, 2019 at 9:56 PM Tony Nelson wrote:
>
>
> It dies trying to pivot-root, so add to the kernel command line
>
> rd.break=pre-pivot
>
Interesting. I was able to drop to a shell. I took a look at the
journal, and it looked like a possible hibernation problem, so I took
that out
On 19-09-04 17:42:40, murph nj wrote:
...
Everything left on the screen after the kernel panic is (too much to
type)
https://imgur.com/a/kf81crl
...
Unfortunately, it goes right to a kernel panic, so no prompts at all
to work with. (I'd have chewed on it more before asking for help if I
h
On Wed, Sep 4, 2019 at 5:42 PM murph nj wrote:
>
> On Wed, Sep 4, 2019 at 4:21 PM stan via users
> wrote:
> >
> > On Wed, 4 Sep 2019 15:05:36 -0400
> > murph nj wrote:
> >
> > > I was able to mount the drives, and check them, no problems.
> >
> > Did that include the boot partition, where the ke
On Wed, Sep 4, 2019 at 4:21 PM stan via users
wrote:
>
> On Wed, 4 Sep 2019 15:05:36 -0400
> murph nj wrote:
>
> > I was able to mount the drives, and check them, no problems.
>
> Did that include the boot partition, where the kernels and initramfs'
> are?
>
I had not, but on your suggestion, I
On Wed, 4 Sep 2019 15:05:36 -0400
murph nj wrote:
> I was able to mount the drives, and check them, no problems. I was
> also able to move all of my important data off of the drives to an
> external, so I'm not worried about any loss to the data on the drives.
> No worries of fatal mistakes anym
I was able to mount the drives, and check them, no problems. I was
also able to move all of my important data off of the drives to an
external, so I'm not worried about any loss to the data on the drives.
No worries of fatal mistakes anymore.
I also took a look at the journals that were left, the
On Wed, 4 Sep 2019 12:33:59 -0400
murph nj wrote:
> The power supply was not the problem, it was the battery. All
> subsequent testing has been done plugged into power. It also boots
> just fine from a USB stick with either Mint or Fedora.
>
> There are three kernels available from the boot me
On Wed, Sep 4, 2019 at 11:45 AM stan via users
wrote:
>
>
> The switch root is changing from the initramfs to the installed OS. If
> there is a power problem, it is possible that memory is not working
> properly, and disk reads are erronious. Fix the power supply before
> you go any further. An
On Tue, 3 Sep 2019 22:31:52 -0400
murph nj wrote:
> I've got an Acer laptop that has been shutting down suddenly. (I
> suspect a bad battery, working on that.)
>
> After a sudden shutdown last night, I now get a kernel panic on boot
> right after "Starting Switch Root..."
The switch root is ch
Hi all:
I've got an odd problem that I was hoping for some help on.
The laptop was previously working fine, I am running F30, updated regularly.
I've got an Acer laptop that has been shutting down suddenly. (I
suspect a bad battery, working on that.)
After a sudden shutdown last night, I now ge
20 matches
Mail list logo
