It's just an information string. Not an error. In first time root device mounted with options from kernel cmdline. You can see mounted device and options in first line. Next time (second line) it's remounted with options from /etc/fstab. Again: second line inform you, what root device remounted with option "errors=remount-ro". Not in ro mode.
For example, from my dmesg:
[ 5.395258] EXT4-fs (md2): re-mounted. Opts: errors=remount-ro
06.07.2017 15:12, Zoran Stojsavljevic пишет:
John,
You should join Ancient Greek philosophers: Plato, Aristotle, Plutarch, Archimedes... The last one would be great Linux programmer, if he lived in Modern World.
This advice I gave (also) to lot of PEs in INTEL IOTG, while I was there... Very handy advice. ;-) _______
Pavel,
Thank you very much for the insight.
I see what you are saying (I did not know that), that the first mount / attributes came out initrd. It probably happens while dracut re-pivots initrd's / to hard drive's /.
Anyway, it should be checked. It says: error, then it says that it remounted sda1 with EXT4-fs as RO (I assume it is /). I do not see very often this line in dmesg (but I see it as seldom occurrence), so it must be some sort of race effect, or...?!
Thank you, Zoran
On Thu, Jul 6, 2017 at 1:34 PM, John Lewis <jlewis@johnlewis.ie mailto:jlewis@johnlewis.ie> wrote:
Yes, as Pavel said, "remount-ro" is just what happens if the filesystem encounters an error which presumably it hasn't, at this point. :) On 06/07/17 12:11, Pavel Alyev wrote:
First line: mount without options from initrd. Second: remount "/" with options from fstab. It's not mean what it mounted in ro mode. 06.07.2017 13:59, Zoran Stojsavljevic пишет:
> If there are critical dmesg values that can be optimized, do not hesitate to point them out! :) [user@localhost dungeon]$ cat marcelo_dmesg.log | grep EXT4 [ 2.127239] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) */_[ 2.332115] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro_/* [user@localhost dungeon]$ Line in */_RED_/* is concerning me. Do you have / ro? Zoran On Thu, Jul 6, 2017 at 11:42 AM, Marcel Maci <elpinguino@gmx.ch <mailto:elpinguino@gmx.ch>> wrote: > By that time (Y2161) I'll look something like this (200Y old man): > https://s-media-cache-ak0.pinimg.com/originals/b1/c9/8f/b1c98fb01833bdbd06513a3ffc8f6590.jpg <https://s-media-cache-ak0.pinimg.com/originals/b1/c9/8f/b1c98fb01833bdbd06513a3ffc8f6590.jpg> > > There are other problems (as well) in your dmesg log. But not to > spoil the situation (KUDOS to John). If you find anything else wrong, > just scream! ;-) > > Zoran Thx for the photo - I see you are optimistic for the future ... ;) If there are critical dmesg values that can be optimized, do not hesitate to point them out! :) Marcel
-- With best regards, Pavel Alyev anotherhosting.net <http://anotherhosting.net> chief administrator
Here, I withdraw my words to John about Ancient Greeks. Apologies.
I guess, I do NOT see these messages in 99.9% of dmesg logs, because all users on all different platforms with various distros stubbornly keep kernel command option: quiet rhgb.
I am 99% sure, if I remove these two options, this message will pop up in my dmesg logs. I'll later do the experiment on my FC26 VM wrt that.
Thus, Pavel and you are All Cool. ;-)
Zoran
On Thu, Jul 6, 2017 at 2:25 PM, Pavel Alyev aliech@aliech.ru wrote:
It's just an information string. Not an error. In first time root device mounted with options from kernel cmdline. You can see mounted device and options in first line. Next time (second line) it's remounted with options from /etc/fstab. Again: second line inform you, what root device remounted with option "errors=remount-ro". Not in ro mode.
For example, from my dmesg:
[ 5.395258] EXT4-fs (md2): re-mounted. Opts: errors=remount-ro
06.07.2017 15:12, Zoran Stojsavljevic пишет:
John,
You should join Ancient Greek philosophers: Plato, Aristotle, Plutarch, Archimedes... The last one would be great Linux programmer, if he lived in Modern World.
This advice I gave (also) to lot of PEs in INTEL IOTG, while I was there... Very handy advice. ;-) _______
Pavel,
Thank you very much for the insight.
I see what you are saying (I did not know that), that the first mount / attributes came out initrd. It probably happens while dracut re-pivots initrd's / to hard drive's /.
Anyway, it should be checked. It says: error, then it says that it remounted sda1 with EXT4-fs as RO (I assume it is /). I do not see very often this line in dmesg (but I see it as seldom occurrence), so it must be some sort of race effect, or...?!
Thank you, Zoran
On Thu, Jul 6, 2017 at 1:34 PM, John Lewis jlewis@johnlewis.ie wrote:
Yes, as Pavel said, "remount-ro" is just what happens if the filesystem encounters an error which presumably it hasn't, at this point. :)
On 06/07/17 12:11, Pavel Alyev wrote:
First line: mount without options from initrd. Second: remount "/" with options from fstab.
It's not mean what it mounted in ro mode.
06.07.2017 13:59, Zoran Stojsavljevic пишет:
If there are critical dmesg values that can be optimized, do not hesitate
to point them out! :)
[user@localhost dungeon]$ cat marcelo_dmesg.log | grep EXT4 [ 2.127239] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) *[ 2.332115] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro* [user@localhost dungeon]$
Line in *RED* is concerning me. Do you have / ro?
Zoran
On Thu, Jul 6, 2017 at 11:42 AM, Marcel Maci elpinguino@gmx.ch wrote:
By that time (Y2161) I'll look something like this (200Y old man): https://s-media-cache-ak0.pinimg.com/originals/b1/c9/8f/b1c9
8fb01833bdbd06513a3ffc8f6590.jpg
There are other problems (as well) in your dmesg log. But not to spoil the situation (KUDOS to John). If you find anything else wrong, just scream! ;-)
Zoran
Thx for the photo - I see you are optimistic for the future ... ;) If there are critical dmesg values that can be optimized, do not hesitate to point them out! :)
Marcel
-- With best regards, Pavel Alyevanotherhosting.net chief administrator
-- With best regards, someone from somewhere...