NAS-newbie

Sadly I am not the type to document stuff like this but I have some wage recollection that there where one more thing in addition to the setting you mention that I had to change to make it work... sorry I cant be more precise 😥

Just out of curiosity what is different from the format performed as part of the array build procedure to formating a disk with a supported file system under Linux on another machine or say in UnRAID as an unassigned disk? Are there some special metadata written, some special req on formating parameters or? What I was hoping to achieve was to be able to fill the disk before it was added to the array (I assume writes are slower in the array as one also need to maintain the parity but perhaps there is no significant difference?)...

I am removing my old small drives and also switching the remaining drives to ZFS and to do this creating a new configuration. I also have one new drive that would like to use in the new array that already is formated with ZFS and contain data I would like to keep (and have included in the initial parity calculation). I tried to create a new configuration consisting of what should become the new parity drive and the already formated ZFS drive but when I start the array and start the parity calculation the new drive is for some reason marked as "unmountable" even though it is perfectly mountable as a "unassigned disk"...?! Is this because I have never done a "preclear" of this drive or what may be the reason? What is my best way forward in this situation?

Can also say I so far really like the build quality and features of the motherboard BIOS etc. It is not an inexpensive board but in this case it seems to deliver what one pay for. And as you say, at least in Sweden where I live, it seems to be the only motherboard you can ACTUALLY BUY if you want a "raptor lake" CPU with ECC memory so not much of a choice.

It is single bit ECC and the cable is this one.

Maybe also temporarily disable dockers and VMs in settings...

Today I use a single cache drive formatted with BTRFS (that I have not felt very confident running in RAID setup) but after upgrading to stable 6.12 where ZFS is available I intend to add an additional identical cache disk and is contemplating what the simplest procedure would be to switch to a two disk ZFS pool? Would I need to first switch all shares to not use the cache, then run the mover, remove the current one disk pool, create a new 2 disk ZFS pool, reset all the shares preferences back to use the cache and finally run the mover again or is there some less time consuming way?

Redid the whole configuration one more time with new credentials and everything and now it works - not sure what I did wrong last time to be honest...

No more errors found and when comparing with backups I found no diffs so must have been parity disk that was incorrect ....

Are any of the SERVER_XXXX parameters mandatory?

I am using the template but have deleted all "optional fields" with empty values related to OpenVPN to make the template more manageable (OpenVPN username and password must be deleted as I got an error message leaving them blank so assumed this was ok) as I only care for wireguard but maybe some of them must be passed empty values? I have double checked that I pasted in the "redacted" keys right so is fairly sure they are ok. Compared to some examples I have seen I am considering if any of the SERVER_XXXX are needed? When I tried filling some of them in the container did not even start so not sure of the syntax/allowed values in that case....

Trying to make the Gluetun UnRAID container to work with wireguard on winscribe VPN. The configuration I downloaded from winscribe looks like this: [Interface] PrivateKey = REDACTED Address = 100.119.95.165/32 DNS = 10.255.255.3 [Peer] PublicKey = REDACTED AllowedIPs = 0.0.0.0/0, ::/0 Endpoint = arn-159-wg.whiskergalaxy.com:65142 PresharedKey = REDACTED and the resulting docker parameters after my configuration looks like this: docker run -d --name='GluetunVPN' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="REDACTED" -e HOST_CONTAINERNAME="GluetunVPN" -e 'TZ'='CET' -e 'VPN_SERVICE_PROVIDER'='windscribe' -e 'VPN_TYPE'='wireguard' -e 'VPN_INTERFACE'='tun0' -e 'OPENVPN_PROTOCOL'='udp' -e 'OPENVPN_VERSION'='2.5' -e 'OPENVPN_VERBOSITY'='1' -e 'OPENVPN_PROCESS_USER'='no' -e 'OPENVPN_IPV6'='off' -e 'WIREGUARD_IMPLEMENTATION'='auto' -e 'WIREGUARD_PRIVATE_KEY'='REDACTED' -e 'WIREGUARD_PRESHARED_KEY'='REDACTED' -e 'WIREGUARD_ADDRESSES'='100.119.95.165/32' -e 'SERVER_REGIONS'='' -e 'SERVER_COUNTRIES'='' -e 'SERVER_CITIES'='' -e 'SERVER_NAMES'='' -e 'SERVER_HOSTNAMES'='' -e 'FIREWALL'='on' -e 'FIREWALL_VPN_INPUT_PORTS'='' -e 'FIREWALL_INPUT_PORTS'='' -e 'FIREWALL_OUTBOUND_SUBNETS'='' -e 'FIREWALL_DEBUG'='off' -e 'LOG_LEVEL'='info' -e 'DOT'='on' -e 'DOT_PROVIDERS'='cloudflare' -e 'DOT_PRIVATE_ADDRESS'='127.0.0.1/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,169.254.0.0/16,::1/128,fc00::/7,fe80::/10,::ffff:7f00:1/104,::ffff:a00:0/104,::ffff:a9fe:0/112,::ffff:ac10:0/108,::ffff:c0a8:0/112' -e 'DOT_VERBOSITY'='1' -e 'DOT_VERBOSITY_DETAILS'='0' -e 'DOT_VALIDATION_LOGLEVEL'='0' -e 'DOT_CACHING'='on' -e 'DOT_IPV6'='off' -e 'BLOCK_MALICIOUS'='on' -e 'BLOCK_SURVEILLANCE'='off' -e 'BLOCK_ADS'='off' -e 'UNBLOCK'='' -e 'DNS_UPDATE_PERIOD'='24h' -e 'DNS_ADDRESS'='10.255.255.3' -e 'DNS_KEEP_NAMESERVER'='on' -e 'HTTPPROXY'='on' -e 'HTTPPROXY_LOG'='off' -e 'HTTPPROXY_STEALTH'='off' -e 'SHADOWSOCKS'='off' -e 'SHADOWSOCKS_LOG'='off' -e ':8388'=':8388' -e 'SHADOWSOCKS_CIPHER'='chacha20-ietf-poly1305' -e 'HEALTH_SERVER_ADDRESS'='127.0.0.1:9999' -e 'HEALTH_TARGET_ADDRESS'='github.com:443' -e 'HEALTH_VPN_DURATION_INITIAL'='6s' -e 'HEALTH_VPN_DURATION_ADDITION'='5s' -e 'UPDATER_PERIOD'='0' -e 'PUBLICIP_FILE'='/gluetun/ip' -e 'PUBLICIP_PERIOD'='12h' -e 'VERSION_INFORMATION'='on' -e 'HTTP_CONTROL_SERVER_LOG'='on' -e 'PUID'='1000' -e 'PGID'='1000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8000]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/qdm12/gluetun/master/doc/logo_256.png' -p '8888:8888/tcp' -p '8000:8000/tcp' -v '/mnt/user/appdata/gluetun':'/gluetun':'rw' --cap-add=NET_ADMIN --restart always 'qmcgaw/gluetun' I get the following in my logs: 023-05-30T18:35:28+02:00 WARN [dns over tls] cannot update files: Get "https://www.internic.net/domain/named.root": context deadline exceeded (Client.Timeout exceeded while awaiting headers) 2023-05-30T18:35:28+02:00 INFO [dns over tls] attempting restart in 40s 2023-05-30T18:35:39+02:00 INFO [healthcheck] program has been unhealthy for 26s: restarting VPN (see https://github.com/qdm12/gluetun/wiki/Healthcheck) 2023-05-30T18:35:39+02:00 INFO [vpn] stopping 2023-05-30T18:35:39+02:00 INFO [vpn] starting and the HTTP proxy does does not work on port 8888 as I expected it to. I had expected to put in the endpoint arn-159-wg.whiskergalaxy.com:65142 somewhere but perhaps not needed? What else may be wrong....

Thanks for the tips about IPMI and USB - I have ordered a UPS and now I know where to plug in the monitoring!

I can report that I am successfully running UnRAID with the Asus Pro WS W680-ACE, a "Raptorlake" CPU and this Crucial memory (2 x 32GB DDR5 ECC sticks at 4800) for weeks. I am using the four SATA connectors on the motherboard as well as the four additional ones available through a "slim SAS" connector (I ordered this cable from Amazon that seem to be ok quality). I have not managed to detect any other temperatures than the CPU, acpitz and my nvme-pci-0400 with the temperature plugin. As cache I use Kingston DC1500M U.2 Enterprise 2,5'' SSD (using this adaptercard) .I have not yet had time to test the IPMI card but that is on my to-do list - not sure if it will provide any options for more advanced management of the hardware from UnRAID (the IPMI plug-ins I have seen seem to only target specific motherboard brands and not ASUS)...

I have now run like 60% of the parity check and there seem to be no more errors discovered in addition to the 513 that was found in the first 8% of the array. My array consists of a 3 "enterprise grade" disks (20TB parity, 20 TB data and 10TB data) and 3 smaller and older "consumer grade" disks that remain from when I first tried out UnRAID (3TB and 2x2TB) that do not contain any data (I moved what little was on them to the new drives a long time ago and the new ones have not filled up enough to start using the small disks since). Assuming no more parity errors are found I feel quite sure one or more of these old drives (that I probably should have removed when adding the new much larger disks) are to be blamed for the parity errors. As they add relatively little capacity to the array and seem likely to cause these serious problems I am planning to remove them from the array. Given that I have not selected "correct parity" in the check I have ongoing what is the best way to do this operation? As I have backups for all critical data I am thinking of risking to go the "new configuration route" (leaves a window of about 36 hours I do not have parity protection for the array and may have to go through restoring backups if I have a failure) and let that build new parity. Any suggestions for a faster/safer/better procedure are appreciated!

I disabled all containers and VMs (to avoid more writes until I have done some more tests) and let the test continue running. Late at night I started receiving a lot of messages like this in the syslog (possibly when "mover" run). Seems strange with memory allocation error as the box has 64GB memory so must be out of a size limited pool.... May 20 23:50:22 NAS nginx: 2023/05/20 23:50:22 [error] 6892#6892: nchan: Out of shared memory while allocating message of size 9059. Increase nchan_max_reserved_memory. May 20 23:50:22 NAS nginx: 2023/05/20 23:50:22 [error] 6892#6892: *274131 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" May 20 23:50:22 NAS nginx: 2023/05/20 23:50:22 [error] 6892#6892: MEMSTORE:00: can't create shared message for channel /devices May 20 23:50:22 NAS nginx: 2023/05/20 23:50:22 [crit] 6892#6892: ngx_slab_alloc() failed: no memory May 20 23:50:22 NAS nginx: 2023/05/20 23:50:22 [error] 6892#6892: shpool alloc failed May 20 23:50:22 NAS nginx: 2023/05/20 23:50:22 [error] 6892#6892: nchan: Out of shared memory while allocating message of size 277. Increase nchan_max_reserved_memory. May 20 23:50:22 NAS nginx: 2023/05/20 23:50:22 [error] 6892#6892: *274140 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/update1?buffer_length=1 HTTP/1.1", host: "localhost" May 20 23:50:22 NAS nginx: 2023/05/20 23:50:22 [error] 6892#6892: MEMSTORE:00: can't create shared message for channel /update1 May 20 23:50:23 NAS nginx: 2023/05/20 23:50:23 [crit] 6892#6892: ngx_slab_alloc() failed: no memory May 20 23:50:23 NAS nginx: 2023/05/20 23:50:23 [error] 6892#6892: shpool alloc failed May 20 23:50:23 NAS nginx: 2023/05/20 23:50:23 [error] 6892#6892: nchan: Out of shared memory while allocating message of size 3603. Increase nchan_max_reserved_memory. May 20 23:50:23 NAS nginx: 2023/05/20 23:50:23 [error] 6892#6892: *274142 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/var?buffer_length=1 HTTP/1.1", host: "localhost" May 20 23:50:23 NAS nginx: 2023/05/20 23:50:23 [error] 6892#6892: MEMSTORE:00: can't create shared message for channel /var May 20 23:50:23 NAS nginx: 2023/05/20 23:50:23 [crit] 6892#6892: ngx_slab_alloc() failed: no memory May 20 23:50:23 NAS nginx: 2023/05/20 23:50:23 [error] 6892#6892: shpool alloc failed and eventually the test was paused at about 35% (with no more errors found than at ~8% interestingly). New diagnostics included if anybody can have a look. Have now restarted the parity check to see if more errors are encountered all over the disks or if the "only" ones are the initialt ~500... nas-diagnostics-20230521-0645.zip

I have recently replaced my motherboard & CPU of my UnRAID server with a new one and after this I wanted to test if parity was ok but contrary to what I expected/hoped I have already got over 500 errors in under 10% of test done. Now it was sadly a few months ago I did the last test so cant say for sure if the problem is with the new hardware or existed also before the switch (lets call it a learning for next hardware change to do one just before). I have not specified to have the errors corrected to be able to investigate better if this type of problem would occur. With the new hardware I initially had some problems to get UnRAID to start properly so had to do a few unclean shutdowns but I do not think data was written at those times (as the system most likely did not start the array). The new motherboard has ECC memory and I did run memory test for a number of hours without any errors before testing it with UnRAID. I also tried installing Linux on an SSD that I conneted in turn to each of the six SATA channels I use for UnRAID (2 are regular separate SATA and four go thorugh a "slim SAS cable with 4 SATA connectors in the other end) and they did at least work reliably enough to seemingly run Linux without any errors. For what it is worth here are the diagnostics. What would be the best action to take in this situation. Run some diag nas-diagnostics-20230520-2051.zip

I temporarily added a video card (in addition to the built in one on the CPU) and then I got to the console and UnRAID also booted as it should again in normal mode. I then did a fresh backup of the flash drive just in case and removed the video card again and then it still boots as it should so cant reproduce the problem. Lets hope it was a one-time thing that will not come back and haunt me again 🙂 Thanks for the help anyhow!

Yes BIOS show normal message to enter it by pressing del but then screen goes blank. No complaint that OS image is not bootable so assume UnRaid boot start but hang or console directed "elsewhere" (or both eventually as machine do not reach DHCP and get an IP as before).... Does UnRaid boot if it for some reason finds no graphics board/chip (headless)?

I have a monitor connected and could see the menu choices before I encountered this problem. Now nothing is displayed when UnRaid boot starts.

But I dont get to the menu (or at least cant see it as the terminal screen is all black)....

I rebuilt my UnRAID system a few days ago with a new CPU/MOBO and it have worked perfectly until I tried enabling CPUs Quick Sync (just downloaded a plugin that did this as well as another plugin that provided a dashboard information about GPU) with the intention of later trying it with Plex and for a completely different reason had to restart the server. I initiated this cleanly from the web console but after this I cant connect over HTTP and the native machine console does not show anything even during UnRAID boot (maybe a natural consequence of enabling GPU that I was not aware of or the system crashed/hang during boot) 😞 Is there a way to force UnRAID into "safe boot" (or perhaps enable a serial console or in some other way debug the problem) in this situation or do I have to rebuild a new USB stick (my backup is quite old so would preferably like to avoid that)?

Thanks amazing advice - changed type back to qcow2 and now it works again. Is it not a bug that this is "silently" changed if you simply change the disk location?!

I have been playing with a VM with Home Assistant for a few days where it has worked great. Now I realized I have located the VM primary file on a share with backup=yes rather than in the domains share and thought I could fix this by: Stopping the VM Moving the directory with the qcov2 file to domains Edit the VM to specify the new primary disk location (under domains) of the qcov2 file. Start the VM again. but sadly the VM do not boot any longer and when I go to the console is just shows "mapping table..." and a "press ESC in one second ..." text rather than booting and no network interfaces are displayed on the VM main page. I even tried moving the directory back and changing the VM definition back but with the same result i.e. still no boot 😞 I tried running "qemu-img check" on the image and this did not find any errors. May I still somehow have destroyed the VM just by moving it or what may have happened? Any tips on things to try?

Sorry for net being very clear - I use a container with privproxy and it accepts OpenVPN config files from any VPN provider like PIA, NordVPN etc. and as I mentioned it actually work (passes all leakage tests I have tried etc) so is ok from a privacy point of view but for some reason I see the mentioned latency problem when looking up new web pages and I assume the reason is some setup problem on my side and was hoping osmebody else have seen a similar problem and solved it or have some ideas how I can diagnose it...