Installed Fedora today. Everything is crashing, and I have no idea why. I have had to go onto my windows laptop to report this.
Going into problem reporting, it shows that all of the crashes were either because the program was killed by SIGSEGV or SIGABRT. For example: gnome-system-monitor killed by SIGSEGV-org.freedesktop.GnomeAbrt. Firefox was another constant crasher, but because of SIGABRT. I tried intentionally crashing firefox by opening and then replacing tabs. This is what happened: (I have no idea what’s going on with the CPU in the background, but almost none of it was being used and then the usage just went all over the place. I did nothing)
ps: The random increases in CPU usage popped up again, and the disk reading and writing. Oh, and in this second time, the network recieving and sending dropped.
Sorry if giving out all this info at once makes things a bit difficult, but I have no idea where to begin with the bug reporting.
S.O.S
The disks passed the SMART tests.
The only things that looked bad in the whole review were: on sda, an SATA Phy Event Counter (Id: 0x0001) command failing due to an ICRC error, and SCT Error Recovery Control having both read and write disabled.
On sdb, also having that same event counter fail, but also id 0x000b experiencing CRC errors within host-to-device FIS
On sr0, a bad responce to the IEC mode page, preventing me from seeing past the compliance.
For the memory thing, I’m gonna need help installing bash. The install page is super confusing.
(Oh yeah, also windows 10 ran perfectly fine before I replaced it with fedora, I should have mentioned that beforehand sorry)
(Another probably important thing to note, in some of the crashes I am just signed out of linux)
Another addition: I tried to check the disks again to see if I missed anything, and Fedora just froze up. Had to turn off the PC and turn it back on again.
Ok me personally with what I just read tells me one of three possible errors going on. Hard Drive failure, Bad or damaged SATA cables, or the SATA Controller is trying to go out on you. If you have a good known working drive I would swap out the drive and try with that first. If the drive electronics are starting to fail it could be causing the errors. Most likely the drive. Windows does a bad job with reporting drive failures. Or at least that has always been my experience.
I have an Alienware Area51m that was doing not exactly the same thing but kept running slow and crashing from time to time in windows. I booted up a live key and looked at the smart data that way and found that my 2.5" disk was reporting errors. I pulled that disk and all the problems went away. Even though I wasn’t using the drive for anything the controller on the drive kept feeding Windows and trying to report the error but windows wasn’t listening. Sorry for the issues you are having but I really would be leaning towards drives starting to fail.
