Jump to content

JorgeB

Moderators
  • Posts

    67,541
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. You can just format the unmountable array disk and then move the data there from UD.
  2. Unfortunately diags after rebooting are not much help, you can try this.
  3. This is not good for Unraid, look for a regular LSI HBA instead, not megaRAID models. Also have some 2.5" drive cages: but for HDDs, the SSDs are in a controller like this one, only 4 data devices, like mentioned it's a small server (parity is NVMe).
  4. I would think (and hope) so. No, it just means there could be some write performance deterioration with time, I have a small SSD array and for now it's performing normally even without trim.
  5. You can use the one built in, it doesn't work with UEFI boot though, only legacy/CSM.
  6. Trim is supported for any pool devices, currently not supported for array devices.
  7. It's filesystem corruption, can't see an apparent reason, and if it's not the first time it might indicate a hardware issue, good idea to run memtest.
  8. Don't see much point, though just to confirm you can start one and stop as soon as there are errors. Yep, no need.
  9. Yes, by clicking on it (if it's an assigned device), if you have unassigned devices than run hotter the current workaround is to set the general settings to that temp and then click on each assigned device and set lower temp thresholds.
  10. You can do that, or just clone disk2 to a new disk then rebuild parity with that one, note that either way some data corruption is expected.
  11. In my experience some SMR disks work fine with Unraid, e.g., the Seagate drives I've have, both the 8TB Archive model as well as 4TB 2.5" drives, they are fast during a rebuild/sync and don't notice any big slowdowns during large sequential transfers (mostly large files, might be different with small files), on the other hand WD and Toshiba SMR drives behave normally during rebuild/sync but they get extremely slow during large transfers, even for large files.
  12. So if the respective folders already exist in disk6 it will be used by Unraid.
  13. The vdisk might be corrupt, no way of knowing.
  14. Best bet is to try a different flash drive, you can see if it works first before transferring the license.
  15. Enabling NOCOW turns off data checksum, so those can't be checked or fixed.
  16. This means it was corrupt, btrfs won't let you copy/read a corrupt file. That shouldn't be a problem. Unlikely to be a device problem, if it's hardware related it's likely RAM.
  17. Use IP from a different subnet.
  18. WD and Toshiba 8TB or above Seagate 10TB or above All others might be.
  19. I would think so, extremely unlikely to have 2 disks returning corrupt data, having one is already very unusual.
  20. Most likely, I would run another one just to make sure, kind of worrying that a disk starts corrupting data out of the blue without any apparent reason, and SMART looks normal.
  21. I've never used that program, best bet is to ask for help directly from them.
×
×
  • Create New...