itimpi
-
Posts
20,694 -
Joined
-
Last visited
-
Days Won
56
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by itimpi
-
You may have a power supply issue as a parity check is one time when all drives are being accessed at the same time. you can edit the config/disk.cfg file on the flash drive to change the startArray option to “no” to avoid starting the array during the boot sequence. That would give you an option to disable the docker and VM services to see if that makes a difference and to do further investigations. You can also try booting in Safe Mode (which stops any plugins from loading) to see if that has any effect.
-
My guess is that the process supporting User Shares has crashed (if you post a copy of your system’s diagnostics we can probably confirm this). If that is the case rebooting the system will be needed to fix this.
-
That sounds like a bug although not at all clear what could trigger it. Maybe the flash drive had dropped offline so that Unraid could not update the array status on it to say it was successfully stopped?
-
Understanding File Transfer Performance in the unRaid Environment
itimpi replied to jeffreywhunter's topic in General Support
@jeffreywhunter you might want to read this section of the online documentation accessible via the ‘Manual’ link at the bottom of the GUI. -
Unraid will report on SMART values, but will only mark a drive as failed if a write to it fails.
-
The diagnostics are a single zip file - please post that instead of all the files inside the zip.
-
Unraid has had problems getting times (and speeds) correct when there are pauses involved. the plug-in takes account of this in the messages it generates (as opposed to the ones Unraid generates), and also in the history record written on completion.
-
I use Edge when on Windows, and Safari on my iOS devices. Not sure which I should be voting for?
-
Was the drive showing as unmountable while it was being emulated before rebuilding it? If so that would not get cleared by a rebuild. the standard process for handling an unmountable disk is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI.
-
You could look at the sub-folders within the appdata share to see which container the space is associated with.
-
If you reboot the system all the standard Unraid permissions will revert to their standard settings as a fresh copy of Unraid is always loaded from the archives on the flash drive as part of the boot process. You may, however, have upset permissions on the appdata share for some of the docker containers.
-
The licence file is tied to the GUID of the flash drive for which it is licensed. There is a process for transferring the licence to a new USB drive (and black-listing the old one), but you will not need to use that if you continue to use the same USB drive.
-
You are going to have to work out how to get into the BIOS on your motherboard. From the message I would think that the correct boot device is not set at the BIOS level. As it was in storage for a long time there is a good chance the CMOS for the BIOS had lost its settings so you have reverted to defaults.
-
Your syslog shows that there appear to be btrfs level problems with device sdf which I think is a cache drive so it cannot be successfully unmounted
-
You have to start the array after setting the slot yo Unassigned to get Unraid to ‘forget’ the old drive. If you simply reboot the change will not get committed - that happens when the array is started after making the change. After doing that you can then stop the array and assign the new drive to the slot.
-
Re-ordering drives invalidates parity2 and changing the number of drives invalidates parity1. If you clicked the Parity is Valid checkbox to avoid immediately rebuilding parity then the behaviour you are seeing will be expected.
-
Do you have the My Servers plugin installed? If so you can get your key file via that. It would also be included in any local backup you have made of the flash drive. There is also the possibility you have it attached to an email from Limetech. In the worst case you can email Limetech and they should then be able to help but that may take a bit longer to get resolved.
-
Basically looks correct. However a step I would add before the one where you reassign the disabled disk is to check that the emulated disk has the expected contents as all the rebuild process does is make the physical disk match the emulated one. If the emulated disk does NOT contain what you expect (or does not mount) then a different action might be more appropriate.
-
You are likely to get better informed feedback if you post your systems diagnostics zip file
-
Unraid does not split files across drives, so you need to make sure a disk has enough space to contain the vdisk when it grows to its maximum size. If there is not enough space then the VM will stop working when the drive runs out of free space. another possibility is to bypass this problem by passing a complete physical drive to a VM.
-
Probably worth pointing out that a version that DOES work with UEFI boot can be downloaded from memtest86.com
-
All drives that are visible to Unraid when starting the array count towards the licence limit. If you are passing a disk controller through to your VM then drives attached to it will not be visible to Unraid and thus not count. However if you are passing through individual drives (i.e. ones that show up under Unassigned Devices) then they DO count.
- 1 reply
-
- 1
-
-
This is purely a user choice and has been for some time. It all depends on whether you want the extra confidence in drive health the pre-clear gives and thus think the time it takes is a good trade-off.
-
No. Rebuild requires all drives other than the failed drive to be able to be read without error to run.
-
Have you restarted the array since making this change? I believe there is a bug in 6.10.0. Rc2 where such a change will not take effect until the array is next started. note that as long as you have set the Minimum Free Space setting for the cache pool (set by clicking on the pool name on the Main tab) to be larger than the biggest file you intend to copy then even with the Yes setting Unraid will start by-passing the cache when the free space falls below that value.
