migration OMV4 to OMV6 files on raid5 missing

NicolasB · 4. März 2023

Good morning,

it's a little panic on my side, I pray that someone can help me...

I had an OMV v4 nas server, in an HP Proliant micro Server N54L, connected to the network in rj45, which contains 1 SSD of 64Gb with the OS on it, and 4 hard disks of 3 Tb each, mounted in raid 5.

above I used the samba and miniDLNA services…

That was 4 days ago...

And the spiral begins...

Impossible to access my films in DLNA with neither the box, nor the TV, nor the rPi in media player, nor chrome cast…

Samba access via my laptop and a small landline disconnect after 20sec to about 10min, the same for the admin interface…

I interpret this as an announced end... I still manage to see the SMART log of my disks and, from memory, everything is "clean"... (I no longer have a precise memory of the logs: Frowning:

I said to myself then that it might be time to migrate from version of OMV I look… we are at version 6… I download it…

Some time ago I had already succeeded in migrating from OMV v3 => v4 everything went well and it automatically found raid 5, my 4 root directories, and all the data there. on discs...

I therefore install OMV v6, I do a “sudo apt update” followed by a “sudo apt upgrade”, I enter the interface…

and there the drama… I no longer see my root directories… (as was the case in the installation of omv v3 to v4)

I can see the disks in raid 5 with the "Clean" notation but where did my data go?

and in addition there is a notion of "mounting volume" that I hesitate to do for fear of losing my data...

here some log from ssh:

Code

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ~# sfdisk -l
Disk /dev/sda: 2,73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EZRX-00S
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdb: 2,73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EZRX-00S
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdc: 2,73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EZRX-00S
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sdd: 2,73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: WDC WD30EZRX-00S
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sde: 58,69 GiB, 63023063040 bytes, 123091920 sectors
Disk model: SanDisk SDSSDP06
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xab072bde

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sde1  *         2048 121092095 121090048 57,7G 83 Linux
/dev/sde2       121094142 123090943   1996802  975M  5 Extended
/dev/sde5       121094144 123090943   1996800  975M 82 Linux swap / Solaris


Disk /dev/md127: 8,19 TiB, 9001374842880 bytes, 17580810240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1572864 bytes

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ~# blkid
/dev/sda: UUID="f125d73b-17d5-0597-dd60-db60ff557073" UUID_SUB="163f9575-1204-c670-407f-a9648abb5acc" LABEL="OMV1:DdRaid5" TYPE="linux_raid_member"
/dev/sdb: UUID="f125d73b-17d5-0597-dd60-db60ff557073" UUID_SUB="a65a3112-c7db-a0e4-03e7-8f4f19d265e4" LABEL="OMV1:DdRaid5" TYPE="linux_raid_member"
/dev/sdc: UUID="f125d73b-17d5-0597-dd60-db60ff557073" UUID_SUB="7a286c96-71b2-5fca-06b5-578b07e937d7" LABEL="OMV1:DdRaid5" TYPE="linux_raid_member"
/dev/sdd: UUID="f125d73b-17d5-0597-dd60-db60ff557073" UUID_SUB="f4d8aaae-4f6d-40f6-a9f3-38a1aedfa0c8" LABEL="OMV1:DdRaid5" TYPE="linux_raid_member"
/dev/sde1: UUID="08c3871d-7232-4b4f-9acc-8f521db0dc1a" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="ab072bde-01"
/dev/sde5: UUID="4ea674ac-b4cb-40ef-9922-56260fa48d88" TYPE="swap" PARTUUID="ab072bde-05"
/dev/md127: LABEL="Fil1" UUID="dad71d93-597e-435e-b28f-10ac4bd46498" BLOCK_SIZE="4096" TYPE="ext4"

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ~# mdadm --examine /dev/sda
/dev/sda:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : f125d73b:17d50597:dd60db60:ff557073
           Name : OMV1:DdRaid5
  Creation Time : Fri Oct 17 09:01:47 2014
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5860271024 sectors (2.73 TiB 3.00 TB)
     Array Size : 8790405120 KiB (8.19 TiB 9.00 TB)
  Used Dev Size : 5860270080 sectors (2.73 TiB 3.00 TB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
   Unused Space : before=262064 sectors, after=944 sectors
          State : clean
    Device UUID : 163f9575:1204c670:407fa964:8abb5acc

    Update Time : Fri Mar  3 10:58:06 2023
       Checksum : 93b64bad - correct
         Events : 1562

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 0
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
   
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ~# mdadm --examine /dev/sdb
/dev/sdb:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : f125d73b:17d50597:dd60db60:ff557073
           Name : OMV1:DdRaid5
  Creation Time : Fri Oct 17 09:01:47 2014
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5860271024 sectors (2.73 TiB 3.00 TB)
     Array Size : 8790405120 KiB (8.19 TiB 9.00 TB)
  Used Dev Size : 5860270080 sectors (2.73 TiB 3.00 TB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
   Unused Space : before=262064 sectors, after=944 sectors
          State : clean
    Device UUID : a65a3112:c7dba0e4:03e78f4f:19d265e4

    Update Time : Fri Mar  3 10:58:06 2023
       Checksum : a71ebd45 - correct
         Events : 1562

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 1
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
   
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ~# mdadm --examine /dev/sdc
/dev/sdc:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : f125d73b:17d50597:dd60db60:ff557073
           Name : OMV1:DdRaid5
  Creation Time : Fri Oct 17 09:01:47 2014
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5860271024 sectors (2.73 TiB 3.00 TB)
     Array Size : 8790405120 KiB (8.19 TiB 9.00 TB)
  Used Dev Size : 5860270080 sectors (2.73 TiB 3.00 TB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
   Unused Space : before=262064 sectors, after=944 sectors
          State : clean
    Device UUID : 7a286c96:71b25fca:06b5578b:07e937d7

    Update Time : Fri Mar  3 10:58:06 2023
       Checksum : 3fb246b6 - correct
         Events : 1562

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 2
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ~# mdadm --examine /dev/sdd
/dev/sdd:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : f125d73b:17d50597:dd60db60:ff557073
           Name : OMV1:DdRaid5
  Creation Time : Fri Oct 17 09:01:47 2014
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5860271024 sectors (2.73 TiB 3.00 TB)
     Array Size : 8790405120 KiB (8.19 TiB 9.00 TB)
  Used Dev Size : 5860270080 sectors (2.73 TiB 3.00 TB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
   Unused Space : before=262064 sectors, after=944 sectors
          State : clean
    Device UUID : f4d8aaae:4f6d40f6:a9f338a1:aedfa0c8

    Update Time : Fri Mar  3 10:58:06 2023
       Checksum : 8b1be759 - correct
         Events : 1562

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 3
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
   
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ~# mdadm --detail /dev/md127
/dev/md127:
           Version : 1.2
     Creation Time : Fri Oct 17 09:01:47 2014
        Raid Level : raid5
        Array Size : 8790405120 (8.19 TiB 9.00 TB)
     Used Dev Size : 2930135040 (2.73 TiB 3.00 TB)
      Raid Devices : 4
     Total Devices : 4
       Persistence : Superblock is persistent

       Update Time : Fri Mar  3 10:58:06 2023
             State : clean
    Active Devices : 4
   Working Devices : 4
    Failed Devices : 0
     Spare Devices : 0

            Layout : left-symmetric
        Chunk Size : 512K

Consistency Policy : resync

              Name : OMV1:DdRaid5
              UUID : f125d73b:17d50597:dd60db60:ff557073
            Events : 1562

    Number   Major   Minor   RaidDevice State
       0       8        0        0      active sync   /dev/sda
       1       8       16        1      active sync   /dev/sdb
       2       8       32        2      active sync   /dev/sdc
       3       8       48        3      active sync   /dev/sdd

Alles anzeigen

I'm counting on you to help me

THANKS

macom · 4. März 2023

You have to mount the filesystem on your RAID. Then create shared folders pointing at the existing folders on the RAID filesystem. For this you can use the browsing functionality.

NicolasB · 4. März 2023

Unfortunately, I can't do that because it only offers me my OS disk and not raid 5...

and I don't want to create new directories, I would like to find my old data which is on raid 5 but how?

macom · 5. März 2023

In your second picture it shows /dev/md127. That is your raid. Can't you select it to mount it?

Zitat von NicolasB

I don't want to create new directories, I would like to find my old data which is on raid 5 but how?

If you are using the browsing function, it does not create new directories. It creates shared folders pointing at the directories you selected. Maybe you need to switch the language of the GUI to English to understand what I mean with "shared folders"

NicolasB · 5. März 2023

Zitat von macom

In your second picture it shows /dev/md127. That is your raid. Can't you select it to mount it?

sorry, there is nothing , no selected item in file systems or shared folder or browsing tree

what could i do???

geaves · 5. März 2023

In your second image in #3 your raid is showing under mount, click on it then click save apply changes then the array will mount

NicolasB · 6. März 2023

I got there, you just had to go through the OMV GUI and not be afraid to click on "validate".

I found all my data

thank you, thank you, thank you

Jetzt mitmachen!