RoninTech

/dev/sdg is now 30% remaining, up from 60%, and the original offender, /dev/sdj is at 90% up from 10%. I'll let them finish and see what the extended tests say.

So neither of the drives are progressing in their smart tests and there's nothing going on with the array. WTH?? EDIT: I've taken the array offline just to see if that helps the tests move along.

So should I have taken the array offline to do this?

Is it my main CPU that runs the self-test or an embedded controller on the drive itself? I kicked off another extended test yesterday on /dev/sdg for which the smartctl output said it should take 587 mins. It is still running almost 24 hours later and says: The original "bad" drive is also still running its test.

Almost 24 hours later and it is still running the test.

I'm positive I pushed the "SMART extended self-test" START button. If/when it finishes, how will I know it's done? Inside the SMART report dump is a line that reads: Its read this for about 3 hours but hopefully this means that the extended test is still running?

Thanks JorgeB. I can now communicate with the bad disk 7 after rebooting. Here are my new diags. Hopefully just a SAS card blip? I used to get more of these years ago but the newer kernels/drivers drastically reduced their occurrence. unraid-diagnostics-20210728-1149.zip

I've attached the diagnostics and am wondering what next? Unfortunately I am a thousand km's away from the machine. Can I just try a reboot and see what happens or do I need to disable all dockers and not do any more writes until I can physically check cables and/or replace the drive? The machine has been running solidly for years. Thanks unraid-diagnostics-20210727-1312.zip

There's a new version of videosort that supports Python3. It fixes the post-processing error I've been getting from videosort.py due to the Python2 deprecation. "git clone https://github.com/nzbget/VideoSort" and then recursively copy the contents to your nzbget scripts folder.

FTL wasn't working either for me which was fixed by writing to the port file. SHIFT+F5 in Brave fixed the display problem for me.

Had to clear my browser cache for the pi-hole and "echo 4711 > /var/run/pihole-FTL.port" in the pi-hole docker console.

Pi-hole was working great with version 5.0. I just updated to version 5.1 and now I see this permanently on the dashboard. Anyone else seeing this? Ad-blocking appears to still be working, so the issue is just a reporting one vs. core functionality.

So I don't have to worry about write cycles? If I've got pre and post active share logging covered and don't have to worry about flash writes I'm happy. Unless I've missed something. 🙂

I've enabled a syslog server on my unraid box in appdata and set the "remote" syslog server to 127.0.0.1. I'm hoping to store the syslog around reset issues I'm having which get lost from the ramdisk syslog. I'm aware that any logging before the appdata share is active won't be in my syslog server but hoping it still should be in /var/logs (until it resets). Goal is to use /var/log for boot problems and appdata logs for reset issues. Does this make sense or have I missed something? Thanks!

Cool. Backup was from when running so If it's not unexpected it's all good. Thanks for the help Jon.

All sorted by Tom. Makes me feel old... P.S. I see a parity check was started. Is that normal when replacing USB sticks?

I think they must match and it isn't blacklisted as I've been using it for 10 years. I'm assuming I'd get an error otherwise?

Thanks, I just received a reply from Jon asking who I was in relation to the name registered with the old USB sticks GUID. Me and a buddy split the cost of the 2 license deal over 10 years ago. Waiting to hear back. I'm guessing the error was due to me putting in an email that didn't match the email of my buddy who actually purchased the 2 sticks (and I paid him half for the second one). If this 10 year old license key wasn't added to their DB I'm guessing I couldn't have been happily running it for a decade? Glad I found this out now vs. when a stick died as I'd be dead in the water. 😮

Hi, I'm trying to replace an old Unraid 1GB USB stick I received from Limetech years ago with a new bigger one. Found the guide and followed the instructions. When I hit Replace Key and enter my email, I get the following error (I starred out the GUID's as I'm not sure if they could be used by someone): I'm confused as the old USB stick works fine, it's just running out of space. The fact its been booting my 20 disk Unraid server fine for years tells me the GUID must be registered correctly. Also, the "Registered GUID" from the first screenshot below matches the "not found as a registered GUID" from the error screenshot. Anyone have any ideas? I've also sent a message to Limetech via the Contact page with the actual GUID's in question. Thanks

Thanks squid. Turns out it was the "-it" options. Now the docker starts as expected. I also was able to hook it up to cron via the docker run command. My last issue I need to work out is how can I permanently add my python parser and init script into this other person's docker container? I see there is a "docker cp" but I don't think that is persistent. Currently I am manually adding these 2 files to the docker startup location /mnt/user/appdata/invtrack which seems a bit mickey mouse.

Hi all, I've had an Unraid cron python script (invtrack - investment tracker) running for about a year that scrapes some web info every day, puts it into a dockered Influxdb and makes it accessible via a dockered Grafana. All of this has been working great within Unraid. Recently the website I am scraping battened down the hatches to obfuscated JavaScript dynamic content. This meant I had to migrate my python parser to use Selenium that requires a browser installation. I found an existing python/selenium/chrome docker here: https://hub.docker.com/r/joyzoursky/python-chromedriver To get it working at first I simply created a /mnt/user/appdata/invtrack folder, put my python scraper script in it, then ran the docker run command they suggest (slightly modified for TZ etc.) from the new folder: docker run --name scraper -e TZ="America/Tijuana" -e HOST_OS="Unraid" -it -v $(pwd):/usr/workspace joyzoursky/python-chromedriver:3.7-selenium bash I can then run my Selenium updated python scraper and everything works as intended. That being said there are some obvious weaknesses to not having been added to the Unraid docker page correctly. The Unraid docker page entry for the scraper does not allow me to edit/update the docker. Hitting the "update ready" link for the docker doesn't work. My Python scraper has to be manually moved to /mnt/user/appdata/invtrack, it's not part of the docker image. I have to manually execute an init script when the docker starts to setup some python dependencies for my scraper. I have to setup a daily Unraid cron job to kick the scraper inside the docker. I enabled docker hub searches in Unraid's Community Apps and found and downloaded "python chromedriver". I then edited the docker parameters as shown in the attached image. When I attempt to start the docker with network set to host I get nothing in the logs. If I set it to bridge I see the following (2 start attempts) but the docker does not come up. Interestingly when I got this docker working outside of Community Apps by just doing the above docker run command, the Unraid docker page shows it as having a "default" network which isn't an option when I add it through Community apps.: Mar 19 22:04:09 unraid kernel: vethef16f86: renamed from eth0 Mar 19 22:04:09 unraid kernel: docker0: port 7(vetha506275) entered disabled state Mar 19 22:04:09 unraid kernel: docker0: port 7(vetha506275) entered disabled state Mar 19 22:04:09 unraid kernel: device vetha506275 left promiscuous mode Mar 19 22:04:09 unraid kernel: docker0: port 7(vetha506275) entered disabled state Mar 19 22:08:15 unraid kernel: docker0: port 7(veth5e15951) entered blocking state Mar 19 22:08:15 unraid kernel: docker0: port 7(veth5e15951) entered disabled state Mar 19 22:08:15 unraid kernel: device veth5e15951 entered promiscuous mode Mar 19 22:08:15 unraid kernel: IPv6: ADDRCONF(NETDEV_UP): veth5e15951: link is not ready Mar 19 22:08:17 unraid kernel: eth0: renamed from veth247fa63 Mar 19 22:08:17 unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5e15951: link becomes ready Mar 19 22:08:17 unraid kernel: docker0: port 7(veth5e15951) entered blocking state Mar 19 22:08:17 unraid kernel: docker0: port 7(veth5e15951) entered forwarding state Mar 19 22:08:18 unraid kernel: veth247fa63: renamed from eth0 Mar 19 22:08:18 unraid kernel: docker0: port 7(veth5e15951) entered disabled state Mar 19 22:08:18 unraid kernel: docker0: port 7(veth5e15951) entered disabled state Mar 19 22:08:18 unraid kernel: device veth5e15951 left promiscuous mode Mar 19 22:08:18 unraid kernel: docker0: port 7(veth5e15951) entered disabled state Mar 19 22:08:30 unraid kernel: docker0: port 7(veth7c2c127) entered blocking state Mar 19 22:08:30 unraid kernel: docker0: port 7(veth7c2c127) entered disabled state Mar 19 22:08:30 unraid kernel: device veth7c2c127 entered promiscuous mode Mar 19 22:08:30 unraid kernel: IPv6: ADDRCONF(NETDEV_UP): veth7c2c127: link is not ready Mar 19 22:08:30 unraid kernel: docker0: port 7(veth7c2c127) entered blocking state Mar 19 22:08:30 unraid kernel: docker0: port 7(veth7c2c127) entered forwarding state Mar 19 22:08:30 unraid kernel: docker0: port 7(veth7c2c127) entered disabled state Mar 19 22:08:33 unraid kernel: eth0: renamed from veth7af64bb Mar 19 22:08:33 unraid kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7c2c127: link becomes ready Mar 19 22:08:33 unraid kernel: docker0: port 7(veth7c2c127) entered blocking state Mar 19 22:08:33 unraid kernel: docker0: port 7(veth7c2c127) entered forwarding state Mar 19 22:08:33 unraid kernel: veth7af64bb: renamed from eth0 Mar 19 22:08:33 unraid kernel: docker0: port 7(veth7c2c127) entered disabled state Mar 19 22:08:34 unraid kernel: docker0: port 7(veth7c2c127) entered disabled state Mar 19 22:08:34 unraid kernel: device veth7c2c127 left promiscuous mode Mar 19 22:08:34 unraid kernel: docker0: port 7(veth7c2c127) entered disabled state So I'm looking for some feedback on any potential errors I've made in adding the docker via Community Apps that are causing the docker to not start. Would also appreciate any tips on how to kick a script inside my docker once it is running, and how to run a setup script (to pip python modules) inside a docker on startup. Thanks, and apologies if this is in the wrong place or has wrong/missing info. I will correct them as soon as I am aware. 😃

OK, I didn't see anywhere to change the new 4TB drive to XFS after doing a new config so I started it and now it's doing a parity rebuild and shows the drive as reiserfs. When the parity is done (assuming I can't stop it?), how do I convert the new empty 4TB drive to XFS?

Thanks Trurl! I've never done a new config before. Once the 1TB disk is empty, do I power down, remove it, replace it with the 4TB, power up, stop the array and then use New Config to format the new 4TB slot to XFS? Finally rebuild parity so the new empty 4TB XFS drive is covered? Does that sound right?

I have read but I think I'm maybe between documented scenarios. ? I have no spare slots to play with but I have a 1TB drive I'd like to get rid of. I'm currently using the unbalance plugin to get everything off this 1TB drive. After that I have a 4TB drive (largest size) I'd like to swap for the 1TB that I'll use as the starting swap disk for FRS to XFS conversion. Monthly parity finished this morning so all is good, dockers disabled so array should be static unbalance everything off the 1TB drive remove the 1TB drive add the 4TB drive formatted as XFS follow the File System Conversion FAQ steps I'm not sure what I need to do for steps 3 and 4 as far as parity checking and Tools->New Config, if anything? I'm hoping I don't have to do an extra parity check somewhere in there to swap out the 1TB drive.

Thank you for this plugin! Is there a way to access a "Run Script" button via a URL? Would love to add links on our phones that we can trigger with a single press rather than opening a browser, going to the user scripts page and then pressing one.