After Upgrade to 4.1.23-1 my mdraid is not mounted etc

  • This was the part I understood, but didn't know how to rectify it

    I have a few ideas on how to fix it depending on the output of some commands. Unfortunately, I don't know how to create the situation to try the solutions on my side.

    omv 5.5.5 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.5
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Hi,
    This does not bode well? :(




    Code
    root@pgnas2:~# partprobe -s

    and it has been sitting there still running/hung , should you get a fast response to the command? , have waited around 3 minutes now

    Code
    root@pgnas2:~# blkid /dev/md127
    root@pgnas2:~#
  • should you get a fast response to the command?

    It took six seconds on my test VM that has 45 drives.


    Here is what I would try to fix it:


    reboot


    # run fsck
    fsck.ext4 -f /dev/md127


    reboot


    That may have been enough to fix it. Is there any output from blkid /dev/md127? If not, move to next step


    # change the uuid of the filesystem
    tune2fs -U $(uuid) /dev/md127


    reboot


    That may have been enough to fix it. Is there any output from blkid /dev/md127? If not, I need to think of something else.

    omv 5.5.5 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.5
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Hi,


    I appreciate your help so very much! , thank you!


    Reboot


    Code
    root@pgnas2:~# blkid /dev/md127
    root@pgnas2:~#


    Code
    tune2fs -U $(uuid) /dev/md127
    tune2fs 1.43.4 (31-Jan-2017)
    Please run e2fsck -f on the filesystem.


    So i ran it again :


    Code
    root@pgnas2:~# fsck.ext4 -f /dev/md127
    e2fsck 1.43.4 (31-Jan-2017)
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    pgnas2: 360942/274702336 files (1.2% non-contiguous), 2014241798/2197601280 blocks
    Code
    root@pgnas2:~# tune2fs -U $(uuid) /dev/md127
    tune2fs 1.43.4 (31-Jan-2017)
    Setting UUID on a checksummed filesystem could take some time.
    Proceed anyway (or wait 5 seconds) ? (y,N) <proceeding>


    reboot



    Code
    root@pgnas2:~# blkid /dev/md127
    root@pgnas2:~#
  • hehe , i am not sure i agree that's its very funny, but it made me laugh anyway :)


    EDIT : is it not strange that zfs_member is listed here? , when we are asking to view /dev/md127
    to give you some background, before the upgrade, i had a three disk zfs volume , and two disks died, so i physically removed those three disks from my box (data loss, but hey raid is not backup)


    Br
    /Patric

  • EDIT : is it not strange that zfs_member is listed here? , when we are asking to view /dev/md127
    to give you some background, before the upgrade, i had a three disk zfs volume , and two disks died, so i physically removed those three disks from my box (data loss, but hey raid is not backup)

    FINALLY!!!! Yes, it is a huge problem that the zfs signature is on the array or disk. Remember this line in my first post on this thread?

    I don't have time to reread all of these posts but we see this a lot when moving to OMV 4.x because there are existing zfs signatures on the mdadm array disks

    You are going to have to wipe the zfs signature with wipefs. There will probably be more than one signature. So, you will have to repeat the following steps many times.


    wipefs --no-act /dev/md127


    get the offset from the zfs signature


    wipefs --offset 0x82fcbbbf000 /dev/md127

    omv 5.5.5 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.5
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Fantastic!


    Thank you soo much @ryecoaaron


    After a marathon of :


    Code
    wipefs --no-act /dev/md127
    and
    wipefs --offset 0x82fcbbe0000 /dev/md127


    Code
    blkid /dev/md127
    /dev/md127: LABEL="pgnas2" UUID="4d724f4a-bdf8-11e9-8883-5fb4dd051701" TYPE="ext4"


    and the arrray is now also listed under filesystems in the gui :)


    is openmediavault open for donations? , i would like to contribute to your team!


    Best Regards
    Patric

Participate now!

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