It’s a complete new HDD , Seagate Barracuda Compute 2,5" (5400rpm), 5TB
Was freshly formatted by DietPi after first DietPi run
root@DietPi:~# dmesg -l 0,1,2,3
[ 1.458299] rockchip-usb2phy ff770000.syscon:usb2phy@e450: failed to create phy
[ 1.459414] rockchip-usb2phy ff770000.syscon:usb2phy@e460: failed to create phy
[ 4.268712] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed
[ 7.201409] OF: graph: no port node found in /i2c@ff3d0000/typec-portc@22
root@DietPi:~#
Ah okay so not firmatted since the error occurred the first time.
Errors seems to be gone, but some files are lost. Some have been stored to /lost+found with inode name. You may try to find the original name/location by their content, then test if the drive now works fine under lead.
The HDD didnt have any worth data on it as it was only used to install fresh DietPi and move the user Data
thank you
Ah right. Then it should be fine. Hopefully it runs stable now.
Regarding NZBGet
After installation via DietPi you see in the WebIf a warning message
If you are receiving the TLS certificate failed error in NZBGet please update your “cacert.pem” file in the NZBGet installation directory. The TLS certificate error is happening due to a DST Root CA X3 certificate that has expired and is causing verification issues since September 30 2021.
Here’s how to fix the error “TLS certificate verification failed for ** certificate has expired”
One solution is to use CURL.
I did this by renaming the file (mv cacert.pem cacert.pem_old) and downloading the new one (curl --output cacert.pem).
The reason I renamed the old one is that I need the new one to assume the same permissions/owner of the old one.
You can do that with “chown --reference=cacert.pem_old cacert.pem”.
The certificate cacert.pem is located in the NZBGet installation folder.
As I moved the UserData to the Harddisk, use the following commands:
cd /mnt/dietpi_userdata/nzbget
mv cacert.pem cacert.pem_old
curl https://nzbget.net/info/cacert.pem --output cacert.pem
chown --reference=cacert.pem_old cacert.pem
After that I restarted NZBGet application via the WebInterface http://<your.IP>:6789 and the check passed!
@MichaIng
Can you add this new cacert.pem to the DietPi installation script so NZBGet is running up to date after installing via DietPi
Main issue is nzbget install script. We just download their installer and extract the files. That’s it. As far as I can see, nzbget project has been archived and no further updates will follow. Means, following “old” issue will not be resolved anymore TLS certificate verification failed for XXXXXX: certificate has expired. For more info visit http://nzbget.net/certificate-verification · Issue #784 · nzbget/nzbget · GitHub and we would need to implement a workaround by downloading the cert ourselves.
@MichaIng Question is what to do with nzbget in general as project has been archived on GitHub.
EDIT
Theoretically a workaround could be quite simple. But yeah, depends if we like to continue support nzbget
[ OK ] DietPi-Software | dash package.run --destdir /mnt/dietpi_userdata/nzbget
[ OK ] DietPi-Software | rm package.run
[ OK ] DietPi-Software | cd /tmp/DietPi-Software
[ OK ] DietPi-Software | curl -sSfL https://nzbget.net/info/cacert.pem -o cacert.pem
[ INFO ] DietPi-Software | Updating file: /mnt/dietpi_userdata/nzbget/cacert.pem
[ OK ] DietPi-Software | mv cacert.pem /mnt/dietpi_userdata/nzbget/cacert.pem
[ OK ] DietPi-Software | Verifying user "nzbget" to run NZBGet
Yes that’s up to you guys.
Remember, SABnzbd has the same cert issue if they didn’t correct the certificate
Hmm is there any benefit of NZBGet over SABnzbd? Efficiency at least (C++ vs Python).
Not as an enduser if you ask me?