Hi. Sorry. Context is I broke my GUI and got it to a point where advice on another thread was to upgrade the kernel. An entire day of Googling and thread reading had me here. I followed the instructions in the prev post and got that error on running that line.
I agree it was too little info. Most people Google a lot and get very stressed before posting. I ended up doing a clean install, and now I'm having grief with that but I'll post separately.
Went down a rabbit hole of posts and Googling how to update Kernel. Just ended up with multi page threads on this site and non OMV sites with instructions that were outdated or didn't work for me. Fresh installed the entire OMV.
make menuconfig
LEX scripts/kconfig/lexer.lex.c
/bin/sh: 1: flex: not found
make[1]: *** [scripts/Makefile.lib:184: scripts/kconfig/lexer.lex.c] Error 127
make: *** [Makefile:559: menuconfig] Error 2
omv-engined -f -d
...allows me to log in! from this post
Failed to connect to socket: Connection refused
Though they updated thier kernel and the instructions don't work for me.
What the hell. The only file in /var/www/openmediavault/ is /var/www/openmediavault/js/omv/util/i18nDict.js
Seems to be the same as this person.
How did you go? I seem to have achieved the same disastrous outcome setting up sendmail: 403 Forbidden - Web UI - Please Help!
I'm getting 403 Forbidden on the Web UI.
I was trying to set up sendmail via CLI for another service (Greyhole): https://www.fosstechnix.com/co…-emails-using-gmail-smtp/
I received a couple of errors which led me to this page: https://alexhunt86.wordpress.c…world-writable-directory/
I ran the suggested commands...
#chmod go-w /
#chmod go-w /etc
#chmod go-w /etc/mail
#service sendmail restart
nginx OMV error log:
directory index of "/var/www/openmediavault/" is forbidden, client: ::ffff:127.0.0.1, server: openmediavault-webgui, request: "GET / HTTP/1.1", host: "127.0.0.1"
And I think that's what broke the OMV GUI.
Any ideas? I guess I need to reset the permissions correctly. Feeling a bit stupid for running those without thinking it through.
As a side omv-firstaid: command not found
Thank you. Will OMV suffer an appreciable performance hit from running off a USB 3 stick? I guess anything that frees up SATA ports for storage pool drives is a good thing.
It was late, I'm days and days into my OMV build and obsessively sticking at it in a Linux baptism of fire. I was smart enough to have a good playpen in Virtualbox. Now I'm building prod.
I don't want to take up my whole SSD with OMV, and I have a need for a Win 10 Desktop. So I Googled dual booting Debian with Win10 which is supposedly easy, and I have dual booted similar operating system combinations before.
After shrinking my drive with Win, I booted in to OMV and clicked through the install script, as I had done so many times in the previous week tuning my perfect install.
You can guess what happened. I didn't make sense of the partition warnings. In future I'd like to see some banner saying "This will blow away your entire target drive", so idiots like me get the message! I recall only seeing a few partition references in numbers, and thought maybe I'd have a chance to select a partition after selecting the disk, or something. Wholly my fault though.
Anyway. No love lost... as the Win 10 install was practically fresh and had no files I needed.
TLDR:
My question...
I have searched these forums and online, but can't find a tutorial to shrink my Debian partitions, so I can install Win 10 back on to the SSD to dual boot. Is there any inherent reason I shouldn't do this? Seems a shame to take up the whole SSD for a 16gb OS.
Otherwise I'm loving OMV so far. And have it working nicely with a manual install of gh. Definately come a long way to improving my Linux chops in the process. Thanks to all that contribute 
.
I have resolved my main issue of having OMV and Greyhole coexisting. Samba seems to be working fine in my playpen after reinstalling Greyhole. Greyhole is doing its thing and managing local redundant copies in my mounted greyhole shares. I'm very happy. Time to build prod
Never mind. Figured out you don't need the tags/headers.
Global extra options go in Settings, Extra Options. Share specific extra options go in Extra Options in the settings for each share.
Edit: Gah! The folder/share level extra option
vfs objects = greyhole
Breaks the share 
They are inaccessible over the network until I remove those options in the GUI.
My whole samba config is here: https://github.com/gboudreau/G…28#issuecomment-613814693
OK I see now after another save, they are written as separate sections. I presume samba will associate them correctly.
Screenshot attached for example...
So in that section I set the below. But none of that exists in /etc/samba/smb.conf even after saving/applying and rebooting the machine...
[global]
unix extensions = no
wide links = yes
[photos]
dfree command = /usr/bin/greyhole-dfree
vfs objects = greyhole
allow insecure wide links = yes
[videos]
dfree command = /usr/bin/greyhole-dfree
vfs objects = greyhole
allow insecure wide links = yes
In my opinion Greyhole is a wonderful storage pooling and drive level local redundancy tool. OMV, I gather, used to have a Greyhole plugin that is no longer developed or compatible with the latest versions of OMV.
Not to worry. GH has a manual install option and works very well on Debian.
Over the last few days getting to know OMV (which I love, and want to migrate to from Amahi). I got it working, but have noticed a few things that conflict. I wonder, rather than maintaining the plugin, if there was some way to address these issues, so at least a manual install of Greyhole persists in the background without getting its config borked.
I logged an issue here for Greyhole:
https://github.com/gboudreau/Greyhole/issues/228
The main issue is OMV is overwriting the samba config that GH requires to work. Namely...
[global]
unix extensions = no
wide links = yes
[share_name]
dfree command = /usr/bin/greyhole-dfree
vfs objects = greyhole
And since symlinks are not displaying on my samba shares after Greyhole distributes copies of files across different physical drives in the pool (i.e. Greyhole runs and files become unavailable over the network). Possibly some combination of...
[global]
allow insecure wide links = yes
[share]
follow symlinks = yes
wide links = yes
If OMV could have areas of samba config that don't get overwritten (I noticed it happens when creating or editing samba shares) a manual install of Greyhole may play nice, and not require plugin development. Alternatively, OMV might have a section for parameters that rewrite custom samba config back in should the config file have to be rewritten. Then custom GH config lines could be managed through the OMV GUI.
Finally got OMV up today for a play. Got badly hung up on Win 10 hogging Hypervisor resources off Virtualbox. But that aside I now have a VM working in a Win 10 host.
I had hoped to connect one of my physical 1TB drives raw with Virtualbox to dedicate it to OMV, but got frequent IO errors setting up the file system and formatting the drive from the web GUI. Though, OMV could see the drive at least. I gave up on that as a possible stable daily driver pretty quickly.
Continuing playing around with file based virtual disks just testing the GUI and file systems. Must say I'm very impressed! I'll probably end up installing it on a dedicated drive. But I want to see if I can get Greyhole up and running in tandem in my playpen first.
To pool many HDDs of varying size in OMV, use mergerfs, unionfs or snapraid.
OK thanks. I'll look in to it. Do any of those options offer drive level redundancy, and self healing that Greyhole does?
And I don't even know what "grayhole" is. I certainly haven't heard it mentioned in connection with OMV before.
Are you sure that you really need a NAS? Network Attached Storage? Perhaps you instead need a DAS? Directly Attached Storage?
For anyone reading...
No, I don't want DAS, I have a pretty elaborate home network. But I have a reasonably low frequency of use for storage. Basically I need somewhere to store and access photos from when my camera SD card fills up plus a few installers and random large files, also for Time Machine and Win Backup and Restore backups over the network.
What appeals about Greyhole is recycling old drives to a storage pool, with the added benefit of drive level redundancy. My failsafe is Google Drive for cloud backup of important docs and photos.
