Beiträge von pa28-181

    --- google.com ping statistics ---

    # ping -c5 google.com

    PING google.com (142.251.116.102) 56(84) bytes of data.

    64 bytes from rt-in-f102.1e100.net (142.251.116.102): icmp_seq=1 ttl=105 time=20.3 ms

    64 bytes from rt-in-f102.1e100.net (142.251.116.102): icmp_seq=2 ttl=105 time=9.44 ms

    64 bytes from rt-in-f102.1e100.net (142.251.116.102): icmp_seq=3 ttl=105 time=10.2 ms

    64 bytes from rt-in-f102.1e100.net (142.251.116.102): icmp_seq=4 ttl=105 time=9.17 ms

    64 bytes from rt-in-f102.1e100.net (142.251.116.102): icmp_seq=5 ttl=105 time=9.--- google.com ping statistics --- (142.251.116.102): icmp_seq=5 ttl=105 time=9.

    After removing omv-extras using the and rerun of the script, I get the following from the apt clean. Which drive has no space left. I used pretty much the default setups. What can be done to clean some space out?




    1. Cleaning apt cache files...

    2. Clearing available dpkg packages...

    3. Removing apt lists...
    removed '/var/lib/apt/lists/_var_cache_openmediavault_archives_Packages'
    removed directory '/var/lib/apt/lists/auxfiles'
    removed '/var/lib/apt/lists/lock'
    removed directory '/var/lib/apt/lists/partial'

    4. Removing OpenMediaVault cache packages...
    removed '/var/cache/openmediavault/archives/Packages'

    5. Creating new OpenMediaVault packages file...

    6. Updating apt...
    Get:1 file:/var/cache/openmediavault/archives InRelease
    Ign:1 file:/var/cache/openmediavault/archives InRelease
    Get:2 file:/var/cache/openmediavault/archives Release
    Ign:2 file:/var/cache/openmediavault/archives Release
    Get:3 file:/var/cache/openmediavault/archives Packages
    Ign:3 file:/var/cache/openmediavault/archives Packages
    Get:4 file:/var/cache/openmediavault/archives Translation-en
    Ign:4 file:/var/cache/openmediavault/archives Translation-en
    Get:3 file:/var/cache/openmediavault/archives Packages
    Ign:3 file:/var/cache/openmediavault/archives Packages
    Get:4 file:/var/cache/openmediavault/archives Translation-en
    Ign:4 file:/var/cache/openmediavault/archives Translation-en
    Get:3 file:/var/cache/openmediavault/archives Packages
    Ign:3 file:/var/cache/openmediavault/archives Packages
    Get:4 file:/var/cache/openmediavault/archives Translation-en
    Ign:4 file:/var/cache/openmediavault/archives Translation-en
    Get:3 file:/var/cache/openmediavault/archives Packages
    Ign:3 file:/var/cache/openmediavault/archives Packages
    Get:4 file:/var/cache/openmediavault/archives Translation-en
    Ign:4 file:/var/cache/openmediavault/archives Translation-en
    Get:3 file:/var/cache/openmediavault/archives Packages
    Ign:3 file:/var/cache/openmediavault/archives Packages
    Get:4 file:/var/cache/openmediavault/archives Translation-en
    Ign:4 file:/var/cache/openmediavault/archives Translation-en
    Get:3 file:/var/cache/openmediavault/archives Packages
    Ign:3 file:/var/cache/openmediavault/archives Packages
    Get:4 file:/var/cache/openmediavault/archives Translation-en
    Ign:4 file:/var/cache/openmediavault/archives Translation-en
    Get:3 file:/var/cache/openmediavault/archives Packages
    Get:4 file:/var/cache/openmediavault/archives Translation-en
    Ign:4 file:/var/cache/openmediavault/archives Translation-en
    Get:5 http://security.debian.org/debian-security bullseye-security InRelease [48.4 kB]
    Err:5 http://security.debian.org/debian-security bullseye-security InRelease Error writing to file - write (28: No space left on device) [IP: 146.75.106.132 80]
    Get:6 http://deb.debian.org/debian bullseye InRelease [116 kB]
    Err:6 http://deb.debian.org/debian bullseye InRelease Error writing to file - write (28: No space left on device) [IP: 146.75.106.132 80]
    Get:7 http://httpredir.debian.org/debian bullseye-backports InRelease [49.0 kB]
    Err:7 http://httpredir.debian.org/debian bullseye-backports InRelease Error writing to file - write (28: No space left on device) [IP: 146.75.106.132 80]
    Get:8 https://openmediavault.github.io/packages shaitan InRelease [12.8 kB]
    Err:8 https://openmediavault.github.io/packages shaitan InRelease Error writing to file - write (28: No space left on device) [IP: 185.199.109.153 443]
    Get:9 https://download.docker.com/linux/debian bullseye InRelease [43.3 kB]
    Err:9 https://download.docker.com/linux/debian bullseye InRelease Error writing to file - write (28: No space left on device) [IP: 143.204.165.39 443]
    Get:10 https://openmediavault-plugin-…github.io/packages/debian shaitan InRelease [3934 B]
    Err:10 https://openmediavault-plugin-…github.io/packages/debian shaitan InRelease Error writing to file - write (28: No space left on device) [IP: 185.199.111.153 443]
    Get:11 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
    Err:11 http://deb.debian.org/debian bullseye-updates InRelease Error writing to file - write (28: No space left on device) [IP: 146.75.106.132 80]
    Get:12 http://packages.openmediavault.org/public shaitan InRelease [12.8 kB]
    Err:12 http://packages.openmediavault.org/public shaitan InRelease Error writing to file - write (28: No space left on device) [IP: 178.254.11.33 80]
    Reading package lists...
    W: Failed to fetch http://deb.debian.org/debian/dists/bullseye/InRelease Error writing to file - write (28: No space left on device) [IP: 146.75.106.132 80]
    W: Failed to fetch http://deb.debian.org/debian/d…ullseye-updates/InRelease Error writing to file - write (28: No space left on device) [IP: 146.75.106.132 80]
    W: Failed to fetch https://download.docker.com/li…/dists/bullseye/InRelease Error writing to file - write (28: No space left on device) [IP: 143.204.165.39 443]
    W: Failed to fetch https://openmediavault-plugin-…n/dists/shaitan/InRelease Error writing to file - write (28: No space left on device) [IP: 185.199.111.153 443]
    W: Failed to fetch http://httpredir.debian.org/de…lseye-backports/InRelease Error writing to file - write (28: No space left on device) [IP: 146.75.106.132 80]
    W: Failed to fetch http://security.debian.org/deb…llseye-security/InRelease Error writing to file - write (28: No space left on device) [IP: 146.75.106.132 80]
    W: Failed to fetch http://packages.openmediavault…c/dists/shaitan/InRelease Error writing to file - write (28: No space left on device) [IP: 178.254.11.33 80]
    W: Failed to fetch https://openmediavault.github.…s/dists/shaitan/InRelease Error writing to file - write (28: No space left on device) [IP: 185.199.109.153 443]
    W: Some index files failed to download. They have been ignored, or old ones used instead.

    7. Saving current package list...

    8. Updating plugin index...
    Creating index of upgradeable packages ...
    Creating index of plugins ...

    END OF LINE

    Don't know if this was the best way or not, but I found a newer version of clonezilla and booted into that via Ventoy, and did a device to device copy with the option set to proportionally expand the partitions. It is not using the whole ssd but my boot drive is no longer stuck at 32Gig

    I have a working OMV6 installation that boots from a 128G thumb-drive, but seems to only uses 32Gig of it. I have a spare sata connection as well as a spare 500Gig hard drive. Is there a safe way to move everything from the thumb-drive (including all the settings) and paths and to expand the boot partition from the 32 Gig so as to use a greater percentage of that drive. I have tried to just clone the thumb-drive and then use gparted, however it does not seem to work correctly.

    ProtonVPN has a free tier that supports openvpn as well as wireguard. StackSocial runs promos for various VPN services that have "lifetime" subscriptions. But be aware it is their lifetime that it seams to be.

    I have my main machine running on a Proxmox server that has multiple NICs that can be passed through to a OMV6 virtual machine. I want to rsync certain files to a second smaller machine on which I will be installing a bare metal OMV6 instance. Hopefully I can directly connect the two machines so that the network traffic does not even hit my main lan so as to increase performance. I know that I somehow need to set up the routing tables.


    For example I assume that my Proxmox OMV6 is at 192.168.1.x and I would put the new bare metal machine on 192.168.2.x?

    1) How would I set up the routing tables?

    2)can this be done through a direct connection/cross over cable?

    2a) if need be I have spare 1Gig 4 port switch that could be used.

    3) do I make the Proxmox OMV6 machine the "gateway" for the bare metal machine or will I need to create a different path arrangement for that box to get updates/internet access (internet access will be not critical on that machine)

    3) is this just a dumb idea to begin with? :)

    I have an OpenmediaVault 6.0 running as a VM in Proxmox 7.2 CE and it has decided to stop pulling any plugins or extras due to what appears to be some type of DNS error. It boots, but does not seem to use the DNS servers from the Proxmox properly. Any debugging ideas, and what settings/logs do I need to provide for help?


    The Openmediavault is on a static ip, but I tried it on a DHCP supplied. I have tried manually setting the DNS to 8.8.8.8 (and some others) but no luck. I previously installed the "extras" and I get a DNS error when I try to update portainer and I get the following:


    Docker storage :: /var/lib/docker
    Agent port:: 8000
    Web port:: 9000
    Yacht port:: 8001
    ee:: 0
    image:: portainer/portainer-ce
    Enable TLS:: 0
    arch :: amd64
    option :: portainer
    state :: install
    extras :: 6.1.1
    DNS error. Exiting ...

    END OF LINE


    Thanks in advance.

    I am trying to set up under Proxmox a OMV5.6 instance and it is setup, however I am having an issue with creating a file system on the large disk that I want to use for media on the Proxmox server. I have been able to pass a drive through to the OMV instance using these instructionshttps://www.johnkeen.tech/prox…sk-to-vm-only-2-commands/ and the OMV5 instance, sees the drive under the disks tab and initializes the drive. However when I go to create a file system and try to mount the drive I get the following errors (sorry for the wall of text)


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color fstab 2>&1' with exit code '1': debian: ---------- ID: create_filesystem_mountpoint_4998d8a6-0500-4e89-879a-5c2ecfd7b7c9 Function: file.accumulated Result: True Comment: Accumulator create_filesystem_mountpoint_4998d8a6-0500-4e89-879a-5c2ecfd7b7c9 for file /etc/fstab was charged by text Started: 13:27:40.123165 Duration: 0.72 ms Changes: ---------- ID: mount_filesystem_mountpoint_4998d8a6-0500-4e89-879a-5c2ecfd7b7c9 Function: mount.mounted Name: /srv/dev-disk-by-uuid-0b4748e0-7b49-402a-826e-f620dd961110 Result: False Comment: mount: /srv/dev-disk-by-uuid-0b4748e0-7b49-402a-826e-f620dd961110: mount(2) system call failed: Structure needs cleaning. Started: 13:27:40.124530 Duration: 84.807 ms Changes: ---------- ID: append_fstab_entries Function: file.blockreplace Name: /etc/fstab Result: True Comment: No changes needed to be made Started: 13:27:40.210012 Duration: 3.944 ms Changes: Summary for debian ------------ Succeeded: 2 Failed: 1 ------------ Total states run: 3 Total run time: 89.471 ms


    OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color fstab 2>&1' with exit code '1': debian:

    ----------

    ID: create_filesystem_mountpoint_4998d8a6-0500-4e89-879a-5c2ecfd7b7c9

    Function: file.accumulated

    Result: True

    Comment: Accumulator create_filesystem_mountpoint_4998d8a6-0500-4e89-879a-5c2ecfd7b7c9 for file /etc/fstab was charged by text

    Started: 13:27:40.123165

    Duration: 0.72 ms

    Changes:

    ----------

    ID: mount_filesystem_mountpoint_4998d8a6-0500-4e89-879a-5c2ecfd7b7c9

    Function: mount.mounted

    Name: /srv/dev-disk-by-uuid-0b4748e0-7b49-402a-826e-f620dd961110

    Result: False

    Comment: mount: /srv/dev-disk-by-uuid-0b4748e0-7b49-402a-826e-f620dd961110: mount(2) system call failed: Structure needs cleaning.

    Started: 13:27:40.124530

    Duration: 84.807 ms

    Changes:

    ----------

    ID: append_fstab_entries

    Function: file.blockreplace

    Name: /etc/fstab

    Result: True

    Comment: No changes needed to be made

    Started: 13:27:40.210012

    Duration: 3.944 ms

    Changes:


    Summary for debian

    ------------

    Succeeded: 2

    Failed: 1

    ------------

    Total states run: 3

    Total run time: 89.471 ms in /usr/share/php/openmediavault/system/process.inc:196

    Stack trace:

    #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()

    #1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()

    #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)

    #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)

    #5 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(920): OMV\Rpc\Rpc::call('Config', 'applyChanges', Array, Array)

    #6 [internal function]: Engined\Rpc\OMVRpcServiceFileSystemMgmt->mount(Array, Array)

    #7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #8 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('mount', Array, Array)

    #9 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('FileSystemMgmt', 'mount', Array, Array, 1)

    #10 {main}


    Help please!

    How do you reset information as to the battery (such as battery install date) in an APC direct attached UPS. And can you substitute/install the apcupsd software (including apctest) and still have it show up as part of the OMV5 dashboard under the services tab?