Jump to content

JorgeB

Moderators
  • Posts

    67,452
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. You could do a new config but would require a parity sync/check, and since the emulated disk is mounting correctly might as well rebuild it instead..
  2. Only if that it making it use a zone with marginal sectors. It's usually good to give a disk a second chance when it's a one time thing but if it keeps having read errors better to replace it.
  3. You can use pv but current dd already shows progress with the status=progress option, as for byte size anything above 1M should be good for performance.
  4. You'd need to post on the appropriate preclear support thread, not sure preclear supports SAS devices.
  5. What data are you missing?
  6. Yes, it should be fine for the rebuild, then probably a good idea to replace it.
  7. Link isn't working but assuming it's a multiple disk enclosure running from a single eSata port it's not recommended, both for performance and reliability, since it will use a Sata port multiplier, if you really need external look for a SAS enclosure.
  8. Look for an 8 port LSI already in IT mode, several are sold ready to use, e.g Art of Server on ebay
  9. Gigabyte boards are known to create HPA partitions by default. Also, you should change the SATA controller to AHCI/SATA and update Unraid to latest.
  10. Unraid is only detecting 2GB of RAM, that's very little for v6, and possibly there's some issue with the server which looks like it has more RAM installed.
  11. There was no need to disconnect, just unassign it, but disconnecting will accomplish the same.
  12. There appears to be a problem with the cache filesystem, to confirm do this: If Docker/VM services are using the cache disable them, then unassign the cache device and start array.
  13. The array shoudd be much faster, especially with just one data drive which makes work similar to a RAID1 array, two things you can test, copying directly to a disk share instead of user share, you can enable disk shares on settings -> global share settings, then copy to \\tower\disk1, another thing would be to add an SSD as cache, for either test do a standard SMB copy using Windows explorer, from a Windows 10 PC if possible.
  14. Try to shutdown the server by typing "shutdown" on the console, if it doesn't after 5 minutes you'll need to force it.
  15. The zip is on the logs folder of yoru flash drive, upload it here directly to the forum.
  16. Feel free to ask for help if you have any doubts.
  17. Loop2 is the docker image and it's corrupt, you need to re-create it, cache filesystem itself looks fine for now, there are a few old corruption errors but those should not increase anymore if the RAM problem was solved, you can see here to clear the errors and continue monitoring it.
  18. If the disk dropped during the SMART test is likely bad, though make sure power is OK.
  19. On the server console using your keyboard/monitor if you have one, alternatively using the terminal window/putty.
  20. You just need to check the result, in doubt post the SMART report.
  21. Not really, you should get reasonably consistent results close to line speed.
  22. SMART test failed, so disk needs to be replaced.
×
×
  • Create New...