Hitcher

Members
  • Posts

    40
  • Joined

  • Last visited

Report Comments posted by Hitcher

  1. 13 hours ago, JorgeB said:

    It can be, since vt-d is now disable delete and re-create the docker image and monitor to make sure no more corruptions are found.

    Thanks, will do.

     

    EDIT: Deleted and rebuilt the docker image but the corruption is still there.

     

    May 29 14:57:46 Tower emhttpd: shcmd (77): /usr/local/sbin/mount_image '/mnt/cache/docker.img' /var/lib/docker 20
    May 29 14:57:46 Tower kernel: loop2: detected capacity change from 0 to 41943040
    May 29 14:57:46 Tower kernel: BTRFS: device fsid e7cdcd01-5af4-4abe-a9e1-80c5bf296181 devid 1 transid 105165 /dev/loop2 scanned by udevd (6410)
    May 29 14:57:46 Tower kernel: BTRFS info (device loop2): flagging fs with big metadata feature
    May 29 14:57:46 Tower kernel: BTRFS info (device loop2): using free space tree
    May 29 14:57:46 Tower kernel: BTRFS info (device loop2): has skinny extents
    May 29 14:57:46 Tower kernel: BTRFS info (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 259, gen 0
    May 29 14:57:46 Tower kernel: BTRFS info (device loop2): enabling ssd optimizations

    What should I do next?

     

    Thanks.

  2. On 5/28/2022 at 12:27 PM, JorgeB said:

    Start by running a scrub, if uncorrectable errors are found look in the syslog for the affected files, if no errors are found or they are corrected reset the counters and keep monitoring, more info here:

    https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582

     

    Did a search for BTRFS in my diagnostics. Is this the corruption in question?

     

    May 29 14:57:46 Tower kernel: BTRFS info (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 259, gen 0

     

    tower-diagnostics-20220529-1638.zip

    • Like 1
  3. Found this thread through this Kodi forum post -

     

    Quote

    NFS network browsing is broken on some servers, certainly FreeNAS and Unraid servers.

    It's a FreeNAS/Unraid issue. Most other NFS servers can be browsed without a problem. The FreeNAS and Unraid servers may just need rpcbind to be compiled with the option --enable-rmtcalls.

    If your NFS server cannot be browsed by Kodi then report the issue to your NFS server software maintainer(s) so that they can hopefully fix it.

    Any thoughts as this is still a problem?