LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Bodhi
User Name
Password
Bodhi This forum is for the discussion of Bodhi Linux.

Notices


Reply
  Search this Thread
Old 01-27-2019, 07:23 AM   #1
cordx
Member
 
Registered: Oct 2018
Location: texas
Distribution: bodhi 5.0
Posts: 176

Rep: Reputation: 25
moksha setting write problems


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

Name:	20190124_020736_HDR_cr2.jpg
Views:	18
Size:	195.9 KB
ID:	29605

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
 
Old 01-27-2019, 01:35 PM   #2
rbtylee
Bodhi Developer
 
Registered: Jun 2018
Location: Ladson, SC US
Distribution: Bodhi
Posts: 108

Rep: Reputation: 125Reputation: 125
Quote:
Originally Posted by cordx View Post
...
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:

Code:
sudo du -h --max-depth=1 /
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.
Old 01-27-2019, 03:01 PM   #3
RonCam
Member
 
Registered: Dec 2008
Posts: 54

Rep: Reputation: 11
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?

Last edited by RonCam; 01-27-2019 at 03:03 PM.
 
1 members found this post helpful.
Old 01-27-2019, 04:50 PM   #4
cordx
Member
 
Registered: Oct 2018
Location: texas
Distribution: bodhi 5.0
Posts: 176

Original Poster
Rep: Reputation: 25
Quote:
Originally Posted by rbtylee View Post
That would be .xsession-errors it is a hidden file in your home folder.
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.

Quote:
Originally Posted by rbtylee View Post
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:

Code:
sudo du -h --max-depth=1 /
i have a screenshot of this saved on my phone and will give it a go next time. thank you for your help
 
Old 01-27-2019, 05:17 PM   #5
cordx
Member
 
Registered: Oct 2018
Location: texas
Distribution: bodhi 5.0
Posts: 176

Original Poster
Rep: Reputation: 25
Quote:
Originally Posted by RonCam View Post
What type of medium is holding the partition that's 'throwing' this error? 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?
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.

Quote:
Originally Posted by RonCam View Post
Try doing a fsck on it, and see if it shows any errors. If it does, of course, fix them.
good idea. i will drop down into a live usb in a bit and give fsck a run.

Quote:
Originally Posted by RonCam View Post
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.
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
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
USB device connection overrides Moksha DE's lock screen (Bodhi 4.5.0, Moksha 0.2.1) Kazuhira_x3 Bodhi 1 11-08-2018 03:54 AM
several problems with moksha bodhi 5.0 matzew Bodhi 1 10-17-2018 04:09 PM
LXer: Bodhi Linux 3.1.0 Will Drop Enlightenment E19 for Moksha Desktop, Arrives in August 2015 LXer Syndicated Linux News 0 04-30-2015 02:24 AM
Bodhi to Fork Enlightenment to Produce "Moksha" jeremy Linux - News 0 04-29-2015 10:30 AM
LXer: Fedora Announces The Moksha Project LXer Syndicated Linux News 0 01-20-2009 06:11 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Bodhi

All times are GMT -5. The time now is 10:07 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration