MisterWolfe

Switching to onboard SATA controller resolved the issue. Thanks for replying.

Good morning, I have just installed an ssd on an existing unraid server (Version: 6.12.4). I'm attempting to copy the docker.img and appdata files from the array to the cache drive. After a short period of time into the copy process I get an error message saying that the drive is read only and can't be written to. I have tried copying using MC and a simply copy command from an ssh window and I get the same behaviour. I want to be clear that the cache drive is initially readable and writable before I start the copy process. It becomes read only after I start the copy process and about 10GB of data has been copied. I did notice that the SSD temperature went up to 55 degrees during the last copy. The ssd is a Samsung 870 EVO. I initially formatted the drive as BTRFS when I first got the error. I reformatted as XFS and I still get the error. The drive is formatted XFS currently. The drive is connected via a PCIE expansion card. (Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)). I've attached the diagnostics file. Thanks for looking! luna-diagnostics-20230927-0857.zip

I'm on 6.9.1 and have an LSI 9200-8i controller. No issues at all with my ironwolf drives, thankfully. I wonder if the issue is card version specific.

Edit: Upgrading from 6.6.1 to 6.6.2 and the plugin works properly again. Having some issues with the NerdPack plugin. When I go into settings and choose nerdpack, none of the packages show up. I've tried removing the plugin, deleting the nerdpack directory, rebooting, & reinstalling the plugin with no change. Is this a just my server issue or have others also experienced this? I'm on v6.6.1. I'm including a screenshot and diagnostics. tower-diagnostics-20181012-1254.zip Thanks

That did it, thanks!

I notice that the docker has been updated Ubooquity version 2.1. It looks like the update made some internal changes that made the existing databases inaccessible. The databases are repopulating from the path set in the docker setup, rather than from the path set in the ubooquity admin area. The admin page is also no longer accessible via the normal url method. Is there a new method I should be using to access the admin page, and if not, how can I revert back to v 1.10? Thanks!

Good to know. Thanks.

I've had some trouble updating mylar to update. The web gui tells me there is a newer version available with 33 new commits. I hit the update option, the web gui goes to an updating page, and then shows me that none of the updates have been applied. Log file gives me this error: 2016-09-22 11:04:37 WARNING Could not get the latest commit from github 2016-09-22 11:04:36 INFO Retrieving latest version information from github I've got it set yp pull from the development branch. I've tried deleting the docker and re-adding it. I've tried creating a new appadata directory with no change. Suggestions?

It was a reply to me. I discovered my error and deleted my post and he must have seen it before I removed it. Excellent script. Works as expected when I try to run it from the proper spot. gfjardim ... was that reply for me? If so i do not understand what you are trying to tell me. I do not have a preclear disk beta tab within settings. FYI i downloaded the 'amended' version by 'search'ing for 'preclear' on the CA apps tab. It downloaded the new version (dated today) and the install script confirmed this but the plugin it installed still shows old timestamps and version number against it and hasn't got 'beta' anywhere to be seen. You know much better than me how these things work. I'm just happy to confirm that it does!!

Using delugeVPN docker 1)Unraid 6.1.8 2) Intel q9550 processor 3) no 4) Module Size Used by xt_nat 1665 10 veth 4401 0 ipt_MASQUERADE 981 11 nf_nat_masquerade_ipv4 1649 1 ipt_MASQUERADE iptable_nat 1615 1 nf_conntrack_ipv4 5626 2 nf_nat_ipv4 4111 1 iptable_nat iptable_filter 1280 1 ip_tables 9310 2 iptable_filter,iptable_nat nf_nat 9789 3 nf_nat_ipv4,xt_nat,nf_nat_masquerade_ipv4 md_mod 30680 6 tun 16465 0 hwmon_vid 2028 0 coretemp 5044 0 r8169 57464 0 mii 3339 1 r8169 ata_piix 24047 6 i2c_i801 8917 0 skge 27834 0 pata_marvell 2843 0 ahci 24107 0 sata_sil 7159 2 libahci 18687 1 ahci asus_atk0110 6874 0 acpi_cpufreq 6074 0 5) - attached supervisord.log and supervisord.log.1 6) I used deluge under 6.1.7 and it worked. After looking at supervisord.1.log, which was generated when I installed delugevpn, I saw that the openvpn folder couldn't be accessed. I changed the owner to nobody.users (from root.root) and restarted. supervisord.log is the file generated after restarting. Edit: Still no webUI access on the LAN supervisord.1.txt supervisord.txt