Hi,
I've upgraded my OMV 3 to newest 4.0.14-1 Arrakis. After that I've noticed that filesystem of RAID 1 is missing in "Filesystem" tab:
RAID1 labeled Matrix is mounted and in clean state:
also I've checked that by ssh, I can see files on Matrix raid.
Basic commands to troubleshoot problem:
cat /proc/mdstat
Code
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sde[1] sdd[0]
1953383488 blocks super 1.2 [2/2] [UU]
bitmap: 0/15 pages [0KB], 65536KB chunk
unused devices: <none>
blkid
Code
root@secure:/# blkid
/dev/sda1: LABEL="CACHE" UUID="a08721ac-0b40-4d34-8508-7550b76a803d" TYPE="ext4" PARTUUID="893c809b-01"
/dev/sdb2: UUID="d7446739-3636-4258-acef-4e44c1a374e2" TYPE="ext4" PARTUUID="64a507c7-361e-4c04-b4e2-aed8becdcb4c"
/dev/sdc1: LABEL="DataSSD" UUID="c26c316d-7469-45f0-b509-58eb516654bd" TYPE="ext4" PARTUUID="bff87c46-2a18-401f-a560-9d4e24208c4d"
/dev/sdd: UUID="df704e6d-b0ec-d791-5d09-09cdb0c6a6c3" UUID_SUB="17fdb3c3-ae58-f912-c38f-a3b06d0f7a24" LABEL="nas:Matrix" TYPE="linux_raid_member"
/dev/sde: UUID="df704e6d-b0ec-d791-5d09-09cdb0c6a6c3" UUID_SUB="a28b7c92-e3ed-1bbb-0467-55016d663085" LABEL="nas:Matrix" TYPE="linux_raid_member"
/dev/sdb1: PARTUUID="0cb69419-e832-4e3f-8f2d-7fd377871fc4"
fdisk -l | grep "Disk "
Code
root@secure:/# fdisk -l | grep "Disk "
Disk /dev/sda: 477 GiB, 512110190592 bytes, 1000215216 sectors
Disk identifier: 0x893c809b
Disk /dev/sdb: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Disk identifier: 0EBBA207-0B19-4F27-8BEC-70088765E75B
Disk /dev/sdc: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Disk identifier: 28024B9D-9A47-4130-9349-83B733347DCF
Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk /dev/md0: 1.8 TiB, 2000264691712 bytes, 3906766976 sectors
Disk /dev/sde: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
cat /etc/mdadm/mdadm.conf
Code
root@secure:/# cat /etc/mdadm/mdadm.conf
# 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/md0 metadata=1.2 name=nas:Matrix UUID=df704e6d:b0ecd791:5d0909cd:b0c6a6c3
# instruct the monitoring daemon where to send mail alerts
MAILADDR monitoring.backup.cloud@gmail.com
MAILFROM root
Alles anzeigen
mdadm --detail --scan --verbose
Code
root@secure:/# mdadm --detail --scan --verbose
ARRAY /dev/md0 level=raid1 num-devices=2 metadata=1.2 name=nas:Matrix UUID=df704e6d:b0ecd791:5d0909cd:b0c6a6c3
devices=/dev/sdd,/dev/sde
uname -a
Code
root@secure:/# uname -a
Linux secure 4.13.0-0.bpo.1-amd64 #1 SMP Debian 4.13.13-1~bpo9+1 (2017-11-22) x86_64 GNU/Linux
omv-sysinfo
Code
= OS/Debian information
================================================================================
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.2 (stretch)
Release: 9.2
Codename: stretch
================================================================================
= openmediavault information
================================================================================
Release: 4.0.14-1
Codename: Arrakis
Alles anzeigen
Please help me to resolve this issue,
thank you in advance for every reply!
Mateusz