Posts by Soma

See my instructions on page 1 for resizing

Is /MainPool a mergerfs?

If it is, you need to move the config folder elsewhere. To a simple FS folder.

Don't use balena to clone.

Use win32diskimager.

And you can then flash the image straight to an USB stick

There's a guide here Somewhere

berti49

Did you started fresh with Bullseye or did you upgrade from Buster?

Run and post in a code box </> the output:

ls -al /etc/apt/*list

ls -al /etc/apt/sources.list.d/

cat /etc/apt/sources.list.d/openmediavault-os-security.list

The previous solution was on this post:

Same list of updates every day on Pi 4 - Page 2 - Updates/Upgrades - openmediavault

This looks like this:

Search Results - openmediavault

Update Management shows same update each day - Updates/Upgrades - openmediavault

Same list of updates every day on Pi 4 - Updates/Upgrades - openmediavault

Quote from KillrBill

1. I have noticed that the Plex database has nearly filled my SD Card. What is the best (safest) way to upgrade my card currently a 16GB card to say a 64GB card? Is there a tutorial I should watch/follow that you would recommend?

If you have the Plex DB on the root partition, this will continue to happen.

The best approach would be to have the DB on a different drive.

More on the answer #2

After you make a clone of the old SD Card (16GiB ), you can then flash it to a bigger one (64GiB ).

Put the bigger SD on the Pi, and see if it boots normally.

You can then, resize the partition to the maximum with:

sudo raspi-config

It will reboot and the partition will be of the full amount ot the SD Card.

Just remember that the next clones, need to be of the same size or bigger.

Quote from KillrBill

2. Plex tells me that there is a server update that i need to do

gderf && raulfg3 will be the better one's to reply on this (I don't use Plex)

As for the DB, it all depends how you launched the Plex container.

Again, the above mentioned people will be a good source of info.

Quote from KillrBill

3. The hostname address that i go to to get to the OMV WebUI "OMV.local" sometimes doesn't work in my browser

Set a Static IP on the OMV (or a reservation on the Router)

Search the whole forum for "Static Ip Address"

[EDIT]

Speed shooter chente

[/EDIT]

Quote from ruudm

I don't think that Docker is the problem because I can hear audio through the analog output.

TL:DR;

If the device isn't passed to docker, you won't have access to it.

As per example:

I have a NoIR camera on one Pi and run docker MotionEye to have it accessible on the LAN/WAN.

Some of the lines that need to be on the YML is:

    devices:
      - /dev/video0

Which correspond to where Debian(RaspiOS) detects/runs the cam.

Without that line, the cam simply isn't seen or binded to the docker container.

Maybe something in the same lines, need to be done with audio devices.

    devices:
      - /dev/snd

Sorry, if deviates on what you're trying.

I can't give you any better info about audio (don't even have it activated on the Pis) but maybe you can dig some more around these lines.

Quote from Indian

This remains same before/after OMV install.

I know, since it's the latest STABLE kernel.

If you use a previous version of the img ( Index of /raspios_lite_armhf/images (raspberrypi.org) ) I think 2021-03-25 ) the kernel version will be earlier versions 5.10.17 )

Just for triage testing.

Quote from ryecoaaron

If it works before installing OMV and not after, it is not the kernel or the Debian base (buster or bullseye)

Quote from Indian

If everything worked in 5.6.13-1, I would try with it and confirm / refute that it works. If it does work as reported on this forum, then it should be a simple matter to find out what changed in 5.6.14 (or any later version) and fix.

In this case, is it possible to see the diff between the install script file from 5.6.13-1 and 5.6.14-1 ???

How?

Indian

How does the button works?

Is it a simple open push button that you short (close) it for a few moment?

Or an On/Off click button? When closed it will send a gracefull shutdown until it's open?

And when Open it will PowerOn?

I can try to set a temporary jumper to simulate it on GPIO3 (Pin5 and Pin6) to see if I can replicate this,

Which kernel is on the legacy?

Haven't tried it yet but i'm confident that is 5.10.63

Quote from heinsenberg82

File name too long.

This has been discussed on the forum:

omv-extras plugins - porting progress to OMV 6.x - Page 13 - Plugins - openmediavault

Quote from Indian

How do I run previous version of the install ?

If everything worked in 5.6.13-1, I would try with it and confirm / refute that it works. If it does work as reported on this forum, then it should be a simple matter to find out what changed in 5.6.14 (or any later version) and fix.

I'm considering other possibility:

Not the update of OMV but the update of the kernel that breaks the GPIO.

If you can try it:

Flash a previous version of Buster and set the kernel on hold.

Then run the script for OMV and see what happens.

The script to install OMV runs automatically, and will download the latest version (AFAIK) and will also updates the kernel.

So, who knows?

If you know what to look, see the script and try to figure what can be changed to install a previous version.

The part that deals with the OMV install is this one:

installScript/install at master · OpenMediaVault-Plugin-Developers/installScript (github.com)

# install openmediavault if not installed already
omvInstall=$(dpkg -l | awk '$2 == "openmediavault" { print $1 }')
if [[ ! "${omvInstall}" == "ii" ]]; then
  echo "Installing openmediavault required packages..."
  if ! apt-get --yes --no-install-recommends install postfix; then
    echo "failed installing postfix"
    exit 2
  fi

  echo "Adding openmediavault repo and key..."
  echo "deb ${omvRepo} ${omvCodename} main" > ${omvSources}
  wget -O "${omvKey}" ${omvRepo}/archive.key
  apt-key add "${omvKey}"

  echo "Updating repos..."
  if ! apt-get update; then
    echo "failed to update apt repos."
    exit 2
  fi

  echo "Install openmediavault-keyring..."
  if ! apt-get --yes install openmediavault-keyring; then
    echo "failed to install openmediavault-keyring package."
    exit 2
  fi

  monitInstall=$(dpkg -l | awk '$2 == "monit" { print $1 }')
  if [[ ! "${monitInstall}" == "ii" ]]; then
    if ! apt-get --yes --no-install-recommends install monit; then
      echo "failed installing monit"
      exit 2
    fi
  fi

  echo "Installing openmediavault..."
  aptFlags="--yes --auto-remove --show-upgraded --allow-downgrades --allow-change-held-packages --no-install-recommends"
  cmd="apt-get ${aptFlags} install openmediavault"
  if ! ${cmd}; then
    echo "failed to install openmediavault package."
    exit 2
  fi

  omv-confdbadm populate
fi

If it was done as an apt install probably should be something like:

apt install openmediavault-5.6.13-1 -y

I'm just speculating but maybe ryecoaaron can give an input.

Maybe activate the "3 Interface Options" on the raspi-config?!?

Now, either don't run OMV or get an Argon Case (the button functions work out of the box) or check the Argon script to see if you can adapt to your case.

Sorry, can't remember anything else

Quote from Indian

GPIO 27

According to what I posted above, is NOT GPIO 27, but GPIO3 to 0v (pin 5 to 6)

Quote from Nefertiti

This is why I insist because I think this is what I have done but the result is still in var

Sorry, you're on your own to sort that one.

You already have NC running with https connection from in and out Internet.

The only method I care about is that one, don't need to learn a different one.

For what it's worth, I always have a $ on my password and it always worked.

Quote from Indian

I have tried this with bullseye and also buster, same behavior with both, once OMV is installed, it kills /boot/config.txt functionality, specifically the gpio-shutdown option.

????

The OMV script doesn't do anything on the /boot/config.txt

If the option is not there, just edit the file and add the line.

dtoverlay=gpio-shutdown,gpio_pin=3

Details:

firmware/README at master · raspberrypi/firmware (github.com)

Name:   gpio-shutdown
Info:   Initiates a shutdown when GPIO pin changes. The given GPIO pin
        is configured as an input key that generates KEY_POWER events.

        This event is handled by systemd-logind by initiating a
        shutdown. Systemd versions older than 225 need an udev rule
        enable listening to the input device:

                ACTION!="REMOVE", SUBSYSTEM=="input", KERNEL=="event*", \
                        SUBSYSTEMS=="platform", DRIVERS=="gpio-keys", \
                        ATTRS{keys}=="116", TAG+="power-switch"

        Alternatively this event can be handled also on systems without
        systemd, just by traditional SysV init daemon. KEY_POWER event
        (keycode 116) needs to be mapped to KeyboardSignal on console
        and then kb::kbrequest inittab action which is triggered by
        KeyboardSignal from console can be configured to issue system
        shutdown. Steps for this configuration are:

            Add following lines to the /etc/console-setup/remap.inc file:

                # Key Power as special keypress
                keycode 116 = KeyboardSignal

            Then add following lines to /etc/inittab file:

                # Action on special keypress (Key Power)
                kb::kbrequest:/sbin/shutdown -t1 -a -h -P now

            And finally reload configuration by calling following commands:

                # dpkg-reconfigure console-setup
                # service console-setup reload
                # init q

        This overlay only handles shutdown. After shutdown, the system
        can be powered up again by driving GPIO3 low. The default
        configuration uses GPIO3 with a pullup, so if you connect a
        button between GPIO3 and GND (pin 5 and 6 on the 40-pin header),
        you get a shutdown and power-up button. Please note that
        Raspberry Pi 1 Model B rev 1 uses GPIO1 instead of GPIO3.
Load:   dtoverlay=gpio-shutdown,<param>=<val>
Params: gpio_pin                GPIO pin to trigger on (default 3)
                                For Raspberry Pi 1 Model B rev 1 set this
                                explicitly to value 1, e.g.:

                                    dtoverlay=gpio-shutdown,gpio_pin=1

        active_low              When this is 1 (active low), a falling
                                edge generates a key down event and a
                                rising edge generates a key up event.
                                When this is 0 (active high), this is
                                reversed. The default is 1 (active low).

        gpio_pull               Desired pull-up/down state (off, down, up)
                                Default is "up".

                                Note that the default pin (GPIO3) has an
                                external pullup. Same applies for GPIO1
                                on Raspberry Pi 1 Model B rev 1.

        debounce                Specify the debounce interval in milliseconds
                                (default 100)

Before the omv-salt command, follow #22

RE: Chronyd and Chrony services failed to start

After the reboot:

systemctl status systemd-timesyncd

systemctl status chrony

Not according to the output of df:

Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
/dev/vda2    3,4G    3,3G    0   100%       /

Your root drive is FULL.

You can follow the other post to try to free some space and then make a bigger partition

Or, run as it is untill it's full again.

I don't run VM so, can't help you on the expand the partition issue.

Quote from xCleaner15

/dev/vda2 3,4G 3,3G 0 100% /

You need a bigger root partition. 3.4 GiB is below the minimum requirements:

Prerequisites — openmediavault 5.x.y documentation

Quote

Before installing openmediavault make sure your hardware is supported.

• CPU: Any x86-64 or ARM compatible processor
• RAM: 1 GiB capacity
• HDD:
  • System Drive: min. 4 GiB capacity (but more than the capacity of the RAM)
  • Data Drive: capacity according to your needs

  
  

As for to try to save your install for now:

[How-To] Fix full OS filesystem - GUI login loop - Guides - openmediavault