• Content count

  • Joined

  • Last visited

Community Reputation

21 Good

About itimpi


  • Gender
  • Location
    United Kingdom
  1. You are protected against 1 disk failing without taking any further action.. The parity calculations for dual parity are independent of each other. When you get the replacement disk then the parity on the re-placement disk will need to be recalculated.
  2. Unfortunately no. The design of unRAID means any file must fit on a single drive. There is no way built into unRAID to allow a file to be split in the way you want. Not sure what would create a single database file that is that huge? You mention NextCloud, but when using that the database is normally relatively small - it is the separate files that are managed by Nextcloud are what takes up the space (and they can be spread across drives).
  3. Cannot see off-hand why files are going to the wrong disk. However you will want to set the Minimum Frees space to something larger than zero. A good value is something like twice the size of the largest file you want to copy. That should at least stop the case of unRAID starting to write a file to a disk and then finding it runs out of space for the file during the copy.
  4. I think you are going to have to provide the exact path for a file you think is going to the wrong disk, and also the share settings for that specific share. The easiest way to do this is to provide the Diagnostics zip file (Tools->Diagnostics) as it includes this information amongst other items useful to those trying to diagnose problems. A point to note is that if you have set the Split Level in your share settings this will over-ride the allocation method setting in the case of a conflict.
  5. That guide is very old and not the way to do things with v6. if you simply install the 'Unassigned Devices' plugin in provides all the functionality required for mounting drives external to the array (including NTFS format ones) with full GUI support. You can optionally share devices mounted this way as shares.
  6. Glad to hear that the issue is resolved. It sounds as if there may be some issue with the support of those controllers at the Linux kernel level, and if so some future kernel version may resolve the issue.? Hopefully you can live with them disabled without it being a major inconvenience?
  7. The log appears to be full of messages relating to USB devices which is not normal. I would suggest unplugging all un-needed USB devices. Also if possible plug the unRAID USB drive into a USB 2 port rather than a USB 3 one.
  8. That syslog appears to be just after a reboot and the array being started. If so then one is needed that covers the period when the error occurred as the logs are cleared when you reboot. Also so rather than just the syslog you should instead post the full diagnostics (Tools->Diagnostics) as that includes much more than just the syslog.
  9. You made an error in the steps when the disk was first disabled and tried to bring it back into operation. You added an additional step which was to format the drive. This told unRAID that it should update parity to say that the disk contains an empty file system. If you had NOT formatted the drive then unRAID would have rebuilt it to contain its original contents. in terms of the latest file system check I have not seen those errors before, and they do not look promising. Did you run the check from the GUI or the command line? If via the command line exactly what command did you use. You should also proved the diagnostics (Tools->Diagnostics) as it gives a lot of additional information to help those who are trying to work out what went wrong.
  10. The loop0 device that the log mentions is where the docker image is mounted.
  11. The command line you used looks incorrect! When using the raw device names you need to include the partition number so you should have been using '/dev/hdb1'. if the array is in maintenance mode then you can use /dev/mdX where X refers to the disk number in the unRAID GUI as the mdX devices already take the partition into account.
  12. The parity drive dropping offline should not be sufficient to stop files being written to the array. It suggests there might be file system corruption on one (or more) of the drives. You should put the array into Maintenance mode and carry out a file system (reiserfsck) check on each of your drives.
  13. User shares do not require parity to be present. Not sure what makes you think this is the case.
  14. You might find to be of use?
  15. No, that is not an option. UnRAID only supports connecting via the network.
Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.