Danuel

Members
  • Posts

    249
  • Joined

  • Last visited

About Danuel

  • Birthday August 17

Recent Profile Visitors

2126 profile views

Danuel's Achievements

Contributor

Contributor (5/14)

9

Reputation

  1. hi, i a, just experimenting this as a replacement for another backup tool, i am noticing that most of the time the client is not connecting to the server also on server side on logs i see DEBG 'urbackup' stdout output: WARNING: SQLite: os_unix.c:36982: (40) openDirectory(/var/urbackup) - errorcode: 14
  2. i would recommend immich, they also have there own sync app
  3. HI, is there anyone using any static site generator for documentation or blog like jekyll or Hugo
  4. so i have recreated docker, checked RAM for faults, 1 stick was bad, now i will see if problem persist last time i checked was 2 weeks ago and all was fine, i think this developed while i was trying to fix my server, force closing i dont think does help on RAM
  5. i also find out this morning all my containers off with this message in the logs Jan 11 05:01:06 Seven kernel: BTRFS error (device loop2: state EA): parent transid verify failed on logical 15736389632 mirror 2 wanted 500599 found 500595
  6. i get this errors Jan 10 20:08:55 Seven emhttpd: read SMART /dev/sdh Jan 10 20:11:34 Seven kernel: certbot[5266]: segfault at 1493304ad489 ip 0000149130296909 sp 00007ffd50c47e08 error 4 in libpython3.10.so.1.0[149130258000+14a000] likely on CPU 3 (core 5, socket 0) Jan 10 20:11:34 Seven kernel: Code: 00 48 89 ac d8 48 2c 00 00 eb 0f 5a 48 89 ef 5b 5d 41 5c 41 5d e9 e6 05 00 00 58 5b 5d 41 5c 41 5d c3 eb 00 48 8b 57 08 31 c0 <f6> 82 a9 00 00 00 40 74 1e 48 8b 8a 48 01 00 00 b8 01 00 00 00 48 Jan 10 20:12:01 Seven kernel: __vm_enough_memory: pid: 6363, comm: monitor, no enough memory for the allocation Jan 10 20:12:01 Seven kernel: monitor[6363]: segfault at 1549bb707014 ip 00001549bb707014 sp 00007ffc8bd82d98 error 14 likely on CPU 5 (core 1, socket 0) Jan 10 20:12:01 Seven kernel: Code: Unable to access opcode bytes at 0x1549bb706fea. Jan 10 20:12:01 Seven crond[1559]: exit status 139 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null Jan 10 20:13:26 Seven kernel: sdspin[9594]: segfault at 200553d68 ip 00000000004e9947 sp 00007ffc38cce520 error 4 in bash[426000+c5000] likely on CPU 0 (core 0, socket 0) Jan 10 20:13:26 Seven kernel: Code: 4c 63 e3 39 1d b2 25 05 00 43 c6 04 22 01 7d 06 89 1d a5 25 05 00 4c 8d 1d e6 25 05 00 4b 8b 0c e3 48 85 c9 0f 84 39 02 00 00 <48> 8b 41 08 43 c6 04 22 00 80 39 54 4b 89 04 e3 75 08 0f be 41 01 Jan 10 20:13:26 Seven emhttpd: read SMART /dev/sdd Jan 10 20:17:02 Seven kernel: sdspin[17114]: segfault at 10053dd98 ip 000000000047baca sp 00007ffec0cc6a70 error 4 in bash[426000+c5000] likely on CPU 2 (core 4, socket 0) Jan 10 20:17:02 Seven kernel: Code: 48 8d 35 f2 46 07 00 e9 64 8c 01 00 0f 1f 40 00 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 53 48 85 ff 0f 84 ff 00 00 00 <4c> 8b 4f 08 49 89 f8 85 f6 0f 8e f0 00 00 00 4d 85 c9 0f 84 e7 00 Jan 10 20:17:02 Seven emhttpd: read SMART /dev/sdf Jan 10 20:25:45 Seven kernel: vethc533d4f: renamed from eth0 Jan 10 20:25:45 Seven kernel: docker0: port 2(veth88bbe62) entered disabled state Jan 10 20:25:45 Seven kernel: docker0: port 2(veth88bbe62) entered disabled state Jan 10 20:25:45 Seven kernel: device veth88bbe62 left promiscuous mode Jan 10 20:25:45 Seven kernel: docker0: port 2(veth88bbe62) entered disabled state Jan 10 20:25:45 Seven kernel: docker0: port 2(vetha1e2732) entered blocking state Jan 10 20:25:45 Seven kernel: docker0: port 2(vetha1e2732) entered disabled state Jan 10 20:25:45 Seven kernel: device vetha1e2732 entered promiscuous mode Jan 10 20:25:45 Seven kernel: docker0: port 2(vetha1e2732) entered blocking state Jan 10 20:25:45 Seven kernel: docker0: port 2(vetha1e2732) entered forwarding state Jan 10 20:25:46 Seven kernel: eth0: renamed from vethae76cc0 Jan 10 20:25:46 Seven kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha1e2732: link becomes ready Jan 10 20:25:46 Seven kernel: BTRFS warning (device loop3): checksum verify failed on logical 15764799488 mirror 1 wanted 0xc50acda6 found 0x983aae68 level 0 Jan 10 20:25:46 Seven kernel: BTRFS info (device loop3): read error corrected: ino 0 off 15764799488 (dev /dev/loop3 sector 31855584) Jan 10 20:25:46 Seven kernel: BTRFS info (device loop3): read error corrected: ino 0 off 15764803584 (dev /dev/loop3 sector 31855592) Jan 10 20:25:46 Seven kernel: BTRFS info (device loop3): read error corrected: ino 0 off 15764807680 (dev /dev/loop3 sector 31855600) Jan 10 20:25:46 Seven kernel: BTRFS info (device loop3): read error corrected: ino 0 off 15764811776 (dev /dev/loop3 sector 31855608) Jan 10 20:28:27 Seven emhttpd: spinning down /dev/sdd here are some logs now i want to restart and i cant, i wa to stop the array Jan 10 20:36:03 Seven emhttpd: shcmd (133752): umount /mnt/cache Jan 10 20:36:03 Seven root: umount: /mnt/cache: target is busy. Jan 10 20:36:03 Seven emhttpd: shcmd (133752): exit status: 32 Jan 10 20:36:03 Seven emhttpd: Retry unmounting disk share(s)... Jan 10 20:36:08 Seven emhttpd: Unmounting disks... Jan 10 20:36:08 Seven emhttpd: shcmd (133754): umount /mnt/cache Jan 10 20:36:08 Seven root: umount: /mnt/cache: target is busy. Jan 10 20:36:08 Seven emhttpd: shcmd (133754): exit status: 32 Jan 10 20:36:08 Seven emhttpd: Retry unmounting disk share(s)... Jan 10 20:36:13 Seven unraid-api[21804]: ✔️ UNRAID API started successfully! Jan 10 20:36:13 Seven emhttpd: Unmounting disks... Jan 10 20:36:13 Seven emhttpd: shcmd (133755): umount /mnt/cache Jan 10 20:36:13 Seven root: umount: /mnt/cache: target is busy. Jan 10 20:36:13 Seven emhttpd: shcmd (133755): exit status: 32 Jan 10 20:36:13 Seven emhttpd: Retry unmounting disk share(s)... Jan 10 20:36:14 Seven unraid-api[21804]: ⚠️ Caught exception: connect ECONNREFUSED /var/run/docker.sock Jan 10 20:36:14 Seven unraid-api[21804]: ⚠️ UNRAID API crashed with exit code 1 Jan 10 20:36:18 Seven nginx: 2024/01/10 20:36:18 [error] 5221#5221: *664752 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.4, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "10.10.10.6", referrer: "http://10.10.10.6/Main" Jan 10 20:36:18 Seven emhttpd: Unmounting disks... Jan 10 20:36:18 Seven emhttpd: shcmd (133756): umount /mnt/cache Jan 10 20:36:18 Seven root: umount: /mnt/cache: target is busy. Jan 10 20:36:18 Seven emhttpd: shcmd (133756): exit status: 32 Jan 10 20:36:18 Seven emhttpd: Retry unmounting disk share(s)... Jan 10 20:36:23 Seven emhttpd: Unmounting disks... Jan 10 20:36:23 Seven emhttpd: shcmd (133757): umount /mnt/cache Jan 10 20:36:23 Seven root: umount: /mnt/cache: target is busy. Jan 10 20:36:23 Seven emhttpd: shcmd (133757): exit status: 32 Jan 10 20:36:23 Seven emhttpd: Retry unmounting disk share(s)... the command umount /var/lib/docker is not working either seven-diagnostics-20240110-2030.zip
  7. i will try this again, maybe i did something wrong
  8. Yes, i have copied the hole config folder into the new drive
  9. I do have a copy of the key file, names unraid plus.key, is just not working on the new usb drive
  10. multiple issue that pointing to what ?
  11. why so many networks ? is this normal ? i know that br0 is my ethernet port and wg0 is VPN but i don't know rest of them, anyone can help me out ?
  12. yes on a different share, because i did not want to stress the USB drive for that, but those are logs that appear in system log, i thought you might see some hardware problems or something that i cant see, like i mention i am now in my third day with this and all started when i wanted to upgrade immich container then all go downhill but still when a crash happen does not show why, only i see forced reboot and then how is coming back online syslog-10.10.10.6.log
  13. i am trying to fix this since Thursday looking into hardware thinking that might be, hardware related, reinstall data remake pools (which cause me data loss) now i have to stay alert that my server can go down at any time, putting all my services offline of which some people depend of it. i think Unraid lost its track, feels like i cant relay on this product is hard to troubleshoot if is a software problem or hardware im starting loosing trust in this wanted to try the a different USB thinking that might be the USB flash drive, but surprise key is not working, cant import, go figure, sad i have looked trough the logs and i cant see anything out of ordinary, i doubt someone else will seven-diagnostics-20231231-2110.zip
  14. Danuel

    usb bootable

    manual method is working, but that is not the point i was almost 1 hour trying to make a bootable drive, supposedly to be easy and simple, i think Unraid lost its track