Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,600

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Not without parity, and if you had parity and did that it would leave you with an unprotected array. You can remove it from the array:
  2. JorgeB
    If it's an option I would test with a non SMR drive in that slot.
  3. JorgeB
    It appears to be an Unraid bug, it's not respecting the set timeout, you had the timeout set to 100 secs, and Unraid was forcing the shutdown after less than 30 secs had elapsed, changing the setting usually makes it stick, same thing happened to a handful of users after upgrading to v6.9.
  4. JorgeB
    No, if there's a problem it's with the LSI driver and some Seagates drives, either LSI or Seagate would need to fix it.
  5. JorgeB
    Btrfs is detecting data corruption, since it's a Ryzen based server possibly overclocked RAM, without the diags can't see if mem is within specs.
  6. JorgeB
    Please post the diagnostics: Tools -> Diagnostics.
  7. JorgeB
    I don't see how this could work, just run another check using the GUI to make sure all is well.
  8. JorgeB
    Shutdown timeout is not being honored, did you try changing to a different number and re-applying?
  9. JorgeB
    There is: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480421
  10. JorgeB
    Thanks, that could be a good workaround for other users.
  11. JorgeB
    That's normal with different size devices in raid1, used space is wrong, but unlike before free space is correct, and that's much more important.
  12. JorgeB
    That could be SMR, though during rebuilds SMR effect is not usually felt, at least for most drives I tested with. Unlikely a new cable would help if there are no ATA errors logged.
  13. JorgeB
    If I understood correctly having the system and appdata shares on a different pool helps? At least the dockers don't go offline like that? P.S. it's normal for CPU usage to go up a lot in the GUI dashboard during any transfer since it accounts for i/o wait, same shouldn't happen for example on top.
  14. JorgeB
    What kind of pool? Or post the diags.
  15. JorgeB
    If you want to copy to share use /mnt/user/Share_name/ if you want to copy to a disk use /mnt/diskX/
  16. JorgeB
    Shares are just top folders, you can just create a folder with the correct name on that disk.
  17. JorgeB
    Whatever you prefer.
  18. JorgeB
    Delete all the diags from the flash drive, do another reboot, post the diags saved there.
  19. JorgeB
    If the source is an unassigned disk there's no problem, problem is copying from disk to share or vice versa in the array.
  20. JorgeB
    That's not a spare. You can do a new config, assign that disk as parity and start array to begin the parity sync.
  21. JorgeB
    What do you mean? Spare should already be unassigned.
  22. JorgeB
    Yes.
  23. JorgeB
    This is a connection problem, not a disk problem. Stop array, assign spare to parity slot (or parity2), start array.
  24. JorgeB
  25. JorgeB
    It's possible, try swapping with a different disk.
×
×
  • Create New...