You are not logged in.
my system was crashing and generating too many printk's like this:
"failed unmounting ...."
for me to see the stack trace.
The one time I saw a stack trace there was something about cache inconsistency so I assumed the worst and thought a CPU core was going bad.
the 3rd time the system crashed the crash had the same symptoms but with the added symptom that on reboot it also lost the ability to boot from the UEFI.
I restored the boot capability using the arch boot usb and setting up grub2 again.
I was hoping eventually a useful system message would show up ... system worked for a week
System crashed again, no useful error messages in the logs, the flood of printk scrolled the panic stack trace away.
but again the UEFI boot for the hard drive went away. It's this one symptom that makes me hope it's the hard drive and not a more expensive component failing. I'm testing the HD yet again with smartctl.
should I be suspecting primarily bad ram / mobo (maybe the HD controller?) OR the cpu?
or is it more likely the hard disk going bad?
smartctl shows no problems with the hard drive, and both times the boot capability went away parted showed the UEFI esp partition is still there with the right flags - both times I didn't need to repair anything other than the grub install.
What do you folks do in this case ... get a new system or spend a month buying one new component to test per week.
Last edited by Sanjeev K Sharma (2015-03-31 14:43:00)
Offline