b3rrytech

For anyone coming upon this post, like I did, because they wanted to rename their zpool in the webUI: I don’t know what was the correct way or not to do this 2 years ago when TS posted the original question. But today, using 7.1.14, the method @JorgeB describes is working great for renaming a zpool in the webUI. If you want to know what unRAID does under the hood when applying the name change in the UI you can run ”zpool history <pool_name>”.

That’s because the motherboard doesn’t support higher memory clock speed than 2667 MHz so it will down clock any RAM capable of higher speeds. https://www.supermicro.com/en/products/motherboard/x11sca-f Maybe this is hackable somehow, but unlikely.

Vorta GUI application for BorgBackup GitHub repository (Vorta): https://github.com/borgbase/vorta GitHub repository (containerized Vorta): https://github.com/borgbase/vorta-docker Vorta documentation: https://vorta.borgbase.com BorgBackup documentation: https://borgbackup.readthedocs.io/en/stable/ DESCRIPTION This is the support for the unRAID Docker template for Vorta, a GUI for BorgBackup. Vorta is a backup client primarily for macOS and Linux desktops. It integrates the mighty BorgBackup with your desktop environment to protect your data from disk failure, ransomware and theft. BorgBackup is originally a CLI based backup tool, so Vorta was created to lower the threshold and allow more people to use it. This containerized version of Vorta gives you access to the GUI over VNC in a browser. NOTES • There are other variables available, if needed. Check the GitHub repository to know more. • The directories needed to interact with the host and/or any external device, is located under '/' in the root of the container. • When restoring from an archive back to this host, this container needs to be run as Privileged. It is strongly (!) advised that you only do this during restores and toggle it off during normal use. • I'm not the author of this Docker container. I only provide the unRAID template. Any issues with the container and the application should be submitted to the official GitHub repository. Use the support thread in the forums for any problems with the template. If possible me, or someone else in the community also might be able to provide some guidance for usage.

Finally! Vorta back in CA. I've also created a support thread for the apps added in my repository.

Yeah I’ve PMed him in January. I thought it was something wrong with my user since I made a username change at the same time. I even started this thread because of it but…yeah, I’m starting to think it wasn’t any problem with my user account. Maybe CA shouldn’t be a one man show anymore, that might create some breathing room.

Hopefully you've already figured this out, but I'll write the answer here for future prosperity. When you want to mount the restore path you need to first stop the container and re-deploy it, but as privileged (default = off) For you others: I've said before that I'm working on getting this published in the CA. Life happened and I haven't gotten around to it. But since a while back I've been trying to get back to this and now the ball is with Squid whom manages CA. Don't know why it takes so long but I promise to update here when it's out. I believe @akmijaresalso have a template sent in too. We'll see who will be published, I'll might withdraw mine if we're both uploaded. No reason to have two templates really.

Read though the github issue and feels like it's related. Do you know why this changed when updating to 7.0.1? Was the kernel driver updated upstream? Drivers are far from my comfort zone so apologies for perhaps a bit "slow" questions.. This seemed to fix it. Rebooted and only NCT6687 loaded. root@Define7:~# lsmod | grep nct nct6687 20480 0 Thanks for the help!

Hi! Since updating to 7.0.1 from 6.12.5 I've encountered a driver issue. I've got @ich777 Nuvoton NCT6687 Driver plugin installed as that is needed for me to get sensors and pwmconfig working. For some reason after upgrading to 7.0.1 the system now loads the NCT6683 driver first and then also loads the NCT6687 from the plugin. This creates a problem as it seems to lock the /sys/class/hwmon/hwmon7/pwm* files from being modified. Thus I cannot change fan speed with my scripts. I only get "permissions denied". The solution I've found is to remove both drivers: modprobe -r nct6683 modprobe -r nct6687 Then reload the correct driver: modprobe nct6687 After that sensors, pwmconfig and my fan scripts works again. Tried blacklisting the NCT6683 driver by: echo "blacklist nct6683" >> /boot/config/modprobe.d/nct6683.conf After reboot the NCT6683 still loads as well as the NCT6687. Tried adding the blacklist and the loading of the correct driver in the go file: echo "blacklist nct6683" >> /boot/config/go echo "modprobe nct6687" >> /boot/config/go After reboot both drivers still loads. Found that /boot/config/modprobe.d seems linked with /etc/modprobe.d so made sure it looked the same in both dirs. After reboot it still loads both drivers. My system now is on a Z590 MB with an 11600 CPU. So what am I doing wrong?

OK, I've answered Thursday 06:36 PM. Is that visible to you? Sorry for nagging.

Hi! Didn't really know where this should go but since it has to do with getting a template published to CA I thought I'd try here. 😅 Looking to get in contact with @Squid. I sent you a PM and we started a conversation about getting an XML published back in january. During that time I switched username on this board and my PM's went radio silent. I think it must have something with the change to do somehow... Life happened for a few month and now I thought I'd find out... 😀 Please send me a PM and we'll see if it works so I can send some XML repo links. /b3rrytech

Support thread for applications in b3rrytech's template repository https://github.com/b3rrytech/unraid-docker-templates After using unRAID for more than a decade and change, I wanted to contribute back to this fantastic community. Value for value! NOTE: I'm not the author of these container images, so for application support you would need to visit each images own project page. Anything regarding the container templates I will do my best to support. Container templates in the repository: Coming soon™ Adaptec maxView Storage Manager (Adaptec-MSM) Template presentation: Post # Application support: GitHub Vorta (GUI application for Borg Backup) Template presentation: Forum post Application support: GitHub

Wow! That’s a nice rack What’s your use case with so many systems? Do you run them as a cluster?

Bit of a necro dive here, but since these drives are becoming more and more available as refurbed also in Europe I thought I’d chime in here in case anyone else finds this thread. @frodrI believe the performance you saw when copying to your RAIDz2 pool probably was only due to the pool configuration and maybe RAM, not a benefit of the 2X18’s possible speed unless you’ve partitioned the drives. Maybe you’ve already figured this out, if so what’s your speeds now? The SATA interface on the 2X18 aren’t able to show the two separate LUNs so it treats them like one append the other. Meaning the drive will first fill up the first LUN, then the second. The end user will only see regular drive speeds. To benefit in speed from the 2X18 SATA you need to partition the drive according to Seagates own documentation. Then you can access both parts of the drive simultaneously and effectively double your performance. If you then put them in a ZFS pool it’s wise to not add both partitions of one drive to the same VDEV. It gets a bit more tricky and you need to think it through before setting it up, especially in regards to fault tolerance and future expandability. More info here: https://forum.level1techs.com/t/how-to-zfs-on-dual-actuator-mach2-drives-from-seagate-without-worry/197067/62?page=3 (link to SATA instructions but the thread is a worthy read from the beginning)

+1 for this! This feature exist in most other services that uses smtp email solutions. I have one gmail account that I only use for notifications from my servers and services. Yes, we have the subject prefix, but it is so much better to alter the sender name (author). Thanks!

Has this release fixed the issues 6.12.6 had with Adaptec HBA cards? I’m still on 6.12.4 because of it.

Just like @itimpisays, do you mean to say that you changed the containers path mapping? Because what you describe sounds like it’s still mapped to /mnt/user.

Yes, that's correct! Maybe wrong wording on my count there. Seems as it wasn't the power cables anyway. Any take on this?

If you change from your custom Docker network to Host, do you get an IP then? I seem to remember that Plex's official container suggests running it with Host, but I'm not sure. I know other Docker images doesn't suggest it.

Backup, backup and backup. 😉 That way it's no problem if something happens.

Do you have the correct cable? There are different cables for connecting from motherboards SATA ports to a SAS-8087 backplane vs connecting SAS-8087 on an HBA card to SATA drives. They look the same, but only works one way. Example (no affiliation with these cables, nor have I tested them): SAS-8087 (host) to 4x SATA (target) 4x SATA (host) to SAS-8087 (target)

For me, the CPU ended up being faulty and Intel replaced it.

Just recapping what happened in the end. The last week it got so bad I couldn't boot anything at all, no Live-USBs or anything. So after months of trying to find the problem I finally couldn't narrow it down any more than to the MB or the CPU. Since I had so many errors that pointed to the CPU I decided to open a warranty ticket with Intel. They accepted after I presented my evidence of my problems and replaced my CPU with a new one. Very nice experience dealing with the support, and I'm glad I bought the boxed and not the trayed version of the CPU since the trayed had shorter warranty. At least for 11th gen, I think the warranty aren't differentiated in the newer generations. Now it runs good again. 👍

Thank you for your answers! It's 4-way splitters directly attached to the 6-pin output on the PSU. Original Seasonic cables. Not ideal, but not terrible either. Looks like it actually was the drive that was the problem. I think.. Restarted the server after moving the cabling around and still got multiple errors. See attached SMART report. Now, perhaps those CRC errors and Current Pending Sector errors might have been a result of the first initial problem, and now causing the drive to behave irrational. I don't know. At first it didn't show at all when connecting it over the HBA. Put it in an external USB enclosure and that made it show up but with no FS or possibility to mount. Added it back to the server and tried it with a SATA cable directly connected to the MB and that worked. Somewhat.. The drive wouldn't mount normally, and after googling the error messages from the syslog I tried mounting it RO in UD and that finally worked. Now I'm copying the 4-5TB data off the drive to an SSD. Figured that would still be faster than restoring from backup. (I really need to setup some cataloging system over what files are in what drive and keep that list somewhere, been on my mind for a long time and that would save so much time in the event of a failure.) It keeps coming more current pending sectors errors during file transfer as well. Will not re-deploy the drive again, if ever, until I've run multiple more tests. Maybe I should just call it DOA and return it. I have another of the same drive bought together with the failing one. A bit hesitant to deploy that now too. But that is also pre-cleared at least. Now, regarding the array. Would it be best now, since I've got no parity, to just not assign any drive to that spot and let it rebuild parity? Or doesn't that work since one device would be missing anyway and it would have no valid parity for it? Should I instead do a New Config again following the same steps as my first post and not assign any thing to Disk 6? In that case I can expand the array with the other HGST 10TB, after parity is rebuilt and then transfer the data from the SSD. Thoughts? HUH721010ALE601_2TGD77RD-20231209-0043.txt define7-diagnostics-20231209-0120.zip

I don’t really see what harm shutting down the server will do at this point, but I’d like someone more experienced to confirm. Any takers?

Have you mapped the container path to “/mnt“ instead of the default “/mnt/user”? If you haven’t done that you will only be able to see user shares and not disks.