After hard update the Raid 1 hdd shown as empty

Triebwerk · Nov 28th 2019, 6:46pm

geaves wrote:

mdadm --stop /dev/md127

root@openmediavault:~# mdadm --stop /dev/md127
mdadm: stopped /dev/md127

geaves wrote:

mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]

root@openmediavault:~# mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb is identified as a member of /dev/md127, slot 1.
mdadm: /dev/sdc is identified as a member of /dev/md127, slot 0.
mdadm: added /dev/sdb to /dev/md127 as 1 (possibly out of date)
mdadm: added /dev/sdc to /dev/md127 as 0
mdadm: /dev/md127 has been started with 1 drive (out of 2).
root@openmediavault:~#

geaves · Nov 28th 2019, 7:40pm

mdadm --stop /dev/md127
mdadm --zero-superblock /dev/sdb
mdadm --add /dev/md127 /dev/sdb

The raid should now rebuild, to check;
cat /proc/mdstat

Triebwerk · Nov 28th 2019, 7:44pm

geaves wrote:

mdadm --stop /dev/md127
mdadm --zero-superblock /dev/sdb
mdadm --add /dev/md127 /dev/sdb

root@openmediavault:~# mdadm --stop /dev/md127
mdadm: stopped /dev/md127
root@openmediavault:~# mdadm --zero-superblock /dev/sdb
root@openmediavault:~# mdadm --add /dev/md127 /dev/sdb
mdadm: Cannot get array info for /dev/md127
root@openmediavault:~#

By the way. Many thanks to everybody for helping me. I really appricate it.

geaves · Nov 28th 2019, 7:59pm

Triebwerk wrote:

mdadm: Cannot get array info for /dev/md127

That I assume was after trying to add the drive, the output implies it's looking at/for mdadm.conf

If the raid is till stopped, which it should be try this again mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]

Need to get it back together before creating the config file.

BTW, does it show as clean/degraded in the GUI

Triebwerk · Nov 28th 2019, 8:06pm

geaves wrote:

mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]

root@openmediavault:~# mdadm --assemble --force --verbose /dev/md127 /dev/sd[bc]
mdadm: looking for devices for /dev/md127
mdadm: no recogniseable superblock on /dev/sdb
mdadm: /dev/sdb has no superblock - assembly aborted
root@openmediavault:~#

The WebGUI shows 3 drives the system drive (sda), and the two raid drives (sdb + sdc).

If I try to create a raid only sdb is shown. Don't know what went wrong.

geaves · Nov 28th 2019, 8:26pm

Under raid management is there no raid displayed at all.

Triebwerk · Nov 28th 2019, 8:36pm

No it isn't.

geaves · Nov 28th 2019, 8:48pm

Ok, never seen this before, so lets's try something

mdadm --assemble /dev/md127 /dev/sdc

after that does it appear under Raid management

Triebwerk · Nov 28th 2019, 8:56pm

geaves wrote:

mdadm --assemble /dev/md127 /dev/sdc

root@openmediavault:~# mdadm --assemble /dev/md127 /dev/sdc
mdadm: /dev/md127 has been started with 1 drive (out of 2).
root@openmediavault:~#

Now there is a raid shown, but just with one singe device (sdc) and the name of the drive is /dev/md127.

geaves · Nov 28th 2019, 9:08pm

Triebwerk wrote:

Now there is a raid shown, but just with one singe device (sdc) and the name of the drive is /dev/md127.

Does it show as clean/degraded

Triebwerk · Nov 28th 2019, 9:21pm

Yes it does.

geaves · Nov 28th 2019, 9:25pm

OK, select the raid by just clicking on it, then on the menu click recover, a dialog box will appear if /dev/sdb is shown select it (a tick will appear in the check box) click ok.

Triebwerk · Nov 28th 2019, 9:28pm

Now it got 2 devices (sdb + sdc) and show a rising percentige of recovering.

It' seems to work now.

geaves · Nov 28th 2019, 9:30pm

Triebwerk wrote:

Now it got 2 devices (sdb + sdc) and show a rising percentige of recovering.

when it's finished run omv-mkconf mdadm don't run it before.

Triebwerk · Nov 28th 2019, 9:35pm

Okay. If the remaining time is shown correct it will take nearly 3 hours. I will run it and tomorrow morning I will run the comand you gave me and I will report it here.

Many, many thanks for your help. I'm sure that I won't make it to this point without your outstanding help.

Triebwerk · Nov 30th 2019, 12:10am

Back agin. Now both drives are recognized but it seems the data of the drives are gone.

How can I get back the data ?

geaves · Nov 30th 2019, 8:09am

Triebwerk wrote:

Now both drives are recognized but it seems the data of the drives are gone.

The data is there the shares are missing in OMV that will display the data, use WinSCP or Filexilla if you have Windows and look in /srv

Triebwerk · Nov 30th 2019, 9:47am

I used WinSCP and the only content in srv is a ftp folder with a file called welcome.msg nothing else. I don't know why there is a ftp folder, because I never used ftp. Not in the previous version (OMV 2.x) and also not in the actual (OMV 4.x)

geaves · Nov 30th 2019, 10:18am

Triebwerk wrote:

I used WinSCP and the only content in srv is a ftp folder with a file called welcome.msg nothing else. I don't know why there is a ftp folder, because I never used ftp. Not in the previous version (OMV 2.x) and also not in the actual (OMV 4.x)

Ah! You had a previous running OMV2 and as @votdev pointed out the norm to upgrade was to backup, wipe the drives and recreate the array in OMV4.

I started using OMV from v3 the upgrade to OMV4 was straightforward, I am wondering if the mount point in OMV2 was in a different folder, you need some help from others @macom @ryecoaaron thanks.

macom · Nov 30th 2019, 10:30am

Before /srv/ filesystems were mounted in /media/