My logwatch presented me with this (among other things) this morning:- --------------------- Kernel Begin ------------------------ WARNING: Kernel Errors Present [ 7.192693] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro ...: 1 Time(s) [ 7.386581] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro ...: 1 Time(s) [ 20.697614] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro ...: 1 Time(s) [ 20.824819] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro ...: 1 Time(s) [ 20.861868] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro ...: 1 Time(s) [ 20.907760] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro ...: 1 Time(s) [ 20.945476] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro ...: 1 Time(s) [ 21.031194] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro ...: 1 Time(s) [ 27.012635] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,comm ...: 1 Time(s) [ 28.113740] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,comm ...: 1 Time(s) [ 28.463488] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,comm ...: 1 Time(s) [ 33.145286] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,comm ...: 1 Time(s) [ 33.649576] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,comm ...: 1 Time(s) [ 34.486168] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,comm ...: 1 Time(s) [ 45.508896] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,comm ...: 1 Time(s) [ 49.252032] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,comm ...: 1 Time(s) ---------------------- Kernel End ------------------------- Should I be worried? That's my 'root' disk:- /dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0) It doesn't have either /home or /bak on it so it's just system configuration that needs to be preserved (which it is). -- Chris Green
A good starting point is usually fsck, try it and find out. -- James. http://www.jamesbensley.co.cc/
On Wed, Dec 14, 2011 at 10:11:22AM +0000, James Bensley wrote:
A good starting point is usually fsck, try it and find out.
Good idea, there are a few errors but it doesn't look as if they're hardware related. I'll get fsck to fix them (ran it read only while mounted just now) and see if that makes everything a bit happier. I guess I can check the SMART diagnostics while I'm about it. -- Chris Green
On 14 December 2011 11:02, Chris Green <cl@isbd.net> wrote:
I guess I can check the SMART diagnostics while I'm about it.
Yeah, then you can run some tests on the drives with -t (apt-get install smartmontools | yum install smartmontools). -- James. http://www.jamesbensley.co.cc/
On Wed, Dec 14, 2011 at 11:11:13AM +0000, James Bensley wrote:
On 14 December 2011 11:02, Chris Green <cl@isbd.net> wrote:
I guess I can check the SMART diagnostics while I'm about it.
Yeah, then you can run some tests on the drives with -t (apt-get install smartmontools | yum install smartmontools).
SMART reports no errors at all. I'll just keep an eye on it but I suspect it's some sort of software glitch rather than the disk hardware. -- Chris Green
participants (2)
-
Chris Green -
James Bensley