JorgeB

Moderators
 View Profile  See their activity

  • Posts

    61472

  • Joined

  • Last visited

  • Days Won

    646

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    As mentioned, many small files will always be slower, this is normal with any OS, it will be the same if you transfer from one Windows PC to another.
  2. JorgeB
    If you want to use zfs won the array you don't need the flash drive. Not in the array. Nest release will still require an array device assigned, at least that's the last I heard, but you can already do a full zfs implementation, if like mentioned, you use a flash drive to fulfill the array device requirement.
  3. JorgeB
    The issue is not using zfs for all, you can also use zfs for the array, but for now, at least one device must be assigned to the array if you want to only use pools, an old flash drive will do it.
  4. JorgeB
    Copying many small files will always be slower than large ones, but you should see a nice boost if you set the share to exclusive mode, or use a disk share.
  5. JorgeB
    Run the make_bootable.bat as admin, syslinux is not needed for UEFI boot, but it is for legacy, and make sure the flash drive is still the first boot device.
  6. JorgeB
    The SMART report for that disk, this part: SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 58305 -
  7. JorgeB
    The pool is using the single profile, i.e., not redundant, and it will only mount if both devices are available, you can convert to raid1 to make it redundant.
  8. JorgeB
    Check filesystem on disk4, run without -n and if it asks for it, use -L.
  9. JorgeB
    Yes, if the drive is encrypted, and still in maintenance mode, you need to use: /dev/mapper/mdXp1
  10. JorgeB
    md device should not be busy in maintenance mode, try rebooting
  11. JorgeB
    Those appear to be the same diags as before, would need current ones, with the pool mounted.
  12. JorgeB
    IMHO it can be considered a bug regarding the errors logged, which are misleading, the behavior itself would be expected, i.e., if the share is set to use one pool, the mover won't move any data from the same share in a different pool.
  13. JorgeB
    If it's configured as a redundant pool yes, you can post new diags to confirm.
  14. JorgeB
    Post the output of btrfs fi show
  15. JorgeB
    Once a disk gets disabled it needs to be rebuilt, but first post new diags to see if the ATA errors are gone.
  16. JorgeB
    Hmm, error may be caused by the file existing in a different pool, media share is set to use the pool "downloads", but those files are in the pool "server", change the share to use the pool server, other settings should remain the same, and run the mover again.
  17. JorgeB
    For both?
  18. JorgeB
    One of the NVMe devices dropped offline, power cycle the server, don't just reboot, to see if it comes back and post new diags after array start.
  19. JorgeB
    SMART test passed so the disk should be OK for now, keep monitoring, you can also replace/swap cables to rule that out if more errors occur.
  20. JorgeB
    Post the output of find /mnt -name 01\ -\ Cannonball.mp3 Search can take some time, wait until you get the cursor back before posting the output
  21. JorgeB
    Server is running out of RAM, see if you can fix that first by limiting the RAM to VMs/containers.
  22. JorgeB
    One possible explanation would be the first time that bit was wrongly correctly, like from a bit flip, so the second pass would correct it again, but you appear to be using ECC RAM, so that should not happen, possible an issue with one of the devices, run another check when possible to see if more errors are found.
  23. JorgeB
    Only one NVMe device is being detected by Linux: 21:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808] Subsystem: Samsung Electronics Co Ltd SSD 970 EVO/PRO [144d:a801] Kernel driver in use: nvme Kernel modules: nvme This is not a software issue, try swapping both NVMe devices and see where the problem follows.
  24. JorgeB
    You just need to restore the complete /config folder, from a backup or from the old flash if still readable, then transfer the key.
  25. JorgeB
    Please post the diagnostics.