Mr.Lobo Posted November 19, 2022 Share Posted November 19, 2022 (edited) hello for the last 2 weeks i have had a lot of problems with my server. It all started after a power outage with a unclean shutdown a few weeks ago. whenever I was doing the parity check, docker would be disabled or not start at all. and many times the cache drive cannot be mounted or is read only. I have now changed the cache drive with a new one. now i get other errors, and the server is very slow, the unraid gui takes a long time to load. and plex is corrupting the database even when I restore the appdata from CA APPDATA BACKUP/ from 2 weeks ago. please any help will be greatly appreciated Nov 19 07:56:01 Tower kernel: docker0: port 12(vethd586829) entered disabled state Nov 19 07:56:01 Tower kernel: device vethd586829 entered promiscuous mode Nov 19 07:56:01 Tower kernel: docker0: port 12(vethd586829) entered blocking state Nov 19 07:56:01 Tower kernel: docker0: port 12(vethd586829) entered forwarding state Nov 19 07:56:01 Tower kernel: docker0: port 12(vethd586829) entered disabled state Nov 19 07:56:02 Tower kernel: eth0: renamed from vethd1a3182 Nov 19 07:56:02 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd586829: link becomes ready Nov 19 07:56:02 Tower kernel: docker0: port 12(vethd586829) entered blocking state Nov 19 07:56:02 Tower kernel: docker0: port 12(vethd586829) entered forwarding state Nov 19 07:56:03 Tower avahi-daemon[31459]: Joining mDNS multicast group on interface vethd586829.IPv6 with address fe80::3862:d6ff:fef6:e06e. Nov 19 07:56:03 Tower avahi-daemon[31459]: New relevant interface vethd586829.IPv6 for mDNS. Nov 19 07:56:03 Tower avahi-daemon[31459]: Registering new address record for fe80::3862:d6ff:fef6:e06e on vethd586829.*. Nov 19 07:56:43 Tower kernel: docker0: port 13(vethc972820) entered blocking state Nov 19 07:56:43 Tower kernel: docker0: port 13(vethc972820) entered disabled state Nov 19 07:56:43 Tower kernel: device vethc972820 entered promiscuous mode Nov 19 07:56:44 Tower kernel: eth0: renamed from veth0238d9f Nov 19 07:56:44 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethc972820: link becomes ready Nov 19 07:56:44 Tower kernel: docker0: port 13(vethc972820) entered blocking state Nov 19 07:56:44 Tower kernel: docker0: port 13(vethc972820) entered forwarding state Nov 19 07:56:46 Tower avahi-daemon[31459]: Joining mDNS multicast group on interface vethc972820.IPv6 with address fe80::54b0:f7ff:febb:3166. Nov 19 07:56:46 Tower avahi-daemon[31459]: New relevant interface vethc972820.IPv6 for mDNS. Nov 19 07:56:46 Tower avahi-daemon[31459]: Registering new address record for fe80::54b0:f7ff:febb:3166 on vethc972820.*. Nov 19 08:00:02 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 1 Nov 19 08:00:02 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 2 Nov 19 08:00:21 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 2 with status: 0 Nov 19 08:00:22 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 1 with status: 0 Nov 19 08:09:32 Tower kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 1385436 off 25207775232 csum 0x705100d1 expected csum 0xaeb9a940 mirror 1 Nov 19 08:09:32 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 Nov 19 09:00:01 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 1 Nov 19 09:00:01 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 2 Nov 19 09:00:22 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 1 with status: 0 Nov 19 09:00:22 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 2 with status: 0 Nov 19 09:57:13 Tower smbd[9044]: [2022/11/19 09:57:13.204348, 0] ../../source3/smbd/close.c:1485(close_directory) Nov 19 09:57:13 Tower smbd[9044]: Could not close dir! fname=data/media/movies/movies3/Slumberland (2022), fd=33, err=116=Stale file handle Nov 19 09:57:13 Tower smbd[9044]: [2022/11/19 09:57:13.204711, 0] ../../source3/smbd/close.c:1485(close_directory) Nov 19 09:57:13 Tower smbd[9044]: Could not close dir! fname=data/media/movies/movies3/Slumberland (2022), fd=35, err=116=Stale file handle Nov 19 10:00:01 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 1 Nov 19 10:00:01 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 2 Nov 19 10:00:20 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 2 with status: 0 Nov 19 10:00:20 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 1 with status: 0 Nov 19 11:00:01 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 1 Nov 19 11:00:01 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 2 Nov 19 11:00:21 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 1 with status: 0 Nov 19 11:00:21 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 2 with status: 0 Nov 19 12:00:01 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 1 Nov 19 12:00:01 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 2 Nov 19 12:00:21 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 1 with status: 0 Nov 19 12:00:21 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 2 with status: 0 Nov 19 12:55:42 Tower kernel: disk_load[10286]: segfault at c48808 ip 0000000000476bee sp 00007ffec34946d8 error 4 in bash[426000+c5000] Nov 19 12:55:42 Tower kernel: Code: ff 48 83 ec 08 e8 22 f5 fa ff c7 00 09 00 00 00 b8 ff ff ff ff 48 83 c4 08 c3 66 90 48 8b 05 21 1a 0c 00 48 63 ff 48 8d 04 f8 <48> 8b 10 48 89 30 48 89 d0 c3 0f 1f 84 00 00 00 00 00 48 8b 05 01 Nov 19 13:00:01 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 1 Nov 19 13:00:01 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 2 Nov 19 13:00:22 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 2 with status: 0 Nov 19 13:00:22 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 1 with status: 0 Nov 19 13:16:32 Tower kernel: traps: python3[9593] general protection fault ip:148258d97d11 sp:1482531305b0 error:0 in ld-musl-x86_64.so.1[148258d89000+48000] Nov 19 13:16:32 Tower kernel: python3[28338]: segfault at 520000 ip 000014965fe9741f sp 00007ffda4683378 error 6 in libpython3.10.so.1.0[14965fe58000+14e000] Nov 19 13:16:32 Tower kernel: Code: e1 40 4c 8d 57 48 74 0a 4c 8d 57 30 eb 04 4c 8b 57 48 48 89 c6 4c 89 d7 e8 7e 0c fc ff 5a 85 c0 40 0f 94 c6 40 0f b6 c6 c3 c3 <48> ff 0f 75 02 eb 6b c3 48 89 f8 48 8d 15 ef 69 22 00 48 c1 e8 26 Nov 19 13:16:33 Tower kernel: traps: python3[28352] general protection fault ip:14e5fb096bd9 sp:7ffe40cdd060 error:0 in libpython3.10.so.1.0[14e5fb058000+14e000] Nov 19 13:16:34 Tower kernel: traps: python3[28377] general protection fault ip:14fc43e96bd9 sp:7fffbbcaee50 error:0 in libpython3.10.so.1.0[14fc43e58000+14e000] Nov 19 13:16:35 Tower kernel: python3[28395]: segfault at 1519943b3aa0 ip 00001519943b3aa0 sp 00007ffec5c47d98 error 15 Nov 19 13:16:35 Tower kernel: Code: 00 00 a0 3a 3b 94 19 15 00 00 b0 66 94 94 19 15 00 00 70 55 94 94 19 15 00 00 b0 55 94 94 19 15 00 00 00 00 00 00 00 00 00 00 <18> 00 00 00 00 00 00 00 20 0b 8b 94 19 15 00 00 11 00 00 00 00 00 Nov 19 13:16:36 Tower kernel: python3[28566]: segfault at 14929cf0a069 ip 000014929c696bbe sp 00007ffe52dce4a8 error 4 in libpython3.10.so.1.0[14929c658000+14e000] Nov 19 13:16:36 Tower kernel: Code: 00 48 89 ac d8 48 2c 00 00 eb 0f 5a 48 89 ef 5b 5d 41 5c 41 5d e9 e6 05 00 00 58 5b 5d 41 5c 41 5d c3 eb 00 48 8b 57 08 31 c0 <f6> 82 a9 00 00 00 40 74 1e 48 8b 8a 48 01 00 00 b8 01 00 00 00 48 Nov 19 13:53:07 Tower samba-dcerpcd[23708]: [2022/11/19 13:53:07.064042, 0] ../../lib/util/fault.c:173(smb_panic_log) Nov 19 13:53:07 Tower samba-dcerpcd[23708]: =============================================================== Nov 19 13:53:07 Tower samba-dcerpcd[23708]: [2022/11/19 13:53:07.064080, 0] ../../lib/util/fault.c:174(smb_panic_log) Nov 19 13:53:07 Tower samba-dcerpcd[23708]: INTERNAL ERROR: Signal 11: Segmentation fault in pid 23708 (4.17.2) Nov 19 13:53:07 Tower samba-dcerpcd[23708]: [2022/11/19 13:53:07.064088, 0] ../../lib/util/fault.c:178(smb_panic_log) Nov 19 13:53:07 Tower samba-dcerpcd[23708]: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting Nov 19 13:53:07 Tower samba-dcerpcd[23708]: [2022/11/19 13:53:07.064097, 0] ../../lib/util/fault.c:183(smb_panic_log) Nov 19 13:53:07 Tower samba-dcerpcd[23708]: =============================================================== Nov 19 13:53:07 Tower samba-dcerpcd[23708]: [2022/11/19 13:53:07.064104, 0] ../../lib/util/fault.c:184(smb_panic_log) Nov 19 13:53:07 Tower samba-dcerpcd[23708]: PANIC (pid 23708): Signal 11: Segmentation fault in 4.17.2 Nov 19 13:53:07 Tower samba-dcerpcd[23708]: [2022/11/19 13:53:07.064193, 0] ../../lib/util/fault.c:292(log_stack_trace) Nov 19 13:53:07 Tower samba-dcerpcd[23708]: BACKTRACE: 4 stack frames: Nov 19 13:53:07 Tower samba-dcerpcd[23708]: #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x1500a7f9e64e] Nov 19 13:53:07 Tower samba-dcerpcd[23708]: #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x1500a7f9e8a9] Nov 19 13:53:07 Tower samba-dcerpcd[23708]: #2 /usr/lib64/libgenrand-samba4.so(+0x2937) [0x1500a7f9e937] Nov 19 13:53:07 Tower samba-dcerpcd[23708]: #3 /lib64/libc.so.6(+0x3a6a0) [0x1500a7a606a0] Nov 19 13:53:07 Tower samba-dcerpcd[23708]: [2022/11/19 13:53:07.064224, 0] ../../source3/lib/dumpcore.c:315(dump_core) Nov 19 13:53:07 Tower samba-dcerpcd[23708]: dumping core in /var/log/samba/cores/samba-dcerpcd Nov 19 13:53:07 Tower samba-dcerpcd[23708]: Nov 19 14:00:01 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 1 Nov 19 14:00:01 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 2 Nov 19 14:00:22 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 2 with status: 0 Nov 19 14:00:22 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 1 with status: 0 Nov 19 14:19:27 Tower ool www[30998]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_scrub 'start' '/mnt/cache' '-r' Nov 19 14:19:27 Tower kernel: BTRFS info (device nvme0n1p1): scrub: started on devid 1 Nov 19 14:20:07 Tower kernel: BTRFS info (device nvme0n1p1): scrub: finished on devid 1 with status: 0 Nov 19 14:23:14 Tower webGUI: Successful login user root from 192.168.1.197 Nov 19 15:00:01 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 1 Nov 19 15:00:01 Tower kernel: BTRFS info (device nvme1n1p1): scrub: started on devid 2 Nov 19 15:00:20 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 1 with status: 0 Nov 19 15:00:20 Tower kernel: BTRFS info (device nvme1n1p1): scrub: finished on devid 2 with status: 0 Nov 19 15:24:38 Tower nginx: 2022/11/19 15:24:38 [error] 9998#9998: *682942 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:24:38 Tower nginx: 2022/11/19 15:24:38 [error] 9998#9998: *684864 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:24:38 Tower nginx: 2022/11/19 15:24:38 [error] 9998#9998: *684864 auth request unexpected status: 504 while sending to client, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:24:54 Tower nginx: 2022/11/19 15:24:54 [error] 9998#9998: *664891 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.197, server: , request: "POST /plugins/unassigned.devices.preclear/Preclear.php HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.54", referrer: "http://192.168.1.54/Settings" Nov 19 15:24:54 Tower nginx: 2022/11/19 15:24:54 [error] 9998#9998: *664891 auth request unexpected status: 504 while sending to client, client: 192.168.1.197, server: , request: "POST /plugins/unassigned.devices.preclear/Preclear.php HTTP/1.1", host: "192.168.1.54", referrer: "http://192.168.1.54/Settings" Nov 19 15:25:12 Tower nginx: 2022/11/19 15:25:12 [error] 9998#9998: *684757 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:25:12 Tower nginx: 2022/11/19 15:25:12 [error] 9998#9998: *684865 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.197, server: , request: "GET /plugins/plexstreams/ajax.php HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:25:12 Tower nginx: 2022/11/19 15:25:12 [error] 9998#9998: *684865 auth request unexpected status: 504 while sending to client, client: 192.168.1.197, server: , request: "GET /plugins/plexstreams/ajax.php HTTP/1.1", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:25:12 Tower nginx: 2022/11/19 15:25:12 [error] 9998#9998: *685096 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:25:12 Tower nginx: 2022/11/19 15:25:12 [error] 9998#9998: *682946 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:25:12 Tower nginx: 2022/11/19 15:25:12 [error] 9998#9998: *682946 auth request unexpected status: 504 while sending to client, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:35:18 Tower nginx: 2022/11/19 15:35:18 [error] 9998#9998: *703545 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:35:18 Tower nginx: 2022/11/19 15:35:18 [error] 9998#9998: *703545 auth request unexpected status: 504 while sending to client, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:35:39 Tower nginx: 2022/11/19 15:35:39 [error] 9998#9998: *703857 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.197, server: , request: "POST /plugins/unassigned.devices.preclear/Preclear.php HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.54", referrer: "http://192.168.1.54/Settings" Nov 19 15:35:39 Tower nginx: 2022/11/19 15:35:39 [error] 9998#9998: *703857 auth request unexpected status: 504 while sending to client, client: 192.168.1.197, server: , request: "POST /plugins/unassigned.devices.preclear/Preclear.php HTTP/1.1", host: "192.168.1.54", referrer: "http://192.168.1.54/Settings" Nov 19 15:35:52 Tower nginx: 2022/11/19 15:35:52 [error] 9998#9998: *684757 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:35:52 Tower nginx: 2022/11/19 15:35:52 [error] 9998#9998: *684757 auth request unexpected status: 504 while sending to client, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:35:52 Tower nginx: 2022/11/19 15:35:52 [error] 9998#9998: *704045 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:35:52 Tower nginx: 2022/11/19 15:35:52 [error] 9998#9998: *704045 auth request unexpected status: 504 while sending to client, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:35:52 Tower nginx: 2022/11/19 15:35:52 [error] 9998#9998: *685096 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:35:52 Tower nginx: 2022/11/19 15:35:52 [error] 9998#9998: *685096 auth request unexpected status: 504 while sending to client, client: 192.168.1.197, server: , request: "GET /plugins/gpustat/gpustatus.php HTTP/1.1", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:35:52 Tower nginx: 2022/11/19 15:35:52 [error] 9998#9998: *704052 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.197, server: , request: "GET /plugins/plexstreams/ajax.php HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" Nov 19 15:35:52 Tower nginx: 2022/11/19 15:35:52 [error] 9998#9998: *704052 auth request unexpected status: 504 while sending to client, client: 192.168.1.197, server: , request: "GET /plugins/plexstreams/ajax.php HTTP/1.1", host: "192.168.1.54", referrer: "http://192.168.1.54/Dashboard" tower-diagnostics-20221119-1446.zip Edited November 19, 2022 by Mr.Lobo Quote Link to comment
Solution JorgeB Posted November 20, 2022 Solution Share Posted November 20, 2022 There are different apps crashing and btrfs detecting data corruption, start by running memtest. 1 Quote Link to comment
Mr.Lobo Posted November 21, 2022 Author Share Posted November 21, 2022 22 hours ago, JorgeB said: There are different apps crashing and btrfs detecting data corruption, start by running memtest. well i just run memtest and there is a lot of errors, within just a few seconds of running the test. i have try to troubleshoot by lowering ram speed below the ram spec. but no I'm getting same errors. should i claim the warranty ? 🤞so far looks promising with the new ram.🤞 not getting the nasty errors for now. ill will update in a few hours thank you for the recommendations. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.