Cannot mound raid after reinstall

answer35 · 4. August 2020

Hello there,

I face an issue that make me nervous.

I was using OMV5 until four days ago. Then I started to have some issues with no space available on disk for docker and after some trials it was working but I think slower than before.

Two days later, it was really slow for everything and the reverse proxy that I used to have on it wasn't responding most of the time.

I decided then to reinstall OMV with a fresh install.

Once it was reinstalled, the RAID wasn't recognize because of an issue with one of the disk. Then I made a wipe of that disk and I was able to rebuild the RAID5.

After two days of resync, the RAID is not in state clean. My issue now is that I cannot mount it because it is not in file system and if I want to create a new one with the RAID it ask me to format it but I still have all my datas on it that I don't want to lose.

Is there anyone to help please ?

answer35 · 5. August 2020

to follow what I could have seen on different subject here are results on different commands :

cat /proc/mdstat

Code

Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md127 : active (auto-read-only) raid5 sdd[2] sdc[1] sdb[0]
      5860268032 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
      bitmap: 0/22 pages [0KB], 65536KB chunk

unused devices: <none>

blkid

Code

/dev/sdb: UUID="924d38d8-fecc-e75e-654f-9379b1a9e7d1" UUID_SUB="9a2acb5c-1177-66fc-1d39-adeff118dffa" LABEL="Serveur:NASData" TYPE="linux_raid_member"
/dev/sdc: UUID="924d38d8-fecc-e75e-654f-9379b1a9e7d1" UUID_SUB="56138d00-7fe4-a6c9-9b30-276862295417" LABEL="Serveur:NASData" TYPE="linux_raid_member"
/dev/sda1: UUID="04ca02fe-0dff-494f-989d-dd6be1a2c45f" TYPE="ext4" PARTUUID="649c6604-01"
/dev/sda5: UUID="4b0360fe-eff6-4e78-aa11-846f8b97f368" TYPE="swap" PARTUUID="649c6604-05"
/dev/sdd: UUID="924d38d8-fecc-e75e-654f-9379b1a9e7d1" UUID_SUB="bf1f4d56-adc6-dd5e-c32a-70fa08966f09" LABEL="Serveur:NASData" TYPE="linux_raid_member"

fdisk -l | grep "Disk "

Code

Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: ST3000VN000-1HJ1
Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: ST3000VN000-1HJ1
Disk /dev/sda: 55.9 GiB, 60022480896 bytes, 117231408 sectors
Disk model: KINGSTON SV300S3
Disk identifier: 0x649c6604
Disk /dev/md127: 5.5 TiB, 6000914464768 bytes, 11720536064 sectors
Disk /dev/sdd: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: ST3000VN000-1HJ1

cat /etc/mdadm/mdadm.conf

Code

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# definitions of existing MD arrays
ARRAY /dev/md127 metadata=1.2 name=Serveur:NASData UUID=924d38d8:fecce75e:654f9379:b1a9e7d1

Alles anzeigen

mdadm --detail --scan --verbose

Code

ARRAY /dev/md127 level=raid5 num-devices=3 metadata=1.2 name=Serveur:NASData UUID=924d38d8:fecce75e:654f9379:b1a9e7d1
   devices=/dev/sdb,/dev/sdc,/dev/sdd

answer35 · 5. August 2020

From OMV Web-GUI interface here is my situation :

geaves · 5. August 2020

mdadm --readwrite /dev/md127 the array is active but in an auto-read-only state

answer35 · 5. August 2020

Okay I made it and it seems that it added a filesystem in /dev/sde. I looked at it quickly but I will take a better look if it is now okay or if something still missing. Thank you for your help

geaves · 5. August 2020

Zitat von answer35

Okay I made it and it seems that it added a filesystem in /dev/sde

Sorry I'm confused by the above, your array has 3 drives, dev/sd[bcd] in your first image the raid is clean with those 3 drives but it doesn't show in File Systems due to the auto-read-only, the command I posted should correct that.

answer35 · 5. August 2020

Oh I checked again after I needed to reboot the command you told me worked but I don't know what to do with this now

geaves · 5. August 2020

Zitat von answer35

after I needed to reboot

Why, OK if something doesn't work then reboot, what's the output of cat /proc/mdstat

answer35 · 5. August 2020

Code

Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md127 : active raid5 sdd[2] sdc[1] sdb[0]
      5860268032 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
      bitmap: 0/22 pages [0KB], 65536KB chunk

unused devices: <none>

geaves · 5. August 2020

The output is fine, the raid is active, so what's the problem

answer35 · 5. August 2020

I would like to have access to the files on it but the file system on OMV isn't there and it seems that I have to create a new one but then it will erase all my datas before. I don't know what happened because I already made new install before without losing anything.

geaves · 5. August 2020

OK, output cat /etc/fstab

answer35 · 5. August 2020

Code

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=04ca02fe-0dff-494f-989d-dd6be1a2c45f               /       ext4    noatime,nodiratime,errors=remount-ro    0 1
# swap was on /dev/sda5 during installation
UUID=4b0360fe-eff6-4e78-aa11-846f8b97f368 none            swap    sw              0       0

Alles anzeigen

Thank you for your help, you look like a 24/7 helper that's crazy

geaves · 5. August 2020

Ok, try mount -a, if there any errors post them, I have a feeling you're going to have to run something else

answer35 · 5. August 2020

no errors

geaves · 5. August 2020

has the raid mounted

answer35 · 5. August 2020

Is there any way to get my files back now already ?

geaves · 5. August 2020

Zitat von answer35

Is there any way to get my files back now already

Yes, but do one thing at a time, output of cat /etc/fstab

answer35 · 5. August 2020

Code

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=04ca02fe-0dff-494f-989d-dd6be1a2c45f               /       ext4    noatime,nodiratime,errors=remount-ro    0 1
# swap was on /dev/sda5 during installation
UUID=4b0360fe-eff6-4e78-aa11-846f8b97f368 none            swap    sw              0       0

Alles anzeigen

What do you mean, do one thing at a time ?

geaves · 6. August 2020

Zitat von answer35

What do you mean, do one thing at a time

Your raid isn't mounting, until that mounts you can do nothing, mount -a did nothing, so try mount /dev/md127 /srv

Jetzt mitmachen!