Jump to content

itimpi

Community Developer
  • Content Count

    7183
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by itimpi

  1. With OpenVPN you are NOT exposing your server to the internet - just the OpenVPN port and that is considered safe. If OpenVPN gets cracked then there will be probably be millions of servers that suddenly become insecure.
  2. Normally one can look at the address other devices (e.g. tablets, phones) are getting issued. I would suggest deleting (or renaming) the network.cfg file is definitely worth trying as that causes the server to revert to using DHCP for getting its address assigned.
  3. To ask the obvious question what subnet is the new router on? If it is not 192.168.0.* then that would explain your symptoms. Do you have a keyboard/monitor attached to your Unraid server? If so you could boot into the GUI that way to set the server back to using DHCP to see what address it end up with. Alternatively deleting the config/network.cfg file of the USB drive will reset networking to defaults (which will also be using DHCP).
  4. That is not how Unraid works as it does not mirror data that is in the array.. You might want to read up on how parity is handled in Unraid. the rules are simple: parity drives cannot be smaller than the largest data drive. the available data space is the sum of the space on the data drives.
  5. There is no way that error should be directly a factor of the 6.7 release. There will be some other factor at work. That error suggests that the USB stick is not being properly picked up during the boot process.
  6. UnRAID does not use any of the standard RAID techniques. It has some similarities in that it has parity protected data but it functions in significantly different manner (hence it's name). The differences make it very suitable for many home users, but one thing you should not be expecting is anything special in the way of performance.
  7. That is true if you are using a single drive for cache. If you are using multiple drives then you can handle a single drive within the cache failing as the BTRFS file system used in such cases stores data redundantly which is similar to how Unraid uses parity on the array to protect against a drive failing.. Having said that having a backup elsewhere is still a good idea as you can lose data on a cache drive (or the Unraid array) for more reasons than simply a drive failing.
  8. If you want files to be on the cache and protected then you need to have a cache pool of 2 or more drives running RAID1 (the default) mode. An alternative approach is to install the CA Backup plugin that will make a backup of the appdata Share to the array on a pre-defined schedule.
  9. Even if Calibre does recognise the drive when USB connected having it as part of the array is not a recommended way of running as USB drives have a tendency to momentarily drop out causing Unraid to disable the drive. If you need access to its files you are likely to be better off having it connected as a Unassigned `device as that is less likely to encounter such issues.
  10. Unfortunately not - that is the way High Water Allocation works. It works through drives in slot number order at each switch point. If you are really concerned then I think the only solution would be to have the 4TB disks on lower slot numbers than the 8TB ones so they started being used first when the 4TB point was reached. Since you only have single parity this could be done without recalculating parity if you really wanted to do this. However is it worth it?
  11. Note that It is already to create a second cache pool managed by Unassigned Devices as long as you do not want it to also participate in the User Share System. You do have to use CLI level commands to initially create the pool as there is no GUI support for setting up such a pool.
  12. What do you have set as the Split Level? In any contention between Allocation and Split Level for choosing the target disk then Split Level always wins. The point at which Allocation method switches drives is always based on the largest drive. This gives split point of 8TB, 4TB, 2TB etc. On that basis the 4TB drives will not start getting used until the existing 8TB drives get to 2TB Free.
  13. That is sensible if you are happy for the files to end up on the main array. And thus protected against drive failure. Some people prefer that they never go to the array to avoid spinning up array drives unnecessarily and thus use different settings. It is a personal preference so there is no ‘right’ answer - it all depends on the behavior you want to achieve.
  14. Nothing stands out there. It is very short so does that mean that the system crashed/froze almost immediately? Not sure what to say other than the fact that such crashes/freezes are nearly always related to hardware in some way. Commonest cause is RAM but you say you have run an extended memtest. Other common possibilities are temperature (causing thermal shutdown of the CPU) or power. Probably will not help but it might be worth starting the array in Maintenance mode and then clicking on each drive in turn to run a file system check. Not sure if that can ever cause your symptoms but checking would be both easy and harmless.
  15. The problem will be that you have explicitly named /mnt/cache in the ftp settings, but the Use Cache setting for the share is set to “Yes” which tells Mover to move it to the array when it runs. If you do not want Mover to touch it set it to Use Cache=Only (or Prefer if you want Mover to move files back from the array to the cache). An alternative would be to set up ftp to use /mnt/user instead of /mnt/cache as that would find files regardless of whether they were on the cache or array.
  16. Since you are on 6.7 it is worth enabling the new syslog feature (Settings >>> Syslog Server) and setting it to mirror the syslog to the flash drive. That way you have a log of what was happening leading up to the crash/freeze.
  17. Do you mean multiple arrays or multiple cache pools - they are not the same thing.
  18. Ok. However the disk contents are being emulated while doing a rebuild and what will be seen after the rebuild is exactly what is available in the emulated contents. If as you said a format command was used then Unraid will sim-lay be rebuilding the disk with an empty file system. At this point is the disk mounting or still showing an ‘unmountable’ state? The latter would be more promising as it would suggest a format was NOT done and a file system repair is still possible.
  19. Your syslog shows lots of connection problems with disk1. These are normally (although not always) caused by bad cabling (SATA or power) to the drive. You should power down and carefully check the cabling to that drive and make sure it is properly seated. The SATA report looks OK so hopefully it is just the cabling to the drive. CRC errors are caused by connection problems. Once they have happened they never get reset to 0. If you click on the disk’s icon on the Dashboard tab there is an option to Acknowlege the current count and Unraid will then only tell you again if it increases. Occasional CEC errors are not a problem but if they are occurring regularly then you have an issue that needs sorting (typically cable related). The disk being disabled means a write to it has failed. When that happens Unraid will mark it as disabled and stop writing to it, instead emulating its contents from the combination of the other data disks plus the parity drive so you can still access its contents as if it were present. At this point you are no longer protected against another drive having problems so you want to clear the disabled state. Hopefully the write failure is due to the connection issues and the drive itself is OK. Because a write failed it no longer has up-to-date data. To clear a disabled state you have to rebuild a drive from the emulated contents, ideally you would do this to a spare/replacement drive and then check the drive that got disabled offline. However if you do not have a spare/replacement drive and you think the one that got disabled is OK and the issue was caused by cabling (and you have corrected this) then you can rebuild to the same drive using the following steps: Stop the array unassign the disabled drive start the array. UnRaid will warn you that the contents of the missing drive are being emulated. This step makes Unraid ‘forget’ the current assignment. stop the array reassign the drive start the array and Unraid will start rebuilding the drive’s contents from the emulated content. You can access the drive normally during this process as Unraid will use the emulated contents while rebuilding. As long as the rebuild finishes without error you are good. If it fails (or any other issue arises) check back for advice and provide new diagnostics. BTW: The diagnostics include the SATA reports for all drives so no need to supply them separately.
  20. itimpi

    Display off

    As far as I know there is no way to configure anything like that. Unraid is normally run as a server where such a capability is not normally required.
  21. You cannot do a rebuild if a format was run in Unraid as all you will end up doing is rebuilding an empty disk.
  22. If the drive cannot be written to then there is definitely a problem with it. You could try to download the ZIP file of the Unraid release and then extract all the bz* type files over-writing the ones on the USB drive. This would fix any of them being corrupted- but it does require you being able to write to the USB stick. You might want to check that the USB drive does not have a switch to ‘lock’ it. This not very common nowadays but they do exist.
  23. I am very confused as with SMB I cannot see how the group could end up as 2000. Something must be setting that somewhere.