On Fri, Jun 14, 2019 at 3:57 PM Mathias G <newsnet-mg-2016@xxxxxxxxxxxxx> wrote: > > Hello together > > For a long time now (surely since the beginning of 2018) I have the > problem that every now and then after a reboot of the system (PC > workstation) the RAID-1 is resynchronized. To be clear, this does not happen every time, right? > > Possibly the problem occurs mostly or always after an kernel update > kernel, but there are cases (like today) where no update was made. > > The RAID-1 consisting of 2x 2TB SATA HDD > > The RAID is built with mdadm, at the earlier days with header version > 0.x, but also completely rebuilt (because of this problem) with header > version 1.2 > > The Linux system is a Debian "testing" (version 10.0) > > Current kernel version: 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 > (2019-05-15) x86_64 GNU/Linux > > But the problem was already at version: 4.17.0-1-amd64 #1 SMP Debian > 4.17.8-1 (2018-07-20) x86_64 GNU/Linux > > The log entry in kern.log (after restart) when the RAID needs to be > resynchronized: > > Jun 14 23:11:01 $hostname kernel: [ 2.132085] md/raid1:md0: not clean -- starting background reconstruction > > Jun 14 23:11:01 $hostname kernel: [ 2.132088] md/raid1:md0: active with 2 out of 2 mirrors > > Jun 14 23:11:01 $hostname kernel: [ 2.132245] md0: bitmap file is out of date (228834 < 228835) -- forcing full recovery > > Jun 14 23:11:01 $hostname kernel: [ 2.132297] md0: bitmap file is out of date, doing full recovery And the bitmap is stored in a file? And the file is on a different disk, right? Thanks, Song > > The new synchronization will look like this (today): > > $ cat /proc/mdstat > > Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] > > md0 : active raid1 sdb1[0] sdc1[3] > > 1953382464 blocks super 1.2 [2/2] [UU] > > [=====>...............] resync = 25.7% (502785344/1953382464) finish=216.8min speed=111498K/sec > > bitmap: 13/15 pages [52KB], 65536KB chunk > > > > unused devices: <none> > > I suspected once that something would not stop correctly before shutting > down, but how could you debug something like that? > > I already tried to replug all SATA cables - without success. In the > meantime even a new mainboard/CPU/RAM is installed and one of the two > SATA 2TB disks is replaced by a new one. But the the problem remained :-/ > > While searching the internet I found a partially similar problem [1] but > without an solution. > > Does anyone have any idea how I could narrow down or fix the problem? > > Thanks a lot! > > [1] https://www.spinics.net/lists/raid/msg47475.html > -- > kind regards > mathias
