Beiträge von FragoulisNaval

    IF we assume

    Depends on what you mean. If the VM is presented with virtual storage that look like virtual disks to the VM, then it will work fine. If you are thinking of installing the ceph client on the VM, then no.

    Thank you for your reply.


    Lets assume that the VM is installed successfully. On the cluster, I will have two pools. One pool consisting of NVMe drives for the VM, one pool consisting of HDDs for storage


    Through docker, I would like to install navidrome in order to stream my music through internet and a samba share that will enable streaming my music to other devices inside my home.


    The samba share would be a folder created through OMV (which is a VM). I will have to somehow pass the HDD pool into the VM. How it would be best to do this? Through cephfs or is there another/better way to do it?

    I want to bult a 3-node proxmox cluster, add ceph and cephfs on it.


    The cluster will run a VM of OMV and will be basically my working place, since i am planning to move my current bare metal omv server to my parents house.

    The omv as a VM will be a file server for sharing files, a music server where all my music will be stored and distributed/streamed to all my devices in the house as well as the place for all my self-hosted services.


    Will OMV work on cephfs? has anyone tried this?

    Hello everybody,


    I am thinking of moving my existing “bare metal” installation of OMV to ProxMox.


    As of today, I kept my my docker configuration folder and associated data on a separate drive than my OS drive, because with this setup it was easier for me to backup those two drives separately and also gave me redundancy in case one drive goes down.


    Now that I will move to ProxMox and setup a HA cluster, I was thinking to have my docker configuration folder on the same drive as my OS drive, because it will be easier to backup the VM containing essentially my entire configuration AND with live migration I will have zero downtime in case something happens with the cluster.


    Do you think the above a good idea or should I retain my existing practice to PoxMox as well??

    Good day to all,


    Today when i updated (together with new containerd and docker version) from 6.3.4-1 to 6.3.6-2 i received the following errors in the log, highlighted in bold letters.


    Preparing to unpack .../openmediavault_6.3.6-2_all.deb ... Unpacking openmediavault (6.3.6-2) over (6.3.4-1) ... Setting up openmediavault (6.3.6-2) ... Installing new version of config file /etc/cron.daily/openmediavault-check_locked_users ... Installing new version of config file /etc/cron.daily/openmediavault-check_ssl_cert_expiry ... Installing new version of config file /etc/cron.daily/openmediavault-cron-apt ... Installing new version of config file /etc/cron.daily/openmediavault-flush-mailq ... Installing new version of config file /etc/cron.daily/openmediavault-mdadm ... Installing new version of config file /etc/cron.daily/openmediavault-pending_config_changes ... Installing new version of config file /etc/cron.weekly/openmediavault-update-smart-drivedb ... Configuration file '/etc/default/openmediavault' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. ==> Using current old file as you requested. Creating configuration database ... Migrating configuration database ... Setting up Salt environment ... [ERROR ] Exception during resolving address: [Errno 2] Host name lookup failure [ERROR ] Exception during resolving address: [Errno 2] Host name lookup failure [ERROR ] Exception during resolving address: [Errno 2] Host name lookup failure [ERROR ] Exception during resolving address: [Errno 2] Host name lookup failure Processing system modifications ... Setting up containerd.io (1.6.19-1) ... Setting up docker-ce-cli (5:23.0.2-1~debian.11~bullseye) ... Setting up docker-ce (5:23.0.2-1~debian.11~bullseye) ... Processing triggers for rsyslog (8.2102.0-2+deb11u1) ... Processing triggers for openmediavault (6.3.6-2) ... Restarting engine daemon ... Updating workbench configuration files ...

    END OF LINE


    1) I have not touched the Configuration file '/etc/default/openmediavault file. how could this be altered?

    2) What does this "[ERROR ] Exception during resolving address" means and how it can be fixed?

    3) What does this "[Errno 2] Host name lookup failure" means and how it can be fixed?


    Thank you for your time

    Much fuzz is in the air the last days regarding the recent decisions from the docker team.


    What to know about the end of Docker Free Teams | Docker
    We apologize for how we communicated and executed sunsetting Docker “Free Team” subscriptions, which alarmed the open source community. Read our FAQ to learn…
    www.docker.com


    How will this affect OMV? Will a decision be made to move to another service, like podman?


    Can anyone please explain in simple words how this change will affect us, the plain users?


    Thank you for your time in explaining all this.

    That didn't help since all of the columns are in one field. I just wanted to add up the memory use. Looks like is a little over 7GB.


    All I can guess is your memory use goes way up when actively using the containers.

    your guess is correct, because from the 32GB of RAM usage, currently only 8GB are free. The rest is consumed by the containers. However, this does not explain the high swap usage, unless what BernH claims is correct, a statement i cannot verify because my knowledge in linux is limited.

    Any chance you could post that in a format that doesn't break the formatting? Like a spreadsheet or csv? That is a lot of containers. Photoprism and its database alone are using 2.5GB of ram. I'm guessing things like paperless, onlyoffice, and duplicati use more when they are actually being used as well. What are you doing with the system other than docker?


    Here is the link in csv format, since the extension is onvalid by the uploader: https://fileshare.fsnaval.com/share/dockerstats


    Other than docker and acting as a NAS server for file sharing and movies streaming (rarely), no other uses.

    Good day to all,


    I have noticed that my system is systematically using all its swap memory. Is there a way i can increase it and how should i do it?


    I am running a lot of containers and maybe this is the cause of the high swap usage. I have 32GB of memory and 1TB nvme for OS, of which i hardly use 20%.


    Thank you!

    I don't think that's a wise approach. It's like refusing to get your oil changed because you're worried about a check engine line.


    The fix for this is literally less than 10sec.

    You do have a point here, nevertheless i will wait a couple of days more to see if anything new comes up before i proceed with the docker upgrade.

    I have also received the notification to upgrade the docker to the new version but after reading here, i will not do so. Is there a way we can choose to skip and/or ignore these docker upgrades from the update management menu, until another docker version comes up without having these issues?

    Good day all,


    I want to setup a backup job of my OS drive using the backup plugin, in particular the dd full disk option.

    However, i am not sure how to set it up correctly.


    In the attached images, i understand that the following fields should be filled in like below:


    Shared folder: None

    Method: dd full disk

    Root device: /dev/nvme0n1 (this is my OS drive)

    Keep: 2


    Is my understanding correct?


    However, i do not see where i should point the backup destination, as i want to backup on an external drive. What am i missing?


    Thank you all for your assistance.



    post the output of


    smartctl -a /dev/sdx


    change the x accordingly

    === START OF INFORMATION SECTION ===

    Model Family: Western Digital Red (SMR)

    Device Model: WDC WD40EFAX-68JH4N0

    Serial Number: WD-WX22D2021D59

    LU WWN Device Id: 5 0014ee 21261f4a1

    Firmware Version: 82.00A82

    User Capacity: 4,000,787,030,016 bytes [4.00 TB]

    Sector Sizes: 512 bytes logical, 4096 bytes physical

    Rotation Rate: 5400 rpm

    Form Factor: 3.5 inches

    Device is: In smartctl database [for details use: -P show]

    ATA Version is: ACS-3 T13/2161-D revision 5

    SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)

    Local Time is: Sun Sep 25 17:34:06 2022 EEST

    SMART support is: Available - device has SMART capability.

    SMART support is: Enabled


    === START OF READ SMART DATA SECTION ===

    SMART overall-health self-assessment test result: PASSED


    General SMART Values:

    Offline data collection status: (0x82) Offline data collection activity

    was completed without error.

    Auto Offline Data Collection: Enabled.

    Self-test execution status: ( 33) The self-test routine was interrupted

    by the host with a hard or soft reset.

    Total time to complete Offline

    data collection: (59760) seconds.

    Offline data collection

    capabilities: (0x7b) SMART execute Offline immediate.

    Auto Offline data collection on/off support.

    Suspend Offline collection upon new

    command.

    Offline surface scan supported.

    Self-test supported.

    Conveyance Self-test supported.

    Selective Self-test supported.

    SMART capabilities: (0x0003) Saves SMART data before entering

    power-saving mode.

    Supports SMART auto save timer.

    Error logging capability: (0x01) Error logging supported.

    General Purpose Logging supported.

    Short self-test routine

    recommended polling time: ( 2) minutes.

    Extended self-test routine

    recommended polling time: ( 190) minutes.

    Conveyance self-test routine

    recommended polling time: ( 2) minutes.

    SCT capabilities: (0x3039) SCT Status supported.

    SCT Error Recovery Control supported.

    SCT Feature Control supported.

    SCT Data Table supported.


    SMART Attributes Data Structure revision number: 16

    Vendor Specific SMART Attributes with Thresholds:

    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE

    1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 1

    3 Spin_Up_Time 0x0027 207 203 021 Pre-fail Always - 2650

    4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 93

    5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0

    7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0

    9 Power_On_Hours 0x0032 079 079 000 Old_age Always - 15390

    10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0

    11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0

    12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 93

    192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 42

    193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 2315

    194 Temperature_Celsius 0x0022 093 086 000 Old_age Always - 54

    196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0

    197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0

    198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0

    199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0

    200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0


    SMART Error Log Version: 1

    No Errors Logged


    SMART Self-test log structure revision number 1

    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

    # 1 Extended offline Interrupted (host reset) 10% 15365 -

    # 2 Short offline Completed without error 00% 8711 -

    # 3 Short offline Completed without error 00% 8543 -

    # 4 Short offline Completed without error 00% 8376 -

    # 5 Short offline Completed without error 00% 8208 -

    # 6 Short offline Completed without error 00% 8207 -

    # 7 Short offline Completed without error 00% 8039 -

    # 8 Short offline Completed without error 00% 7885 -

    # 9 Short offline Completed without error 00% 7717 -

    #10 Short offline Completed without error 00% 7549 -

    #11 Short offline Completed without error 00% 7381 -

    #12 Short offline Completed without error 00% 7213 -

    #13 Short offline Completed without error 00% 7045 -

    #14 Short offline Completed without error 00% 6879 -

    #15 Short offline Completed without error 00% 6711 -

    #16 Short offline Completed without error 00% 6571 -

    #17 Short offline Completed without error 00% 6551 -

    #18 Short offline Completed without error 00% 6383 -

    #19 Short offline Completed without error 00% 6216 -

    #20 Short offline Completed without error 00% 6081 -

    #21 Short offline Completed without error 00% 5914 -


    SMART Selective self-test log data structure revision number 1

    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS

    1 0 0 Not_testing

    2 0 0 Not_testing

    3 0 0 Not_testing

    4 0 0 Not_testing

    5 0 0 Not_testing

    Selective self-test flags (0x0):

    After scanning selected spans, do NOT read-scan remainder of disk.

    If Selective self-test is pending on power-up, resume after 0 minute delay.