Beiträge von bzzez

  • libapt-inst2.0 1.8.2.2 installation problem

    I've the same problem(rpi4), but not only with the "libapt-inst2.0 1.8.2.2" package. There are 62 packages that get installed over and over again.

    e.g. Unpacking sudo (1.8.27-1+deb10u3) over (1.8.27-1+deb10u3) ...



    After latest update to 5..6.3-1 I got system emails every day:


    but when I look at the list of current available updates the same packages are listed there.

    So "sudo apt update && sudo apt upgrade" installs all the packages (again). After this only the "libapt-inst2.0 1.8.2.2" package is still shows as upgradable, and "apt clean && apt install libapt-inst2.0" solves the problem for it.


    However, the above situation happens again after next run of the cron for automatic security updates.

  • Communication failure

    I've the same "Communication failure" problem when trying to enable or disable Extras repo.

    Sometimes the details tab show this:


    <html>
    <head><title>504 Gateway Time-out</title></head>
    <body bgcolor="white">
    <center><h1>504 Gateway Time-out</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>
    <!-- a padding to disable MSIE and Chrome friendly error page -->
    <!-- a padding to disable MSIE and Chrome friendly error page -->
    <!-- a padding to disable MSIE and Chrome friendly error page -->
    <!-- a padding to disable MSIE and Chrome friendly error page -->
    <!-- a padding to disable MSIE and Chrome friendly error page -->
    <!-- a padding to disable MSIE and Chrome friendly error page -->


    OMV 5.6.1-1 on raspberry pi 4.


    The system is not heavy loaded. Cleaned the brewers cache, tried with other browser. No difference.

    After log out, login the setting is in desired position, so looks like it's applied even there was an error.


    Has anybody found the root cause/solution of this ?

  • Locked users overview

    Hi,



    I'm too getting similar emails with subject "Locked users overview" and some strange content:



    ----------------------------------------------------
    The following users are locked/banned or are candidates for too many failed login attempts: Login Failures Latest failure From root 50501 02/14/72 23:48:01 daemon 18878 12/22/77 05:28:19 bin 6423 06/14/58 05:55:46 Q& &.s> !Z2t- 3N}1K q!V+D sys 2863 11/11/65 03:51:51 sync 35470 02/07/24 02:31:24 W e9E/~ games 46844 05/30/85 21:24:53 man 35748 02/05/33 23:59:32 r:}9 lp 15565 10/28/58 15:18:39 $ mail 45991 04/11/36 11:42:01 Uy3= news 23804 06/19/61 15:41:07 ' OD%JW( uucp 50400 06/16/90 06:31:56 MUd y&c8 [NONAME] ....


    and bunch of this lines
    ----------------------------------------------------


    No idea what is this.


    There is nothing similar in /var/log/auth.log file and no issue when logging in via web gui.


    Version 4.1.23-1 (Arrakis)
    Kernel Linux 4.19.57-v7+


    The server runs on rpi with no access from outside.

  • How to get SMART on external drives

    Thanks for the details @tkaiser.


    Zitat von tkaiser

    It would be great if you could double check with latest Raspbian release with all updates applied too whether you can query your disk via SMART there.


    I was planning to give it a try as you suggested, but noticed new kernel version is available for OMV (and some other libs too) and after updating to the new kernel version the problem with SMART has gone, it works as expected.


    Linux 4.19.42


    smartctl -x /dev/sda
    smartctl 6.6 2016-05-31 r4324 [armv7l-linux-4.19.42-v7+] (local build)
    Copyright (C) 2002-16, Bruce Allen, Christian Franke, http://www.smartmontools.org


    === START OF INFORMATION SECTION ===
    Model Family: Seagate Samsung SpinPoint M8 (AF)
    Device Model: ST1000LM024 HN-M101MBB
    Serial Number: S2ZPJ9DD420656
    LU WWN Device Id: 5 0004cf 20a1a8a5d
    Firmware Version: 2AR20002
    User Capacity: 1,000,204,886,016 bytes [1.00 TB]
    Sector Sizes: 512 bytes logical, 4096 bytes physical
    Rotation Rate: 5400 rpm
    Form Factor: 2.5 inches
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: ATA8-ACS T13/1699-D revision 6
    SATA Version is: SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
    Local Time is: Sat May 18 19:57:52 2019 +04
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    AAM feature is: Disabled
    APM level is: 127 (intermediate level with standby)
    Rd look-ahead is: Enabled
    Write cache is: Enabled
    ATA Security is: Disabled, NOT FROZEN [SEC1]
    Wt Cache Reorder: Enabled


    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED

  • How to get SMART on external drives

    I've the same issue on ARM (rpi 3) with Seagate .


    Open Media Vault, version 4.1.22-1 (Arrakis)
    Linux 4.14.98-v7+ #1200
    smartctl 6.6 2016-05-31 r4324 [armv7l-linux-4.14.98-v7+] (local build)


    smartctl --health -d sat /dev/sda

    Read Device Identity failed: scsi error unsupported field in scsi command
    A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.


    with -T permissive


    smartctl --health -d sat -T permissive -x /dev/sda


    Read Device Identity failed: scsi error unsupported field in scsi command


    === START OF INFORMATION SECTION ===
    Device Model: [No Information Found]
    Serial Number: [No Information Found]
    Firmware Version: [No Information Found]
    Device is: Not in smartctl database [for details use: -P showall]
    ATA Version is: [No Information Found]
    Local Time is: Thu May 16 23:55:02 2019 +04
    SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
    SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
    A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options


    I added UAS blacklist in /etc/modprobe.d/usb-storage-quirks.conf for this drive but it did not help.
    Actually without blacklisting lsusb -t shows that the driver is usb_storage and not uas:


    /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
    |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
    |__ Port 3: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M


    Output of armbianmonitor -u
    http://ix.io/1Jf0


    @tkaiser you mentioned "on ARM all of this happens automagically in the background" - looks like this is why blacklisting did not make any difference in Driver.
    Any idea what can be the problem ?


    Thanks