Beiträge von tannaroo

  • Docker Stacks

    Zitat von KM0201

    Is your server online?


    What is the output of


    Code
    ping -c5 google.com


    It looks like it might be a DNS error.

    Its online and receiving data

  • Docker Stacks

    Zitat von KM0201

    Never seen that one.


    Did you try a second one to see if maybe it was just something wrong with that stack?

    Yes tried all of them.


    This is a further log for resilio. Looks like some connection issue?

  • Docker Stacks

    portainer has been uninstalled/removed from omv web gui.

    setup docker compose with mapped data drive per post #2

    ran docker-compose up -d

    logged into portainer ui

    tried to deploy one of my stacks - didn't work.

    edit: log says No log line matching the '' filter

  • Docker Stacks

    Ok. I don't know what I am doing. And I am giving up with this. I just dont have the patience anymore.


    For me, I always run into problems and yes it is probably 99% the user.

  • Docker Stacks

    I've done all that but I still cant get the stacks working. Just got a long red box message something about the container is already in use but its not installed.

  • Docker Stacks

    I've had to re-install OMV. Tring to redeploy my saved stacks but none of them are working. Has the way stacks are deployed in Portainer changed recently?

  • nginx failure, then succeeds but then fails agains

    Zitat von Zoki

    how are youaccessing the drive?

    Boot linux live cd from usb stick? Then the question is where to put the copy. Maybe you can add snother usb stick which you can read on your other computer.

    Then use the file manager to copy the file. /my_broken_disk/etc/openmediavault/config.xml to that usb. unplug the usb and try to read the file from windows.

    i've setup a new omv installation from a usb stick, then using nano to read the config file but I wanted to copy the contents into a text file some how but it wont allow me to copy the contents from nano

  • nginx failure, then succeeds but then fails agains

    not sure if that i'm chasing. basically my omv system is on a standalone drive, docker is on another drive, then i have several data drives.


    if i setup a new omv system on a standalone drive and use the same directories for docker, shared folders etc - can the new omv work with my old docker setup (i.e. if I install docker to my existing standalone drive)?

  • nginx failure, then succeeds but then fails agains

    These are the errors (abridged as can't copy all of it) but it shows the attributes you were after. I tried running fsck -p /dev/sda1 but it hasn't seem to have fixed the error


    Is the drive toast or can it be recovered?


    root@OMV:~# smartctl -a /dev/sda

    smartctl 6.6 2017-11-05 r4594 [x86_64-linux-5.10.0-0.bpo.8-amd64] (local build)

    Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

    === START OF INFORMATION SECTION ===

    Model Family: IBM Travelstar 48GH, 30GN, and 15GN

    Device Model: IC25N020ATDA04-0

    Serial Number: 63A63J51410

    Firmware Version: DA3OA70A

    User Capacity: 20,003,880,960 bytes [20.0 GB]

    Sector Size: 512 bytes logical/physical

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

    ATA Version is: ATA/ATAPI-5 T13/1321D revision 3

    Local Time is: Sat Jan 29 19:14:18 2022 GMT

    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: ( 0) The previous self-test routine completed

    without error or no self-test has ever

    been run.

    Total time to complete Offline

    data collection: ( 645) seconds.

    Offline data collection

    capabilities: (0x1b) SMART execute Offline immediate.

    Auto Offline data collection on/off supp ort.

    Suspend Offline collection upon new

    command.

    Offline surface scan supported.

    Self-test supported.

    No Conveyance Self-test supported.

    No 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.

    No General Purpose Logging support.

    Short self-test routine

    recommended polling time: ( 2) minutes.

    Extended self-test routine

    recommended polling time: ( 27) minutes.

    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 0x000b 081 081 062 Pre-fail Always - 27459770

    2 Throughput_Performance 0x0005 103 103 040 Pre-fail Offline - 6012

    3 Spin_Up_Time 0x0007 126 126 033 Pre-fail Always - 1

    4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 1250

    5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0

    7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0

    8 Seek_Time_Performance 0x0005 120 120 040 Pre-fail Offline - 36

    9 Power_On_Hours 0x0012 048 048 000 Old_age Always - 22951

    10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0

    12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 849

    191 G-Sense_Error_Rate 0x000a 100 100 000 Old_age Always - 0

    192 Power-Off_Retract_Count 0x0032 099 099 000 Old_age Always - 214

    193 Load_Cycle_Count 0x0012 094 094 000 Old_age Always - 69894

    194 Temperature_Celsius 0x0002 157 157 000 Old_age Always - 35 (Min/Max 13/66)

    196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 219

    197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 66

    198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0

    199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0



  • nginx failure, then succeeds but then fails agains

    I've attached a monitor, disconnected all external drives and it seems to get to a certain point and not go further, so I guess the system drive is toast.

    I tried to setup using recovery model to run fsck -p but it stops below.

    Is there a way I can repair the drive somehow without a full re-install?


  • nginx failure, then succeeds but then fails agains

    Zitat von Soma

    Check the SMART status of that drive and see the errors of fields 5; 197; 198 on information-->>Attributes

    unfortunately, I can't log in now it says 'failed to connect to socket' with this error message.

    Code
    Error #0:
OMV\Rpc\Exception: Failed to connect to socket: Connection refused in /usr/share/php/openmediavault/rpc/rpc.inc:141
Stack trace:
#0 /var/www/openmediavault/rpc/session.inc(57): OMV\Rpc\Rpc::call('UserMgmt', 'authUser', Array, Array, 2, true)
#1 [internal function]: OMVRpcServiceSession->login(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('login', Array, Array)
#4 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('Session', 'login', Array, Array, 3)
#5 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()
#6 {main}

  • nginx failure, then succeeds but then fails agains

    Thanks, I see a lot of I/O errors - would this mean I have a failing hard drive (sdc) which is causing nginx failure?

    root@omv:~# dmesg | grep error

    [157379.641395] blk_update_request: I/O error, dev sdc, sector 19127064 op 0x0:( READ) flags 0x0 phys_seg 1 prio class 0

    [157572.140009] blk_update_request: I/O error, dev sdc, sector 19127064 op 0x0:( READ) flags 0x0 phys_seg 1 prio class 0

    [161358.723272] blk_update_request: I/O error, dev sdc, sector 19127064 op 0x0:( READ) flags 0x0 phys_seg 1 prio class 0

    [161545.161932] blk_update_request: I/O error, dev sdc, sector 19127064 op 0x0:( READ) flags 0x0 phys_seg 1 prio class 0

    [165331.790198] blk_update_request: I/O error, dev sdc, sector 19127064 op 0x0:( READ) flags 0x0 phys_seg 1 prio class 0

    [165518.152838] blk_update_request: I/O error, dev sdc, sector 19127064 op 0x0:( READ) flags 0x0 phys_seg 1 prio class 0

    [167459.557361] blk_update_request: I/O error, dev sdc, sector 14424904 op 0x0:( READ) flags 0x80700 phys_seg 32 prio class 0

    res 51/40:28:b8:59:3e/00:00:b7:27:74/e1 Emask 0x9 (medi a error)

    [167639.271268] ata1.00: error: { UNC }

    [167639.276138] sd 0:0:0:0: [sdc] tag#2 Add. Sense: Unrecovered read error - aut o reallocate failed

    [167639.276145] blk_update_request: I/O error, dev sdc, sector 20863416 op 0x0:( READ) flags 0x80700 phys_seg 5 prio class 0

    res 51/40:08:b8:59:3e/00:00:2f:27:74/e1 Emask 0x9 (medi a error)

    [167643.595139] ata1.00: error: { UNC }

    [167643.600005] sd 0:0:0:0: [sdc] tag#18 Add. Sense: Unrecovered read error - au to reallocate failed

    [167643.600013] blk_update_request: I/O error, dev sdc, sector 20863416 op 0x0:( READ) flags 0x0 phys_seg 1 prio class 0

    res 51/40:08:b8:59:3e/00:00:27:eb:48/e1 Emask 0x9 (medi a error)


    This is only part of it as the whole error is more than 10000 characters so I couldn't paste here

  • nginx failure, then succeeds but then fails agains

    This is the output - not sure what it means