tazman
Members
-
Joined
-
Last visited
Everything posted by tazman
-
Hi, My control page always shows an orange circle = "represents and open operation". The help text says that "For each disk the build and export state is maintained in near real-time." To test this I added a test file (text, created with nano) to a disk and waited for 18 hours for it to appear in the export hash file. But it didnt. It took a manual export for the file to be listed. What is the expected behaviour? What do the orange circles really mean? Could it be that I am wrongly configured? Thanks for sharing your wisdom! Tazman
-
Upgraded from 7.0.1 to 7.2.3 without problems
-
I have been using unRAID since 2012 and, until last year, never experienced any problems with upgrading. My first failure was shortly after the new upgrade GUI was introduced and I am also anxious to update and still stuck on 7.0.1. I welcome this discussion and would suggest not to jump to conclusions until someone actually involved in the releasing provides insights and an assessment why releases have, seemingly, become less reliable. Maybe it is due to the increasing variety of hardware, maybe because of the increasing complexity of the software. These would be harder to fix than a sloppy/rushed release process, for example.
-
I had to add a 10sec wait as the files were not there yet: # Fix NGINX limits # sed cannot find the file when executed directly, waiting for 10 secs first sleep 10 sed -i "s;zone=authlimit:1m rate=30r/m;zone=authlimit:1m rate=60r/s;g" /etc/nginx/nginx.conf sed -i "s;zone=authlimit burst=20;zone=authlimit burst=60;g" /etc/nginx/conf.d/locations.conf /usr/sbin/nginx -s reload
-
Upgraded from 6.12.14 to 7.0.0 with 1.0 patches without problems.
-
Thanks, bringing up SSDs is a great point. They might be way more reliable than initially estimated.
-
Dear unRAID community, This is a commemorative post, I hope you find it insightful. My last 2TB drive had raw read errors three days ago and I decided to retire it. It is the last disk I started unRAID with in 2012. It bought it on 6 August 2010, so it dies just short its 14th birthday It had 9years, 4 months of power-on hours The drive holds the clear record among my drives regarding longevity. It's a Western Digital purple WDC_WD20EVDS-63T3B0. I only had one other purple. The other one also turned out to be very long lasting. What are your longest lasting drives? Best, tazman
-
Upgrade from 6.10.12 worked without issues
-
Thanks for that. No, I didnt clear. Trying right now.
-
After I upgraded my desktop to Windows 11 I started to notice those error messages in the log: Jun 3 21:46:43 SS nginx: 2024/06/03 21:46:43 [error] 13437#13437: *32614 limiting requests, excess: 20.615 by zone "authlimit", client: 192.168.1.9, server: , request: "PROPFIND /login HTTP/1.1", host: "192.168.1.6" I was getting 16-17 of those error messages per second. Too many and the GUI (that nginx is running) will respond with a 503 and the server needs to be rebooted. It turned out that they are caused by my file synchronization software Syncovery that backs-up data from the desktop to the unraid server. The developer of Syncovery confirmed that Syncovery uses SMB and does not execute any PROPFINDs, which is WebDAV. So it seems as if Windows 11 is mixing SMB and WebDAV somehow. There are also many reports about that error by others recently. Instead of fixing Windows 11 I was looking for a way to increase the rate limit. It worked and I am not getting these errors anymore since 3 days. See general information here for what is going on: https://blog.nginx.org/blog/rate-limiting-nginx . Limits are set per client (ie. IP) To increase the limit: open the nginx config file at /etc/nginx/nginx.conf Look for the request limiting config statement: limit_req_zone $binary_remote_addr zone=authlimit:1m rate=30r/m; 1m: size of the shared memory zone: 1m is big enough to keep information for about 16,000 IP addresses rate=30r/m: limits requests to 30 requests per minute Increase the rate (r) per time (m=minute) e.g. to 60r/s (s=second) (=120x) "nginx -t" to test the configuration "nginx -s reload" to restart with the new configuration see: https://nginx.org/en/docs/beginners_guide.html Note: nginx.conf only defines the limit. The ./conf.d/locations.conf applies the limit with the command: limit_req zone=authlimit burst=20 nodelay; This means that 20 more requests can be accepted and are queued without delay to be processed within the limit set by the rate. I did not change this. I have increased the limit to 60r/s (120x) and the error messages stopped. Unfortunately, the changes to the config file do not persist a reboot. Hence this report. @limetech Tom, could you suggest a way to make those changes stick or provide other means to customize the rate or increase the rate e.g. to 60r/s or even higher in one of the next releases? Any suggestion for an interim fix? Ie. run a script at startup that overwrites and reloads the patched nginx.conf? When/how to run this best? Thanks, Tom
-
My exclusions do not work. I have set: Excluded folders: .Trash-99 .incoming Data_Shadow Documents_Shadow Public Stickware .Recycle.Bin .cache Excluded files: *.nfo , metadata.db But still get: BLAKE3 hash key mismatch (updated), /mnt/disk7/Books/Calibre/.cache/calibre/server-log.txt was modified BLAKE3 hash key mismatch (updated), /mnt/disk7/Books/Calibre/metadata.db was modified Any idea how to fix that? Thanks!
-
Thanks, JorgeB!
-
Thanks, so is the assumption that the segfault destabilized the system, causing the write error on the second drive and the stalling of the rebuild? So it's basically bad luck?
-
I rebooted. No events logged in the bios, memtest passed. The first rebuild completed at the usual speeds. The second is running now. Another dual failure hopefully averted. I have 22 data disks which is stretching it. I am really waiting for the multiple-arrays to be ready in Unraid 7.
-
Hi, My disk 15 got disabled, so I started a rebuild. The rebuild is stuck at 1.8% and does not progress. Probably at the same time, disk 12 got write errors and also got disabled. I tried to pause, then cancel the rebuild to use another drive to rebuild to, but the commands do not do anything. The GUI is responsive but the CPU Meter on Dashboard does not repaint. The log does not show anything new since 45min. With the following two errors at the end: Jun 1 15:46:40 SS emhttpd: error: hotplug_devices, 1709: No such file or directory (2): tagged device WDC_WD40EFAX-68JH4N1_WD-WX22DC1RNJP0 was (sds) is now (sdah) ... Jun 1 15:46:40 SS kernel: emhttpd[9837]: segfault at 67c ip 0000000000418359 sp 00007fff0d396560 error 4 in emhttpd[404000+1a4000] likely on CPU 3 (core 1, socket 0) Disk 12 is NJP0 mentioned in the first error. Diags attached. What do you advise? Wait? Reboot and retry? Thanks! Tomss-diagnostics-20240601-1625.zip
-
Happy to report that the upgrade using Tools.Update OS worked this time. Thanks, JorgeB!
-
Thanks, JorgeB, I copied the root folder files from the 6.12.8 backup to the USB stick and ran make_bootable.bat. Server booted and it looks ok. What to do now with 6.12.9? Should I try the upgrade again from the GUI or is there a better way? USB Tool is the Creator from here? https://unraid.net/getting-started
-
Update from 6.12.8 failed. The USB stick will not boot anymore. First time I used the new update dialog. USB stick is still readable and I was able to make a backup without read errors. Looking into this now. Tipps welcome. Thanks!
-
Just found this statement: My understanding is that the next WD release, the 24TB (Gold and U/star), will be the largest they'll be able to make in CMR format so that may indeed be the one to have in future years. Source: https://www.backblaze.com/blog/backblaze-drive-stats-for-q3-2023/ (in the comment section)
-
I tried one which immediately failed. The RMA replacement is running fine since 4 years. I have not re-considered them and stick to WD reds instead.
-
Hi, With "best" I mean: this size will be available by all providers (=competition) and has the chance of being the most cost-effective in cents/GB for the next couple of years and has a technology that is reliable and proven. When I started with unRAID back in 2011 2TB drives were the only choice. Relatively soon, 4TB drives became the standard and were the ones with the lowest cost per GB until now. I mostly use WD reds now after HGST was bought by them with some bad experiences with Seagate and Toshiba in-between. At the moment it seems that higher capacities start to challenge the 4TB prices. WD currently has an attractive Black Friday deal for their 18TB Pros. I am wondering if it is the time to swap out the drives starting with my two parity drives. But is 18TB the "right" size to adopt as the new standard? I know that unRAID does not care about drive size as long as the parities are the biggest ones. But with so many new large capacity drives that add yet another TB or two on top I don't want to constantly swap out the parity drives. So I wonder what the your opinion is about: 1. What hard disk sizes are, from a technology perspective, the most reliable ones? I always thought that doubles 2-4-8-16 would be a a logic. 2. Which disk size has the potential to become the new "lowest cost per TB" leader for the next years? I researched this but could not find any clear answers. BackBlaze thinks that the cost will come down to 1ct/GB in 2025: https://www.tomshardware.com/news/backblaze-expects-one-cent-per-gb-hdds-by-2025. They seem to use 16TB drives now but the reports says that the 1ct will be achieved by the 22/24TB drives. 24 would be doubles again. Interim sizes like 16, 18 or 20 would be shorter-lived in-betweens!? So wait for the 24TB? The prospect of parity checks/rebuilds taking 3.5 days with 24TB (my 4TB take 14 hours) scares me a bit. Overall, the WD Reds Plus 12TB seems to be the current non-deal sweet spot and every provider has 12TB drives. So is 12TB a good size to go for now? Appreciate you insights and wisdom. Thanks! Tazman
-
Dear all, I have .nfo files excluded, as they change frequently. So the Export correctly states that files are skipped: Finished - exported 216628 files, skipped 122 files. Duration: 00:01:59 Yet, upon export, the syslog is flooded with error messages like: Aug 30 17:08:47 SS bunker: error: no export of file: /mnt/disk8/Movies/Brooklyn (2015)/movie.nfo Yes, Mr. Fileintegrity, .nfos should not be exported as configured. Why do you complain about this? It was so bad that the syslog partition (standard size: 128mb) overflowed and nothing was logged anymore. Yet, unraid continued to run like a charm (!!!!). The error message is only generated for excluded files (ie. *.nfo) , not folders. Bug? Please fix! Feature? Please make it configurable! Thanks! The bigger issue at hand seems to be that files handled by Mover are not recognized as modified. Like .nfo files when they are touched by Sonar when a new episode is added. So excluding them is my attempt to prevent me getting flooded by bunker verify warnings. Now, my syslog gets flooded. Can't avoid the flood. Maybe it's global warming! Ultimately, this makes the plugin less useful as you constantly need to remember to run manual Builds and Exports. Could this be schedulable? Tazman
-
Triple Parity
-
+1. I am running 22 mostly 4TB data drives with overall 82T I also experienced dual drive failure for the second time recently. Surely a nail biting and nerve wrecking experience I do not want to go through again.
-
Hi Vr2Io, thanks, they are red when a drive is in only. The headers are clean. I just replaced the backplane with most problems (some of the slots were not working, the drives in the other two with a red middle LED are all ok) with a one from Supermicro that I had lying around and so far, the preclears are going good. I am also hanging towards your suspicion of a board failure as power and the SATA cables are working ok now. Best regards, Thomas
