Each 2nd boot resync

  • Hi there,


    mostly each time, as soon as I reboot / boot my NAS it is resyncing. About two weeks ago I got a SMART Error nearly on all of my disks " ATA error count increased from 4 to 6". The SMART error seems to be disappeard so far.



    So, what shall I do now? It's annoying to wait for so long time.

  • I'm quite not sure if my disks are really dying.


    It's strange, cause I'm getting the SMART Error mails for all of my five NAS RAID disks. All the mails contain "ATA error count increased from 4 to 5". I think it is not a cable related issue. The temperatures look so far fine.


    Maybe my Mainboard seems to generate such errors ?


    Smart just says:
    [sorry had to post it down into 3 separate posts.]


    • Offizieller Beitrag

    Read here about smart https://www.backblaze.com/blog/hard-drive-smart-stats/


    Also if I recall someone mentioned the wd reds 3tb are disks to avoid. Quality problems, 2 and 4tb apparently ok.



    i recall a case here were the problem was that the disk weren't wiped initially for the raid causing constant re synching at boot .



    I am stil waiting for the commands form the sticky post it would be good also that you post dmesg as an attachment .

  • I am using OMV now, since April, 2013. The issues has just appeared now ~ 2 years later.
    here is the requested output:




    Code
    root@NAS:~# cat /proc/mdstat
    Personalities : [raid6] [raid5] [raid4]
    md127 : active raid5 sdc[0] sdb[5] sdf[3] sde[2] sdd[4]
          11721060352 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]
          [=====>...............]  resync = 25.3% (743292928/2930265088) finish=262.9min speed=138640K/sec
    
    
    unused devices: <none>


    Code
    /dev/sda1: UUID="7e1eb966-ab72-44fd-a601-48d92291b67f" TYPE="ext4"
    /dev/sda5: UUID="875ba166-bcfe-4a35-a051-f239ad0b27a4" TYPE="swap"
    /dev/sdd: UUID="3dd4ca91-9424-6d7c-e3ec-592f1ca94161" UUID_SUB="0e40e778-b03d-000b-b654-a626e8b6d7fc" LABEL="NAS:Raid5" TYPE="linux_raid_member"
    /dev/sde: UUID="3dd4ca91-9424-6d7c-e3ec-592f1ca94161" UUID_SUB="726e968d-91b2-f293-18c0-e55f8899017f" LABEL="NAS:Raid5" TYPE="linux_raid_member"
    /dev/md127: LABEL="Raid5" UUID="9caa7155-ffb5-4235-8b71-4a563f17273f" TYPE="ext4"
    /dev/sdc: UUID="3dd4ca91-9424-6d7c-e3ec-592f1ca94161" UUID_SUB="c0f05dbe-130c-0dc7-a19f-bf3f8ea3f5b0" LABEL="NAS:Raid5" TYPE="linux_raid_member"
    /dev/sdf: UUID="3dd4ca91-9424-6d7c-e3ec-592f1ca94161" UUID_SUB="88ec22c3-d4f4-54bc-5ed5-0dbbc3654f3a" LABEL="NAS:Raid5" TYPE="linux_raid_member"
    /dev/sdb: UUID="3dd4ca91-9424-6d7c-e3ec-592f1ca94161" UUID_SUB="116d4e29-25a3-d5f0-8e27-7d3bf1df2478" LABEL="NAS:Raid5" TYPE="linux_raid_member"


    • Offizieller Beitrag

    Maybe your power supply is getting weak? It looks like the errors happen when it is trying to spin up. Because one or more spin up late, it causes problems with raid array.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Oh yeah, at all a good point. I'll have to watch out now for a different power supply. Thank you


    Really strange, due to my issues with suspending and waking up my nas, the resync process will be set up each time as the procedure fails:





    Additionally I didnt get the SMART error so far.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!