Recovering journal при загрузке linux ubuntu

Thread: [solved]/dev/sda1: recovering journal

Thread Tools

[solved]/dev/sda1: recovering journal

i keep getting the error /dev/sda1: recovering journal and then it says clean after that but then computer goes through the boot process a second time after which i get the advanced boot option. i just go to the ubuntu option and computer starts correctly. seems like this started happening after last kernel update. everything seems to run fine once i get logged in. this is on lubuntu 18.04.2, i believe is most recent version. only thing i have tried is reinstalling grub, which made no difference.

anyone have any ideas?

Last edited by missmoondog; May 22nd, 2019 at 02:52 PM . Reason: solved

Re: /dev/sda1: recovering journal

Using ext4? Tried booting into an older kernel? Have you run smartctl on this disk?

Re: /dev/sda1: recovering journal

don’t know about ext4! using xfce. this is a rather old, single core laptop. will that smartctl even work on it? no, didn’t try older kernel as newest one works, just makes it go through boot 2 times, every time. don’t use laptop very often either.

Re: /dev/sda1: recovering journal

will show which file systems are in use. And yes, smartctl will work.

Re: /dev/sda1: recovering journal

will give that a try in a few days and get back with you.

Re: /dev/sda1: recovering journal

sorry took so long to get back. had other issues.

yes, file system is ext 4 and running

now. 44 minutes to complete.

Re: /dev/sda1: recovering journal

had to give up on that test above. doubt if i would’ve known what to do afterwards anyway considering when setting up the tool, i had to enter some info about mail of which i didn’t know what to do!

just noticed this morning on my other 32bit machine that it does the same thing as far as starting and restarting twice. in fact, both machines simply quit booting on first try and have to hold power button to get it to resrart then goes through boot precoess twice which brings up boot options. simply hit boot normally and finally get to desktop.

Читайте также:  Заправка картриджа canon mf3010 инструкция

almost inclined to believe this is more of a 32bit bug than any other issue?


Проблема при загрузке

Привет всем, решил я такой загрузится в убунту. Первый раз-мигает ее логотип, потом черный экран. Ну и так по кругу. Ладно, баг подумал я. Загрузился второй раз, появился экран типо /Dev/sdb5: recovering journal, полегли логи. Загрузилась в итоге. С чем это могло быть связано?

Эта запись появляется тогда, когда что-то нарушает целостность файловой системы на устройстве. Это может быть из-за того, что ты выключил устройство по питанию, или у тебя отказывает ЖД.

Да, в первый раз на кнопку питания зажал. Может из-за этого?

Скорее всего, да. Но SMART нужно посмотреть.

Перезаугрзил, все нормально. Только при загрузке не логотп, а логи на фиолетовом фоне, ошибок никаких. Логи типо [OK] started gnome display manager и т.д

Я же тебе команды выше дал, как SMART смотреть, при чем тут логи загрузки?

Хорошо, сейчас проверю . От этого же не могут данные утеряться? В Линуксе просто Новичок (, а на диске 44гб фоток

От проверки SMART — нет. От помирающего диска — да.


How to Fix recovering journal Error on Ubuntu boot up

Recent day i was faced Recovering journal Error on Ubuntu boot up multiple times in a day, so i was debugged system checked all the system logs to get fixed this issue. And finally i found this problem happens when my system direct shutdown due to some power reason(after all i was fixed power issue by changing power supply) but still Ubuntu showing “recovering journal” error on Ubuntu boot up, because it didn’t write anything to the disk. So after some troubleshoot I’m able to solve this problem

So lets checkout following steps to solve recovering journal Error on Ubuntu boot up, don’t worry it can be fixed with following some easy steps;

Step #1: Lets first check your file system for errors.

To check the file system on your Ubuntu partition…

  • boot to the GRUB menu
  • choose Advanced Options
  • choose Recovery mode
  • choose Root access
  • at the # prompt, type sudo fsck -f /
  • repeat the fsck command if there were errors
  • type reboot

Step #2: If for some reason you can’t do the above…

  • boot to a Ubuntu Live DVD/USB
  • start gparted and determine which /dev/sdaX (be sure about your exact Ubuntu system installed partition) is your Ubuntu EXT4 partition (you can use also $ lsblk command)
  • quit gparted
  • open a terminal window
  • type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier
  • repeat the fsck command if there were errors
  • type reboot
Читайте также:  Как заправить принтер бразер hl 1110r

After reboot system if you show to the tty1 terminal then you need to install the ubuntu-desktop environment using following command;

This command will solve your problem, and you should be able to use GUI like normal.

I hope this quick guide will help you and can solve your issue successfully, if you had any issue during recovery, please comment below.


Thread: /dev/sda1: recovering journal??

Thread Tools

/dev/sda1: recovering journal??

So I insatlled Ubuntu Server 9.10 (64bit) on a VMware ESXi. I then cloned the installation. On the one that I cloned, I noticed this on boot:

fsck from util-linux-ng 2.16
/dev/sda1: recovering journal
/dev/sda1: clean, 170/24096 files, 36423/96356 blocks
fsck from util-linux-ng 2.16
/dev/sda3: recovering journal
/dev/sda3: clean 21/91392 files, 14489/365478 blocks
fsck from util-linux-ng 2.16
/dev/sda4: clean, 54686/243840, 310391/973940 blocks

It happens every time I reboot the VM. I do not notice that same message on the original VM. Is this something I need to be concerned with?

Re: /dev/sda1: recovering journal??

So after some troubleshooting, I figured out that I only get this message if I install vmware tools.

If I do not install vmware tools, the system boots up without the

/dev/sda1: recovering journal
/dev/sda3: recovering journal

Anyone else using Ubuntu Server in a ESXi environment.

Re: /dev/sda1: recovering journal??

I don’t know the solution. but at least I can confirm the problem (although it doesn’t seem like a real problem so far). It only does it for the /home partition, for me at least.

I also noticed, with vmware tools installed, that it doesn’t need to recover it when I reboot immediately (hence not much writing to /home).

Re: /dev/sda1: recovering journal??

It’s not a «problem» at all, it’s a forced file system check to make sure of the integrity of the virtual disk. It does not hurt a thing, in fact, it’s a good thing™

Hard to find and obsolete PC and server parts. «If we can’t find it, it probably doesn’t exist»


MX Linux Forum

Support for MX and antiX Linux distros

Forum users

  • Please read this before asking for help, and don’t forget to add Quick System Info to help requests!
  • Please follow the Forum Rules

Current releases
— MX-21 release info here
— Migration information to MX-21 here
— antiX-21 (Grup Yorum) release info here

— MX Linux on social media: here
— New Forum Features, Marking Solved and Referencing a User: here

Читайте также:  Linux узнать параметры сети

[*Solved] Recovering journal

[*Solved] Recovering journal

#1 Post by 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 ?

Re: Recovering journal

#2 Post by 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?

Re: Recovering journal

#3 Post by 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

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

Edit2: Turning off tmp as tmpfs won’t affect the issue. Tested.

Re: Recovering journal

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

Reg. linux user #395339.

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

antiX with runit — lean and mean.

Re: Recovering journal

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


Поделиться с друзьями