dvd.collector

Sigh, OK tried a different USB drive and it seems to work. Can only assume I had a failed USB drive which only manifested when I tried the upgrade..

eeek, update - I copied my backup back onto the USB and now am seeing exactly the same issue ... Now I'm in trouble! I did not see this issue when I restored files from the "backup" folder previously. Also tried recreating the USB on version 7.2.0 and still won't boot. I am really going to be in the family bad books now 😵

@JorgeB I recreated the flash using the usb creator tool using the 7.2.2 zip and the server still hard reboots as soon as it finishes loading bzroot. Does this mean something in my hardware is incompatible with whatever version of linux is in 7.2.2?

After upgrading from 7.2.0 to 7.2.2 using the webgui the server now hard reboots when loading bzroot (see attached video). I've reverted back to 7.2.0 and all is fine. Any ideas how to debug? tower.mp4

Hmm OK. Seems so complicated to do something seemingly so simple! 😢

Thanks for the reply. Is there a way to have a share span two pools then?

I currently have 1 NVME drive formatted as BTRFS used to store non critical data in a share (outside of the array). I'd like to add another NVME drive to expand this storage without adding redundancy as I'm happy to lose data and I want the most space possible. If I understand correctly my only option is to use RAID0 for BTRFS which stripes data across both drives. Meaning if one drive fails I lose ALL data, rather than just whats on that one drive. Is there a way to configure both drives to work effectively as singles but be able to have share spanning both of them (similar to how the array works)?

Hi all. I'm on an older unraid version (6.8.3) and am sure i've had this plugin installed in the past. However when i search in community applications, i can't find this plugin. Does this plugin work with my version of unraid and if so, how can i install it if it doesn't show in community applications?

From what I've read, you can add SSDs to the array, however TRIM will never run. Which is bad for SSDs

My current unraid server is pretty old now, however it still works fine - so have no reason to upgrade/replace the hardware. However with SSD prices dropping, I recently bought 2x 4tb sata SSDs to replace two array drives (one parity and one data). Having now set all of that up, i read that this is probably a bad idea and I shouldn't use SSDs within the array. So the solution seems to be to use the SSDs in a btrfs pool outside of the array, as that would support trim. However the version of unraid I am using (6.8.3) does not support multiple pools. The reason I have never upgraded unraid is that some years ago when i tried upgrading to v6.9.x this broke passthru on my vm's. No one on the forums was able to help me fix that at the time. So I reverted back to a working 6.8.3. I'm thinking that i should try upgrading again to the latest version and see where I stand. However as I am so far behind, I'm concerned I won't be able to revert easily if things don't go as expected. Can anyone advise if downgrading back to v6.8.3 from v6.12.x is possible?

Yes mine is doing the same after updating today. How were you able to rollback?

Anyone else having issues with PIA today? 2021-10-11 11:55:29,641 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token from URL 'https://privateinternetaccess.com/gtoken/generateToken' [info] 8 retries left [info] Retrying in 10 secs... Seeing this error on all of the endpoints I have tried (around 10). Annnnndddd its working again now. Presumably an issue at PIA.

I had exactly the same problem and raised a thread on here. No updates, so rolled back to 6.8.3.

Has anyone else started seeing this error today? 2021-04-15 15:50:53,919 DEBG 'start-script' stdout output: parse error: Invalid numeric literal at line 1, column 7 2021-04-15 15:50:53,919 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token from URL 'https://10.0.0.1/authv3/generateToken' [info] 12 retries left [info] Retrying in 10 secs... It just keeps repeating in the logs over and over.

anyone know if PureVPN works?

So I've tried every endpoint in the PIA list and all throw this: 2020-09-09 10:39:03,388 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- [info] ca-toronto.privateinternetaccess.com [info] ca-montreal.privateinternetaccess.com [info] ca-vancouver.privateinternetaccess.com [info] de-berlin.privateinternetaccess.com [info] de-frankfurt.privateinternetaccess.com [info] france.privateinternetaccess.com [info] czech.privateinternetaccess.com [info] spain.privateinternetaccess.com [info] ro.privateinternetaccess.com [info] israel.privateinternetaccess.com [info] Attempting to get dynamically assigned port... 2020-09-09 10:39:24,196 DEBG 'start-script' stdout output: [warn] Exit code '52' from curl != 0 or no response body received [info] 12 retries left [info] Retrying in 10 secs... 2020-09-09 10:39:24,196 DEBG 'start-script' stdout output: [warn] Exit code '52' from curl != 0 or no response body received [info] 12 retries left [info] Retrying in 10 secs... Is PIA removing port forwarding ability completely? If so, is there a different VPN that supports port forwarding that anyone would recommend? EDIT, saw this on the PIA website: * The information contained within this article will only work with our Current/Previous Generation servers. Our Next Generation servers do not currently offer port-forwarding outside of the application. * So I guess as they upgrade their servers this will stop working. Back to my other question then, can anyone recommend a different VPN that will work well with this docker?

OK I switched to Germany and it seems to work now.

Attached log. I am assuming that this is the issue: [warn] Unable to download file from url 'http://209.222.18.222:2000/?client_id=b911029a01c805dd6c6d72c547ed627e84ec450593a5c59d3a94bbd10f4cff5a', exiting script... [warn] PIA VPN port assignment API currently down, terminating OpenVPN process to force retry for incoming port... Is this a PIA problem? supervisord - clean.log

Hi all, this container has been working fine for me for ages, but in the last couple of days I've been seeing this error: 2020-07-20 09:39:43,246 DEBG 'start-script' stdout output: [info] Attempting to get dynamically assigned port... 2020-07-20 09:39:43,372 DEBG 'start-script' stdout output: [warn] Exit code '56' from curl != 0 or no response body received [info] 12 retries left [info] Retrying in 10 secs... 2020-07-20 09:39:53,431 DEBG 'start-script' stdout output: [warn] Exit code '52' from curl != 0 or no response body received [info] 11 retries left [info] Retrying in 10 secs... ... 2020-07-20 09:41:44,100 DEBG 'start-script' stdout output: [warn] Exit code '56' from curl != 0 or no response body received, exhausted retries 2020-07-20 09:41:44,101 DEBG 'start-script' stdout output: [warn] Unable to download file from url 'http://209.222.18.222:2000/?client_id=d69a030e782a094400b7a58b95cd54440c69b881358170e6b28ea3c437f4f223', exiting script... 2020-07-20 09:41:44,101 DEBG 'start-script' stdout output: [warn] PIA VPN port assignment API currently down, terminating OpenVPN process to force retry for incoming port... 2020-07-20 09:41:44,102 DEBG 'start-script' stdout output: Mon Jul 20 09:41:44 2020 event_wait : Interrupted system call (code=4) Neither privoxy or rtorrent works. Any ideas what is causing this?

Has anyone had issues with Sonarr not automatically starting when the array starts recently. All was fine until a couple of days ago and now Sonaar will not auto start. It starts fine if I go and manually choose start from the menu.... Am unsure exactly which parts of the log are current as it doesn't seem to create a new log when it starts, but these are the last entries from when it does not startup. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.

yep thats got it, thanks

attached. rtorrent.rc

Hmm, I've updated the container to the latest and still can't get to rutorrent, just seems to be looping trying to start. Privoxy works fine.

Ah how did I miss that...! Thanks, changed to France and its working now. I think I was confused as I had a different issue related to PIA as well. I could not access their website due to the SSL_PROTOCOL_ERROR. After googling it seems this is related to my ISP's WEBSAFE filter, which seems to have started causing issues with PIA from yesterday. After disabling the WEBSAFE filter on my ISP account settings I can now access the PIA website again. Seems too co-incidental that both issues happen at once, but maybe i'm just unlucky!

Is anyone having issues with PIA today? Suddenly this docker will not work and I cannot access the PIA website (from another pc) which throws the error ERR_SSL_PROTOCOL_ERROR. The docker log seems to show this error over and over again: 2018-04-03 11:03:00,913 DEBG 'start-script' stdout output: [info] Attempting to curl http://209.222.18.222:2000/?client_id=3663b5f1cc355a121364e709954f045c7b1bc67d6aabf721ee1eb382e30aa751... 2018-04-03 11:03:00,946 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 [info] 12 retries left [info] Retrying in 10 secs... 2018-04-03 11:03:00,980 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 212.92.117.185 2018-04-03 11:03:10,975 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 [info] 11 retries left [info] Retrying in 10 secs... 2018-04-03 11:03:21,013 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 [info] 10 retries left [info] Retrying in 10 secs... 2018-04-03 11:03:31,040 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 [info] 9 retries left [info] Retrying in 10 secs... 2018-04-03 11:03:41,072 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 [info] 8 retries left [info] Retrying in 10 secs... 2018-04-03 11:03:51,099 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 [info] 7 retries left