Jump to content

bonienl

Community Developer
  • Content Count

    7411
  • Joined

  • Last visited

  • Days Won

    41

Everything posted by bonienl

  1. This would be the case if the disk is formatted with a file system known to Unraid. E.g. you move the disks of your existing Unraid system to a completely new Unraid system, in this case all data is preserved.
  2. I work on these plugins when time and oppertunity arises, and I don't have much spare time lately. The S3 sleep plugin is just a GUI wrapper, it won't solve the problem that people have with WoL.
  3. There is no need to clear the disks when a new array is created. Unraid will format the disks with the default file system (XFS) and start syncing the parity disk. Expect a duration between 8 and 10 hours with 4 TB disks.
  4. Both 512e and 4kn disks work internally with 4k blocks, but a 512e model presents this as 512 blocks externally, to maintain compatability with 'older' controllers.
  5. You need to change the "network type" of the container to a custom network (Custom: br0 in your case). You can set both an IPv4 and IPv6 address (if used) as fixed address for Pihole. In addition: under Docker settings you need to enable br0 as custom network
  6. Currently Unraid is only available in English without multi-language support. Peut-être qu'un jour plusieurs langues seront supportées 😊
  7. Running VMs and Docker containers from data disks in the array results in very poor performance due to the parity calculation overhead. Hence it is recommended to create a cache (pool) and use this for VMs/Docker. A cache device/pool can consist of SSDs and this greatly improves the performance and overall experience. Some users run a cache device of 128G, which is okay but it should not be used as cache for the data array (i.e. copy files directly to the array and not cache). Use the biggest size you can afford, a bigger cache gives more headroom. Better performance and reliability is achieved when using a cache pool. A 2 disks cache pool allows for redundancy (raid1), while a 4 disks cache pool allows for both redundancy and higher disk throughput (raid10).
  8. Yes you can mix 512e and 4kn drives without negative effects. Unraid treats every disk as an independent drive, unlike a true raid system.
  9. Bonding is a good solution for two main reasons Higher availability. When a link fails, your server stays reachable for local and remote clients Higher throughput. This is beneficial when several local clients access your server at the same time
  10. The most common way is to assign the bridge function to a specific interface. This allows the bridge (br1) to become available to VMs, which results in VMs using their own dedicated connection separate from the Unraid management connection.
  11. To turn off this message, go to the Network settings and click on "Port Down" for eth1.
  12. Correct, change assignments here and reboot your server afterwards.
  13. WoL is not officially supported by Unraid. There is just too much hardware dependencies to guarantee correct functioning for each and every system (including the system proceedings after waking up). It seems only RealTek NICs are affected, hopefully Realtek releases an updated driver for the Linux kernel soon(tm).
  14. @CHBMB LOL that's asking for a lot attention... but indeed no reason to make different requests for the same thing.
  15. Which containers in Unraid need docker swarm? All containers can run autonomously.
  16. This sounds like you are having some hardware related issue.
  17. With "Mirror syslog to flash" enabled, everything is copied to the same file on the flash device, including the log after booting.
  18. Good you've found the culprit. Debug isn't an option in the GUI and only manual changing (editing the file) is possible. Will have a look why the setting cause so much havoc.
  19. I would remove the *.cfg files and check again. Btw have you tried to clear the browser cache completely? Sometimes the browser may keep corrupted data, clearing the cache solves that.
  20. Yes, that's why it is recommended to use it only while troubleshooting (as explained in the Help) This function ensures everything is captured from the start of the system, unlike the local syslog server which only starts capturing after the network and shares are available.
  21. Yes, I use them. Can recommend them, well made and working great (make sure you use good quality SATA cables too)
  22. For troubleshooting purposes the setting "Mirror syslog to flash" is introduced. This will copy everything logged to the flash device (even when the system is rebooted) With this setting enabled, it is not necessary to set up a syslog server explicitely.
  23. You may want to start "fresh" Save a copy of your current flash contents (see Main -> Flash -> Flash Backup). This can be used to restore - if needed Use the USB creator tool to create a "virgin" USB stick with Unraid 6.7.0 Copy your key file (*.key) to the folder /config on the USB stick Copy the file super.dat to the folder /config on the USB stick The above starts with a clean and registered system with all disks assigned as before.