Dear OMV Community
I am a starter when it comes to running servers and software suits like openmediavault.
After running my rasberryPi 4 server with OMV 5.10.103-v7l+ for arround 1 year connected with my qnap tr-004 storage over USB3 ( Hardware RAID 10 - 4 Disk of 4 TB each)
one disk failed a few days ago. Because this was my first failure ever I directly bought a new disk and switched it with the faulty one.
One main problem I forgot was doing the rebuild with openmediavault after reading alot of posts here now. Instead I connected the storage box to my windows device, and let the qnap software rebuild the raid (all disks where green after the rebuild). The next thing I did, I hooked it back up to the openmediavault server and now the web gui says I got a missing file system. I know if I had knewn more about it I would certainly have followed the steps on the forum here first but
I thought fixing the raid problem with the software that came with the storagebox was primarly.
Therefor I now ask for your help to solve this issue if it is still posible.
The commands I first run for diagnostic data are the next ones
Command: cat /proc/mdstat
root@openmediavault:~# cat /proc/mdstat
cat: /proc/mdstat: No such file or directory
Command: lsblk
root@openmediavault:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 256M 0 part /boot
└─sda2 8:2 0 465.5G 0 part /
sdb 8:16 0 7.3T 0 disk
Command: grepdisk
root@openmediavault:~# fdisk -l | grep "Disk "
The primary GPT table is corrupt, but the backup appears OK, so that will be used.
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram8: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram9: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram10: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram11: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram12: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram13: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram14: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/ram15: 4 MiB, 4194304 bytes, 8192 sectors
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Forty
Disk identifier: 0x1e168b04
Disk /dev/sdb: 7.3 TiB, 8001456963584 bytes, 15627845632 sectors
Disk model: TR-004 DISK00
Disk identifier: 0E5DD83B-7627-47B6-B69E-DD4C0163A147
Command: cat /etc/mdadm/mdadm.conf
root@openmediavault:~# cat /etc/mdadm/mdadm.conf
# 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
What I found so far on the forum is that in most cases cat: /proc/mdstat should output something
to continue with but for me it can't find anything
With the fdisk -l | grep "Disk " I get the message: "The primary GPT table is corrupt, but the backup appears OK, so that will be used. "
Does this means there is still hope for a solution?
The screenshots I included are the one with the missing filesystem from de OMV Web GUI and my storage units.
The raid management screen is empty.
If someone know how to fix this problem and help me through this
very much appreciated.
If you need more information I can provide it
Kind Regards
ShadowVault