ChatNoir

Moderators
  • Posts

    1592
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by ChatNoir

  1. 15 minutes ago, nametaken_thisonetoo said:

    I assume the two step mover will work for all of the system based shares - Appdata, System, Domains, isos?

    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.

    • Like 1
  2. 1 hour ago, nametaken_thisonetoo said:

    All relevant shares have been adjusted to Cache:Prefer with the new cache drive also selected. Mover did not move any of the data when invoked (something that seems to be a constant problem with Mover in many situations

    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 :

    1. use the mover twice the shares to cache YES, run the mover, then set them to the proper pool and run the mover again.
    2. 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. :)

    • Thanks 1
  3. 1 hour ago, shrekfx said:

    ?? Can you alternate?

    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.

  4. 1 hour ago, Robot said:

     

    I see. I'll have to dig into both those options do decide whether or not it's worth for me.

     

    Now, in case I want to go XFS, what should I do? Stop array, go into the cache settings, and just set it to XFS? And then install the TRIM plugin, of course.

     

    Thank you.

    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.

    • Like 1
  5. 50 minutes ago, ljm42 said:

    Maybe unplug the UPS while you are sitting there watching it and see what happens?  Keep the syslog window open and be ready to copy data out or take a screenshot.

    It is generally not advised to unplug as all items connected will also loose ground.

    It would be better to use the circuit breaker.

    • Like 2
  6. 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.

  7. 1 hour ago, S0UND54 said:

    je pourrais essayer vers la fin de semaine mais j'ai l'impression d'être sur le bon chemin !

    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 ?  😁

    • Like 1
  8. D'accord, pas de soucis. :) 

    19 minutes ago, Twano_O said:

    J'ai aussi sortie le dsik2 de tout mes shares, pour eviter d'y retrouver des données par la suite.

    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. :D 

     

    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.