Jump to content

JorgeB

Moderators
  • Posts

    67,397
  • Joined

  • Last visited

  • Days Won

    705

Everything posted by JorgeB

  1. Just to confirm, when you connect the disk to a SATA port what error do you get? "Unmountable: invalid partition" or is it a different one?
  2. Basically no, you can connect the new disk to the server when you open it, but just leave it unassigned until the parity swap finishes, then go ahead and add the new disk to the array.
  3. Bumping this because it keeps popping up on the forum from time to time, note that it also happens with single parity, if the user tries to add a new disk at the same time as parity or before parity finishes syncing, and while it's just an annoyance it shouldn't be a complicated fix, if parity isn't valid and a new data disk is added give an error that actually gives a clue to the user what the problem is.
  4. You'll get this if parity isn't yet valid, though the error you get is nonsensical, it's an old bug, wait for parity sync to finish then add new disk.
  5. Possibly, there's a bug report about a similar issue, maybe post your experience there.
  6. Not sure it's so easy in Windows since you probably can only check if trim is enable or not, maybe difficult to confirm if the SSD it's actually being trimmed, but see here.
  7. Yes, but trial requires internet.
  8. Only the trial requires internet connection, registered keys don't.
  9. Yes, been using it for over a month now, no issues so far.
  10. Cache drive can just be re-assigned, but not the data device, you'd need to do a new config and re-sync parity, but first you need a new parity disk, since current one is failing.
  11. The 860 EVO supports trim, in fact it should even work with the LSI controller, since it's a SAS3 model and the SSD supports deterministic read zeros after trim, you can try again after connecting it to the LSI but would be surprised if it worked, likely an issue with the SSD, not with the 860 EVO in general which is known to work with Unraid and used by many, but with that one, or an issue with the 860 EVO 4TB model in general, since there won't be many in use with Unraid.
  12. Remove all plugins, start adding back one by one, though Dynamix, CA and related plugins would all be OK, unless out of date.
  13. -Tools -> New Config -> Retain current configuration: All -> Apply -Then on the main page check all disks are correctly assigned, assign any missing disks if needed, we're going to assume parity is mostly valid, maybe even 100% valid, so check "parity is already valid" before starting the array. After array start if all disks mount correctly run a parity check, if not post new diags. There's always some risk if any of the disks is really failing or have a corrupt file system, but the other options also have similar risks.
  14. Redo flash drive, backup, recreate using the USB tool, restore only config folder from the backup.
  15. Likely related to the RAID controller used, which BTW only supports up to 2TiB disks, though that by itself it's not a reason, still try formatting them on the onboard SATA ports.
  16. You likely have flash drive issues, try running chkdsk on it.
  17. This last check was correct, so when done do a non correcting one and if all is well it should find 0 errors. P.S. SMART reports are included with the diags, no need to post them also.
  18. This isn't a very straight forward situation, you could re-enable disk4 as 4TB and rebuild disk13, but if disk13 is healthy it would be probably best to do a new config and re-sync parity, can you get a SMART report for disk13? It's not on the diags.
  19. https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive Feel free to post diags if you want a second opinion.
  20. You can also just restore the existing key to the newly created flash, to the config folder.
  21. Looks like it has dual bult-in SAS expanders, you juts need a standard LSI HBA (better a model with external ports) then one or two SFF-8088 to SFF-8088 cables, if the external SAS ports come with the case, might also need the internal cables if not included.
  22. Yes, and the shares will also stay, but with default settings.
  23. Sorry, no idea what's going on, I suggest redoing the flash drive to rule out any config issue, backup current one, then re-do it and only restore super.dat (disk assignments) and the key file, both to the config folder, if it works then restore the other config files one by one or just reconfigure the server.
  24. Looks like trouble finding the share, please check or post output of: ls -lh /mnt/user to make sure share doesn't exist exist with both caps an no caps on the first letter. If it's not that create a new test share and see if that one works.
  25. Yes, but without the #, anything after that is ignored, it's used for commenting.
×
×
  • Create New...