Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,877

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    If it was disabled you wouldn't see the HT cores.
  2. JorgeB
    Only by doing a new config and re-syncing parity, but by doing this you lose the ability to rebuild disk2 and recover any data there.
  3. JorgeB
    Nothing relevant logged that I can see, that usually points to a hardware problem, one thing you can try is 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.
  4. JorgeB
    Look for a BIOS update for the board, updating to Unraid v6.11 might also help because of the much newer and different kernel.
  5. JorgeB
    I wouldn't worry about that.
  6. JorgeB
    Parity works with bits only, if doesn't know or care if the disks are empty or not. https://wiki.unraid.net/Parity#How_parity_works
  7. JorgeB
    Try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
  8. JorgeB
    There's nothing logged, no idea what it could be, you can try disabling plugins and/or containers one at a time to see if you can find something.
  9. JorgeB
    Please post those diagnostics if you still have them.
  10. JorgeB
    It does list the docker image, so recreate it and run another scrub to see if it still finds errors.
  11. JorgeB
    Very unlikely, unless they are sharing the DMI bandwidth with other things, start by posting the diags during a rebuild/check.
  12. JorgeB
    If you don't get the same call trace you should enable the syslog server then create a new thread in the general support forum and post your diagnostics together with the permanent log after a crash.
  13. JorgeB
    After the scrub look at the syslog, it will list the corrupt files(s), delete/restore those form backups, if there's also or only corrupt metadata then best to re-format the pool.
  14. JorgeB
    What to mean ZFS pool array? Unraid does not currently support ZFS, you can mount the old disks in the array, together with the new ones if you don't parity installed for now, then copy the data, remove the old disks and add parity.
  15. JorgeB
    Oct 30 21:25:43 Tower root: umount: /mnt/disk1: target is busy. Something is preventing disk1 from unmounting, make sure there's not an SSH connection open to that disk for example.
  16. JorgeB
    Post new diags.
  17. JorgeB
    Disk7 is failing and since there already another disable disk you are in a bad spot, you can try cloning disk7 to a same size disk with ddrescue than use the clone to rebuild disk4, but there will likely be some data loss, how much depends on the amount of data ddrescue can recover.
  18. JorgeB
    You can use screen or similar.
  19. JorgeB
    emhttp is crashing, try booting in safe mode to rule out any plugin issue.
  20. JorgeB
    Floor for that share is set to 2TB, more than available in any of the array disks.
  21. JorgeB
    Enable the syslog server and post that after a crash.
  22. JorgeB
    This happening for multiple devices: Oct 29 20:05:29 Tower-Transfer kernel: sd 1:0:4:0: Power-on or device reset occurred Oct 29 20:05:29 Tower-Transfer kernel: sd 1:0:7:0: Power-on or device reset occurred Oct 29 20:05:29 Tower-Transfer kernel: sd 1:0:1:0: Power-on or device reset occurred usually suggests a power/connection problem.
  23. JorgeB
    user share vs disk share
  24. JorgeB
    Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  25. JorgeB
    Do you mean it reboots during booting Unraid? If yes try booting CSM or UEFI, and normal and with the GUI mode, sometimes it makes a difference.
×
×
  • Create New...