Error: openmediavault-update-smart-drivedb

  • I receive the following error message by mail:


    /etc/cron.weekly/openmediavault-update-smart-drivedb:
    mesg: ttyname failed: Unpassender IOCTL (I/O-Control) fürdas Gerät



    A query with smartctl provides the following information for only a drive:
    === START OF INFORMATION SECTION ===
    Device Model: WDC WD800AAJB-00J3A0
    Serial Number: WD-.................
    LU WWN Device Id: 5 0014ee 206df06af
    Firmware Version: 01.03E01
    User Capacity: 80.026.361.856 bytes [80,0 GB]
    Sector Size: 512 bytes logical/physical
    Device is: Not in smartctl database [for details use: -P showall]
    ATA Version is: ATA8-ACS (minor revision not indicated)
    Transport Type: Parallel, ATA8-APT
    Local Time is: Wed Dec 27 23:28:51 2017 CET
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled


    All other drives have: Device is: In smartctl database


    How can I update the database?

  • The database thing is new to me. I also saw the first part of the message:


    mesg: ttyname failed: Inappropriate ioctl for device


    I think this won’t help you.


    Greetings Hoppel

    ----------------------------------------------------------------------------------
    openmediavault 6 | proxmox kernel | zfs | docker | kvm
    supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
    ---------------------------------------------------------------------------------------------------------------------------------------

    Einmal editiert, zuletzt von hoppel118 ()

  • You may need to update your database:


    Source: https://manpages.debian.org/st…e-smart-drivedb.8.en.html

  • Somehow I still do etas wrong. I just do not get any further.


    -bash: update-smart-drivedb: command not found.


    If it is possible, please give a short tutorial on how to update the database via PuTTY.
    I'm Linux beginner, so the easy question to the experts.

  • I get similar Error Messages every night. Something seems strange with the cron and anacron jobs.



    Some examples:
    I w mails at the same time
    Mail1, everthing fine:


    Mail2, stating error:

    Code
    /etc/cron.daily/openmediavault-cron-apt:
    mesg: ttyname failed: Unpassender IOCTL (I/O-Control) für das Gerät

    Corresponding Log-Entrys:


    Bottomline:


    I get a lot of "mesg: ttyname failed: Unpassender IOCTL (I/O-Control) für das Gerät" Error messages related to anacron (even if not activated) and I aswell don't know where to start.

  • @Hotzenplotz78


    Have a look at the link I posted above. Some other guys and I had the same error as you.


    Greetings Hoppel

    ----------------------------------------------------------------------------------
    openmediavault 6 | proxmox kernel | zfs | docker | kvm
    supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
    ---------------------------------------------------------------------------------------------------------------------------------------

  • For me it works as expected. So it should also work for you. ;)


    Greetings Hoppel

    ----------------------------------------------------------------------------------
    openmediavault 6 | proxmox kernel | zfs | docker | kvm
    supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
    ---------------------------------------------------------------------------------------------------------------------------------------

  • @daniel.971 The fix he meant was that:

    The issue is explained here and here and is no problem, it simply creates an annoying output, nothing more.


    A simple fix may be to edit /root/.profile and replace

    Bash
    mesg n || true

    with

    Bash
    test -t 0 && mesg n || true


    @hoppel118


    It worked for me, the message is gone, only valid messages got through.
    But just to get me smarter than before: What did I do with that? I don't understand all parts of the command......

  • Hi,


    i got the same warning message.


    The solution that @Hotzenplotz78 postet from @votdev only supress the warning message.


    The basic problem is that den script 'update-smart-drivedb', from the smartmontools, was removed
    by debian (and ubuntu since 16.04) because of 'unauthenticated downloads' (see here).


    If you have hdd's that wasn't in your drivedb.h, you can manually update the drivedb.


    For example like this (Taken from here - german)




    This didn't remove the warning message, but you get an actual drivedb for the smartmontools.


    An other solution was to manually add the script back. But i didn't test this.


    I hope it will help someone :)

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!