Leaderboard

Try this one..... root@matrix:/mnt/disk1/dvb# check-config.sh .config-swarm info: reading kernel config from .config-swarm ... Generally Necessary: - cgroup hierarchy: properly mounted [/sys/fs/cgroup] - CONFIG_NAMESPACES: enabled - CONFIG_NET_NS: enabled - CONFIG_PID_NS: enabled - CONFIG_IPC_NS: enabled - CONFIG_UTS_NS: enabled - CONFIG_CGROUPS: enabled - CONFIG_CGROUP_CPUACCT: enabled - CONFIG_CGROUP_DEVICE: enabled - CONFIG_CGROUP_FREEZER: enabled - CONFIG_CGROUP_SCHED: enabled - CONFIG_CPUSETS: enabled - CONFIG_MEMCG: enabled - CONFIG_KEYS: enabled - CONFIG_VETH: enabled (as module) - CONFIG_BRIDGE: enabled - CONFIG_BRIDGE_NETFILTER: enabled - CONFIG_NF_NAT_IPV4: enabled (as module) - CONFIG_IP_NF_FILTER: enabled (as module) - CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled - CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled - CONFIG_NETFILTER_XT_MATCH_IPVS: enabled (as module) - CONFIG_IP_NF_NAT: enabled (as module) - CONFIG_NF_NAT: enabled (as module) - CONFIG_NF_NAT_NEEDED: enabled - CONFIG_POSIX_MQUEUE: enabled Optional Features: - CONFIG_USER_NS: enabled - CONFIG_SECCOMP: enabled - CONFIG_CGROUP_PIDS: enabled - CONFIG_MEMCG_SWAP: enabled - CONFIG_MEMCG_SWAP_ENABLED: enabled (cgroup swap accounting is currently enabled) - CONFIG_LEGACY_VSYSCALL_EMULATE: enabled - CONFIG_BLK_CGROUP: enabled - CONFIG_BLK_DEV_THROTTLING: enabled - CONFIG_IOSCHED_CFQ: enabled - CONFIG_CFQ_GROUP_IOSCHED: enabled - CONFIG_CGROUP_PERF: enabled - CONFIG_CGROUP_HUGETLB: missing - CONFIG_NET_CLS_CGROUP: enabled (as module) - CONFIG_CGROUP_NET_PRIO: enabled - CONFIG_CFS_BANDWIDTH: enabled - CONFIG_FAIR_GROUP_SCHED: enabled - CONFIG_RT_GROUP_SCHED: enabled - CONFIG_IP_NF_TARGET_REDIRECT: enabled (as module) - CONFIG_IP_VS: enabled (as module) - CONFIG_IP_VS_NFCT: enabled - CONFIG_IP_VS_PROTO_TCP: enabled - CONFIG_IP_VS_PROTO_UDP: enabled - CONFIG_IP_VS_RR: enabled (as module) - CONFIG_EXT4_FS: enabled (as module) - CONFIG_EXT4_FS_POSIX_ACL: enabled - CONFIG_EXT4_FS_SECURITY: missing enable these ext4 configs if you are using ext3 or ext4 as backing filesystem - Network Drivers: - "overlay": - CONFIG_VXLAN: enabled (as module) Optional (for encrypted networks): - CONFIG_CRYPTO: enabled - CONFIG_CRYPTO_AEAD: enabled - CONFIG_CRYPTO_GCM: enabled (as module) - CONFIG_CRYPTO_SEQIV: enabled - CONFIG_CRYPTO_GHASH: enabled (as module) - CONFIG_XFRM: enabled - CONFIG_XFRM_USER: enabled - CONFIG_XFRM_ALGO: enabled - CONFIG_INET_ESP: enabled - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled - "ipvlan": - CONFIG_IPVLAN: enabled (as module) - "macvlan": - CONFIG_MACVLAN: enabled (as module) - CONFIG_DUMMY: enabled (as module) - "ftp,tftp client in container": - CONFIG_NF_NAT_FTP: enabled (as module) - CONFIG_NF_CONNTRACK_FTP: enabled (as module) - CONFIG_NF_NAT_TFTP: enabled (as module) - CONFIG_NF_CONNTRACK_TFTP: enabled - Storage Drivers: - "aufs": - CONFIG_AUFS_FS: missing - "btrfs": - CONFIG_BTRFS_FS: enabled - CONFIG_BTRFS_FS_POSIX_ACL: enabled - "devicemapper": - CONFIG_BLK_DEV_DM: enabled (as module) - CONFIG_DM_THIN_PROVISIONING: enabled (as module) - "overlay": - CONFIG_OVERLAY_FS: enabled - "zfs": - /dev/zfs: missing - zfs command: missing - zpool command: missing Limits: - /proc/sys/kernel/keys/root_maxkeys: 1000000 Unraid-v6.7.1rc1-swarm-v2.zipswarm-v2.patch

I don't know about you, but my wife does this all the time (usually in anger) and expects me to remember everything...

All the conf files are in the config folder. /config/nginx/site-confs/default is the one you want to edit for https redirection. There are instructions in there

What you describe should work. however it is worth pointing out that for important data you normally you want a backup that is independent of the server in case the server itself has some sort of catastrophic failure.

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.

60 Gig is insane for the size of a docker.img Vast majority of users only require 20Gig Max (assuming that everything is configured correctly), But either way, the docker.img is getting write errors. Because the system is in the process of shutting down, its hard to tell exactly where its being stored, (whether on the cache or disk3), but either way your initial trouble shooting is to disable the docker service, delete the image file, re-enable the service, then hit Apps, Previous Apps, and check off everything you had installed.

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.

Add it outside the array by using the Unassigned Devices plugin

That's host networking, not bridge. See the first item on the list above

The process many people follow is to create the initial array with one disk which you let Unraid partition and format. You then attach one of your existing disks to Unraid and use the Unassigned Devices plugin to mount it so that you can copy its data to the array. When the copy completes you can the add that drive to the array and let Unraid partition and format it to get more space in the array. Rinse-and-repeat until all the data is on the Unraid array.

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).

Argh.... Sorry. I found the problem and will fix it asap. Sorry for the inconvenience.

Only when expanding an existing array. When creating a new array, it doesn't matter. unRaid will format the drives though. No. A single data drive has to be present.

AIRVPN.ORG best vpn i've had,

There are several ways to disable the various mitigations, both via kernel parameters and at run-time (though this will require us to include 'debugfs' which we can do). Google 'linux disable meltdown spectre zombieland mitigations' for a number of how-to articles. If it gets serious enough we'll probably add debugfs support and perhaps a config page. Having all these mitigations in place is mainly a C.Y.A. move in my opinion.

Go to Nerd Tools and make sure atop isn't installed. Let us know what you find there. Rebooting would clear that out, or you could delete that from the command line.

Also, please note that on the "--device /dev/dri:/dev/dri" line that goes in Extra Parameters, there are two dashes in front of the word "device" and not just one. It is easy to see that as just one dash and that will not work.

I already answered you twice, but looks like I wasn't clear, so let me say it one more time: As long as the disk is properly partitioned and formatted in one of 3 filesystem recognized by unRAID it can be done elsewhere, including ubuntu. Assuming the disk is >2TB it needs to be GPT partitioned, easiest way is to use sgdisk, like so: sgdisk -o -a 64 -n 1:64:0 /dev/sdX This assumes a cleared disk.