755 root:root /etc/openmediavault
660 root:openmediavault-config /etc/openmediavault/config.xml
And please remark it as omv5 thread.
755 root:root /etc/openmediavault
660 root:openmediavault-config /etc/openmediavault/config.xml
And please remark it as omv5 thread.
thats my view of things too and i agree with your statement. in general and related to your support.
But the thread starts with geavis... my criticism was for him.
Why...
and you may see whats going wrong. and when.
that has to do with learning ... and didn't do it twice... and so on...
Maybe I value the abilities of the audience wrong, yes.
but this is more a philosohic point because you can not treat everyone the way you do the stupidest.
I know what I'm writing about, I'm a supporter to, but in a different environment and i know the phrases that needed to survive.
but this is offtopic.
try
# cat /var/log/apt/history.log|grep apache
and/or
# zcat /var/log/apt/history.log.*.gz|grep apache
and you may see whats going wrong. and when.
apt logs all changes.
maybe
#apt purge apache2
help
but do a backup of /etc/apache2 at first.
i agree, that it is not a good idea to raid via usb. absolutly!
but its not impossible, for learning and testing scenarios... why not?
In my view the pi is invented as a educational computer!
so what is the problem testing raid5 with 3 usbsticks??
you may use it for other challeges...like pi-hole, a bt-seeder, tv/media/plex head or whatever.. but as a pi user you are always at your own. Most people.. even the guys with a pi.. are able to use a shell too.
But about omv and Raid as (Linux) principe, you are simply wrong.
The tool to admin softraids is not omv, it is mdadm.
show me in omv how to insert a spare drive to a raid.. or manage a rebuild, stripe sizes, and so on...
its nice to see how easy it is to klick a simple raid together in omv ... but thats not all. And i think you know that too.
So why do you dont tell the poeople where to find knowledge about raids, even if you cant or will not help?
Is omv your only way to get access to a system? Why you try to hide things on a open system and tell people to use omv instead learning using the right shell commands? You try to protect people from the system but you make the people dependent!
I would understand it if you work on a better version of omv-raid ... but ...
I would say, that depends...
i think it will work but this is a standard gaming/desktop setup, not a energy saving nas setup and not a real Server.
but your conditions are far away from normal nas usage too.
Did you actually read any of this thread! The OP is using a Raspberry Pi 3B+ the option for creating a raid using USB devices was disabled on OMV4. Does the Pi have a bios no! Does it have uefi no!
yes i read and decide to write a system independend minihowto about setup/rescue a raid.
as the title describe:
the steps to config a raid are:
but no.. on pi there is no uefi.... so i must be wrong...
thank you geaves
the steps to config a raid are:
#apt-get install mdadm parted
#parted /dev/sdX mklabel gpt
or
#parted /dev/sdX mklabel msdos
depends on bios and uefi
#parted /dev/sdX set 1 raid on
do it on all raid disks XYZ
next single step is optional and depends if you want raid disks (jump) or raid patitions (do it).
#parted -a optimal -- /dev/sdX mkpart primary 0% 99%
on partition raids do a
#mdadm --create /dev/md0 --auto md --level=5 --raid-devices=3 /dev/sdX1 /dev/sdY1 /dev/sdZ1
on disk raids do a
#mdadm --create /dev/md0 --auto md --level=5 --raid-devices=3 /dev/sdX /dev/sdY /dev/sdZ
this will take a looooong time.
watch about it at
#watch cat /proc/mdstat
if its ready and up, take a look at
#cat /etc/mdadm/mdadm.conf
it shoud contain a line like
ARRAY /dev/md/md0 metadata=1.2 name=nas:md0 UUID=264....bla blub
if not, do a
#mdadm --detail --scan >> /etc/mdadm/mdadm.conf
now your raid appear and is hopefully fine, view it with
#mdadm --detail /dev/md/md_test
if you break the (re)assmebly... what i think, you need to reassemble.
##mdadm --assemble /dev/md0 /dev/sdX(1) /dev/sdY(1) /dev/sdZ(1) --force
(depends on Disk or Partition arrays) and think about.. it needs lot of time!
if the array was ready and gone, try
#mdadm --assemble --run --force --update=resync /dev/md0 /dev/sdX(1) /dev/sdY(1) /dev/sdZ(1)
if the array is fine, you can set up a FS.
maybe this one.
#mkfs.ext4 -b 4096 -E stride=128,stripe-width=384 /dev/md0
and mount it via omv or by hand in /etc/fstab
if you wanna boot from, install grub and, make a
#update-initramfs -u
sometimes raids appear as md0 or md127, i dont know why.
and last but not least...read a good mdadm howto!
the plex plugin is worthless, you can only switch plex service on and off... and change the data path as defined in /etc/default/plexmediaserver -> PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR="/var/lib/plexmediaserver/Library/Application Support" to one of the omv mount points. (which is not a good idea to change from the viewing point of plex, you lost all imported media info if you change that) and
# service plexmediaserver start
and
# service plexmediaserver stop
via shellinabox do the same.
you dont realy need omv-plex.
But update a system with a Linux 3.2 kernel, omv 1.x and plex ? is a good idea, i agree.
you dont need any html tags to serve a text via http. do a
# ls -la /etc > test.html
at your webroot and call it via browser...
its not a nice one... but works.
with >> you can catenate headers and footers but...
if you want tables, colors, fontsize, css or whatever in html, you need a (parametric) parser like doxygen.
You can use # ls -la /etc | sed ... too... if you are a feng shui master of regular Expressions.
no hostname.. hm... do a
#hostnamectl set-hostname host.example.com
something like #hostnamectl set-hostname openmediavault.local
as desribed in your hosts file. and restart.
i think this will fix it and nginx will start too.
ok now i found a easy way to manage alternate configs via default and env-vars.
but why nobody hints about this if someone asked for?
i think my problems are fixed now.. or made by myself maybe possible the omv4 and I still find together at the future.
Well, I wanted to use omv to save time ... in the meantime, I'll spend more time getting it right as I need it. That bothers me. Yes I missed the parameter in the Docu, you can now make fun of it for days and laugh. If I have more time, I might really sit down and try to write something for omv - but I already know what I'll hear ... "that's not the design goal of omv".
But if i ask a precise question and get fray Bullshit as Answer...that realy annoys me. Sorry. Simply ask ryecoaaron how long and how many posts does it takes to get a simple info about "omv-mkonf mdadm".
Because of salt, I think this software is more suitable for configuring server farms (cluster management) than controlling local daemons with simple textfiles. It may work, but it does not make things any easier and is incomprehensible like the Windows registry in conjunction with AD servers. Something like that does not need a Nas and that is not Linux philosophy too.
Maybe i'm wrong about Salt... but: https://en.wikipedia.org/wiki/KISS_principle
its not my job to decide which software or scripts is used in omv, but its my decission to use it or not. So i will not update to and even not develop on omv5. You say, there is no more development on omv4.. ok.. all things told.
And yes, maybe it was not a good idea to use omv for my needs... maybe i do it in the future by hand again.. as in the last 30 Years! I do not complain about that.
I tried to help but this is just turning unpleasant. I'm done wasting your time with my worthless posts...
ok i didn't found them... but you show me the reference... thats ok. its not worthless.
As i say... i stop complaining.
thank you
slowly....
logging= is invalid. they speak about logging in the docu but there was and there is no parameter "logging=" inside!
printer admin is deprecated since samba 3.6 and it was anounced as dead earlier.
thats what i told.
maybe the omv 5 as officialy called "beta" may have'nt these problems - but omv4 is the stable release.
but i don't want to talk about update and release politics or how riding a dead horse (saltstack), i want to complain about a wrong, not documented and missleading parameter "logging=" in smb.conf. And its not a theoretical discussion, it manifests on wrong logs or better 0-logs. everyone cant try on its own system! this is what i described and you and Volker can do what ever you want with this proven info... fixing this isue is one of lot's of possibilitys.
maybe you can't fix this isue because of Volker... whyever.. maybe he is the biggest linux guru on earth.. but you can build your own Opinion about that and check/proven my arguments.
And now again... logging= is not a valid config entry. show it in the docu.. or remove it from the /usr/share/openmediavault/mkconf/samba.d/10global!
If you (or Volker) show me a valid reference for logging=syslog or whatever it takes as parameter, i will immediately stop complaining and ask the guys from samba, why they dont support doccumented parameters... but now it's on OMV.
maybe inotify is your friend...or auditd. Or lsof. Or iotop.. or iostat...
try to insert the usb disk but not mount it and disable smart. now it stops after few mins. or is it running?
if it stops, mount it... now it stops after few mins. or is it running
if it stops, enable smart. now it stops after few mins. or is it running?
if its running... which damons running in the testtimeframe? take a look on /var/log/daemon.log and /var/log/syslog and var/log/kern.log and #dmesg
You can even do a #init 1 (switching to singleusermode) on ssh to see if it depends on deamons on the runlevels. and so on...
i woud try at first #iotop -o -d 30
logging=syslog is simply wrong!
please show me only one official link to samba doku which describe a config item and parameter as "logging=syslog" and i never more complain about this.
Yes, there are parameters like syslog=0 ... but this is not logging=syslog.
And no, i will not do discussions about this on github! Its your job to rtfm sambadocus because you build configs by your design!
And even no, i don't know why testparm do not compalin about the config/parameter logging=, but i see testparm complaining on very old obsoletet config entrys in smb.conf made by omv4! But Testparm is not the omniscient garbage dump!
if this all is no reason to take a look for you ... then even github will not help you.
i try to fix some omv errors and want to read samba logs.. - as defined in smb.conf -> log file = /var/log/samba/log.%m
but samba create files in /var/log/samba/log.ipaddress with a leght of 0
i found that there is a buggy entry "logging=syslog" which depends on that.
You can use syslog... or logfiles like these in /var/log/samba/ ... but if you set both, that will go wrong!
the problem is..."logging=syslog" and the logs are hardcoded strings in /usr/share/openmediavault/mkconf/samba.d/10global
Now i removed the buggy "logging=syslog" and all things fine. so please - on the next omv4 update, fix that.
i don't want to fear the next update... and do it all again...