Jump to content

itimpi

Members
  • Content Count

    6396
  • Joined

  • Last visited

  • Days Won

    7

itimpi last won the day on September 2 2018

itimpi had the most liked content!

Community Reputation

204 Very Good

About itimpi

  • Rank
    Advanced Member
  • Birthday 06/10/1950

Converted

  • Gender
    Male
  • Location
    United Kingdom

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. UnRAID has disabled disk2 due to a write error and is now emulating its contents using the combination of the other disks plus the parity disk (which is why you can still see its contents). Once a disk is disabled Unraid stops writing to it. However this means that the array is now unprotected until the problem disk is recovered back to normal state so another disk getting disabled would cause data loss so you want to get the array back to a good state ASAP. The disk is quite likely to be OK as write errors are frequently due to external factors (e.g. cabling, power). If you post your diagnostics zip file (obtained via Tools->Diagnostics) then you will likely get some feedback as to whether the disks looks OK. The recovery process involves rebuilding to a good disk to get the physical disk back inline with the contents that Unraid is currently emulating.
  2. itimpi

    Complete Movie Folders Not Moved

    The Unraid mover does not work at the folder level so there is no easy way to do what you want. What might work is to set the Minimum Free Space for the share to be at least the size of the largest folder you intend to move. That way any particular folder should always complete.
  3. itimpi

    Unraid OS version 6.6.7 available

    That suggest that when doing the update the write to flash either failed or dropped offline. It would also explain why the parity check was instigated as if the disk state cannot be written to the flash after shutting down the array Unraid will think it was an unclean shutdown. You might want to try putting the flash drive into a Windows or Mac system and let it heck for corruption? If so make sure that it can be fixed just in case there is a real problem with the flash drive. Is the flash drive a USB2 one and do you use a USB2 port on your Unraid system? Just asking as using USB2 for both of those seems to be much less prone to unexpected errors. While plugged into your PC/Mac it would be a good idea to make sure you have a backup of the config folder? You then have the option of erasing the current flash drive, creating it as a new flash drive with the 6.6.7 release and then overwriting the config folder with your saved one to set back all your settings and your license key. Alternatively if you created a backup of the flash drive from the Unraid GUI you could use that.
  4. I think that is normal due to UnRAID having to check the file does not already exist on another drive. Belonging to the share (although I could be wrong ) it is likely that using the Folder Caching plugin will help here. I know that recently some people have had problems with that plugin but it could well have been due to the same kernel bug that was causing these small writes? I guess we will have to see what others find out?
  5. That is fine when you can get to the GUI (and should always be the preferred way for exactly the reason you give) I was just mentioning the other option for completeness as there are scenarios where it is the only viable option.
  6. Just for reference it is probably worth mentioning that you can if needed by-pass the GUI and edit the syslinux/syslinux.cfg file on the flash drive directly and move the 'menu default' entry appropriately.
  7. itimpi

    Ability to Pause Parity Check

    I am afraid that certainly will not make my initial release. That is concentrating on you providing a start-stop time for running parity check increments. It is something that can be considered as a 'wishlist' item to look into when the base functionality is working well. However any development will be hindered by the fact that my Unraid server does not support S3 sleep so testing will be difficult.
  8. Where is that path configured? Back slashes in Linux are not folder separators in a path.
  9. Did you scroll to the bottom of the page where there is a zip file link for all recent stable releases?
  10. itimpi

    Ability to Pause Parity Check

    Yes. I am currently testing a ‘Parity Check Tuning’ plug-in I am developing that utilises this feature to allow the parity check to be run in increments spread over several days (only running at defined times). Not too fancy at the moment but still looks like being very useful for those who have large drives and do not want the parity check to be bogging down performance by having it running during prime time.
  11. I would be happy with a license that simply limit the maximum drive size (perhaps to only 1GB or less) as that would do for testing. I actually have a spare license at the moment which I use testing. However I may want to use the spare license anger and some way to keep a small test environment would be convenient.
  12. itimpi

    Specify VNC port for VMs

    I do not think you can set the 'port' and 'websocket' to the same value. I always set the 'websocker' entry to a value in the 5700 range rather than the 5900 range and that seems to work fine. Cannot remember where I got the idea that the 'websocket' should be in that range
  13. itimpi

    [6.6.6] update errors in UI (js)

    What browser are you using?
  14. Are you sure they have beenformatted? When you first started the array Unraid would partition them but not format them. At that time UnRAID will have offered a format option but you have to manually activate it. The ‘auto’ option just means that Unraid will format to whatever is set as the default format under Disks->Disk Settings. If you want a different format then (with the array stopped) set any drive explicitly to the desired format. On restarting the array you can then use the format option to format the drive to that specific format.
  15. itimpi

    Array taking 30+ minutes to start up

    It is always a trade-off between the cost of allowing for the worst possible case, and using a lower value that handles the vast majority of cases but not all of them. The key point is that if to realise that once you start writing a file and Unraid has chosen the target drive it will not be taking into account the size of the file in picking the drive. It will just error out when free space gets to zero. As an example if you had 60GB free and you chose to write the 80GB file you mentioned. then Unraid would choose the cache drive (as it has more than the 50GB free that you intend to set) and then error out after writing 60GB (which fills the drive). If you had only been writing a 50GB file then it would have succeeded and you would have been left with 10GB free. At that point you would be below the Minimum Free Space value and subsequent writes would by-pass the cache. In terms of the meaning of the setting turn on the Help in the Unraid UI and that should make it clear how you can enter values and what they mean.