Hi guys, sorry if this topic has allready been adressed, sure it is, but not found any help nowhere.
I spent 6 hours to identify why network files transferts were extremly slow (4Mb/s max),
and discovered with a local "rsync" test that it was not the network the problem…
then I took a look at dmeg logs and found "advices" to do a "fsck" to the disk,
what I think I suceed, but maybe not on the good one, because I still have the same message in the logs.
is there a known way to perform a disk cleaning (i think that some hard reboots put some trouble in some disk files….)
I followed online tuto linuxuprising —> how-to-force-fsck-filesystem
to do and verify that fscl had been performed on /dev/md1 with sucess.
server:~# tune2fs -l /dev/sda1 | grep checked Last checked: Tue Apr 7 02:33:23 2020 server:~# tune2fs -l /dev/md1 | grep checked Last checked: Tue Apr 7 02:33:23 2020 but maybe check has been done but without repair ?
I have to put the disk out and do that from another linux system ?
here is my dmesg…
if someone know how to solve this small issue…
Will be very welcome !
thanks
sd 1:0:0:0: [sda] Attached SCSI disk md: Waiting for all devices to be available before autodetect md: If you don't use raid, use raid=noautodetect md: Autodetecting RAID arrays. md: Scanned 2 and added 2 devices. md: autorun ... md: considering sda2 ... md: adding sda2 ... md: adding sda1 ... md: created md1 md: bind<sda1> md: bind<sda2> md: running: <sda2><sda1> md1: WARNING: sda2 appears to be on the same physical disk as sda1. True protection against single-disk failure might be compromised. raid1: raid set md1 active with 2 out of 2 mirrors md1: detected capacity change from 0 to 2047803392 md: ... autorun DONE. md1: unknown partition table kjournald starting. Commit interval 5 seconds EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3 FS on md1, internal journal EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) on device 9:1.