Welcome!

Please read this important information about Spectre and Meltdown vulnerabilities.
Please read this important information about MX sources lists.
News
  • MX Linux on social media: here
  • Mepis support still here
Current releases
  • MX-17 Final release info here
  • MX-16.1 release info here
  • antiX-17 release info here
    New users
    • Please read this first, and don't forget to add system and hardware information to posts!
    • Read Forum Rules

[*Solved] Recovering journal

Help for Current Versions of MX
Message
Author
dr-kart
Forum Novice
Forum  Novice
Posts: 80
Joined: Sun Oct 22, 2017 8:12 pm

[*Solved] Recovering journal

#1 Postby dr-kart » Mon Jan 08, 2018 5:08 pm

Another thing that disturbs me just found.

MX17x64 runs on two desktops now.
First is intel cpu with conventional (bit problematic according to smart report) hdd. (**ms-dos partition table is used). It works for months with no tangible issues or warnings. But one thing I find weird though.
I get recovering journal message upon bootup. (then "Clean" message follows) I'd like to name it hit or miss. But no, it's happening rather frequently. Anyway I wouldn't regard it as an issue since hdd there is not perfect.

But I have another desktop with amd cpu onboard and brand new ssd (**GPT p/table). And I get there such message too.

I'm not an expert. But I think it might be kind of common issue regardless kernel in use. I have these messages with MX main line kernel and debian 4.9 as well. Maybe system is not shutting down correctly on daily basis? And that's why I've been facing root file system check almost every time at boot process' begining ?
Last edited by dr-kart on Wed Jan 10, 2018 3:50 pm, edited 1 time in total.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 14113
Age: 59
Joined: Fri Dec 15, 2006 8:07 pm

Re: Recovering journal

#2 Postby Stevo » Mon Jan 08, 2018 7:04 pm

Yes, you only should see that message if you don't get a clean shutdown. Normally you see that if you lose power, for example. That is worrying. I know there are some command line ways to perform shutdowns, but we have to research that...I don't recall any except "reboot" at the moment.

Do you still get the message if you just boot to the login screen and then shutdown? How about after warm reboots?

dr-kart
Forum Novice
Forum  Novice
Posts: 80
Joined: Sun Oct 22, 2017 8:12 pm

Re: Recovering journal

#3 Postby dr-kart » Mon Jan 08, 2018 7:12 pm

Well now I have autologin on both machines.
But I did try to logout to lightdm welcome screen and shutdown then. Then turned power on and found recovering journal message again (second desktop with new ssd)

FWIW I have to add that both PCs are using tmp mounted as tmpfs via fstab
viewtopic.php?p=429945#p429945

Edit: Turned autologin off and made a test. The same.

Edit2: Turning off tmp as tmpfs won't affect the issue. Tested.
Last edited by dr-kart on Mon Jan 08, 2018 7:33 pm, edited 1 time in total.

User avatar
anticapitalista
Forum Veteran
Forum Veteran
Posts: 5297
Joined: Sat Jul 15, 2006 10:40 am

Re: Recovering journal

#4 Postby anticapitalista » Mon Jan 08, 2018 7:29 pm

dr-kart wrote:
FWIW I have to add that both PCs are using tmp mounted as tmpfs via fstab
viewtopic.php?p=429945#p429945



Turn that off and what happens?
anticapitalista
Reg. linux user #395339.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX-15 "Killah P!" - lean and mean.
http://antix.mepis.org

dr-kart
Forum Novice
Forum  Novice
Posts: 80
Joined: Sun Oct 22, 2017 8:12 pm

Re: Recovering journal

#5 Postby dr-kart » Mon Jan 08, 2018 7:35 pm

Just did it anticapitalista with no effect

dr-kart
Forum Novice
Forum  Novice
Posts: 80
Joined: Sun Oct 22, 2017 8:12 pm

Re: Recovering journal

#6 Postby dr-kart » Mon Jan 08, 2018 8:07 pm

One more question on /var/log/fsck/checkfs file:

Code: Select all

Log of fsck -C -R -A -a
Tue Jan  9 01:31:17 2018

fsck from util-linux 2.29.2

Tue Jan  9 01:31:17 2018
----------------

Does the date above reflect actual latest file system check? And it should not be updated when normal boot occurs. In other words, if I permanently observe updated file system check date here - it means that system always tries to check file system for a reason (improper shutdown for instance). Or this fsck date is being updated every bootup even when everything is ok?

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 7324
Joined: Sun Dec 16, 2007 1:17 pm

Re: Recovering journal

#7 Postby dolphin_oracle » Mon Jan 08, 2018 9:27 pm

there is a fsck every boot. a quick one.

are you just seeing the "clean" message, or do you actually see the "recovering journal" message. I get the fsck on everyboot, but I only see the "recovering journal" type stuff in the invent that I've hosed something.
http://www.youtube.com/runwiththedolphin
eeepc 904ha antix 15 32 bit (streaming media player)
acer c720p chromebook - chromeos / MX15-64 (custom snapshot) live USB.
lenovo s21e - antiX-16 MX16(live-usb)

dr-kart
Forum Novice
Forum  Novice
Posts: 80
Joined: Sun Oct 22, 2017 8:12 pm

Re: Recovering journal

#8 Postby dr-kart » Tue Jan 09, 2018 4:09 am

dolphin_oracle wrote: are you just seeing the "clean" message, or do you actually see the "recovering journal" message

Just like I said before and named the topic.
I do see "recovering journal" message (with "Clean" following) on two desktops:
1st - intel cpu+hdd with 4.14.0-3-amd64 #1 SMP Debian 4.14.12-2~mx17+1 (2018-01-06) kernel
2nd - amd cpu+ssd with 4.9.0-5-amd64 debian kernel (4.9.65-3+deb9u2)

dr-kart
Forum Novice
Forum  Novice
Posts: 80
Joined: Sun Oct 22, 2017 8:12 pm

Re: Recovering journal

#9 Postby dr-kart » Tue Jan 09, 2018 9:48 am

:confused: what journal/log file to check and see (maybe) why filesystem wasn't unmounted properly during last shutdown/reboot?

dr-kart
Forum Novice
Forum  Novice
Posts: 80
Joined: Sun Oct 22, 2017 8:12 pm

Re: Recovering journal

#10 Postby dr-kart » Tue Jan 09, 2018 5:53 pm

finally
I found culprit (I'm not using NM viewtopic.php?f=107&t=43611 )
it's wicd set to autoconnect. Manual disconnect before reboot would resolve the issue.

Now I need to come up with perfect shutdown without manual wicd disconnection.


Return to “MX Help”

Who is online

Users browsing this forum: penguin48 and 10 guests