So I ran into this problem again and couldnt log in. I was able to but now no containers work. Everything is running in portainer but if I try to connect to plex it says server is not available. If I try to open transmission connection refused. I cant even access my files from windows explorer. It says windows cannot access my server.
Edit: Even more confused. My raid is not in OMV at all. Its not mounted and status says its missing.
Edit 2: One of my HDDs is missing from under disks in OMV
Didnt work.
Removing cloudcommander Recreating 5356fd797a7a_cloudcommander ... [1A[2K Recreating 5356fd797a7a_cloudcommander ... [31merror[0m [1B ERROR: for 5356fd797a7a_cloudcommander Cannot start service cloudcmd: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"/usr/src/app/bin/cloudcmd.js\": stat /usr/src/app/bin/cloudcmd.js: no such file or directory": unknown ERROR: for cloudcmd Cannot start service cloudcmd: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"/usr/src/app/bin/cloudcmd.js\": stat /usr/src/app/bin/cloudcmd.js: no such file or directory": unknown Encountered errors while bringing up the project.If you highlight the above you will see the error I get. Not sure why it pasted that way.
Hey all. I keep getting:
[1A[2K Starting cloudcommander_web_1 ... [31merror[0m [1B ERROR: for cloudcommander_web_1 Cannot start service web: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"/usr/src/app/bin/cloudcmd.js\": stat /usr/src/app/bin/cloudcmd.js: no such file or directory": unknown ERROR: for web Cannot start service web: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"/usr/src/app/bin/cloudcmd.js\": stat /usr/src/app/bin/cloudcmd.js: no such file or directory": unknown Encountered errors while bringing up the project..
I used this video:
Can anyone help?
No, you'd have noticed if it was checking that large a space... must not have been required for some reason.
Log in to the webUI, and check your root partition under filesystems, and it should now show much bigger w/ plenty of empty space.
Yup. Everything looks good. All containers running fine. Thanks for your help!
Now reboot to OMV, and it's probably going to say something about a filesystem error, and ask to do a filesystem check (fsck), let it do that.
It never said that or if it did it it was very fast bc its back on the omv login.
Yes.
Okay that's done
That's fine... create a logical partition, then format it as swap.
Under format it only has linux-swap so thats the one?
That's weird.
Yeah, just make it extended, and then format the extended partition as swap.
Format is grayed out. I can go to unallocated and click new and all thats for create is logical partition
Wow, that was fast.
Now the end partition at the very end (the 20gigs)
Format that as a swap partition.
For create as there is no swap. Its only primary or extended so im assuming extended? Or extended and make partition name swap?
OK... so in Gparted.. .drag that main partition (the right side)... all the way to the right, until there is about, 20k mb on the end.
Okay. For free space preceeding that just stays blank?
Speed up your system? No, that would be highly unlikely.
How long it would take? The filesystem check when you first boot I would anticipate taking at least 10min. The actual resizing... That's hard telling. It may not take as long as I'm thinking since the whole latter part of the drive is basically empty and all it has to do is be extended.
1 sounds easier so I'll go with that.
Display MoreOK.
Now you've got 1 of 2 ways to proceed... tell me which you want to do so I know what you're doing.
1. This will probably take the longest. Basically we'll resize your main partition from 44gigs, to.. probably 150-160ish, then put a swap partition on the end. This will take longer, and the system will probably have to run a filesystem check when you reboot. The good thing is, you won't have to do anything after this as long as plex doesn't fill up your root partition (which at approx. 150gigs.. it really shouldn't).
2. This will probably be quicker, but you'll have to follow those instructions I gave you earlier on moving your container folder, creating symlinks, etc. Basically you would split the 173gig partition you have now, into two.. a swap partition, and large 150-160ish partition that will be formatted. You can then move your containers to that partition and create symlinks as i told you above. The advantage of this, your containers will be off your main your partition, so you wouldn't have to worry about the server not booting from a full root partition, should your plex database become humongous.
Any idea around how long 1 would take? If we did 2 would that also speed up my system? Just trying to think of pros and cons. Which is easier? With my history of issues thats better lol
If you click where it says extended, can you delete it? If so, do that, that should give you 1 big unallocated partition.
Yes. Now the big unallocated is 179.91 Gib. Now I can resize. In MiB what is the equivalent of 20 gb?
Go ahead and format the 15gigs again, as swap... .then report back.
Format isnt available for the 15 gigs. Its only available for /dev/sdk2 extended file sytem.
Read it again. You can't move anything there if it's not formatted and mounted.
Sounds like you'll have to use Gparted to format it
In gparted. Erased like to said. Now have 2 unallocated plus the install. It says the maximum size I can extended too is 44708 MiB. Does that sound right?
Display MoreYou might be able to format/mount the unallocated space in the webUI... not sure on that.
Go to Drives/New, and see if you can choose the unallocated space to put a filesystem on. If you can, do so and mount it. Otherwise use Gparted and then boot OMV and mount it.
Create a shared folder on the new unallocated drive ("Containers")
Stop Docker systemctl stop docker
Check docker status systemctl status docker . At the very top it should show docker as not running.
Follow those instructions, using your Containers folder in place of /mnt/pd0/whatever
Once you're done, start docker systemctl start docker
Okay so first follow those steps after caution and then try to format and mount that unallocated space
Cant format or mount the unallocated space. It doesnt appear in the web ui
Display MoreThis might save you a lot of hassle... (I've followed the steps after the 'Caution' part, and it works well)
https://forums.docker.com/t/ho…stallation-directory/1169
You could take that unallocated space, format it, move your docker containers folder there, create a symbolic link, and you're done.
1. You've reclaimed all that unused space, while simultaneously clearing your OS root partition.
2. You moved your docker folder off the OS partition, and onto a much larger partition (that even if it went full, shouldn't prevent the OS from booting)
3. You done all this without losing any of your current docker settings, containers, etc.
With that way no need for g parted? The space would automatically combine into the new partition?
This is what I get
root@openmediavault:~# service docker stop
Failed to get properties: Unit name cockpit-wsinstance-https@.socket is neither a valid invocation ID nor unit name.
I think docker is stopped though bc both plex and transmission wont connect. Connection refused.
