ChatNoir

Moderators
  • Posts

    1592
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by ChatNoir

  1. While your diags are from today, the syslog stops on the 13th, so I cannot see anything recent happening. Maybe try to get them again. If it's the same, try to reboot ? @Squid, you had better chance than me or you didn't check the date ?
  2. Except I don't have it and never did, hence my initial answer. Not using Dynamix Fan though.
  3. It would work for any share that you need to move really. For the shares you mention, you will have to disable the VM and Docker services from Settings before moving files. You can enabled them once the files are where you want them to be.
  4. Mover only moves from pool to array and from array to pool. Never from pool to pool. Might change one day ? There are two solutions : use the mover twice : the shares to cache YES, run the mover, then set them to the proper pool and run the mover again. use the built-in Midnight Commander (mc in the console) to move file directly from pool to pool. The first option is longer (twice the work and go through the slower HDDs), but safer if you don't know MC. The second has the opposite advantages. Should be faster but requires to take the time to understand MC. Be sure to move files POOL to POOL and NOT to involve SHARES, or there could be data loss. MC is not so hard when you understand : TAB to go from one tree to the other arrows to select Enter to go in a directory Enter on /.. to go back and ALT+number from the top row of the keyboard to launch a command the command is done from the active tree to the inactive one You could also use the second method from your main computer if you enable disk shares ? If your OS is recent enough, the copy should happen within the server and not go through your computer. Still need to be careful not to mix disks and pools. Hopefully you don't have shares named like one of the pool.
  5. Your diagnostics could show what happened. If the drive is OK, you will have to rebuild as parity2 is most probably not in sync anymore.
  6. You should probably delete the libvirt file from disk1 if you are not using it (ie if the correct one is on cache).
  7. I am not sure what you mean by Airflow in the context of the Unraid dashboard.
  8. Your docker image is corrupted, probably because the pool got full. You should delete the image and reinstall your dockers from previous apps.
  9. Does not seem a reasonable time. Are you having other read write operation on the Array ? Please post new diagnostics.
  10. Not sure I understand what you mean by alternate. If you want the operation to be quicker, do it without parity and sync it afterwards. If you want the operation to be safer, do it with parity active. Your choice.
  11. Unless your drives are empty and/or you don't care about their content, you should move the data to the array before changing the File System and back to the pools once the format is finished.
  12. Salut, j'avais raté ton message. Je ne partage pas la clé sur le réseau pour des questions de sécurité, mais je viens de tester et je n'ai pas ce problème. Je vois bien les fichiers, je peux en créer un, le modifier, l'effacer. J'ai fait mon essai avec le SMB en Secure et les droits d'accès correspondant à la machine W10.
  13. It is generally not advised to unplug as all items connected will also loose ground. It would be better to use the circuit breaker.
  14. Not using it, but there is a community mobile app :
  15. @resin1980 you should not display the address to your admin interface. I edited your post.
  16. Your log is spammed but it does not seem to have anything to do with your drives. (unless some stuff about drives is hidden between all the call traces) Sep 14 10:16:10 UnraidServer kernel: WARNING: CPU: 1 PID: 13609 at mm/truncate.c:447 truncate_inode_pages_range+0x39d/0x438 Sep 14 10:16:10 UnraidServer kernel: Modules linked in: md_mod macvlan xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle nf_tables veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs i915 iosf_mbi i2c_algo_bit drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops it87 hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding x86_pkg_temp_thermal intel_powerclamp mxm_wmi coretemp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper rapl intel_cstate intel_uncore i2c_i801 i2c_smbus i2c_core ahci wmi video input_leds atl1c led_class e1000e backlight libahci fan thermal button [last unloaded: md_mod] Sep 14 10:16:10 UnraidServer kernel: CPU: 1 PID: 13609 Comm: emhttpd Tainted: G U W 5.10.28-Unraid #1 Sep 14 10:16:10 UnraidServer kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Z77X-UD5H, BIOS F16k 04/11/2018 Sep 14 10:16:10 UnraidServer kernel: RIP: 0010:truncate_inode_pages_range+0x39d/0x438 Sep 14 10:16:10 UnraidServer kernel: Code: fc 08 4e 8b b4 fc 88 00 00 00 4d 39 ec 77 d8 4c 8d 6b ff eb 34 4c 89 f7 e8 04 f8 ff ff 4c 89 f7 e8 c2 f6 ff ff 4c 39 e8 74 02 <0f> 0b 4c 89 f7 e8 d3 ab ff ff 48 89 ef 4c 89 f6 e8 0b fc ff ff 4c Sep 14 10:16:10 UnraidServer kernel: RSP: 0018:ffffc900004dfca8 EFLAGS: 00010216 Sep 14 10:16:10 UnraidServer kernel: RAX: 00000000cbb7406d RBX: 0000000000000000 RCX: 0000000000000018 Sep 14 10:16:10 UnraidServer kernel: RDX: ffffea001ad7f008 RSI: 0000000040000040 RDI: ffffea0014bd1c80 Sep 14 10:16:10 UnraidServer kernel: RBP: ffff88810486c828 R08: 0000000000000000 R09: 0000000000000000 Sep 14 10:16:10 UnraidServer kernel: R10: ffffc900004dfc30 R11: ffffc900004dfc30 R12: ffffffffffffffff Sep 14 10:16:10 UnraidServer kernel: R13: 000000001d99c85e R14: ffffea0014bd1c80 R15: 0000000000000000 Sep 14 10:16:10 UnraidServer kernel: FS: 000014adae1be700(0000) GS:ffff8887ff280000(0000) knlGS:0000000000000000 Sep 14 10:16:10 UnraidServer kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 14 10:16:10 UnraidServer kernel: CR2: 000014ac65e62050 CR3: 0000000103abc006 CR4: 00000000001706e0 Sep 14 10:16:10 UnraidServer kernel: Call Trace: Sep 14 10:16:10 UnraidServer kernel: ? mce_intel_cmci_poll+0x20/0x3d Sep 14 10:16:10 UnraidServer kernel: __blkdev_put+0x73/0x199 Sep 14 10:16:10 UnraidServer kernel: blkdev_close+0x1d/0x20 Sep 14 10:16:10 UnraidServer kernel: __fput+0xf7/0x1ba Sep 14 10:16:10 UnraidServer kernel: task_work_run+0x70/0x81 Sep 14 10:16:10 UnraidServer kernel: exit_to_user_mode_prepare+0x51/0xc6 Sep 14 10:16:10 UnraidServer kernel: syscall_exit_to_user_mode+0x45/0x53 Sep 14 10:16:10 UnraidServer kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Sep 14 10:16:10 UnraidServer kernel: RIP: 0033:0x14adae9575bb Sep 14 10:16:10 UnraidServer kernel: Code: 0f 05 48 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8 13 fc ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2f 44 89 c7 89 44 24 0c e8 51 fc ff ff 8b 44 Sep 14 10:16:10 UnraidServer kernel: RSP: 002b:000014adae1bdc40 EFLAGS: 00000293 ORIG_RAX: 0000000000000003 Sep 14 10:16:10 UnraidServer kernel: RAX: 0000000000000000 RBX: 0000000000421876 RCX: 000014adae9575bb Sep 14 10:16:10 UnraidServer kernel: RDX: 000014ad9c000e00 RSI: 0000000000000002 RDI: 0000000000000008 Sep 14 10:16:10 UnraidServer kernel: RBP: 000014adae1bdf00 R08: 0000000000000000 R09: 0000000000000001 Sep 14 10:16:10 UnraidServer kernel: R10: 0000000000004000 R11: 0000000000000293 R12: 00007ffd7941586e Sep 14 10:16:10 UnraidServer kernel: R13: 00007ffd7941586f R14: 000014adae1bdfc0 R15: 000014adae1be700 Sep 14 10:16:10 UnraidServer kernel: ---[ end trace 903f783f2067e73e ]--- Looks more like a networking thing.
  17. C'est idéal de tester avec du matos de récup. Tu peux voir ce qui te plait ou non, voir si le matos convient pour ton usage ou s'il faut plus. J'avais vidé tout mon stock de pièces peu de temps avant de décider de me faire un serveur. Du coup j'ai acheté direct et je suis peut-être allé un peu fort sur les specs. 👼 Bon, on va dire que j'ai de la marge du coup ? 😁
  18. D'accord, pas de soucis. Tu as raison, tant que tu restes avec un disque émulé. Penses bien à tout remettre en place par la suite, sinon tu risques de te demander pourquoi ça rempli toujours sur les autres. Pour le reste, je comprends tes précautions. Mais je préfère préciser qu'en l'état tu n'es pas protégé d'une autre défaillance (simple parité) C'est certes peu probable, mais à garder à l'esprit.
  19. Are you sure the drive is dead ? Diagnostics could provide more information.
  20. How is power delivered to your drives ? How many drives per lead from the PS ?
  21. You should ask for support on the Unassigned Plugin support thread.
  22. You should monitor attributes 1 and 200 on WD drives. It is not done by default since other manufacturers manage those differently. You should run an extended SMART test instead of a preclear in my opinion on older hard drive.