Posts by ryecoaaron

Quote from 71CHi2OOeuF2

he situation is the following:

- It doesn't work. The lock file doesn't get deleted

- OMV maintainers claim it works

- The SMB maintainer doesn't answer

=> Broken.

So figure out what is wrong with the smb.conf that OMV generates. The one OMV maintainer doesn't use windows. So, somethings are very hard to test. It is very possible that this is a samba bug that OMV can't fix.

Quote from 71CHi2OOeuF2

My advice: Just move on and take something else. OMV is dead to me.

This is ridiculous that you wouldn't use a product because something doesn't automatically empty a recycle bin.

Install OMV on a system.

Put the PVR disks in the OMV system.

Share them via samba.

Quote from m4tt0

I have sufficient space on there, but just started wondering about "wear and tear". Would you guys recommend moving the docker folder to the HDD Raid instead? And if so, how would you do that with containers being installed?

Your nvme life should be plenty long to not worry about. Also, if your config and data volumes for docker are stored on the OS drive, that is a bit tougher to move. If they aren't, you can just move the docker directory and recreate your containers with the same volumes.

/dev path is the device path. You don't want to use that. You want to use the /srv path. If you look in shared folders and add the absolute path column, you can see the full path of each shared folder.

Quote from edogd

How can I tell if the plugin is running.

There is nothing to run. It just mounts some directories with higher level of writes to tmpfs. If the plugin is installed, they should be mounted. If you still don't believe it, then grep folder2ram /proc/mounts

Quote from edogd

Has anyone observed something similar?

Yes, they get hot. There is nowhere for them to dissipate heat and they are in a warm usb socket. I have a few of the that have been running OMV non-stop for a couple years as the OS drive with the flash memory plugin. If you have 16gb ram, I doubt you are swapping enough to cause much heat. They have a five year warranty. So, back up your drive and don't worry about it. I keep a backup on hand just in case.

Quote from Zephalon

Isn't that a shame. Providing a perfectly fine install script but no way to get rid of it...

Really. What is my motivation for making a remove script? 99.9% don't remove it. The script wasn't designed to install on an old existing install. You could make an infinite number of settings changes. There is no way a script could return the system to pre-OMV. That is what a backup does. If you don't like OMV, you could just remove the plugins then the OMV package

apt-get purge openmediavault-*

apt-get purge openmediavault

Quote from Zephalon

I'll need at least some kind of hints what I need to change in the sshd_config file...

I'm not sure why you need to change anything. But of course, I have no idea what you did to remove OMV. I just removed omv as I instructed above and it didn't affect ssh - no problems logging in.

Quote from Zephalon

Is there some kind of guide how to reverse the changes to the user management?

nope.

Quote from Zephalon

How can I login via SSH again?

Configure ssh. Start the service and change settings in /etc/ssh/sshd_config

Coming to the OMV to ask how to get rid of OMV is normally not going to get you much help though.

minidlna submits the image to client and the image is compiled in if I remember correctly. https://sourceforge.net/p/mini…it/ci/master/tree/icons.c

sudo rm  /var/lib/dpkg/data/openmediavault-netatalk.postrm then run the script again.

Quote from crashtest

I haven't tried Yacht yet, but one of first things I'd be looking at would be easy MacVlan configuration.

Being able to assign a separate IP address to a container is a desirable feature but it seems that configuring a MacVlan interface is an exacting exercise, with pitfalls, where the config doesn't work.

That was one of my suggestions

1. Will it or can it handle docker-compose files? They are very popular with the OMV crowd and people don't always get the compose/stacks stuff. I might not have watched the video long enough if I missed it (sorry, working)
2. Is there an easy way to update a container? If the restart option had another option to restart and pull new, people here would love that.
3. Can the ports be auto-populated from the image with button click or something fast?
4. Can the volumes be auto-populated from the image with a button click or something fast?
5. Lots of people are using macvlan and it is confusing for many. Not sure how to make that faster but just a note.
6. Might have missed this too but can people edit the settings of a running container and have it restart after changing the settings? Haven't needed that myself but the plugin could do it and people miss it in portainer.

Most are already being worked. macvlan is on the radar now.

nextcloud has never been a plugin. Read this - RE: Why should you use or not use dockers

Quote from geaves

Has anyone looked at or installed Yacht this is an alternative to Portainer, this is new and very much a work in progress but is supposed to be more intuitive, there is a video on YouTube

One of the devs contacted me about adding it to omv-extras. Sent some suggestions on things to add that OMV users ask for. So maybe people can add suggestions to this thread so Myth3k can see them.

Try the proxmox kernel (tab to install it in omv-extras) to see if it helps. And is there anything in /var/log/watchdog/?

Something is going on with the system according to watchdog. So, it is unresponsive. What kernel are you using?

Quote from BackWoodsTech

I'd like to have my one SD card slot available

Probably easier to just by a usb card reader if you need an SD card on an arm board.

Quote from BackWoodsTech

I may wrongly be under the impression of a better lifespan for the eMMC vs SD.

It does last longer but is also a lot more expensive. I have had the same SD card on some of my systems for a couple of years. For the cost difference, you could just buy 3 SD cards and clone one to the others. If one started acting weird, switch to a new one.

Quote from BackWoodsTech

Also, I'm wishing I had known in advance about the OS expansion since i'll only be able to clone to a card of equal size moving forward.

Not true. With rsync or fsarchiver, you could use any size as long as what was backed up wasn't larger than the new SD card. The best way to restore is write the armbian image to the new sd card and then restore the backup (just files) over that. It doesn't care what size the filesystem is.

Quote from BackWoodsTech

I don't really see any of this in the help docs unless i've missed them.

What help docs? The screen literally says it is expanding the OS partition when it boots the first time. I'm sure it is documented on the Armbian site and omv install guides.

Quote from BackWoodsTech

Is there a best practice for this (aside from / rather than cloning the SD?

The two dd options are the only ones that backup blank space. fsarchiver and rsync just backup files. They aren't as easy to restore though (can't just write image to sd card). The best option is still to take the sd card out and clone it with clonezilla.

Quote from BackWoodsTech

Specifically related to shrinking the partitions?

Shrinking? Boot gparted-live on the system you wrote the card with and shrink the partition. Easy.

Quote from BackWoodsTech

Also, I had planned to NAND-SATA-INSTALL my SD install to my eMMC module but will that even work now if the eMMC is smaller than the SD?

Why? What are you hoping to gain? I've never used the nand-sata-install.

Quote from MrFloppy

Maybe the amount of drives is too much (9 drives at all)?

I've had 20+ drives connected to an OMV system with no problem before. I would check syslog and/or the screen to see why it is rebooting.

Quote from gresec-root

Did the script change the UUID from the SSD ?

No. But I have said time and time again to flash the SD card and then run the script before you do anything else. I have never tested running the script from usb boot (I only have time to test so many configs). It is hard to say what package or OMV config caused this.

You would have to use inotify or something like that to generate checksum on write. You would be better off to have multiple backups. Borgbackup would let you do that with the same setup (it dedupes and compresses) and detect checksum issues when backing up.