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

    • Resolved
    • OMV 4.x
    • geaves wrote:

      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 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • mrpg wrote:

      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 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Hi,

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

      Source Code

      1. root@pgnas2:~# fsck.ext4 -f /dev/md127
      2. e2fsck 1.43.4 (31-Jan-2017)
      3. Pass 1: Checking inodes, blocks, and sizes
      4. Inode 150011953 extent tree (at level 1) could be narrower. Fix<y>? yes
      5. Inode 150143135 extent tree (at level 2) could be narrower. Fix<y>? yes
      6. Inode 150340913 extent tree (at level 2) could be narrower. Fix<y>? yes
      7. Inode 150627266 extent tree (at level 2) could be narrower. Fix<y>? yes
      8. Inode 150627273 extent tree (at level 1) could be narrower. Fix<y>? yes
      9. Inode 150627291 extent tree (at level 2) could be narrower. Fix<y>? yes
      10. yInode 173017914 extent tree (at level 1) could be narrower. Fix<y>? yes
      11. Inode 177409638 extent tree (at level 1) could be narrower. Fix<y>? yes
      12. Pass 1E: Optimizing extent trees
      13. Pass 2: Checking directory structure
      14. Pass 3: Checking directory connectivity
      15. Pass 4: Checking reference counts
      16. Pass 5: Checking group summary information
      17. pgnas2: ***** FILE SYSTEM WAS MODIFIED *****
      18. pgnas2: 360942/274702336 files (1.2% non-contiguous), 2014241798/2197601280 blocks
      Display All
      Reboot

      Source Code

      1. root@pgnas2:~# blkid /dev/md127
      2. root@pgnas2:~#


      Source Code

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

      So i ran it again :

      Source Code

      1. root@pgnas2:~# fsck.ext4 -f /dev/md127
      2. e2fsck 1.43.4 (31-Jan-2017)
      3. Pass 1: Checking inodes, blocks, and sizes
      4. Pass 2: Checking directory structure
      5. Pass 3: Checking directory connectivity
      6. Pass 4: Checking reference counts
      7. Pass 5: Checking group summary information
      8. pgnas2: 360942/274702336 files (1.2% non-contiguous), 2014241798/2197601280 blocks

      Source Code

      1. root@pgnas2:~# tune2fs -U $(uuid) /dev/md127
      2. tune2fs 1.43.4 (31-Jan-2017)
      3. Setting UUID on a checksummed filesystem could take some time.
      4. Proceed anyway (or wait 5 seconds) ? (y,N) <proceeding>

      reboot


      Source Code

      1. root@pgnas2:~# blkid /dev/md127
      2. root@pgnas2:~#

      The post was edited 1 time, last by mrpg ().

    • Well, that's fun. What is the output of: wipefs --no-act /dev/md127 (no it won't wipe your drive)
      omv 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • hehe , i am not sure i agree that's its very funny, but it made me laugh anyway :)

      Brainfuck Source Code

      1. root@pgnas2:~# wipefs --no-act /dev/md127
      2. offset type
      3. ----------------------------------------------------------------
      4. 0x82fcbbbf000 zfs_member [filesystem]
      5. LABEL: zfsvol1
      6. UUID: 9642737082427346663
      7. 0x438 ext4 [filesystem]
      8. LABEL: pgnas2
      9. UUID: 4d724f4a-bdf8-11e9-8883-5fb4dd051701
      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

      The post was edited 1 time, last by mrpg ().

    • mrpg wrote:

      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?

      ryecoaaron wrote:

      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 4.1.23 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Fantastic!

      Thank you soo much @ryecoaaron

      After a marathon of :

      Source Code

      1. wipefs --no-act /dev/md127
      2. and
      3. wipefs --offset 0x82fcbbe0000 /dev/md127


      Source Code

      1. blkid /dev/md127
      2. /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
    • Users Online 1

      1 Guest