On Fri, Jan 13, 2023 at 11:45:31AM -0800, Philip Guenther wrote:
> On Fri, Jan 13, 2023 at 10:59 AM Nick Templeton <nick@nicktempleton.com>
> wrote:
>
> > Ever since upgrading my machine to 7.2 I've been unable to relink my
> > kernel, anybody have any idea why?
>
> ...
>
> > Running "/usr/libexec//reorder_kernel" manually resulted in a kernel panic:
> >
> > mode = 0100600, inum = 7, fs = /tmp
> > panic: ffs_valloc: dup alloc
> > Stopped at db_enter+0x10: popq %rbp
> >
>
> You have at least one filesystem with latent corruption. You should reboot
> in single-user mode and run fsck with the -f option on each partition.
But it would be wise to check the hardware first, because he also mentions:
> Rebooting the machine results in this at the login prompt:
>
> login: ahci0: attempting to idle device
> ahci0: couldn't recover NCQ error, failing all outstanding commands.
> ahci0: attempting to idle device
> ahci0: couldn't recover NCQ error, failing all outstanding commands.
This could be caused by a faulty sata cable, dirty connector, or something
more serious.
Probably not a great idea to get half way through an fsck and have the drive
start failing commands.
No comments:
Post a Comment