Hi, Guus.
I've just run the memtest from archiso. Just passed, no error reported. So I'm afraid it has to be an fs bug or other hardware error... I'm looking forward to running a SMART test later. But the current Arch installation is on a Kingstom USB drive, is that okay with the SMART test?
In fact, what confused me most now is why both pacman and fsck reported segmentation fault... It can't just be a coincidence, right?
Oh, remembered one more thing. I tried to remove the gnome-extra group again this afternoon. The same error, the same output. More specifically, even exactly the same time the error happened (when attemptting to remove package telepathy-idle). Funny enough, Uhm? ;)
Thx a lot!
RW
Guus Snijders <gsnijders(a)gmail.com> wrote:
>Op 14 mei 2017 04:29 schreef "Robert W0ng via arch-general" <
>arch-general(a)archlinux.org>:
>
>Hello again, All.
>
>Update:
>
>I ran fsck in archiso this morning, and found sth interesting.
>
>To sum up, fsck.f2fs exit with signal 11, arguing segmentation fault.
>
>
>AFAIK segfaults are memory errors (where $program tries to read or write
>memory that isn't his).
>
>If there is a problem with the fs, fsck should complain and if possible fix
>it, not just crash.
>
>Try memtest86 (give it a few hours) and see if something comes up.
>
>
>Mvg, Guus Snijders
