15 Nov
2021
15 Nov
'21
07:33
Hi David and thanks for your detailed guidance.
As I just wrote in my previous letter to the list I think I misinterpreted
what was happening. The raid is not rebuilding but trying to run a integrity
check. I have never noticed this before, but on the other hand I have never
had disks this size in a old low performance pc.
On 15. november 2021 05.04.40 CET David C. Rankin wrote:
> On 11/14/21 3:56 AM, Klaus Vink Slott wrote:
> > Hi.
> >
> > I use a retired office pc with core i5 with as a NAS. I have dropped in 2
> > disks (3.5T sata) and configured as md raid1 and with lvm on top. It has
> > worked flawless for a year or so, but now after the latest 2 reboots it
> > has triggered a raid rebuilding.
> >
> > Only thing I find in dmesg (but I am not sure what to search for)
> >
> > klaus@raagi:~> sudo dmesg | grep " md"
> > [ 4.131071] md/raid1:md127: active with 2 out of 2 mirrors
> > [ 4.282183] md127: detected capacity change from 0 to 4000261472256
> > [ 64.407382] md: data-check of RAID array md127
^^^^^^^^^
data-check, not rebuilding
> > [21681.409218] md: md127: data-check interrupted.
> > [25477.760407] md: data-check of RAID array md127
> > [47096.271827] md: md127: data-check interrupted.
> >
> > I left the PC running after reboot, so I am not sure why the data-check
> > was interrupted.
> >
> > Any ideas on why it has started to rebuild after every reboot?
>
> Also, add details about what OS, Release or at least the kernel, mdadm and
> LVM versions. (LVM shouldn't matter)
OpenSUSE 15.3 LEAP
Linux raagi 5.3.18-59.27-default #1 SMP Tue Oct 5 10:00:40 UTC 2021 (7df2404)
x86_64 x86_64 x86_64 GNU/Linux
> First thing I would check is 'smartctl -a /dev/drive'
SMART overall-health self-assessment test result: PASSED
- on both drives
> 'mdadm -D /dev/md127' (as root).
...
Number Major Minor RaidDevice State
0 8 18 0 active sync /dev/sdb2
1 8 2 1 active sync /dev/sda2
> (look at last two lines here
Seem ok
> BACKUP your DATA from the GOOD disk NOW! (fix the problem after that)
No worries. Data is mirrored to another location, and borgbackup keeps data
safe on a third location.
So I ventured down into /etc/sysconfig/mdadm and found MDADM_CHECK_DURATION
# Amount of time to spend checking md arrays each morning.
# A check will start on the first Sunday of the month and run
# for this long. If it does not complete, then it will be
# continued each subsequent morning until all arrays have
# been checked. Any string understood by "date --date="
# can be used. An empty string disables automatic checks.
So taken in account that I have quite big disks on a relativly low performance
system it is more that likely that this what I saw, and also the reason why
the check gets interrupted.
--
Regards
Klaus