Hi,
i've a fresh install of 4.1.23-1 Akaris OMV
a 4 disk existing mdadm raid (build in a v2OMV if i remember correctly), it work like a charm
Bash: mdadm --detail /dev/md2
/dev/md2:
Version : 1.2
Creation Time : Sat Mar 5 10:56:57 2016
Raid Level : raid5
Array Size : 8776594944 (8370.01 GiB 8987.23 GB)
Used Dev Size : 2925531648 (2790.00 GiB 2995.74 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Update Time : Mon Aug 5 23:03:03 2019
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Name : MatrhackNas:2
UUID : c37b74f5:c334d137:793d2414:2f1e6eb6
Events : 55657
Number Major Minor RaidDevice State
5 8 32 0 active sync /dev/sdc
1 8 53 1 active sync /dev/sdd5
3 8 21 2 active sync /dev/sdb5
4 8 64 3 active sync /dev/sde
Alles anzeigen
but i don't understand something.
my share won't work in afp or smb; so i dig a little and find that
Bash: grep -n dev-disk\|shared /etc/samba/smb.conf /etc/netatalk/afp.conf
/etc/samba/smb.conf:36:path = /dev-disk-by-label-1.42.6-3211//p
/etc/samba/smb.conf:58:path = /dev-disk-by-label-1.42.6-3211//tmp
/etc/netatalk/afp.conf:9:path = /srv/dev-disk-by-label-1.42.6-3211/TimeMachine
/etc/netatalk/afp.conf:22:path = /srv/dev-disk-by-label-1.42.6-3211/p
/etc/netatalk/afp.conf:35:path = /srv/dev-disk-by-label-1.42.6-3211/tmp
if i run something like :
sed-i 's@/srv/dev-disk-by-label-1.42.6-3211/@/sharedfolders/@g' /etc/samba/smb.conf /etc/netatalk/afp.conf&& systemctl restart smbd.service netatalk.service
Both smb and afp share work ok.
So, is this normal omv create share with this weird path or i miss something ??
Note; i dont show you any screenshot of omv interface but i've setup my share with it.
I hope you understand my question and my self learn english.
Thanks anybody answer me