some time last summer i started getting this error warning pop-up window on my bodhi 4.5 system:

at that point i was considering switching to 5.0 anyways and went ahead with doing so. the warning persisted and Jeff suggested on reddit that if it followed me through a fresh install, it was probably indicative of some kind of hardware failure. sure enough, i found a smart error on my hdd after the extended test and was thankful that he was able to point out the probable failure before i lost any important data.

fast forward a few months (to early december) of smooth sailing with 5.0 and unfortunately the same error popped back up. the first time i wrote it off to "glitches happen even though this one is eerily similar" and the reboot was way easier than when it happened before since i didn't have to button punch my laptop off and on because it got stuck in a shutdown loop. this week it popped back up for the fourth time in a couple months and obviously means something is amiss.

i have tested the hdd a couple times since the first message and gotten no warnings. smartd runs in the background and hasn't thrown any warnings in the system logs which i now keep an eye on with lnav. i ram memtest to make sure the ram is still good. no issues there. the first time this happened, Jeff asked if i was running out of disk space. i still have hundreds of gigs to spare.

the reboots are still easier because this time around i can close any open window and reboot with terminology. nothing really seems to be problematic when it starts back up, but i was hoping there might be a way to look into this so i didn't get forced to reboot every couple weeks.

rbtylee, i thought i remembered you saying something about checking xsessionmanager in a previous thread. i couldn't find the one i was thinking of to link it. i am not even sure what xsessionmanager might be, but point being i don't mind checking other log files or conf files if that's where the issue might be. just not sure how to proceed since nothing shows as being amiss with enlightenment in the system logs.

thanks in advance for any help

That would be .xsession-errors it is a hidden file in your home folder. There may or may not be clues as to what is causing this issue. My first idea is that perhaps something is filling up your hard drive and Moksha can't actually write to it and rebooting clears the data. Like an app writing to your /tmp folder. Maybe temp files are being created and then not deleted until whatever is causing it crashes. So next time it happens do not reboot go in a tty and check. I could write an app that did that on purpose, lol.

Perhaps in the tty run:

just an idea.

My second idea is some kind of weird moksha bug you have run into. Another idea is still some kind of hardware problem. Might be hard to debug.

1 members found this post helpful.

What type of medium is holding the partition that's 'throwing' this error?

Try doing a fsck on it, and see if it shows any errors. If it does, of course, fix them.

I had this type of error twice, likely because I'm running the OS on a type A1 SD card. The first time I fixed it by returning the card for a new one, the second time I fixed it by cleaning the SD card slot contacts (given the age of the netbook, I'd be surprised if the contacts didn't need cleaning).

Now, after cleaning, reading and writing is (so far) behaving normally.

But, if this error is coming from a magnetic drive, you may want to run some diagnostics on it. Also, consider how long the drive has been in use?

1 members found this post helpful.

no obvious errors jumped out me on my first read-through though most of the info is very unfamiliar. i'll take a longer look to see if i missed something.

i have a screenshot of this saved on my phone and will give it a go next time. thank you for your help

it is a standard wd hdd. after the initial issue last year, i found smartcontrol to check a drive's smart status. that is what told me my old drive was dying. this round of this error is on a new drive with 1153 lifetime hours (less than 48 days uptime) since install last august or september. smartcontrol has a smartd daemon that runs in the background to monitor for smart errors. that log is clean.

when i was looking into the issue last year, i did a search for hard drive diagnostics. smartcontrol was the only one i found. if you are aware of any others, i would be happy to give them a go.

good idea. i will drop down into a live usb in a bit and give fsck a run.

it feels like this would be a lot less likely on an internal hdd (especially since it ran just fine for a few months before acting up again), but i am willing to give it a go if only to be thorough. thank you for your thoughts and consideration as well