Danuel
-
Posts
249 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Danuel
-
-
i would recommend immich, they also have there own sync app
-
HI,
is there anyone using any static site generator for documentation or blog like jekyll or Hugo
-
4 hours ago, JorgeB said:
That's a corrupt docker image, which together with the other segfault errors can be the result of bad RAM.
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
-
1
-
-
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
-
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/sddhere 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
-
2 minutes ago, itimpi said:
If you did this and it is a new drive then you should be taken through the licence transfer process as the licence is tied to the drive for which it was initially licenced.
i will try this again, maybe i did something wrong
-
Did you put it into the ‘config’ folder on the flash drive before booting?
Yes, i have copied the hole config folder into the new drive -
I do have a copy of the key file, names unraid plus.key, is just not working on the new usb drive
-
17 minutes ago, JorgeB said:
Looks like you are having multiple issue, I would first try to fix the crashing and only after that look at the docker issues, you can boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
multiple issue that pointing to what ?
-
i get this error
Fix Common Problems: Error: Machine Check Events detected on your server
Dec 31 20:19:07 Seven root: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead.
Dec 31 20:19:07 Seven root: CPU is unsupported
-
so i did a roll back to 6.12.3 and the problem is still there now is start to crash after a while
-
i wonder if this is CPU related
i wanted to install older RAM and the CPu did not recoqnize them, took me 1 h for the older ram to work again
both sets of RAM that i have tested they are fine, anyone any thoughts ?
or is it possible top be the flash drive ?
-
i had to put unraid on different USB, now when i try to activate it i receive
Downloading ...
ERROR: 8the key is on the drive
i did try to use Redeem Activation Code but i have no conde in my purchaise
-
is this regarding to VM ?
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C000: Found 2 idle states
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C002: Found 2 idle states
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C004: Found 2 idle states
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C006: Found 2 idle states
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C001: Found 2 idle states
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C003: Found 2 idle states
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C005: Found 2 idle states
Dec 31 14:37:13 Seven kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Dec 31 14:37:13 Seven kernel: ACPI: \_PR_.C007: Found 2 idle states -
what i see, if i manage to start 1-2 containers the 3 one will spin and if i try to acces log from UI i have blank
also sometime after a fresh boot when i navigate on UI TOOLS tabs, or settings it takes time to load
-
those are the latest logs, i dont know what happen, but i came back and unraid UI and started again to have a parity and all containers were off
now i see something regarding CPU not supported
-
Does the unradUi is getting slow after you start a container ?
My problem is a bit similar -
Is there any way or tool that i can check for hardware faults ? I dont know what is with my server, sometimes work ok, sometimes work like a very old system or freezes, need some help please some ideas on what to try
-
any news regarding those diagnostics ?
-
from what is see, is behaving like a slow system, even with docker off, Unraid homepage still take a bit to refresh or load
i wonder if is a corrupted docker image ?
and downgrading to 6.12.4 does not help, another thing i noticed is that sometime when i am trying to start a container i get execution error, or takes up to 5 min to start a container
-
ZFS 100% ?
can that be the problem ?
-
just happen to notice that sometimes server shut down itself when trying to start a container, it take like 5 minutes
anyway does take long time to start or stop a container
-
now after all this restarting and trying to understand what happens i see a container that i dont know what it is, i dont remember installing it, this just showed up
-
here are the diagnostics
1942 are the latest
seven-diagnostics-20231228-1942.zip seven-diagnostics-20231228-1726.zip seven-diagnostics-20231228-1751.zip
[Support] binhex - UrBackup
in Docker Containers
Posted
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