Tag auch,
Nutze testweise OMV auf dem Raspberry Pi 3, sowie, zum Vergleich, den Odroid XU4.
Habe Nach diversen Grundeinstellungen einen RAID0 gebildet, welcher leider nach jedem Neustart des Systems verloren geht (auf beiden Geräten!!!)
Ich hab gestern diesbezüglich recherchiert und einige Lösungsansätze gefunden. Oftmals scheint mdadm.conf ein Auslöser hierfür zu sein.
Frage hierzu ist, wie ich das am Besten fixen kann.
Dazu meine 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=odroidxu4:RAID0 UUID=4bc439e4:71967b76:06980f8$
und mdadm in /etc/default
# INITRDSTART:
# list of arrays (or 'all') to start automatically when the initial ramdisk
# loads. This list *must* include the array holding your root filesystem. Use
# 'none' to prevent any array from being started from the initial ramdisk.
#INITRDSTART='none'
# AUTOSTART:
# should mdadm start arrays listed in /etc/mdadm/mdadm.conf automatically
# during boot?
AUTOSTART=true
# AUTOCHECK:
# should mdadm run periodic redundancy checks over your arrays? See
# /etc/cron.d/mdadm.
AUTOCHECK=true
# START_DAEMON:
# should mdadm start the MD monitoring daemon during boot?
START_DAEMON=true
# DAEMON_OPTIONS:
# additional options to pass to the daemon.
DAEMON_OPTIONS="--syslog"
# VERBOSE:
# if this variable is set to true, mdadm will be a little more verbose e.g.
# when creating the initramfs.
VERBOSE=false
Gruß