KoNeko

i do like graphs and lines

kinda a prtg ish something or 1 of the other tools.

you parity Disk needs to be the same or Bigger than your biggest data disk. So the 6 TB is good. So with 1 parity 1 disk may fail and you in theory still keeps all data. if you get more disks you might think about a second party disk. Many ppl say 1 parity till 20 disks works ok.

Ok great its Fixed now

i let the drive finsch it's check and that is done. now im doing the preparing to test. i put the array in maintenance mode and check the disk but i dont see the button check. It was a XFS before like all hdd's

ok did all steps it does say now Unraid Disk 2 error: 07-09-2020 20:56 Warning - Disk 2, drive not ready, content being reconstructed WDC_WD120EDAZ-11F3RA0_8CKZESUF (sdf) but it says unmountable. Is there a big difference in stopping now and do the filessystem check or do it later after the rebuild is done ? How do i do the filesystem check ?

Not totally sure. but i might have switched the parity and disk 2. and did start the array. Its now stopped. thanekos-diagnostics-20200907-1829.zip

i replaced my USB stick after it was unmounted in unraid. After starting up and replacing the key. i needed to assign all hdd's again. Might have mixed 2-3 hdd's up in the order because it says on 1 hdd Unmountable: No file system. i have 3x 12 tbs 1 parity and 2 data 12 tb and others are 3 and 8 the 8 tb is on the same spot again and the 2x3 are also i think. how can i fix this spot without losing the data? it says format to give it a file system.

i did use the previous apps section. i found the file with some settings and did it manually

1 of the docker settings got messed up and failed to update etc so it was removed when i readd it all settings on the docker are gone. I did a restore of yesterday and checked but still all settings of that docker are gone. i even tried the backup of the day before yesterday. Some problem.. How can i get those settings back, are they in a file or so. the files it self in the docker are still there just not the settings when you edit the image.

My switch died so i replaced it with a working old one for now. Internet and all is up again but i cant access my unraid server by host nor IP. i dont see it on my router either. Does unraid check for new network connections somehow? i also cant get video on the video ports.

Will remember that next time.

If your parity the biggest Disk in the array ? i think if the parity is not the Biggest disk i can go wrong. i might be wrong so feel free to correct me.

i gave the unraid server a kick (restart) Total size:8 TB Elapsed time:4 minutes Current position:34.4 GB (0.4 %) Estimated speed:142.1 MB/sec Estimated finish:15 hours, 34 minutes For now it seems to be better speed. So will see how it goes.

i replaced aa 3 TB for a new 8 TB. did a preclear on the 8 tb disk took some 40 hours. It passed the test. now i want to add it to my array in the place of my old 3 TB but its VERY slow. Total size:8 TB Elapsed time:18 hours, 30 minutes Current position:2.60 TB (32.5 %) Estimated speed:3.3 MB/sec Estimated finish:18 days, 17 hours, 27 minutes sometimes it goes to 20-25 MB/s but is still slow. Since i started this it also affects the total performance of the whole unraid server. any idea what it can be?

How do i use it with unraid gui?. With compose i can follow the examples to add it.

I turned on Privileged and it works for the website and bitwarden. bitwarden only on the login part it still shows the site.

/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='letsencrypt' --net='br0' --ip='192.168.1.15' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'TCP_PORT_80'='' -e 'TCP_PORT_443'='443' -e 'EMAIL'='@gmail.com' -e 'URL'='.nl' -e 'SUBDOMAINS'='www,bitwarden' -e 'ONLY_SUBDOMAINS'='false' -e 'DHLEVEL'='4096' -e 'VALIDATION'='dns' -e 'DNSPLUGIN'='transip' -e 'cap-add'='NET_ADMIN' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/appdata/letsencrypt':'/config':'rw' -v '/mnt/user/appdata/bitwarden/log/':'/log':'rw' 'linuxserver/letsencrypt' 697237b82c1fa9c198a7507d22255f87c991adebc68c08ab615127cfa14e83a2 The command finished successfully! also when i run iptables -S iptables v1.8.4 (legacy): can't initialize iptables table `filter': Permission denied (you must be root) Perhaps iptables or your kernel needs to be upgraded. or Iptables -L the passwd files says abc:x:99:100::/config:/bin/false nginx:x:100:100:nginx:/var/lib/nginx:/sbin/nologin for those 2 ids

i have setup the letsencrypt docker (soon to be a other name i was reading) with the fail2ban i got bitwarden running. i added some filters etc. but when open a terminal session on the letsencrypt docker and type iptables -L i get this error iptables v1.8.4 (legacy): can't initialize iptables table `filter': Permission denied (you must be root) Perhaps iptables or your kernel needs to be upgraded. and seeing there isnt a Sudo. in the fail2ban log 2020-08-12 21:14:50,008 fail2ban.utils [388]: ERROR 147d3985c450 -- exec: iptables -w -N f2b-bitwarden iptables -w -A f2b-bitwarden -j RETURN iptables -w -I INPUT -p tcp -j f2b-bitwarden 2020-08-12 21:14:50,008 fail2ban.utils [388]: ERROR 147d3985c450 -- stderr: "iptables v1.8.4 (legacy): can't initialize iptables table `filter': Permission denied (you must be root)" 2020-08-12 21:14:50,008 fail2ban.utils [388]: ERROR 147d3985c450 -- stderr: 'Perhaps iptables or your kernel needs to be upgraded.' 2020-08-12 21:14:50,008 fail2ban.utils [388]: ERROR 147d3985c450 -- stderr: "iptables v1.8.4 (legacy): can't initialize iptables table `filter': Permission denied (you must be root)" 2020-08-12 21:14:50,009 fail2ban.utils [388]: ERROR 147d3985c450 -- stderr: 'Perhaps iptables or your kernel needs to be upgraded.' 2020-08-12 21:14:50,009 fail2ban.utils [388]: ERROR 147d3985c450 -- stderr: "iptables v1.8.4 (legacy): can't initialize iptables table `filter': Permission denied (you must be root)" 2020-08-12 21:14:50,009 fail2ban.utils [388]: ERROR 147d3985c450 -- stderr: 'Perhaps iptables or your kernel needs to be upgraded.' 2020-08-12 21:14:50,009 fail2ban.utils [388]: ERROR 147d3985c450 -- returned 3 2020-08-12 21:14:50,009 fail2ban.actions [388]: ERROR Failed to execute ban jail 'bitwarden' action 'iptables-allports' info 'ActionInfo({'ip': 'ip.ip.ip.ip', 'family': 'inet4', 'fid': <function Actions.ActionInfo.<lambda> at 0x147d392323a0>, 'raw-ticket': <function Actions.ActionInfo.<lambda> at 0x147d39232a60>})': Error starting action Jail('bitwarden')/iptables-allports: 'Script error'

i want the same thing you have. Also i already have a domain. setting it up was very easy but that beside the point. I have it currently open to the interwebs Except for the /admin that is not avail via web only via Lan. Looking at fail2ban which is included in the letsencrypt docker if i can make that very ban happy.

This works perfectly. very nice. Using the letsencrypt docker. ip/admin works sub/domain/admin error normally im only using the IP because its internal only. But the web vault stopped working needed the https. That is only possible with the certificate. which makes the letsencrypt docker easy. I use the DNS plugin there. So only adding the bitwarden. subdomain and done it works. (When added to the DNS of the domain)

Ok thx will put it on testing as its still doing its check.

Aug 3 17:30:01 ThaNekos parity.check.tuning.php: DEBUG: -----------MONITOR start------ Aug 3 17:30:01 ThaNekos parity.check.tuning.php: DEBUG: array drives=6, hot=0, warm=0, cool=6 Aug 3 17:30:01 ThaNekos parity.check.tuning.php: DEBUG: Read-Check with all drives below temperature threshold for a Pause Aug 3 17:30:01 ThaNekos parity.check.tuning.php: DEBUG: -----------MONITOR end------- i enabled the Debug normal that is off. But i see 6 drives which is correct for the array. It doesnt check the Cache ones?

yea i just say the update and did the update.

Unraid was performing a parity check and it kept saying temp to high pause parity. But when i check the temp of the parity disk it wasnt too high. The warning temp is set at 50 C. When checked the smart it says. Current 37 during parity check and Max temp 42. So how can the parity check say temp is too high? Aug 2 12:29:46 ThaNekos kernel: Aug 2 12:30:02 ThaNekos parity.check.tuning.php: Paused Read-Check (24.2% completed) : Following drives overheated: temp temp Aug 2 12:30:02 ThaNekos kernel: mdcmd (910): nocheck PAUSE Aug 2 12:30:02 ThaNekos kernel: Aug 2 12:30:05 ThaNekos kernel: md: recovery thread: exit status: -4 Aug 2 12:34:46 ThaNekos kernel: mdcmd (911): set md_write_method 0 Aug 2 12:34:46 ThaNekos kernel: Aug 2 12:35:01 ThaNekos parity.check.tuning.php: Resumed Read-Check (24.2% completed) as drives now cooled down Aug 2 12:35:01 ThaNekos kernel: mdcmd (912): check RESUME Aug 2 12:35:01 ThaNekos kernel: Aug 2 12:35:01 ThaNekos kernel: md: recovery thread: check ... Aug 2 12:39:47 ThaNekos kernel: mdcmd (913): set md_write_method 1 Aug 2 12:39:47 ThaNekos kernel: Aug 2 12:40:03 ThaNekos parity.check.tuning.php: Paused Read-Check (24.4% completed) : Following drives overheated: temp temp Aug 2 12:40:03 ThaNekos kernel: mdcmd (914): nocheck PAUSE Aug 2 12:40:03 ThaNekos kernel: Aug 2 12:40:06 ThaNekos kernel: md: recovery thread: exit status: -4 Aug 2 12:44:47 ThaNekos kernel: mdcmd (915): set md_write_method 0 Aug 2 12:44:47 ThaNekos kernel: Aug 2 12:45:01 ThaNekos parity.check.tuning.php: Resumed Read-Check (24.4% completed) as drives now cooled down