Just installed OMV and started copying files to the RAID array. Yesterday OMV was shut down normally, but when I started it this morning, the device-names had changed and the RAID was missing. The boot-drive (a SSD) was no longer sda but instead sdc, and the HDDs in the RAID was no longer sdb, sdc and sdd but instead sda, sdb and sdd. I assume that is why the RAID is no longer active? What to do?
Best regards,
Morten
1x120GB Kingston SUV400S37120G (boot)
3x6TB Toshiba P300 HDWD260
Code
root@openmediavault:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : inactive sdb[1](S) sdd[0](S) sda[2](S)
17581171464 blocks super 1.2
unused devices: <none>Code
root@openmediavault:~# blkid
/dev/sda: UUID="d7a7ac09-e506-6c4a-23d7-946aecca4121" UUID_SUB="9a982dc5-79b8-ba73-9048-8202f54484ed" LABEL="openmediavault:0" TYPE="linux_raid_member"
/dev/sdd: UUID="d7a7ac09-e506-6c4a-23d7-946aecca4121" UUID_SUB="32f72a72-4395-1e48-ecbc-9f0f78b81ca4" LABEL="openmediavault:0" TYPE="linux_raid_member"
/dev/sdc1: UUID="CA01-72F3" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="d6a3b1a3-d0d8-4374-824b-ca3185795f5d"
/dev/sdc2: UUID="e8a2327f-d4fb-4ea7-9fe3-5b6406fc870d" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="3e0aaee5-83fa-4d08-befd-ee265507f61d"
/dev/sdc3: UUID="f790b49a-cef6-4407-b62b-56ff6c6a603d" TYPE="swap" PARTUUID="02699c2e-d604-4f9d-bc42-5d56c0392079"
/dev/sdb: UUID="d7a7ac09-e506-6c4a-23d7-946aecca4121" UUID_SUB="d168f3cb-e373-96a3-5dcb-a3a6c5fdce9d" LABEL="openmediavault:0" TYPE="linux_raid_member"
root@openmediavault:~#
root@openmediavault:~#
root@openmediavault:~# fdisk -l | grep "Disk "
Disk /dev/sda: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: TOSHIBA HDWD260
Disk /dev/sdd: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: TOSHIBA HDWD260
Disk /dev/sdc: 111,79 GiB, 120034123776 bytes, 234441648 sectors
Disk model: KINGSTON SUV400S
Disk identifier: C094D529-8201-4DA5-AFD6-5563DE41E9A0
Disk /dev/sdb: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: TOSHIBA HDWD260Code
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
ARRAY /dev/md0 metadata=1.2 name=openmediavault:0 UUID=d7a7ac09:e5066c4a:23d7946a:ecca4121Code
root@openmediavault:~# mdadm --detail --scan --verbose
INACTIVE-ARRAY /dev/md0 num-devices=3 metadata=1.2 name=openmediavault:0 UUID=d7a7ac09:e5066c4a:23d7946a:ecca4121
devices=/dev/sda,/dev/sdb,/dev/sdd
