itimpi
-
Posts
20,780 -
Joined
-
Last visited
-
Days Won
57
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by itimpi
-
It is NEVER a requirement that you preclear a drive before adding it as if necessary Unraid will 'Clear' the drive when it is added. The main reason for running a preclear is as an initial stress test of the drive.
-
This is an issue with the USB Creator tool on some systems (i.e. not a GUID issue). Using the Manual install method in such a case. No - the GUID is built into the hardware. It is just that the MacOS version of the tool successfully read it off the flash drive.
-
To access the docker containers you will need to set up a VPN. E.g. WireGuard, Tailscale
-
I assume from the Edit that you now have set the share for exclusive access?
-
I think the primary Use Case for ZFS at the moment is that those who want performance can set up a ZFS pool and they can also make this to be redundant and have shares that live exclusively on that pool. The downside is that expanding ZFS pools is nowhere near as easy as the main Unraid array or BTRFS pools. At the moment only the main Unraid array can act as secondary storage.
-
This is not an option in the current Unraid releases as you cannot move files between pools - only to/from a pool and the main Unraid array. it is likely that this restriction will disappear in the Unraid 6.13 release where we have been told that the current Unraid array becomes just another pool type, but there is no ETA when this will be available, and there is always the chance that things do not turn out as expected.
-
I am trying to understand why you need hard links? It looks as if all the shares except ‘downloads’ have mutually exclusive content so once you move a file from the ‘downloads’ share to the correct target share no hard link is required. What am I missing?
-
Have you tried booting in Safe Mode in case you have a plugin installed that is not compatible with 6.11.5? -
You said that you formatted them via UD so they were no longer all zeroes. During the initial add Unraid would have ‘cleared’ them to be all zeroes so parity remained valid. The rebuild is putting them back to that state. BTW: you can add as many NEW drives as you want at the same time. What you cannot do is rebuild more failed drives than you have parity drives.
-
For reference the process for adding disks 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.
-
I have been saying for a long time that the pool setting should be used when for a pool for caching purposes and the share setting used when writing to the main array. The only time the share setting should apply to a pool is if the share is set to only be on the pool.
-
This will happen if you set the Minimum Free Space for the pool (cache) irrespective of whether you have set a Min9mum Free Space for a share.
-
What are you using to do the copy? What is the source and target paths you are using in the co-y?
-
Unraid only supports a file being in 1 location (I.e. on a pool OR on the array) at a given point in time.
-
Have you checked that the option to show disk shares is set under Settings->Global Share settings?
-
You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.
-
Since Preclear is not a standard part of Unraid the rebuild process does not check whether the disk has a Preclear signature. I agree that it could as an optimisation but that would be a new feature/enhancement.
-
The first thing to do is to update to 6.12.3 as this fixes an issue that is known to result in unclean shutdowns. If the issue persists after the upgrade you should try the steps mentioned 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.
-
According to the diagnostics mover is finding nothin to do! Which share contains files you expect to be moved?
-
The rebuild process does not need a disk to have been precleared so since Preclear is not a standard Unraid feature it is not taking this into account.
-
By default logs are only in RAM so are lost when the server reboots. If you want persistent logs then you need to enable the syslog server.
-
Enable the syslog server with the option to mirror to flash. The resultant log will be in the 'logs' folder on the flash drive.
-
The diagnostics you posted seem to be just after a reboot so do not give us much to wok on! I would suggest that you turn on mover logging and then manually start mover from the Main tab. After doing that post new diagnostics. It would also help if you would mention what share(s) you think should be moved that are not being moved.
-
The parity drive has no file system. It is jus a collection of bits that in conjunction with the data drives can reconstruct the contents of a failed drive and has no concept of file system. That is why the Unraid array can have a mixture of file systems.
-
unloading "appdata" and "domains" to SSD, with backup on array.
itimpi replied to m00nman's topic in General Support
Not as you describe. A file is meant to only be in one place, either array or a pool. The closest you will get is using a plugin like Appdata Backup to periodically backup the appdata share to another location on the array.
