Jump to content

bonienl

Community Developer
  • Content Count

    7457
  • Joined

  • Last visited

  • Days Won

    42

Posts posted by bonienl


  1. On 6/11/2019 at 8:13 PM, itimpi said:

    I seem to get a hash key mismatch on every file which is a hard link (at the User Share level) to another file in the same User Share.   Is this expected behaviour?    Is there anything I can do to avoid getting this error?  

     

    The links are in a sub-folder of a user share - do I have to use the Custom folder option to exclude the sub-folders containing these hard links.  If so can I have a folder name of the form FILMS/!3D.

    I have never tested with hard links. This utility write information in the extended attributes of a file, and I am not sure how these are handled in hard links.

     

    When excluding folders, you can enter its unique name (e.g. !3D), a full path is automatically generated by the tool.


  2. On 6/11/2019 at 6:06 PM, DivideByZero said:

    I could use another set of eyes on this issue:  Integrity check ran last night and created an bad.log export.  Listed below is the exact message:

    BLAKE2 hash key mismatch,  is corrupted
    BLAKE2 hash key mismatch,  is corrupted
    BLAKE2 hash key mismatch,  is corrupted

     

    No path or file name to reference.  I checked the SysLog and the following messages are logged:

     

    Jun 10 23:34:47 Tower bunker: error: BLAKE2 hash key mismatch, is corrupted
    Jun 10 23:50:56 Tower bunker: error: BLAKE2 hash key mismatch, is corrupted

    Jun 11 03:47:27 Tower bunker: error: BLAKE2 hash key mismatch, is corrupted

     

    Apparently there are 3 files that require attention, but no reference to the specific files.  Does anyone have any idea how I can proceed?

     

    Thanks

     

     

    This is strange, because normally the file name is included in the message, but it seems the file name is empty here.

     

    You could make a selective "check" per disk and try to pinpoint the file(s).

     


  3. 5 hours ago, Marshalleq said:

    Why the unraid GUI has such a limited capability for network configuration

    Assigning interfaces is possible from the GUI (see Interface Rules).

    5 hours ago, Marshalleq said:

    Why it requires so many reboots

    It shouldn't. With a correct procedure a single reboot is required.

    5 hours ago, Marshalleq said:

    Why it loses connection and requires local console access

    When tossing interfaces, it requires to move the physical cable


  4. If you have a cache device and "appdata" is set to "cache only" then it is preferred to use "/mnt/cache/appdata".

    When no cache device is present then use "/mnt/user/appdata" instead.

     

    "/mnt/disks" refers to "Unassigned Devices". Some users prefer to use UD to make a dedicated disk for Docker instead of the standard cache device.

     


  5. There is a syntax error in the gateway declaration in the network.cfg file.

    GATEWAY[0]="192.168.1.1#213"

    The "#213" part must be removed. This is automatically done when upgrading via the GUI (legacy removal).

    Did you do a manual upgrade?