[SOLVED] Grow RAID5 array failure

  • Sigh...


    The command "cat /proc/mdstat" confirms that md127 is no more present:

    Code
    root@DIYNAS-OMV:~# cat /proc/mdstat
    Personalities : [raid0] [raid6] [raid5] [raid4] [linear] [multipath] [raid1] [raid10]
    md0 : active raid5 sdb[2] sda[3] sdf[0] sde[1] sdc[4]
    23441567744 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]
    bitmap: 0/44 pages [0KB], 65536KB chunk



    ...but the "grow" fails again (but with different message) ;(


  • I noticed that "/dev/sdd" is now present in the RAID Array list, but as a spare disk:

  • This is the output:

    Code
    root@DIYNAS-OMV:~# mdadm --grow --raid-devices=6 /dev/md0
    mdadm: ARRAY line /dev/md/ddf0 has no identity information.


    And this is what appears in GUI:


    I suppose we've to wait a lot... ;):D

  • That explains that error, I wonder where that came from, cos that doesn't look like an OMV setup but it could be OMV picked up some metadata from a drive/s

    Raid is not a backup! Would you go skydiving without a parachute?

  • What does that means

    Pass, sorry

    And what do I have to do to eventually solve (without risks)

    Pass again, seen this once before when a user was having an issue with a Raid50, it was never really looked at, it's there, it's doing nothing and will not affect your system

    Raid is not a backup! Would you go skydiving without a parachute?

  • BTW you have now moved into what I call 'squeaky bum' territory, 6 drives in a Raid5 8| 'rule of thumb' is, once you get over 4 drives move to Raid6 especially when using larger drives.

    Raid is not a backup! Would you go skydiving without a parachute?

  • mbinax

    Changed the title of the thread from “Grow RAID5 array failure” to “[SOLVED] Grow RAID5 array failure”.
  • mbinax

    Added the Label OMV 5.x
  • mbinax

    Added the Label resolved

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!