Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,521

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Depends on how the cache mode is set to, see here (or use the GUI help).
  2. JorgeB
    Recommend adding that SAMBA SMB multichannel is still experimental and not recommended for production as in some rare cases it can cause data corruption, from the SAMBA manpage:
  3. JorgeB
    The problem appears to have happen when the mover ran, make sure files are not being moved/accessed by other things during the mover, you can schedule it for a different time if needed.
  4. JorgeB
    No, but it does happen to some, it's usually caused by a docker that moves files, you'd need to test one at a time to find out which one.
  5. JorgeB
    I though the diags were right after booting, you have a previous shfs crash, rebooting should fix it.
  6. JorgeB
    You have something creating /mnt/user before Unraid does it. Sep 26 02:25:52 Tower emhttpd: shcmd (3389): mkdir /mnt/user Sep 26 02:25:52 Tower root: mkdir: cannot create directory '/mnt/user': File exists
  7. JorgeB
    Disk1 dropped offline, power down, check cables and post new diags.
  8. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  9. JorgeB
    See if copying to the disk share is faster, like this one:
  10. JorgeB
    It's possible, you'd need to test without it running.
  11. JorgeB
    Did some more testing and googling and no idea what this could be, can't find anyone else complaining of something similar, I've been using snapshots together with send/receive to backup most of my Unraid servers for years now, most times during the backup I delete older snapshots from every data disk, and the space recovery always starts after a few seconds, in fact sometimes it even causes the server to perform slowly while it's deleting snapshots from multiple disks simultaneously, but it never took more than a few minutes to recover all the space.
  12. JorgeB
    According to the syslog it was already in IT mode, just on a very old firmware.
  13. JorgeB
    If you need to try the default config you can restore the key file and super.dat, both on the config folder. Syslog stops after loading all the plugins, before starting GUI and other services, another thing you can try, before redoing the flash, is to boot in safe mode.
  14. JorgeB
    Click on it and choose acknowledge.
  15. JorgeB
    Boot process isn't finishing, try redoing the flash drive with your config (backup config folder then restore), if it still doesn't boot try a new config.
  16. JorgeB
    For parity2 to be valid all data disks must be on the original slots, parity1 remains valid if all data disks are present, regardless of order, also note that parity1 and 2 are not interchangeable.
  17. JorgeB
    Disk looks OK, you can also swap cables with another disk to rule them if it happens again, and if it does don't forget to grab the diags before rebooting.
  18. JorgeB
    Enable CSM boot on the board or enable UEFI on the Unraid flash (by renaming the EFI- folder to EFI).
  19. JorgeB
    This time there were issues with disks sdn, sdo and sdp, they likely share the same miniSAS cable, so I would start by replacing that.
  20. JorgeB
    Thanks for posting back, few users using NFS, so more difficult to get help here.
  21. JorgeB
    Was looking for this, both were not linking at full speed/width, but one of them especially bad linking only at 5GT/s and x1.
  22. JorgeB
    You should reboot to clear the log.
  23. JorgeB
    Helium level on SMART for all helium drives I've seen so far, except the one above, was always 100, including the ones I have.
  24. JorgeB
    Speedtest docker should show them, if not use lspci -vv on the console
  25. JorgeB
    Then they are not helium, at least not from WD or HGST, AFAIK all have attribute #22 to indicate level, not sure if about Seagates.
×
×
  • Create New...