Posts by Soma

Quote from Birdybird

my ssd is 91 percent full.

If this is your root drive, then 91% is enough to be considered full.

There's no rule of thumb but the constant opinion is that your root drive should never go over 60-70% full or performance will degrade.

This is only info I've read over the years about Linux.

Is it true or not?

Maybe some more expert opinions will give a better insight about this.

This is just one info I read in 2013:

How is the minimum file system free space decided? (linuxquestions.org)

And following it:

Impact of space usage on file system performance - Blue Light - Blue Light Wiki (bluelightav.org)

Quote from Birdybird

cat: write error: No space left on device

This should be self-explain:

Your disk is full.

Damn, forgot the enable,

Quote from leonovo

systemctl status openmediavault-engined.service

systemctl unmask openmediavault-engined.service

systemctl start openmediavault-engined.service

Quote from presence

I was troubleshooting the old one...it somehow has been set to read-only. No tooling can change it

How to Fix Write-Protected MicroSD Card on Windows and Mac (wondershare.com)

Quote from presence

Crap...why do I have a feeling that arm7l is 32 bit. Man, I'm really frosty now. How could the "current" version of raspbian lite be 32 bit

Use the raspiOS lite version arm64.

The "standard" version is always 32bit so it's retro-compatible with all Raspberry boards.

Isn't your drive full?

Run df -h

Quote from jackblk

Same issue on OMV 6.0.30. Just hit Enter (to hit Cancel button) when it is configuring DHCP IPv6.

Instead of using the OMV iso, use the Debian netinstall method and then, run the script bypassing the network configuration:

installing_omv6_i386_32_bit_pc [omv-extras.org]

OpenMediaVault-Plugin-Developers/installScript: script that installs omv-extras and openmediavault if not installed already. (github.com)

Welcome to the forum

I use this one's in 32Gb and haven't had a fail yet (the most used one is running LibreELEC for almost 2 years)

Amazon.com: Cartão de Memória SanDisk Extreme microSD UHS-3 : Everything Else

Quote from presence

Yeah, I bought it from amazon like above. I used h2testw to determine if it was "fake" before I used it.

Ok, it seems a legit card and not some alienexpress knock-off.

But, I insist with you: you're better off having 2 or 3 16Gb cards and do as I told before, use 1 and after everything is set, clone it to another and rotate them often.

Quote from ifelixculpa

any video tutorial for more easy guidance sir ? this is absolutely new stuff for me

The guides are well written and easy to follow.

You won't find any videos around here.

And even if you follow any youtube guide, it will probably be outdated and whoever creates them, don't care about anything and won't give any support.

Quote from ifelixculpa

Hi members , i have somehow managed to setup nas using raspberry pi 4 and omv 6 but need to access these files when away from home network

please guide how to do it

thankyou

The guides section have a lot of info:

For e.g. [How-To] Web services using Swag (Proxy) in docker - Guides - openmediavault

Or with a Wireguard VPN, access the server as if you were in the LAN:

[How-To] Install Wireguard (VPN) in docker, server mode - Guides - openmediavault

Can you post a link to where you bought that Sdcard?

And don't take this wrong but, as a personal experience, when it comes to sdcard on Pis, bigger isn't better.

The logic behinds this is:

For backup, a couple of sdcards of 16gb will be cloned/flashes/rotated in less then 30m.

You'll always have a failsafe backup of the OS.

Do this every week or 2 and you won't sorry much.

Quote from presence

400GB sd

???

SD or SSD?

If sd, why would you want a SDcard that big?

A Pi with a 16/32Gb SDcard for OS/OMV is more than enough and way easier to clone.

And to buy a 400Gb sdcard (never saw or heard about that size until now) must mean you don't have only the OS on it.

So, the wear-and-tear might happened sooner.

Quote from ryecoaaron

I have done it hundreds of times on an RPi.

Ahh, I knew that you only here for the Pis,

Quote from presence

Its not old.

...

If it still is failing afterward, I'll bit the bullet and reinstall, which might be enough effort to just drop the whole thing

You won't believe the amount of times I've already installed RaspiOS/OMV on the Pis.

And no, it's not difficult to have a "busted" SDcard.

I can give you several of them that won't work anymore.

Not only SDcards but also USB sticks.

Quote from Snuupy

cons:

- need to kernel patch unless you use their OS image (not mainlined? wat.)

You should edit this to something like:

Need kernel patch if you want to use the 4 ethernet ports.

I can assure you that it runs raspiOS lite OOB.

Yes, it probably will be more expensive than other solutions but, in the end you'll have that fuzzy-warm feeling that you helped a small company thrived.

Quote from vcdwelt

So maybe it is enough to set the Docker.service start delay a little higher.

Try it/ check the files mentioned on the thread and see what you can change.

See if helps.

Quote from vcdwelt

Or settings the Host Path instead of /media/Disk_? directly to the real path /srv/dev_disk_by...

It doesn't matter.

Either /media/Disk... or /srv/dev... are the already mounted drives. Only changes the name where they are seen on the FS.

Just mentioned it because OMV doesn't use the mountpoint /media since OMV4.

Found the thread that had this mentioned. It's a very good reading:

[Help needed] Docker not starting Portainer - Randomly - Docker - openmediavault

Quote from vcdwelt

But Plex and some other Containers (e.g. SABnzbd) can't connect to the Storage configured insite the Container. A simple Restart (in Portainer) of the affected Container solves the problem until the next reboot.

Your drives are probably not mounted yet, when docker starts.

The fact that you have disks mounted by Label and on /media also tells that you have come from very old OMV version. (or you mounted them by hand)

There was a long time ago, issues with drives plugged via USB that weren't ready when docker was launched, so, the same issue you have would occur.

A time-delay was set to docker.service to wait some seconds/minutes before launching.

But this as been standard on recent OMV versions. It shouldn't happen anymore.

Some better description of what you're running, how you got there, how the drives are connected, etc, might help narrow it down.

Quote from Agricola

I don't point ALL container volumes to it, just the config folders. Isn't that not what you do Soma?

Yes to the appdata/config but I don't make it shared on the LAN.

The way I see it (maybe just due to lack of better understanding) it will set permissions that aren't needed