3Monate nicht darum gekümmert, jetzt riesen Probleme. Hilfe :(

[Soliver84]

Hallo

Ich habe Unraid Pro 6.11.5 auf einem QNAP NAS Laufen, es scheint das der USB Stick die grätsche macht.

 

hab ich noch die möglichkeit die richtigen sachen zu kopieren so das bei einem Neuen Stick nicht alles neue gemacht werden muss?

Das sind die Errors im Live LOG (LOGS angehängt):
Nov 29 09:14:02 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x72f9a8 len 4096 err no 10
Nov 29 09:14:02 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x72f9b0 len 4096 err no 10
Nov 29 09:14:02 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x72f9b8 len 4096 err no 10
Nov 29 09:14:02 Tower unraid-api[25872]: ⚠️ Caught exception: EIO: i/o error, stat '/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/50fd5231eb24c7c0d9764b33cb99ada920e9290861563b61c8401fa93fac96cc/work'
Nov 29 09:14:02 Tower unraid-api[25872]: ⚠️ UNRAID API crashed with exit code 1
Nov 29 09:14:04 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x52f9a0 len 4096 err no 10
Nov 29 09:14:04 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x52f9a8 len 4096 err no 10
Nov 29 09:14:04 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x52f9b0 len 4096 err no 10
Nov 29 09:14:04 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x52f9b8 len 4096 err no 10
Nov 29 09:14:04 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x72f9a0 len 4096 err no 10
Nov 29 09:14:05 Tower unraid-api[28883]: ✔️ UNRAID API started successfully!
Nov 29 09:14:06 Tower kernel: btrfs_dev_stat_print_on_error: 120 callbacks suppressed
Nov 29 09:14:06 Tower kernel: BTRFS error (device md1: state EA): bdev /dev/md1 errs: wr 1, rd 7998711, flush 0, corrupt 0, gen 0
Nov 29 09:14:06 Tower kernel: BTRFS error (device md1: state EA): bdev /dev/md1 errs: wr 1, rd 7998712, flush 0, corrupt 0, gen 0
Nov 29 09:14:06 Tower kernel: BTRFS error (device md1: state EA): bdev /dev/md1 errs: wr 1, rd 7998713, flush 0, corrupt 0, gen 0
Nov 29 09:14:06 Tower kernel: BTRFS error (device md1: state EA): bdev /dev/md1 errs: wr 1, rd 7998714, flush 0, corrupt 0, gen 0
Nov 29 09:14:06 Tower kernel: _btrfs_printk: 3 callbacks suppressed
Nov 29 09:14:06 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x52f9a0 len 4096 err no 10
Nov 29 09:14:06 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x52f9a8 len 4096 err no 10
Nov 29 09:14:06 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x52f9b0 len 4096 err no 10
Nov 29 09:14:06 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x52f9b8 len 4096 err no 10
Nov 29 09:14:06 Tower kernel: blk_print_req_error: 16 callbacks suppressed
Nov 29 09:14:06 Tower kernel: I/O error, dev loop2, sector 1167776 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
Nov 29 09:14:06 Tower kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 1, rd 258204, flush 0, corrupt 0, gen 0
Nov 29 09:14:06 Tower kernel: BTRFS error (device md1: state EA): bdev /dev/md1 errs: wr 1, rd 7998715, flush 0, corrupt 0, gen 0
Nov 29 09:14:06 Tower kernel: BTRFS error (device md1: state EA): bdev /dev/md1 errs: wr 1, rd 7998716, flush 0, corrupt 0, gen 0
Nov 29 09:14:06 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x72f9a0 len 4096 err no 10
Nov 29 09:14:06 Tower kernel: BTRFS error (device md1: state EA): bdev /dev/md1 errs: wr 1, rd 7998717, flush 0, corrupt 0, gen 0
Nov 29 09:14:06 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x72f9a8 len 4096 err no 10
Nov 29 09:14:06 Tower kernel: BTRFS error (device md1: state EA): bdev /dev/md1 errs: wr 1, rd 7998718, flush 0, corrupt 0, gen 0
Nov 29 09:14:06 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x72f9b0 len 4096 err no 10
Nov 29 09:14:06 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x72f9b8 len 4096 err no 10
Nov 29 09:14:06 Tower kernel: I/O error, dev loop2, sector 3264928 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
Nov 29 09:14:06 Tower kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 1, rd 258205, flush 0, corrupt 0, gen 0

 

oder ist das sogar was anderes

 

Edit:

 

Nach dem Update auf die neue Unraid version habe ich nur noch diesen Fehler:
Nov 29 09:59:41 Tower smbd[23183]: [2023/11/29 09:59:41.484424,  0] ../../source3/smbd/smb2_service.c:772(make_connection_snum)
Nov 29 09:59:41 Tower smbd[23183]:   make_connection_snum: canonicalize_connect_path failed for service QNAPZFS2, path /QNAPZFS2
Nov 29 09:59:43 Tower smbd[23183]: [2023/11/29 09:59:43.500127,  0] ../../source3/smbd/smb2_service.c:772(make_connection_snum)
Nov 29 09:59:43 Tower smbd[23183]:   make_connection_snum: canonicalize_connect_path failed for service QNAPZFS2, path /QNAPZFS2
Nov 29 09:59:45 Tower smbd[23183]: [2023/11/29 09:59:45.516610,  0] ../../source3/smbd/smb2_service.c:772(make_connection_snum)
Nov 29 09:59:45 Tower smbd[23183]:   make_connection_snum: canonicalize_connect_path failed for service QNAPZFS2, path /QNAPZFS2
Nov 29 09:59:47 Tower smbd[23183]: [2023/11/29 09:59:47.532833,  0] ../../source3/smbd/smb2_service.c:772(make_connection_snum)
Nov 29 09:59:47 Tower smbd[23183]:   make_connection_snum: canonicalize_connect_path failed for service QNAPZFS2, path /QNAPZFS2
Nov 29 09:59:49 Tower smbd[23183]: [2023/11/29 09:59:49.548911,  0] ../../source3/smbd/smb2_service.c:772(make_connection_snum)
Nov 29 09:59:49 Tower smbd[23183]:   make_connection_snum: canonicalize_connect_path failed for service QNAPZFS2, path /QNAPZFS2
Nov 29 09:59:51 Tower smbd[23183]: [2023/11/29 09:59:51.564478,  0] ../../source3/smbd/smb2_service.c:772(make_connection_snum)
Nov 29 09:59:51 Tower smbd[23183]:   make_connection_snum: canonicalize_connect_path failed for service QNAPZFS2, path /QNAPZFS2
Nov 29 09:59:53 Tower smbd[23183]: [2023/11/29 09:59:53.580948,  0] ../../source3/smbd/smb2_service.c:772(make_connection_snum)
Nov 29 09:59:53 Tower smbd[23183]:   make_connection_snum: canonicalize_connect_path failed for service QNAPZFS2, path /QNAPZFS2

Danke euch.

Viele Grüße

Alex

tower-diagnostics-20231129-0854.zip

Tower_Dashboard.html Tower_Main.html

Edited November 29, 2023 by Soliver84

[Ford Prefect]

12 hours ago, Soliver84 said:

Nov 29 09:14:02 Tower kernel: BTRFS warning (device md1: state EA): direct IO failed ino 257 rw 0,0 sector 0x72f9a8 len 4096 err no 10

Das ist nicht der unraid Stick, weil der nicht BTRFS formatiert ist...sondern md1 ist Disk1 im Array...nach Deinem Screenshot zu urteilen, die Samsung Evo SSD.

12 hours ago, Soliver84 said:

Nov 29 09:59:41 Tower smbd[23183]:   make_connection_snum: canonicalize_connect_path failed for service QNAPZFS2, path /QNAPZFS2

Das allerdings scheint im ZFS-Pool zu sein.

Ob ZFS oder Samba / smbd Problem vermag ich nicht zu sagen.