Ubuntu - no
RPi OS Lite - yes
Ubuntu - no
RPi OS Lite - yes
PeteyBling i used this Mean Well power supply. I cut up this cable to solder up a cable for the 12V connectIon. The plug on the top of the sata hat is a four pin square molex. Here’s a pic of the top of the hat: https://www.friendlyarm.com/im…escription/M4v2_en_09.jpg
The square plug center front is the 12 V supply that powers everything, board and hard drives. The four pan in-line plug right behind the sata ports is what powers the hard drives.
According to Friendly Elec the M4 is discontinued and the M4V2 is temporarily stopped production. With the sata hat you will need a 12V power supply to run the sata drives and the M4V2. There is a 12V plug on the sata hat. The heat sink is also an advisable addition.
Did you get a cert from Swag when you ran docker logs -f swag?
Well, to begin with PUID=998 is wrong. You need to create a user in the Users tab of OMV. It will have a PUID of 1000 if you haven’t created one already. You can find out what your user’s id is by ssh into your server and enter id <user-name>
Bearpunzel I know that this thread is a number of days stale, but I felt the need to say just a few words. I hate to see it when a newcomer to the forum gets his/her feelings hurt. You greatly misunderstand us. I hope you haven’t moved on/away.
I’m sorry but I couldn’t see any obvious comments by geaves or chente that could have been intentionally offensive. They were merely expressing their frustration over a common problem that many of us share. You cannot imagine how often this sort of thing is dealt with on the forum. I believe that much of your “distress” is over following a dead end for so long, only to have a couple of users point the fact out. Don’t shoot the messenger. You cannot imagine the amount of tireless help these two have been to countless “distressed” users.
YouTube is great if you are looking for a How-To for replacing wheel bearings on a 1974 Chevy Silverado, but not so much if you are looking to set up OMV on a RPi4. OMV is evolving rapidly. Believe me, YouTube is a topic we have discussed at some length “behind the scenes”. We really do not have a solution to the problem. Because there is a revenue stream for the video creators there is little incentive for them to correct or remove their videos. As you noted, one of our own forum users has a massive YouTube listing on the forum. Many/most of those videos are based on end-of-life versions of OMV. That user has been inactive on this forum for several months now. We don’t delete users’ posts on this forum unless they are spam or some other filthy rot.
Hang around. Everybody is friendly and helpful here. And stay away from YouTube unless you need to replace wheel bearings on a 1974 Chevy Silverado.
I have have this kind of problem a few times, where I cannot get Docker and/or Portainer to re-install. Go into the OMV-Extras tab and select apt clean from the Updates pull-down. When the process finishes try to install your Docker from OMV-Extras.
A little background: every time you create a new user in OMV they automatically become a part of the group “users” which is PGID 100. That is why the yml (or stack) needs “PGID=100”.
The line of code that I added to /etc/fstab was //192.168.1.140/media /mnt/samba cifs username=myuser,password=mypassword,file_mode=0666,dir_mode=0777 0 0
The file_mode and dir_mode is what I had to add to make it work.
When I manually mount this SMB/CIFS share in my Ubuntu LXC
How did you do this on your Ubuntu? I had a similar issue on my Debian machine. When I mounted a SMB share from OMV to my desktop the ownership/permissions of the mount point would change after it mounted, no matter what chmod and chown I used to set up the mount location.
First thing that comes to mind would be to put them on the same network. Go to your networks tab in Portainer and change the network for one of the stacks to the network of other.
I need to back away from the last post above. the Samba utility (Smb4K) was painfully slow and a couple of times crashed my file browser. So I went back in search of a command line solution. Here is what I came up with, mostly from here:
It does not matter what permissions or ownership I set for the samba folder, when I rebooted and the share mounted there, ownership would change to root root and I could not write to the shares. Only after I added the file_mode and dir_mode to the end of step 5 was I able to write to the shares.
Not being extremely ownership/permissions savvy, is this a good/safe practice or no?
If you post your stack inside a code block (which keeps spaces) see this button </> in the editor.
--- version: "2" services: plex: image: ghcr.io/linuxserver/plex container_name: plex network_mode: host environment: - PUID=1000 - PGID=100 - VERSION=latest volumes: - /symlinks/disk4/appdata/plex:/config - /symlinks/pool/media/animation:/Animation - /symlinks/pool/media/cartoons:/Cartoons - /symlinks/pool/media/movies:/Movies - /symlinks/pool/media/movies2:/Movies2 - /symlinks/pool/media/music:/Music - /symlinks/pool/media/audiobooks:/Audiobooks - /symlinks/pool/media/photos:/Photos - /symlinks/pool/media/sports:/Sports - /symlinks/pool/media/tv:/TV - /symlinks/pool/media/tv2:/TV2 - /symlinks/pool/media/videos:/Videos restart: unless-stopped
Shouldn't your PGID be 100?
- PLEX_CLAIM= #optional
As the comment reads, this is optional. There is a claim key you get from plex that should be there. My guess if you don't have a claim key this line is not needed. It may in fact be causing you trouble without the competed argument.
That was intentional... I was trying to narrow down his problem so I started w/ just the very basics... I figured if we got it going we'd just go back and add them to the stack later and redeploy.
I thought that might be the case, but just thought it might have an effect. Besides that, I saw you mention covid a few days ago, and wondered if you might be delirious. What about the Time and Date settings in OMV; is that a possibility? And his yml?
Well, dang it, the code box didn’t hold my bold highlight. It was line 2 and the last line. Also, in your yml example There was no path to media.
The op never showed his yml. You may have given it to him straight but he may have made a mistake in adjusting it. His error log complained about something to do with syntax and his GUID. Also, there was mention in it about click. He may may not have his time and date set properly. I’ve highlighted the parts in the log below:
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/188.8.131.5219-c43dc0277/PLEX MEDIA SERVER/ebc563af-3a9a-447d-151f6a93-8ac98bb4.dmp Error in command line:the argument for option '--serverUuid' should follow immediately after the equal sign Crash Uploader options (all are required): --directory arg Directory to scan for crash reports --serverUuid arg UUID of the server that crashed --userId arg User that owns this product --platform arg Platform string --platformVersion arg Platform version string --vendor arg Vendor string --device arg Device string --model arg Device model string --sentryUrl arg Sentry URL to upload to --sentryKey arg Sentry Key for the project --version arg Version of the product --allowRetries arg Whether we will allow retries Starting Plex Media Server. libc++abi: terminating with uncaught exception of type std::__2::system_error: clock_gettime(CLOCK_MONOTONIC) failed: Operation not permittedlibc++abi: terminating with uncaught exception of type std::__2::system_error: clock_gettime(CLOCK_MONOTONIC) failed: Operation not permitted
I’m not sure how you are set up, but most people operate OMV on a two drive concept: one small for your operating system, and a larger drive for your data. Under most circumstances it is not wise to have any kind of data (media and documents) on your system disk. Many users run their operating systems on a 16 or 32 GB flash drive.
On your data disk you can create two shares. Name them data and appdata. The data share can have all of your media and file folders: movies, music, e-books, documents, downloads, etc. The appdata share can contain all of your config folders for the services you build with docker containers. The appdata share is a good place to put the docker folder. Your docker folder will do nothing to harm the rest of the drive. It is just a config folder for Docker.