Jump to content

itimpi

Moderators
  • Posts

    20,784
  • Joined

  • Last visited

  • Days Won

    57

Everything posted by itimpi

  1. Are you replacing or adding drives? Are you expecting to keep any data on those drives? The process you seem to be going through is to add new drives? If so then Unraid has to Clear them (write all zeroes) to the drives to avoid invalidating parity and then they need to be formatted to create empty file systems on the drives.
  2. in principle anything that is not under /boot or /mnt is normally RAM based. you may find this section of the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page helps with understanding this. The Unraid OS->Manual section in particular covers most features of the current Unraid release.
  3. Those locations are only in RAM (like most of Unraid OS) which is why they do not survive a reboot. You need to add something to the Unraid boot sequence (such as entries in the config/go file) to re-instate any such changes after the Unraid OS has been loaded into RAM.
  4. That is not a standard feature built into Unraid.
  5. Are you sure the timeout for stopping the array is long enough? You mentioned you do not get an unclean shutdown if you stop the array first.
  6. Have you tried the steps documented here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page that relate to troubleshooting unclean shutdowns? The Unraid OS->Manual section in particular covers most features of the current Unraid release.
  7. Short test does not test much of the drive - you need to use the extended test for that (but unfortunately that takes much longer).
  8. It looks like your cache pool is probably corrupt, and the docker.img file on that pool is definitely corrupt. a common cause of btrfs corruption is RAM issues so you should finitely run memtest to check it out (if you boot in UEFI mode use the version from memtest86.com).
  9. That is for sharing individual drives, not User Shares. Each User Share has an Export setting and you do not want it set to No if you want to access it over the network.
  10. Have you checked that the Shares are not set to Export=No (the default) as shares with that setting are not visible on the network.
  11. Have you tried accessing the server via its IP address rather than via its name? if you need to provide further information you want to provide your system’s diagnostics zip file as this includes both logs and a raft of information about your system setup.
  12. If you want to test the drives run the extended SMART tests on them. If that fails they need replacing.
  13. You need to rerun that check without -n and add -L
  14. It is up to you although it is normally easiest and least error prone to start with preserve all and then make changes from that position. for reference the New Config tool is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. The Unraid OS->Manual section in particular covers most features of the current Unraid release.
  15. I am confused - Unraid should be running a server, not on your Mac. Have I missed something?
  16. Have you tried unsettling the option in the pool settings to allow it to be used for User Shares? Nor sure if that would work or not?
  17. Unraid will automatically create a User Share for any top level folders on any pool that can be used for User Shares but with default settings. the thing to do in your case is to go into the share settings and set the Primary storage to the pool, and the secondary storage to None. This will not remove it from the GUI but it will function as expected and all its contents stored on the pool. No need for you to manually play around with the SMB settings.
  18. You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.
  19. You could check the health of the drive by clicking on it on the Main tab and running the extended SMART test.
  20. Whatever you do you must NOT format the disk unless you want to lose all its contents.
  21. You should be posting to the Unassigned Devices thread. However it is worth mentioning that I DO have those on my Unraid 6.12.4 system
  22. You should enable the syslog server so that we can get a syslog covering the period up to the reboot. By default the RAM copy of the syslog included the diagnostics restarts afresh on every boot.
  23. Have you rebooted since trying to install the purchased licence key?
  24. Not quite sure what you are asking? Your screen shot just shows the diagnostics collection process going through the process of applying its anonymisation rules to the syslog files.
×
×
  • Create New...