Rav20
Members
-
Joined
-
Last visited
-
Thanks for responding, I'm not able to pull logs for the moment but I did want to provide feedback on #1/2 that the server updated and I noticed the issue about about 9 hours later so I don't believe it was intervention of it going down during a migration. Otherwise from memory the error I saw in the docker log was on repeat every 10 lines or so was "Error: Unable to set up server: sqlite3\_statement\_backend::loadOne: database or disk is full (N4soci10soci\_errorE)".
-
just adding in, same issue. there's nothing full. i did a restore from 3 days ago and same issue. i rebooted and same issue. as i stated, nothing is full, temp isnt full, the appdata folder isnt full, ram isnt full,ect. rollback to 1.40.2.8395-1-01 restored functionality
-
Seeking plots took too long: 181.45854 seconds! i keep getting the above error, between 65-600+ seconds yet. when im watching the summary screen i see everything under 1 second. HDD's dont spin down, local on the array not network or anything. any advice for tracing down the problem?
-
bueller ?
-
so when i have a custom IP in BR0 with VPN enabled i cannot access the GUI. if i disable the VPN, i am able to access the GUI. if i use bridge mode i can access the gui but i now have a need to change it to a unique IP address. i've also tried the below commands but it made no change. any advice? whatcha need from me? echo "# force iptable mangle module to load (required for *vpn dockers)" >> /boot/config/go echo "/sbin/modprobe iptable_mangle" >> /boot/config/go and reboot
-
thank you so very much for this! your instructions work perfect. my 9207-8i did require P14 sas2flash but just noting incase anyone else with a 9207-8i uses this information!
-
parity drive had write errors. the drive was removed and readded to the array. rebuilding would have been a better way to say it.
-
just a heads up, I believe ca.mover.tuner caused instability in the parity write during a large extended move (mover was moving and files were being written to cache as fast as it could move, resulting in a "move" run of about 4 hours). I ignored the warning that it was incompatible. I am running 6.9.0-RC1 with multiple cache pools. HDD checked out fine on smart and is happily rebuilding for an hour so far. needless to say, i've uninstalled it until it is updated. I would not recommend running until its sorted.