Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,662

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    That is normal, for any array or pool disk, user shares are just top level folders. That's not needed for that, but it should be set to twice the file size you expect to copy to that share.
  2. JorgeB
    Only the gigabit NICs are being detected, this is not an OS problem, check to see if the NICs are enable in the BIOS.
  3. JorgeB
    Start array to see if both emulated disks are mounting (disk16 will start rebuilding), since server was rebooted which was the other disk that showed read errors during the rebuild?
  4. JorgeB
    Emulated disk is mounting so you can rebuild on top, disk looks fine but there are several UDMA CRC errors, so you should replace the SATA cable before rebuilding.
  5. JorgeB
    That's still a local transfer, so the problem is not the server, I remember reading about other users with poor performance with Krusader, mc should perform normally, you can also try for example rsync. Also note that transfers made using disks shares can always be faster then transfers between user shares, i.e.: /mnt/disk3/plots/ to /mnt/disk9/plotsraid/ can be faster than /mnt/user/plots/ to /mnt/user/plotsraid/
  6. JorgeB
    Trim is disabled for all arrays devices, though you can still use an SSD. Since there's no parity you's need to do a new config and re-assign the devices, any data on the original array disk won't be copied, if you need some you'd need to that manually, assuming the disk is still working, without diags can only guess.
  7. JorgeB
    Yep. That's a good idea.
  8. JorgeB
    Do you mean still copying from Unraid share to share?
  9. JorgeB
    Missed the problem earlier, global cache share is disable: shareCacheEnabled="no" There's a bug and if this is disable before updating to v6.9.x it can't be enabled using the GUI, you need to manually edit config/share.cfg and change that to yes, then reboot.
  10. JorgeB
    If means data corruption is being detected, and since you're overclocking the RAM with Ryzen that's a likely cause, or just bad RAM, see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  11. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  12. JorgeB
    There's nothing logged about the crash, this usually points to a hardware problem, but one thing you can try it to boot the server in safe mode with all docker/VMs disable, 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.
  13. JorgeB
    Sometimes there are compatibility issues with a specific device and a controller, for example some recent 2.5" SATA HGST disks don't work correctly with LSI controllers, I think I also remember reading that some implementations of Intel SCU SAS controller could be kind of iffy.
  14. JorgeB
    If it's not the hardware it could be an issue with the LSI driver, if using a different version, can't think of anything else that would make sense.
  15. JorgeB
    Btrfs has data and metadata chunks, all the data you copy there will use raid0, metadata (and system) is where the filesystem information is stored, only that part is raid1, if you for a example get a bad sector where metadata is stored you can lose the complete filesystem, with raid1 metadata there's still another copy if that happens, and again metadata takes so little space compared to data that it doesn't make sense to use raid0 for it, but you can if want.
  16. JorgeB
    IMHO bad idea to try to fix the array while there are multiple disk errors, need to fix that first, i.e., try another PUS, controller, cables, etc.
  17. JorgeB
    Because there were errors on another disk, Unraid can't emulate it any longer, rebooting should fix it, it there aren't any more errors on different disks.
  18. JorgeB
    There wasn't a valid btrfs filesystem on that SSD since boot, whatever happened it did before these diags, or it was a xfs filesystem.
  19. JorgeB
    You can enable syslog mirror to flash than post that after a crash, might be something visible there.
  20. JorgeB
    I did because of this: My mistake since it wasn't posted by the OP, removed SOLVED.
  21. JorgeB
    shfs crashed, rebooting will fix the shares issue, disk problem is unrelated, but due to log span can't see what happened.
  22. JorgeB
    See if this applies to you: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
  23. JorgeB
    You have disk shares enables, are you sure you're copying to the user share?
  24. JorgeB
    If now it's working correctly it's difficult to say, but maybe it was some docker running in the background, if it happens again, the parity check being very slow, post diags grabbed at that time.
  25. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
×
×
  • Create New...