mattekure

what is the recommended filesys for pool devices? Should I convert over to btrfs?

Phase 1 - find and verify superblock... - block cache size set to 3079832 entries Phase 2 - using internal log - zero log... zero_log: head block 167005 tail block 167005 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 3 - agno = 1 clearing reflink flag on inode 874966336 clearing reflink flag on inode 874966387 clearing reflink flag on inode 874967432 clearing reflink flag on inode 874967441 clearing reflink flag on inode 875203506 clearing reflink flag on inode 537434009 clearing reflink flag on inode 456271 clearing reflink flag on inode 268699468 clearing reflink flag on inode 268699472 clearing reflink flag on inode 537434010 clearing reflink flag on inode 268699473 clearing reflink flag on inode 456272 clearing reflink flag on inode 268699476 clearing reflink flag on inode 456273 clearing reflink flag on inode 268699485 clearing reflink flag on inode 456275 clearing reflink flag on inode 456276 clearing reflink flag on inode 537607433 clearing reflink flag on inode 456277 clearing reflink flag on inode 268699490 clearing reflink flag on inode 268699491 clearing reflink flag on inode 268699492 clearing reflink flag on inode 268699493 clearing reflink flag on inode 268699494 clearing reflink flag on inode 456278 clearing reflink flag on inode 456280 clearing reflink flag on inode 456281 clearing reflink flag on inode 537607440 clearing reflink flag on inode 537607441 clearing reflink flag on inode 537607446 clearing reflink flag on inode 537607450 clearing reflink flag on inode 537607452 clearing reflink flag on inode 537607453 clearing reflink flag on inode 537607454 clearing reflink flag on inode 537607455 clearing reflink flag on inode 537607458 clearing reflink flag on inode 537607460 clearing reflink flag on inode 537607463 clearing reflink flag on inode 537607465 clearing reflink flag on inode 537607466 clearing reflink flag on inode 537611395 clearing reflink flag on inode 537611404 clearing reflink flag on inode 537611405 clearing reflink flag on inode 537611411 clearing reflink flag on inode 537611454 clearing reflink flag on inode 537612072 clearing reflink flag on inode 537612073 clearing reflink flag on inode 537612089 clearing reflink flag on inode 537612671 clearing reflink flag on inode 537612993 clearing reflink flag on inode 537612994 clearing reflink flag on inode 537612995 clearing reflink flag on inode 537613001 clearing reflink flag on inode 537613003 clearing reflink flag on inode 537613006 clearing reflink flag on inode 537613007 clearing reflink flag on inode 537613008 clearing reflink flag on inode 537613009 clearing reflink flag on inode 537613011 clearing reflink flag on inode 537613012 clearing reflink flag on inode 537613014 clearing reflink flag on inode 537613015 clearing reflink flag on inode 537613017 clearing reflink flag on inode 537613019 clearing reflink flag on inode 537613020 clearing reflink flag on inode 537613021 clearing reflink flag on inode 537613022 clearing reflink flag on inode 537613024 clearing reflink flag on inode 537613025 clearing reflink flag on inode 537613026 clearing reflink flag on inode 537613027 clearing reflink flag on inode 537613028 clearing reflink flag on inode 537613029 clearing reflink flag on inode 537613030 clearing reflink flag on inode 537613031 clearing reflink flag on inode 537613032 clearing reflink flag on inode 537613033 clearing reflink flag on inode 537613034 clearing reflink flag on inode 537613035 clearing reflink flag on inode 537613036 clearing reflink flag on inode 537613037 clearing reflink flag on inode 537613038 clearing reflink flag on inode 537613039 clearing reflink flag on inode 537613040 clearing reflink flag on inode 537613041 clearing reflink flag on inode 537613042 clearing reflink flag on inode 537613043 clearing reflink flag on inode 537613044 clearing reflink flag on inode 537613045 clearing reflink flag on inode 537613046 clearing reflink flag on inode 537613050 clearing reflink flag on inode 537613051 clearing reflink flag on inode 537613052 clearing reflink flag on inode 537613053 clearing reflink flag on inode 537613054 clearing reflink flag on inode 537613055 clearing reflink flag on inode 537615872 clearing reflink flag on inode 537615874 clearing reflink flag on inode 537615881 clearing reflink flag on inode 537615883 clearing reflink flag on inode 537615887 clearing reflink flag on inode 537615891 clearing reflink flag on inode 537615899 clearing reflink flag on inode 537615900 clearing reflink flag on inode 537615903 clearing reflink flag on inode 537615905 clearing reflink flag on inode 537615909 clearing reflink flag on inode 537615913 clearing reflink flag on inode 537615914 clearing reflink flag on inode 537615917 clearing reflink flag on inode 537615918 clearing reflink flag on inode 537615921 clearing reflink flag on inode 537615923 clearing reflink flag on inode 275214333 clearing reflink flag on inode 537615925 clearing reflink flag on inode 537615926 clearing reflink flag on inode 11514136 clearing reflink flag on inode 537615929 clearing reflink flag on inode 537615932 clearing reflink flag on inode 537615933 clearing reflink flag on inode 537615934 clearing reflink flag on inode 537615935 clearing reflink flag on inode 537643906 clearing reflink flag on inode 537643907 clearing reflink flag on inode 537643910 clearing reflink flag on inode 537643911 clearing reflink flag on inode 537643912 clearing reflink flag on inode 537643913 clearing reflink flag on inode 537643914 clearing reflink flag on inode 537643915 clearing reflink flag on inode 537643917 clearing reflink flag on inode 537643918 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... XFS_REPAIR Summary Sun May 22 08:46:33 2022 Phase Start End Duration Phase 1: 05/22 08:46:30 05/22 08:46:30 Phase 2: 05/22 08:46:30 05/22 08:46:30 Phase 3: 05/22 08:46:30 05/22 08:46:32 2 seconds Phase 4: 05/22 08:46:32 05/22 08:46:32 Phase 5: 05/22 08:46:32 05/22 08:46:32 Phase 6: 05/22 08:46:32 05/22 08:46:33 1 second Phase 7: 05/22 08:46:33 05/22 08:46:33 Total run time: 3 seconds done

ok. had to wait for the parity check to finish. running the xfs_repair -nv I get the following. Phase 1 - find and verify superblock... - block cache size set to 3079832 entries Phase 2 - using internal log - zero log... zero_log: head block 32959 tail block 32959 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 3 - agno = 2 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Sun May 22 08:25:41 2022 Phase Start End Duration Phase 1: 05/22 08:25:37 05/22 08:25:37 Phase 2: 05/22 08:25:37 05/22 08:25:37 Phase 3: 05/22 08:25:37 05/22 08:25:39 2 seconds Phase 4: 05/22 08:25:39 05/22 08:25:39 Phase 5: Skipped Phase 6: 05/22 08:25:39 05/22 08:25:41 2 seconds Phase 7: 05/22 08:25:41 05/22 08:25:41 Total run time: 4 seconds

Thanks much

Something crashed and now a bunch of my shares are missing. The logs are filled with this. May 21 17:20:01 Tower kernel: blk_update_request: I/O error, dev loop2, sector 1230432 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 May 21 17:20:01 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 55, rd 5410, flush 0, corrupt 0, gen 0 May 21 17:20:01 Tower kernel: blk_update_request: I/O error, dev loop2, sector 3327584 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0 May 21 17:20:01 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 55, rd 5411, flush 0, corrupt 0, gen 0 Any clue what happend? tower-diagnostics-20220521-1720.zip

LOL, No, but that did it. Thank you!!!

Since updating to v6.10, Everytime I try to connect to a running VM I get the following error. Diagnostics attached. tower-diagnostics-20220518-1544.zip

I just had my first big HW component failure. I came into my home office and smelled burnt electronics, and discovered my Unraid servers power supply was starting to smell. Luckily it doesnt appear any data is lost or anything, and no damage to any other componenets that I could see. I will see on Thur when the new power supply arrives. I've replaced hard drives now and then, but this is the first extended outage I've had with Unraid since I purchased it years ago.

I am having an issue getting Privoxy to work with this container. I currently have 3 of your docker containers set up, and 2 of them work just fine, including the privoxy. They are all set up the same for VPN connection, PIA via Wireguard. The VPN connection does work and connects fine. the rest of the docker functions all work fine. I have the privoxyvpn and qbittorrentvpn ones working fine. But when I enable privoxy in the sabnzbdvpn docker, I get get this endless stream in the logs. Is there anything else I can test/check to see why privoxy wont start with just this one? In an attempt to get it to work I even deleted the docker and the template, to download a brand new fresh copy, but it didnt help. redacted debug enabled log attached supervisord.log

So far I am loving it. I got it integrated into my Ultimate UNRAID dashboard. and it all seems to be running smoothly. Thanks for making it.

I attempted to install this. During the install the influxdb username and password fields could not be left blank, they required information to be added, which caused my authentication with influxdb to fail. To complete the install I ended up deleting those two variables and recreating them, so they could be left blank.

Well, the dashboard informed me of one thing I wasnt previously aware of. I have an older SSD thats been in my server for years. Its not doing much now, but its gone WAAAY beyond its expected life used. The manufacturer reports a TBW of 150TB

For the SSD stats, I had to go in and tweak some of the settings. I have a Samsung SSD 860 EVO. In the SSD Life Used query, I determined that the query WHERE name = Data_Units_Written did not work because that data was not being reported. Instead, I had to change it to WHERE name = Total_LBAs_Written and then alter the math function.

safe travels

By zooming out as far as the map would go so that the top caret was visible Then carefully mousing from the top until the mouse cursor changed to the move panel shape (looks like a + with arrows on each end. Then click once so the dropdown menu shows, then hit the e button on the keyboard.

Check out https://grafana.com/grafana/plugins/grafana-worldmap-panel At the very bottom is a section that talks about changing the default center. edit. You can change it by editing the panel. It was difficult to get the edit button to work, the hand wouldnt line up for me very well. And then scroll to the bottom of the right hand side panel configuration. There will be a section where you put in the center.

I am also using Sensors. This is how I got them showing up. temps Power fan End Result

Thanks so much for making this. I finally got it all set up and working the way I want it to. Figured out how to compensate for the non-server hardware without the api. A couple of issues I ran into along the way. Using the telegraf:latest, there were no instructions on adding lm_sensors. the apk add command doesnt work for it. But adding apt-get -y install lm-sensors did seem to work. Also, after setting up varken and the plex monitoring stuff, I noticed that two of the panel types were not included with grafana by default, so they showed an error. It was the pie chart panel and the worldmap panel plugin. They were easy to install just by going to the grafana console and typing. grafana-cli plugins install grafana-piechart-panel grafana-cli plugins install grafana-worldmap-panel Once I did that they worked just fine.

Apparently I missed the note that backups were now automated. woke up this morning with the cache drive full. All fixed now though.

I own foundry. How do I install the files for this docker? EDIT* Nevermind. it was as simple as downloading the linux version of the files, and copying them over to the appdata FoundryVTT\fvtt\ folder and restarting the docker. all running now. Thank you.

I have the draw.io docker running. And when I attempt to open an image from google drive, I am asked to authorize the app. When I do, I get the following error.

Try the cAdvisor docker. It will give you lots of info about the dockers and how much cpu, ram, disk they use.

Out of Memory errors are caused when the docker tries to use more memory than the system has. Usually its because limits were not set within the docker. The best way to prevent those is to determine for your system, how much memory the docker is safe to use and calculate that as a percentage of your total system memory. So if you have a total of 8Gb, and you feel it is safe for the BOINC docker to take up 3GB of that, you calculate 3GB/8GB = 37.5%. In boinc, go to the Options->Computing Preferences, and switch to the "Disk and Memory" tab. set that percentage in the memory section for both the in use and not in use fields. With those fields set, BOINC will limit itself to the amount of memory you have said it could use. BOINC isnt super strict though, it can fluctuate a little above the set percentage, so you may want to round down like to 35% or whatever fits your system specs.

Yeah, it totally makes sense that the work would ramp up now, not be going down. and I think our Unraid group is doing a great thing with donating the computing power.

I imagine more covid related tasks are being submitted relatively frequently.