Hoox

Members
  • Posts

    19
  • Joined

  • Last visited

Posts posted by Hoox

  1. On 11/3/2022 at 3:23 AM, biggiesize said:

    Might possibly be a permissions issue. Unraid defaults to nobody:users 99:100 for permissions. Try running these commands from the unraid terminal.

     

    # Owned by user ID of Docker container (1000)

    chown -R 1000 /mnt/user/appdata/ddns-updater

    # all access (for creating json database file data/updates.json)

    chmod 700 /mnt/user/appdata/ddns-updater

    # read access only

    chmod 400 /mnt/user/appdata/ddns-updater/config.json

    Thanks, did this. Still the same.

    ERROR unexpected end of JSON input

    Tried updating to new version also, but same error.

  2. 1 hour ago, biggiesize said:

    Make sure you have bind mounted the file correctly. Usually unexpected end of JSON input means it's an empty file or there is a missing bracket somewhere. The JSON you sent looks correct though, maybe try with https://jsonlint.com/ to be sure.

    jsonlint.com says it's valid.

    Any way I can debug or see if it manages to read the json file? To me it looks kind of like it doesnt even read it.

  3. I'm trying to run the ddns container, but I keep getting "ERROR unexpected end of JSON input"

     

    This is my docker run from Unraid:

    docker run
    -d
    --name='ddns-updater'
    --net='bridge'
    -e TZ="Europe/Paris"
    -e HOST_OS="Unraid"
    -e HOST_HOSTNAME="Unraid"
    -e HOST_CONTAINERNAME="ddns-updater"
    -e 'TZ'='Europe/Berlin'
    -e 'PUBLICIP_FETCHERS'='all'
    -e 'PUBLICIP_HTTP_PROVIDERS'='all'
    -e 'PUBLICIPV4_HTTP_PROVIDERS'='all'
    -e 'PUBLICIPV6_HTTP_PROVIDERS'='all'
    -e 'PUBLICIP_DNS_PROVIDERS'='all'
    -e 'PUBLICIP_DNS_TIMEOUT'='3s'
    -e 'UPDATE_COOLDOWN_PERIOD'='5m'
    -e 'HTTP_TIMEOUT'='10s'
    -e 'PUID'='99'
    -e 'PGID'='100'
    -e 'UMASK'='002'
    -e 'BACKUP_DIRECTORY'='/updater/data/backup'
    -e 'BACKUP_PERIOD'='0'
    -e 'LOG_LEVEL'='info'
    -e 'LOG_CALLER'='hidden'
    -e 'ROOT_URL'='/'
    -e 'SHOUTRRR_ADDRESSES'=''
    -e 'HEALTH_SERVER_ADDRESS'='127.0.0.1:9999'
    -l net.unraid.docker.managed=dockerman
    -l net.unraid.docker.webui='http://[IP]:[PORT:8000]'
    -l net.unraid.docker.icon='https://github.com/DiamondPrecisionComputing/unraid-templates/blob/main/templates/img/ddnsgopher.png?raw=true'
    -p '8008:8000/tcp'
    -v '/mnt/user/appdata/ddns-updater':'/updater/data':'rw' 'qmcgaw/ddns-updater'

     

    I tried various chown and chmod commands on the config.json file but still same error message. Even if I rename the config.json to something entirely different.

  4. Just tells me the drive. Maybe that means it's in metadata?

    Oct 30 12:48:08 Unraid kernel: BTRFS info (device nvme0n1p1): scrub: started on devid 1
    Oct 30 12:48:08 Unraid kernel: BTRFS info (device nvme0n1p1): scrub: started on devid 2
    Oct 30 12:48:13 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 202, gen 0
    Oct 30 12:48:13 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 7001026560 on dev /dev/nvme0n1p1
    Oct 30 12:48:21 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 247, gen 0
    Oct 30 12:48:21 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 7001026560 on dev /dev/sdb1
    Oct 30 12:48:50 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 203, gen 0
    Oct 30 12:48:50 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 130705846272 on dev /dev/nvme0n1p1
    Oct 30 12:48:50 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 204, gen 0
    Oct 30 12:48:50 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 130705854464 on dev /dev/nvme0n1p1
    Oct 30 12:48:50 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 205, gen 0
    Oct 30 12:48:50 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 130705858560 on dev /dev/nvme0n1p1
    Oct 30 12:48:51 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 206, gen 0
    Oct 30 12:48:51 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 132943687680 on dev /dev/nvme0n1p1
    Oct 30 12:48:52 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 207, gen 0
    Oct 30 12:48:52 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 134249148416 on dev /dev/nvme0n1p1
    Oct 30 12:48:54 Unraid kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 145327968256 on dev /dev/nvme0n1p1, physical 145327968256, root 5, inode 344007, offset 5067124736, length 4096, links 1 (path: system/docker/docker-xfs.img)
    Oct 30 12:48:54 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 208, gen 0
    Oct 30 12:48:54 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 145327968256 on dev /dev/nvme0n1p1
    Oct 30 12:48:59 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 209, gen 0
    Oct 30 12:48:59 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 188664184832 on dev /dev/nvme0n1p1
    Oct 30 12:49:15 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 210, gen 0
    Oct 30 12:49:15 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 339410247680 on dev /dev/nvme0n1p1
    Oct 30 12:49:23 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 211, gen 0
    Oct 30 12:49:23 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 212, gen 0
    Oct 30 12:49:23 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 399801520128 on dev /dev/nvme0n1p1
    Oct 30 12:49:23 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 399793057792 on dev /dev/nvme0n1p1
    Oct 30 12:49:24 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 213, gen 0
    Oct 30 12:49:24 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 415410094080 on dev /dev/nvme0n1p1
    Oct 30 12:49:25 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 214, gen 0
    Oct 30 12:49:25 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 423818018816 on dev /dev/nvme0n1p1
    Oct 30 12:49:31 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 215, gen 0
    Oct 30 12:49:31 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 457979002880 on dev /dev/nvme0n1p1
    Oct 30 12:49:32 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 216, gen 0
    Oct 30 12:49:32 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 467824631808 on dev /dev/nvme0n1p1
    Oct 30 12:49:36 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 217, gen 0
    Oct 30 12:49:36 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 487593226240 on dev /dev/nvme0n1p1
    Oct 30 12:49:36 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 218, gen 0
    Oct 30 12:49:36 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 487800012800 on dev /dev/nvme0n1p1
    Oct 30 12:49:47 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 219, gen 0
    Oct 30 12:49:47 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 541795184640 on dev /dev/nvme0n1p1
    Oct 30 12:49:49 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 220, gen 0
    Oct 30 12:49:49 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 551333945344 on dev /dev/nvme0n1p1
    Oct 30 12:49:50 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 221, gen 0
    Oct 30 12:49:50 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 557072101376 on dev /dev/nvme0n1p1
    Oct 30 12:49:52 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 222, gen 0
    Oct 30 12:49:52 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 565232926720 on dev /dev/nvme0n1p1
    Oct 30 12:49:53 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 223, gen 0
    Oct 30 12:49:53 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 567585722368 on dev /dev/nvme0n1p1
    Oct 30 12:49:56 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 224, gen 0
    Oct 30 12:49:56 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 1188201512960 on dev /dev/nvme0n1p1
    Oct 30 12:49:57 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 225, gen 0
    Oct 30 12:49:57 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 1116920274944 on dev /dev/nvme0n1p1
    Oct 30 12:49:59 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 226, gen 0
    Oct 30 12:49:59 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 1177725014016 on dev /dev/nvme0n1p1
    Oct 30 12:49:59 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 227, gen 0
    Oct 30 12:49:59 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 228, gen 0
    Oct 30 12:49:59 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 726756610048 on dev /dev/nvme0n1p1
    Oct 30 12:49:59 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 726764367872 on dev /dev/nvme0n1p1
    Oct 30 12:50:00 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 229, gen 0
    Oct 30 12:50:00 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 729036849152 on dev /dev/nvme0n1p1
    Oct 30 12:50:02 Unraid kernel: BTRFS info (device nvme0n1p1): scrub: finished on devid 1 with status: 0
    Oct 30 12:51:47 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 248, gen 0
    Oct 30 12:51:47 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 130705846272 on dev /dev/sdb1
    Oct 30 12:51:47 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 249, gen 0
    Oct 30 12:51:47 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 130705854464 on dev /dev/sdb1
    Oct 30 12:51:47 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 250, gen 0
    Oct 30 12:51:47 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 130705858560 on dev /dev/sdb1
    Oct 30 12:51:51 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 251, gen 0
    Oct 30 12:51:51 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 132943687680 on dev /dev/sdb1
    Oct 30 12:51:54 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 252, gen 0
    Oct 30 12:51:54 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 134249148416 on dev /dev/sdb1
    Oct 30 12:52:05 Unraid kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 145327968256 on dev /dev/sdb1, physical 145306996736, root 5, inode 344007, offset 5067124736, length 4096, links 1 (path: system/docker/docker-xfs.img)
    Oct 30 12:52:05 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 253, gen 0
    Oct 30 12:52:05 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 145327968256 on dev /dev/sdb1
    Oct 30 12:52:33 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 254, gen 0
    Oct 30 12:52:33 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 188664184832 on dev /dev/sdb1
    Oct 30 12:54:03 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 255, gen 0
    Oct 30 12:54:03 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 339410247680 on dev /dev/sdb1
    Oct 30 12:54:46 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 256, gen 0
    Oct 30 12:54:46 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 399801520128 on dev /dev/sdb1
    Oct 30 12:54:46 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 257, gen 0
    Oct 30 12:54:46 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 399793057792 on dev /dev/sdb1
    Oct 30 12:54:53 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 258, gen 0
    Oct 30 12:54:53 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 415410094080 on dev /dev/sdb1
    Oct 30 12:54:59 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 259, gen 0
    Oct 30 12:54:59 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 423818018816 on dev /dev/sdb1
    Oct 30 12:55:27 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 260, gen 0
    Oct 30 12:55:27 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 457979002880 on dev /dev/sdb1
    Oct 30 12:55:34 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 261, gen 0
    Oct 30 12:55:34 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 467824631808 on dev /dev/sdb1
    Oct 30 12:55:51 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 262, gen 0
    Oct 30 12:55:51 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 487593226240 on dev /dev/sdb1
    Oct 30 12:55:51 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 263, gen 0
    Oct 30 12:55:51 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 487800012800 on dev /dev/sdb1
    Oct 30 12:56:46 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 264, gen 0
    Oct 30 12:56:46 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 541795184640 on dev /dev/sdb1
    Oct 30 12:56:54 Unraid kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 549850263552 on dev /dev/sdb1, physical 545534324736, root 5, inode 344007, offset 17856720896, length 4096, links 1 (path: system/docker/docker-xfs.img)
    Oct 30 12:56:54 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 265, gen 0
    Oct 30 12:56:54 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 549850263552 on dev /dev/sdb1
    Oct 30 12:56:56 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 266, gen 0
    Oct 30 12:56:56 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 551333945344 on dev /dev/sdb1
    Oct 30 12:57:03 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 267, gen 0
    Oct 30 12:57:03 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 557072101376 on dev /dev/sdb1
    Oct 30 12:57:11 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 268, gen 0
    Oct 30 12:57:11 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 565232926720 on dev /dev/sdb1
    Oct 30 12:57:15 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 269, gen 0
    Oct 30 12:57:15 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 567585722368 on dev /dev/sdb1
    Oct 30 12:57:29 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 270, gen 0
    Oct 30 12:57:29 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 1188201512960 on dev /dev/sdb1
    Oct 30 12:57:37 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 271, gen 0
    Oct 30 12:57:37 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 1116920274944 on dev /dev/sdb1
    Oct 30 12:57:49 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 272, gen 0
    Oct 30 12:57:49 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 1177725014016 on dev /dev/sdb1
    Oct 30 12:57:50 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 273, gen 0
    Oct 30 12:57:50 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 726756610048 on dev /dev/sdb1
    Oct 30 12:57:50 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 274, gen 0
    Oct 30 12:57:50 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 726764367872 on dev /dev/sdb1
    Oct 30 12:57:50 Unraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/sdb1 errs: wr 0, rd 0, flush 0, corrupt 275, gen 0
    Oct 30 12:57:50 Unraid kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 729036849152 on dev /dev/sdb1
    Oct 30 12:57:59 Unraid kernel: BTRFS info (device nvme0n1p1): scrub: finished on devid 2 with status: 0

    What's the best/correct way to migrate cache to pool and delete/recreate cache?

     

  5. Tried to run a full balance on my cache pool but came out with balance: ended with status: -5

    Never ran a scrub, so I did that and found about 80 errors. Ran again with repair and it managed to repair about half.

    Now I get

    btrfs scrub status /mnt/cache
    UUID:             60ebf4ec-dfe8-4615-9212-af5cdb217848
    Scrub started:    Sun Oct 30 12:48:08 2022
    Status:           finished
    Duration:         0:09:51
    Total to scrub:   502.49GiB
    Rate:             871.18MiB/s
    Error summary:    csum=57
      Corrected:      0
      Uncorrectable:  57
      Unverified:     0

     

    Whats the best way to proceed? Should I remove and recreate the cache pool?

    Can I pinpoint the files that reside in the uncorrectable areas to find out if I'm able to just recreate those?

  6. Hi,

     

    I keep getting kernel panics on my 6.9.2 server. I read about the docker macvlan solution, and I think I've done the suggested solution, if I understand it correctly. None of my docker containers got static IPs and my vlans (not br0) are also configured with dynamic IP.

     

    I guess the kernel panic is sometime between May  4 03:40:51 and 07:16:31. It seems to be the pattern as I usually see the mover running at 3:40 before needing to reset the server in the morning.

     

    Any clue on what's going on?

    PXL_20210504_051347769 (1).jpg

    unraid-diagnostics-20210504-0726.zip unraid-syslog-10.0.0.8-20210504-0525.zip

  7. Any clue on how to get RPC connection to transmission from other docker containers (Radarr, Sonarr etc.)?

    This is my transmission settings.json

        "rpc-authentication-required": false,
        "rpc-bind-address": "0.0.0.0",
        "rpc-enabled": true,
        "rpc-host-whitelist": "",
        "rpc-host-whitelist-enabled": false,
        "rpc-password": "{3b46cf1a32c36234d53a361bce15946e9ecfd7e91RLaWffw",
        "rpc-port": 9091,
        "rpc-url": "/transmission/",
        "rpc-username": "user11",
        "rpc-whitelist": "127.0.0.1,192.*.*.*",
        "rpc-whitelist-enabled": false,

    Sonarr just says "Unable to connect". I can get to the webinterface.

    If I'm going to http://ip:9091/transmission/rpc/ I get a website showing 409: Conflict. "Your request had an invalid session-id header"

    Anyone knows how to fix this?

  8. Sorry for the late reply.

    I have still not managed to solve this.

     

    I tried to run the commands you listed and running the mover again. Still same error messages.

    Looks like all files/dirs were correct before running the commands (files were 660 without exec bit).

     

    I also deleted all created users in unraid and just copy files to the cache using guest through SMB. Still same errors.

     

    I found another tread on the forum with a problem like this that was found to be hardware error. I checked that and I don't have anything that could show hardware errors in the syslog.

     

    I haven't changed anything in the config files or running any addons. Could my mover script be wrong?

  9. I still get the same errors unfortunately.

    Seems like the pictures are getting copied though, but not removed from cache drive.

     

    Aug 9 13:42:42 Atom emhttp: shcmd (62): /usr/local/sbin/mover |& logger &
    Aug 9 13:42:42 Atom logger: mover started
    Aug 9 13:42:42 Atom logger: moving Photo/
    Aug 9 13:42:42 Atom logger: ./Photo/FOTOGRAF NANO 2012/Shutter stock/._shutterstock_108684953.tif
    Aug 9 13:42:42 Atom logger: rsync: get_xattr_data: lgetxattr("Photo","user.org.netatalk.supports-eas.zQdo9D",0) failed: Exec format error (
    Aug 9 13:42:42 Atom logger: .d..t...... Photo/
    Aug 9 13:42:42 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/
    Aug 9 13:42:42 Atom logger: .d..tp..... Photo/FOTOGRAF NANO 2012/Shutter stock/
    Aug 9 13:42:42 Atom logger: >f+++++++++ Photo/FOTOGRAF NANO 2012/Shutter stock/._shutterstock_108684953.tif
    Aug 9 13:42:48 Atom logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7]
    Aug 9 13:42:48 Atom logger: ./Photo/FOTOGRAF NANO 2012/Shutter stock/shutterstock_108684953.tif
    Aug 9 13:42:48 Atom logger: rsync: get_xattr_data: lgetxattr("Photo","user.org.netatalk.supports-eas.zQdo9D",0) failed: Exec format error (
    Aug 9 13:42:48 Atom logger: .d..t...... Photo/
    Aug 9 13:42:48 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/
    Aug 9 13:42:48 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/Shutter stock/
    Aug 9 13:42:48 Atom logger: >f+++++++++ Photo/FOTOGRAF NANO 2012/Shutter stock/shutterstock_108684953.tif
    Aug 9 13:42:51 Atom logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7]
    Aug 9 13:42:51 Atom logger: ./Photo/FOTOGRAF NANO 2012/Shutter stock/shutterstock_76435258.tif
    Aug 9 13:42:51 Atom logger: rsync: get_xattr_data: lgetxattr("Photo","user.org.netatalk.supports-eas.zQdo9D",0) failed: Exec format error (
    Aug 9 13:42:51 Atom logger: .d..t...... Photo/
    Aug 9 13:42:51 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/
    Aug 9 13:42:51 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/Shutter stock/
    Aug 9 13:42:51 Atom logger: >f+++++++++ Photo/FOTOGRAF NANO 2012/Shutter stock/shutterstock_76435258.tif
    Aug 9 13:43:08 Atom logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7]
    Aug 9 13:43:08 Atom logger: ./Photo/FOTOGRAF NANO 2012/Shutter stock/._shutterstock_76435258.tif
    Aug 9 13:43:08 Atom logger: rsync: get_xattr_data: lgetxattr("Photo","user.org.netatalk.supports-eas.zQdo9D",0) failed: Exec format error (
    Aug 9 13:43:08 Atom logger: .d..t...... Photo/
    Aug 9 13:43:08 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/
    Aug 9 13:43:08 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/Shutter stock/
    Aug 9 13:43:08 Atom logger: >f+++++++++ Photo/FOTOGRAF NANO 2012/Shutter stock/._shutterstock_76435258.tif
    Aug 9 13:43:08 Atom logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7]
    Aug 9 13:43:08 Atom logger: ./Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/full size til arkiv/01 Ramsland, Henrik Print???/.__MG_2912.jpg
    Aug 9 13:43:08 Atom logger: rsync: get_xattr_data: lgetxattr("Photo","user.org.netatalk.supports-eas.zQdo9D",0) failed: Exec format error (
    Aug 9 13:43:08 Atom logger: .d..t...... Photo/
    Aug 9 13:43:08 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/
    Aug 9 13:43:08 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/
    Aug 9 13:43:08 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/full size til arkiv/
    Aug 9 13:43:08 Atom logger: >f......... Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/full size til arkiv/01 Ramsland, Henrik Print#357#200#250/.__MG_2912.jpg
    Aug 9 13:43:09 Atom logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7]
    Aug 9 13:43:09 Atom logger: ./Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/full size til arkiv/01 Ramsland, Henrik Print???/.__MG_2916.jpg
    Aug 9 13:43:09 Atom logger: rsync: get_xattr_data: lgetxattr("Photo","user.org.netatalk.supports-eas.zQdo9D",0) failed: Exec format error (
    Aug 9 13:43:09 Atom logger: .d..t...... Photo/
    Aug 9 13:43:09 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/
    Aug 9 13:43:09 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/
    Aug 9 13:43:09 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/full size til arkiv/
    Aug 9 13:43:09 Atom logger: >f......... Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/full size til arkiv/01 Ramsland, Henrik Print#357#200#250/.__MG_2916.jpg
    Aug 9 13:43:09 Atom logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7]
    Aug 9 13:43:09 Atom logger: ./Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/full size til arkiv/01 Ramsland, Henrik Print???/.__MG_2995.jpg
    Aug 9 13:43:09 Atom logger: rsync: get_xattr_data: lgetxattr("Photo","user.org.netatalk.supports-eas.zQdo9D",0) failed: Exec format error (
    ....
    

  10. Thank you for your reply, Helmonder.

     

    I tried the things you suggested. Restarted a few times. Checked that user0 exists. Ran the permissions script.

    Before running the script most of the files were owned by the user that transfered them. After running they are owned by root.

    Looks like this:

    -rw-rw---- 1 nobody users 6148 2012-08-06 21:35 .DS_Store
    -rw-rw---- 1 nobody users 4096 2012-08-06 21:35 ._.DS_Store
    drwxrwx--- 7 nobody users  264 2012-07-26 16:47 Photo/
    
    
    -rw-rw----  1 nobody users 6148 2012-08-06 21:35 .DS_Store
    drwxrwx---  2 nobody users  176 2010-02-11 20:31 Bilder\ som\ ikke\ hører\ til\ noe.ï©/
    drwxrwx---  4 nobody users  120 2012-08-06 23:22 FOTOGRAF\ NANO/
    drwxrwx--- 10 nobody users  384 2012-08-02 14:11 FOTOGRAF\ NANO\ 2012/
    drwxrwx--- 25 nobody users  800 2012-01-18 12:37 Simoneï¨/
    drwxrwx---  2 nobody users  224 2012-08-07 12:49 _gsdata_/
    
    
    -rw-rw---- 1 nobody users   82052 2012-08-06 23:22 ._CIMG0058-u.jpg
    -rw-rw---- 1 nobody users   80258 2012-08-06 23:22 ._CIMG0058.jpg
    -rw-rw---- 1 nobody users  657796 2009-12-04 16:12 CIMG0058-u.jpg
    -rw-rw---- 1 nobody users 2997038 2009-11-27 09:22 CIMG0058.jpg
    

     

    I still got the same errors with rsync though...

    I'm using Goodsync on a mac to sync/backup files.

  11. I backup alot of photos regularly to a SSD cache disk to be moved to the array.

    However, most of the time this doesn't work. Often the files just stays at the cache drive without being moved. Sometimes the files are copied but not deleted from the cache drive.

     

    This is what fills the mover log:

     

    Aug  7 07:54:10 Atom logger: mover started
    Aug  7 07:54:10 Atom logger: moving Photo/
    Aug  7 07:54:10 Atom logger: ./Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/full size til arkiv/01 Ramsland, Henrik Print?\200?
    Aug  7 07:54:10 Atom logger: rsync: get_xattr_data: lgetxattr("Photo","user.org.netatalk.supports-eas.zQdo9D",0) failed: Exec format error (
    Aug  7 07:54:10 Atom logger: .d..t...... Photo/
    Aug  7 07:54:10 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/
    Aug  7 07:54:10 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/
    Aug  7 07:54:10 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/full size til arkiv/
    Aug  7 07:54:10 Atom logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7]
    Aug  7 07:54:10 Atom logger: ./Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/full size til arkiv/avis og tk?\200?
    Aug  7 07:54:10 Atom logger: rsync: get_xattr_data: lgetxattr("Photo","user.org.netatalk.supports-eas.zQdo9D",0) failed: Exec format error (
    Aug  7 07:54:10 Atom logger: .d..t...... Photo/
    Aug  7 07:54:10 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/
    Aug  7 07:54:10 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/
    Aug  7 07:54:10 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/Henrik Ramsland 12.04.12/full size til arkiv/
    Aug  7 07:54:10 Atom logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7]
    Aug  7 07:54:10 Atom logger: ./Photo/FOTOGRAF NANO 2012/Alfred 02.08.12/collage
    Aug  7 07:54:10 Atom logger: rsync: get_xattr_data: lgetxattr("Photo","user.org.netatalk.supports-eas.zQdo9D",0) failed: Exec format error (
    Aug  7 07:54:10 Atom logger: .d..t...... Photo/
    Aug  7 07:54:10 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/
    Aug  7 07:54:10 Atom logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7]
    Aug  7 07:54:10 Atom logger: ./Photo/FOTOGRAF NANO 2012/Alfred 02.08.12/Alfred 02.08.12/JPG
    Aug  7 07:54:10 Atom logger: rsync: get_xattr_data: lgetxattr("Photo","user.org.netatalk.supports-eas.zQdo9D",0) failed: Exec format error (
    Aug  7 07:54:10 Atom logger: .d..t...... Photo/
    Aug  7 07:54:10 Atom logger: .d..t...... Photo/FOTOGRAF NANO 2012/
    Aug  7 07:54:10 Atom logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7]
    Aug  7 07:54:10 Atom logger: ./Photo/FOTOGRAF NANO 2012/Alfred 02.08.12/Alfred 02.08.12/_MG_8188.dng
    Aug  7 07:54:10 Atom logger: rsync: get_xattr_data: lgetxattr("Photo","user.org.netatalk.supports-eas.zQdo9D",0) failed: Exec format error (
    .....
    

     

    ...and it just goes on like this.

     

    I tried copying to the cache disk both through SMB and AFP. Using Unraid 5.0 rc5.

    Anyone knows how to fix these errors?