Jump to content

itimpi

Moderators
 View Profile  See their activity

  • Posts

    20,775

  • Joined

  • Last visited

  • Days Won

    57

 Content Type 

Everything posted by itimpi

  1. itimpi
    If you have a current release of the Unassigned Devices plugin install, then it will create a /mnt/addons folder under which you can safely create mount points.
  2. itimpi
    You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.
  3. itimpi
    You will need to run without -n before anything gets fixed, and also add -L if it is asked for. After that restarting the array in normal mode should mount the drive.
  4. itimpi
    A User Share on the array can span multiple drives under the share name so you get a single view of the folders and/or files within that share. It is just that any individual file is always contained on a single drive. That means no file can be larger than the drive that holds it.
  5. itimpi
    @comet424 Have you checked on your Main server that Settings->Unassigned Devices->SMB Security is set to something other than No? If set to No then it cannot be accessed over the network.
  6. itimpi
    Assuming you are talking about disk images (e.g. .vdi files under VirtualBox) that the VM sees as if they were a disk drive then the same applies on Unraid. As far as the basic Unraid system is concerned these are just a file like any other file. One constraint using Unraid is that such a file must fit onto a drive (I.e. cannot span drives) as under Unraid each array drive is a self-contained filing system (that could potentially be read in isolation outside Unraid).
  7. itimpi
    You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.
  8. itimpi
    Have you checked under Settings->Unassigned Devices->SMB Security that it is set to something other than No?
  9. itimpi
    That should work (although it might be necessary to reset permissions).
  10. itimpi
    It will if you have not restarted the array in normal mode.
  11. itimpi
    Have you tried restarting the array in normal mode? I would expect the drive to now mount OK.
  12. itimpi
    In Unraid you would have 8TB of usable space with 3 drives as you would lose one drive to parity.
  13. itimpi
    That is quite standard, you need to rerun it adding the -L option (and without -n for any changes to be made).
  14. itimpi
    If you want anything to survive a reboot you need to have a copy on the flash drive that you reinstate as part of the startup sequence.
  15. itimpi
    Assuming that is the location within the container, have you tried mapping it to a location outside the container?
  16. itimpi
    Chances you will the torrent failing with ‘out of space’ errors. Once a drive has been selected for a file Unraid will never change its mind and will generate an error if the file does not fit. In your stated case it might make a difference if you have the torrent client set to allocate all the space for files from the outset or not and what you have set as the Minimum Free Space setting for the cache as to whether any part of the torrent will overflow to the main array.
  17. itimpi
    If a file already exists it is opened ‘in situ’ wherever it already is (cache or array) at the moment. The cache drive would come into play for new files.
  18. itimpi
    If you have the array running in normal mode then you should be able to view the contents of what is being reconstructed even though it is still in progress. Can you do this and does it look like what you expect?
  19. itimpi
    In that case I cannot see why new files for that share would not go to the cache drive.
  20. itimpi
    Do the target file names already exist on the array? If a file already exists then it is overwritten in-situ. Only new files would get sent to the cache.
  21. itimpi
    It is not clear to me where the formatting and reading are taking place? I would expect you to be partitioning and formatting on the Unraid side to ensure the partitioning conforms to Unraid standards. You should then be trying to read this on the Debian system to prove it can be read outside Unraid. Your narrative suggests you might be trying the other way around?
  22. itimpi
    You have got this in your syslog: Mar 6 18:40:40 Apollo kernel: BTRFS critical (device sdb1): corrupt leaf: block=4926130962432 slot=84 extent bytenr=4950498230272 len=49152 unknown inline ref type: 129 which indicates corruption the on 'cache' pool. The SMART information for that drive does not indicate an issue however.
  23. itimpi
    Not quite sure what you mean by this as the main array does not 'pool' drives? Perhaps posting a screenshot of the Main tab, or alternatively posting your system's diagnostics zip file to your next post in this thread might make things clearer as to the current state of your system.
  24. itimpi
    I obviously need new glasses as I had not spotted that the last drive was only 2GB
  25. itimpi
    It looks like a problem reading from the flash drive and if it is this, sometimes downloading the zip file for the release that is on the flash drive from the Unraid web site and extracting all the bz* type files overwriting the ones on the flash drive can sometimes fix this.
×
×
  • Create New...