Missing file system after upgrade from 3.x to 4.x

    • OMV 4.x
    • Upgrade 3.x -> 4.x
    • New

      This is a new one

      logged in as root

      run /proc/mdstat

      get Permission denied error

      root@omv2:~# /proc/mdstat
      bash: /proc/mdstat: Permission denied
      root@omv2:~#


      So I ran:

      root@omv2:~# cat /proc/mdstat
      Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
      md127 : active (auto-read-only) raid5 sdc[1] sde[3] sdb[0] sdd[2]
      8790405120 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
      unused devices: <none>
      root@omv2:~#

      Then ran:
      root@omv2:~# mdadm --readwrite /dev/md127
      root@omv2:~# cat /proc/mdstat
      Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
      md127 : active raid5 sdc[1] sde[3] sdb[0] sdd[2]
      8790405120 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
      unused devices: <none>
      root@omv2:~#


      Shows active raid5 now

      rebooted

      file system still shows as:
      referenced = yes
      mounted = no
      Status = missing

      this is turning into a real puzzle ;)


      any more advice?

      thanks for all your help.
    • New

      ggibeau wrote:

      Shows active raid5 now

      rebooted
      Your array was fixed with the command but after rebooting, it is probably going into auto-read-only again. This generally happens when something is wrong with the array/drive in the array. I would fix it with the readwrite command again and then omv-mkconf mdadm. Leave the system on for a while to make sure everything is happening on the array that needs to happen.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      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!
    • New

      Ran these commands with these results - - will leave on for awhile without touching to see what happens.

      Thanks

      root@omv2:~# cat /proc/mdstat

      Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
      md127 : active (auto-read-only) raid5 sdb[0] sdc[1] sdd[2] sde[3]
      8790405120 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]

      unused devices: <none>

      root@omv2:~# mdadm --readwrite /dev/md127

      root@omv2:~# cat /proc/mdstat

      Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
      md127 : active raid5 sdb[0] sdc[1] sdd[2] sde[3]
      8790405120 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]

      unused devices: <none>

      root@omv2:~# omv-mkconf mdadm

      update-initramfs: Generating /boot/initrd.img-4.18.0-0.bpo.1-amd64
      update-initramfs: Generating /boot/initrd.img-4.9.0-8-amd64
      update-initramfs: Generating /boot/initrd.img-4.9.0-0.bpo.6-amd64

      root@omv2:~#
    • New

      ggibeau wrote:

      file system still showing as missing
      If the array starts in auto-read-only mode every time you reboot, there is something wrong with the array. I'm not sure what is causing the issue though. Maybe google has an answer.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      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!
    • Users Online 1

      1 Guest