Vodka2014 Posted September 12, 2023 Share #651 Posted September 12, 2023 (edited) Hi @Peter Suh Anything else I can do or anything. I have the old USB on v7.1.1 that does not have the HBA should i add this back, add back the other SATA Drive and remove the SAS disks or how do i see if the controller has dropped the disks etc.. as you mentioned above. Thanks EDIT: Or how can i downgrade to Update 1 via SSH. Will it help if i move the Disks to another setup of mine or will there be an issue ? If i can how do i do all of this etc please Edited September 12, 2023 by Vodka2014 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted September 12, 2023 Author Share #652 Posted September 12, 2023 42 minutes ago, Vodka2014 said: Hi @Peter Suh Anything else I can do or anything. I have the old USB on v7.1.1 that does not have the HBA should i add this back, add back the other SATA Drive and remove the SAS disks or how do i see if the controller has dropped the disks etc.. as you mentioned above. Thanks EDIT: Or how can i downgrade to Update 1 via SSH. Will it help if i move the Disks to another setup of mine or will there be an issue ? If i can how do i do all of this etc please I will show you how to extract logs from the problematic loader USB stick. please wait for a moment. 1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted September 12, 2023 Author Share #653 Posted September 12, 2023 (edited) 56 minutes ago, Vodka2014 said: Hi @Peter Suh Anything else I can do or anything. I have the old USB on v7.1.1 that does not have the HBA should i add this back, add back the other SATA Drive and remove the SAS disks or how do i see if the controller has dropped the disks etc.. as you mentioned above. Thanks EDIT: Or how can i downgrade to Update 1 via SSH. Will it help if i move the Disks to another setup of mine or will there be an issue ? If i can how do i do all of this etc please Can I access that path shown in the bottom using sftp? Please download the two files dmesg and linuxrs.syno.log using sftp and attach them to a new post. Edited September 12, 2023 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted September 12, 2023 Share #654 Posted September 12, 2023 4 minutes ago, Peter Suh said: Can I access that path shown in the bottom using sftp? Please download the two files dmesg and linuxrs.syno.log using sftp and attach them to a new post. right now i am on the Loader screen. I take it can load winscp or must i reboot into the loader and then try and log in ? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted September 12, 2023 Author Share #655 Posted September 12, 2023 6 minutes ago, Vodka2014 said: right now i am on the Loader screen. I take it can load winscp or must i reboot into the loader and then try and log in ? In my case, I use portx, which makes it easy to use sftp. This is free software that can be downloaded from the link below. It is simple and good to use only ssh / sftp. https://portx.online/ru/ winscp seems to be possible, but I'm not sure. The loader does not require a reboot. Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted September 12, 2023 Share #656 Posted September 12, 2023 (edited) 23 minutes ago, Peter Suh said: In my case, I use portx, which makes it easy to use sftp. This is free software that can be downloaded from the link below. It is simple and good to use only ssh / sftp. https://portx.online/ru/ winscp seems to be possible, but I'm not sure. The loader does not require a reboot. Ok then how do i connect to what Port etc... please as if i connect to the IP there is now on 22 then i do not see anything. Edited September 12, 2023 by Vodka2014 Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted September 12, 2023 Share #657 Posted September 12, 2023 (edited) UPDATE NOTES: I SSH'd Into my NAS and tried to see what is going on and this is what i found. Not sure i am looking in the right spot. Seems after the Reboot i did is when all the issues started as i mentioned. It seems the disks are getting seen but that is about it. lrwxrwxrwx 1 root root 0 Sep 12 10:30 sdc -> ../devices/pci0000:00/0000:00:01.0/0000:07:00.0/host2/port-2:0/end_device-2:0/target2:0:0/2:0:0:0/block/sdc lrwxrwxrwx 1 root root 0 Sep 12 10:30 sdd -> ../devices/pci0000:00/0000:00:01.0/0000:07:00.0/host2/port-2:1/end_device-2:1/target2:0:1/2:0:1:0/block/sdd lrwxrwxrwx 1 root root 0 Sep 12 10:30 sde -> ../devices/pci0000:00/0000:00:01.0/0000:07:00.0/host2/port-2:2/end_device-2:2/target2:0:2/2:0:2:0/block/sde lrwxrwxrwx 1 root root 0 Sep 12 10:30 sdf -> ../devices/pci0000:00/0000:00:01.0/0000:07:00.0/host2/port-2:3/end_device-2:3/target2:0:3/2:0:3:0/block/sdf lrwxrwxrwx 1 root root 0 Sep 12 10:30 synoboot -> ../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3.1/2-1.3.1:1.0/host1/target1:0:0/1:0:0:0/block/synoboot systemctl status synostoraged.service ● synostoraged.service - Synology daemon for monitoring space/disk/cache status Loaded: loaded (/usr/lib/systemd/system/synostoraged.service; static; vendor preset: disabled) Active: inactive (dead) find . -name proc_name ps PID TTY TIME CMD 11791 pts/0 00:00:00 sudo 11792 pts/0 00:00:00 ash 11855 pts/0 00:00:00 ps df Filesystem 1K-blocks Used Available Use% Mounted on /dev/md0 2385528 1430224 836520 64% / devtmpfs 2994244 0 2994244 0% /dev tmpfs 3048436 4 3048432 1% /dev/shm tmpfs 3048436 8016 3040420 1% /run tmpfs 3048436 0 3048436 0% /sys/fs/cgroup tmpfs 3048436 280 3048156 1% /tmp systemctl status ● NAS State: degraded Jobs: 0 queued Failed: 2 units Since: Tue 2023-09-12 10:30:47 CAT; 2h 4min ago CGroup: / ├─ 1 /sbin/init ├─5980 ./ttyd login ├─sshd.slice │ └─sshd.service │ ├─10010 sshd: /usr/bin/sshd -D [listener] 0 of 10-100 startup │ ├─12661 sshd: Synology [priv │ ├─12665 sshd: Synology@pts/ │ ├─12666 -sh │ ├─12723 systemctl status │ └─12724 systemctl status ├─system.slice │ ├─avahi.service │ │ └─10849 avahi-daemon: running [NAS.local │ ├─synoneteventd.service │ │ └─7800 /usr/syno/sbin/synoneteventd │ ├─systemd-journald.service │ │ └─7593 /usr/lib/systemd/systemd-journald │ ├─pkg-synobrm-agentd.service │ │ └─11044 /usr/local/bin/synology-backupd │ ├─systemd-udevd.service │ │ └─8434 /usr/lib/systemd/systemd-udevd │ ├─mcelog.service │ │ └─7558 /usr/sbin/mcelog --daemon --foreground │ ├─synonetd.service │ │ └─7783 /usr/syno/sbin/synonetd │ └─ip-conflict-detect.service │ └─10817 /usr/syno/sbin/syno_ip_conflict_detect --start ├─syno_dsm_internal.slice │ ├─nginx.service │ │ ├─10603 nginx: master process /usr/bin/nginx -c /etc/nginx/nginx.conf.run -g pid /run/nginx.pid; daemon on; master_process on │ │ ├─10604 nginx: worker process │ │ ├─10605 nginx: worker process │ │ ├─10606 nginx: worker process │ │ ├─10607 nginx: worker process │ │ ├─10608 nginx: worker process │ │ ├─10609 nginx: worker process │ │ ├─10610 nginx: worker process │ │ └─10611 nginx: worker process │ ├─synocgid.service │ │ └─10008 /usr/syno/sbin/synocgid -D │ ├─synoplugind.service │ │ └─7635 /usr/syno/sbin/synoplugind │ ├─dbus-system.service │ │ └─7728 /sbin/dbus-daemon --system --nopidfile │ ├─hotplugd.service │ │ └─10034 /usr/syno/sbin/hotplugd │ ├─dbus-session.service │ │ └─7690 /sbin/dbus-daemon --session --fork --print-address │ └─syslog-ng.service │ └─7985 /usr/bin/syslog-ng -Fe --worker-threads=24 -u system -g log └─syno_dsm_desktop.slice ├─synoscgi.service │ ├─ 9903 synoscgi │ ├─10899 synoscgi │ ├─10900 synoscgi │ ├─10901 synoscgi │ ├─10902 synoscgi │ ├─10903 synoscgi │ ├─10904 synoscgi │ ├─10905 synoscgi │ ├─10906 synoscgi │ ├─11570 synoscgi │ ├─11571 synoscgi │ ├─12720 synoscgi │ └─12722 synoscgi └─synoscgi-socket.service └─10186 /usr/bin/synonode /usr/syno/sbin/synoscgi_socket.js Edited September 12, 2023 by Vodka2014 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted September 12, 2023 Author Share #658 Posted September 12, 2023 1 hour ago, Vodka2014 said: Ok then how do i connect to what Port etc... please as if i connect to the IP there is now on 22 then i do not see anything. Is this the correct window status for the M SHELL TCRP loader build? It is correct to connect to SFTP port 22. Do you have the settings below? No logs/jr path? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted September 12, 2023 Author Share #659 Posted September 12, 2023 (edited) 28 minutes ago, Vodka2014 said: UPDATE NOTES: I SSH'd Into my NAS and tried to see what is going on and this is what i found. Not sure i am looking in the right spot. Seems after the Reboot i did is when all the issues started as i mentioned. It seems the disks are getting seen but that is about it. lrwxrwxrwx 1 root root 0 Sep 12 10:30 sdc -> ../devices/pci0000:00/0000:00:01.0/0000:07:00.0/host2/port-2:0/end_device-2:0/target2:0:0/2:0:0:0/block/sdc lrwxrwxrwx 1 root root 0 Sep 12 10:30 sdd -> ../devices/pci0000:00/0000:00:01.0/0000:07:00.0/host2/port-2:1/end_device-2:1/target2:0:1/2:0:1:0/block/sdd lrwxrwxrwx 1 root root 0 Sep 12 10:30 sde -> ../devices/pci0000:00/0000:00:01.0/0000:07:00.0/host2/port-2:2/end_device-2:2/target2:0:2/2:0:2:0/block/sde lrwxrwxrwx 1 root root 0 Sep 12 10:30 sdf -> ../devices/pci0000:00/0000:00:01.0/0000:07:00.0/host2/port-2:3/end_device-2:3/target2:0:3/2:0:3:0/block/sdf lrwxrwxrwx 1 root root 0 Sep 12 10:30 synoboot -> ../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3.1/2-1.3.1:1.0/host1/target1:0:0/1:0:0:0/block/synoboot systemctl status synostoraged.service ● synostoraged.service - Synology daemon for monitoring space/disk/cache status Loaded: loaded (/usr/lib/systemd/system/synostoraged.service; static; vendor preset: disabled) Active: inactive (dead) find . -name proc_name ps PID TTY TIME CMD 11791 pts/0 00:00:00 sudo 11792 pts/0 00:00:00 ash 11855 pts/0 00:00:00 ps df Filesystem 1K-blocks Used Available Use% Mounted on /dev/md0 2385528 1430224 836520 64% / devtmpfs 2994244 0 2994244 0% /dev tmpfs 3048436 4 3048432 1% /dev/shm tmpfs 3048436 8016 3040420 1% /run tmpfs 3048436 0 3048436 0% /sys/fs/cgroup tmpfs 3048436 280 3048156 1% /tmp systemctl status ● NAS State: degraded Jobs: 0 queued Failed: 2 units Since: Tue 2023-09-12 10:30:47 CAT; 2h 4min ago CGroup: / ├─ 1 /sbin/init ├─5980 ./ttyd login ├─sshd.slice │ └─sshd.service │ ├─10010 sshd: /usr/bin/sshd -D [listener] 0 of 10-100 startup │ ├─12661 sshd: Synology [priv │ ├─12665 sshd: Synology@pts/ │ ├─12666 -sh │ ├─12723 systemctl status │ └─12724 systemctl status ├─system.slice │ ├─avahi.service │ │ └─10849 avahi-daemon: running [NAS.local │ ├─synoneteventd.service │ │ └─7800 /usr/syno/sbin/synoneteventd │ ├─systemd-journald.service │ │ └─7593 /usr/lib/systemd/systemd-journald │ ├─pkg-synobrm-agentd.service │ │ └─11044 /usr/local/bin/synology-backupd │ ├─systemd-udevd.service │ │ └─8434 /usr/lib/systemd/systemd-udevd │ ├─mcelog.service │ │ └─7558 /usr/sbin/mcelog --daemon --foreground │ ├─synonetd.service │ │ └─7783 /usr/syno/sbin/synonetd │ └─ip-conflict-detect.service │ └─10817 /usr/syno/sbin/syno_ip_conflict_detect --start ├─syno_dsm_internal.slice │ ├─nginx.service │ │ ├─10603 nginx: master process /usr/bin/nginx -c /etc/nginx/nginx.conf.run -g pid /run/nginx.pid; daemon on; master_process on │ │ ├─10604 nginx: worker process │ │ ├─10605 nginx: worker process │ │ ├─10606 nginx: worker process │ │ ├─10607 nginx: worker process │ │ ├─10608 nginx: worker process │ │ ├─10609 nginx: worker process │ │ ├─10610 nginx: worker process │ │ └─10611 nginx: worker process │ ├─synocgid.service │ │ └─10008 /usr/syno/sbin/synocgid -D │ ├─synoplugind.service │ │ └─7635 /usr/syno/sbin/synoplugind │ ├─dbus-system.service │ │ └─7728 /sbin/dbus-daemon --system --nopidfile │ ├─hotplugd.service │ │ └─10034 /usr/syno/sbin/hotplugd │ ├─dbus-session.service │ │ └─7690 /sbin/dbus-daemon --session --fork --print-address │ └─syslog-ng.service │ └─7985 /usr/bin/syslog-ng -Fe --worker-threads=24 -u system -g log └─syno_dsm_desktop.slice ├─synoscgi.service │ ├─ 9903 synoscgi │ ├─10899 synoscgi │ ├─10900 synoscgi │ ├─10901 synoscgi │ ├─10902 synoscgi │ ├─10903 synoscgi │ ├─10904 synoscgi │ ├─10905 synoscgi │ ├─10906 synoscgi │ ├─11570 synoscgi │ ├─11571 synoscgi │ ├─12720 synoscgi │ └─12722 synoscgi └─synoscgi-socket.service └─10186 /usr/bin/synonode /usr/syno/sbin/synoscgi_socket.js Do you have a total of 4 SAS disks? Doesn't any of the 4 disks appear in DSM's Storage Manager? Edited September 12, 2023 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted September 12, 2023 Share #660 Posted September 12, 2023 1 minute ago, Peter Suh said: Do you have a total of 4 SAS disks? Doesn't any of the 4 disks appear in DSM's Storage Manager? I cannot log into DSM at all via the WebUI it keeps on stating it is Busy and try again later. Before i rebooted There was only 1 SAS and 3 SATA the Array was all ok. Data was all there no issues at all. Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted September 12, 2023 Share #661 Posted September 12, 2023 (edited) 7 minutes ago, Peter Suh said: Is this the correct window status for the M SHELL TCRP loader build? It is correct to connect to SFTP port 22. Do you have the settings below? No logs/jr path? I am there now what is the password for this please ? Edited September 12, 2023 by Vodka2014 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted September 12, 2023 Author Share #662 Posted September 12, 2023 Just now, Vodka2014 said: I am there no what is the password for this ? tc / P@ssw0rd 1 Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted September 12, 2023 Share #663 Posted September 12, 2023 (edited) Hi @Peter Suh Please see the attached. I removed the MAC Addresses from the files. Thanks for the help and I really hope you find what has gone wrong here. Let me know if anything else is needed. linuxrc.syno.log dmesg Edited September 12, 2023 by Vodka2014 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted September 12, 2023 Author Share #664 Posted September 12, 2023 53 minutes ago, Vodka2014 said: Hi @Peter Suh Please see the attached. I removed the MAC Addresses from the files. Thanks for the help and I really hope you find what has gone wrong here. Let me know if anything else is needed. linuxrc.syno.log 8.3 kB · 2 downloads dmesg 69.75 kB · 2 downloads There doesn't seem to be anything special related to the mpt3sas module. You can find out by just following the mpt2sas and mpt3sas keywords in these logs. And, the mpt3sas module used is from ARPL, I will remount and distribute the modules I recently compiled for TCRP. The module version will be v1.55. When the module version is confirmed in the link below Please build the loader again. https://github.com/PeterSuh-Q3/arpl-modules/releases It is likely to be applied in about 3 to 4 hours. Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted September 12, 2023 Share #665 Posted September 12, 2023 (edited) 13 minutes ago, Peter Suh said: There doesn't seem to be anything special related to the mpt3sas module. You can find out by just following the mpt2sas and mpt3sas keywords in these logs. And, the mpt3sas module used is from ARPL, I will remount and distribute the modules I recently compiled for TCRP. The module version will be v1.55. When the module version is confirmed in the link below Please build the loader again. https://github.com/PeterSuh-Q3/arpl-modules/releases It is likely to be applied in about 3 to 4 hours. Thanks alot. So i will rebuild it the same way as i did with TCRP With Friend and the same settings for the HBA. Same Model as well etc.. Keep you posted once done thanks alot Edited September 12, 2023 by Vodka2014 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted September 12, 2023 Author Share #666 Posted September 12, 2023 34 minutes ago, Vodka2014 said: Thanks alot. So i will rebuild it the same way as i did with TCRP With Friend and the same settings for the HBA. Same Model as well etc.. Keep you posted once done thanks alot v1.55 released. https://github.com/PeterSuh-Q3/arpl-modules/releases/tag/v1.55 1 Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted September 12, 2023 Share #667 Posted September 12, 2023 (edited) 36 minutes ago, Peter Suh said: v1.55 released. https://github.com/PeterSuh-Q3/arpl-modules/releases/tag/v1.55 Never mind it just took a long time to connect. Load Built and now rebooting so lets see. Edited September 12, 2023 by Vodka2014 Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted September 12, 2023 Share #668 Posted September 12, 2023 (edited) Hi @Peter Suh It is still in the same state. "System Getting Ready" Please Log In later What is the next steps for this please. It must be able to see the disks somehow since it showed me to Recover again and the lights on the controller was blinking. Is there a way to Downgrade, Move back to the SATA Controller ? How do i know if there is still data on my disks since i cannot see them as it seems it is not loading after reboot. It is strage that it worked once when i upgrade and never again so far. Edited September 12, 2023 by Vodka2014 Quote Link to comment Share on other sites More sharing options...
asaf Posted September 12, 2023 Share #669 Posted September 12, 2023 6 minutes ago, Vodka2014 said: Hi @Peter Suh It is still in the same state. "System Getting Ready" Please Log In later What is the next steps for this please. It must be able to see the disks somehow since it showed me to Recover again and the lights on the controller was blinking. Is there a way to Downgrade, Move back to the SATA Controller ? How do i know if there is still data on my disks since i cannot see them as it seems it is not loading after reboot. It is strage that it worked once when i upgrade and never again so far. You can easily boot from an Ubuntu flash drive and see what's on the disks. Or take out the disks and check them on another PC. The disks are sliced into a bunch of partitions. Most probably the partition with the data is OK. It's just the partition with the DSM that's broken. Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted September 12, 2023 Share #670 Posted September 12, 2023 1 minute ago, asaf said: You can easily boot from an Ubuntu flash drive and see what's on the disks. Or take out the disks and check them on another PC. The disks are sliced into a bunch of partitions. Most probably the partition with the data is OK. It's just the partition with the DSM that's broken. Do you have some steps on how to load this once i get Ubuntu Loaded ? As i do not want to break this if i do this. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted September 12, 2023 Author Share #671 Posted September 12, 2023 Hi @Peter Suh It is still in the same state. "System Getting Ready" Please Log In later What is the next steps for this please. It must be able to see the disks somehow since it showed me to Recover again and the lights on the controller was blinking. Is there a way to Downgrade, Move back to the SATA Controller ? How do i know if there is still data on my disks since i cannot see them as it seems it is not loading after reboot. It is strage that it worked once when i upgrade and never again so far.To me, it seems like the DSM is messed up rather than the disk being in an abnormal condition. It would be better if I had a side job, but I don’t think that’s the case. I recommend reinstalling DSM. This will prevent data partitions from being overwritten. Only the system partition will be initialized. Please enter “J” within 7 seconds during FRIEND boot. After a while, you will be able to reinstall DSN.Sent from my iPhone using Tapatalk 1 Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted September 12, 2023 Share #672 Posted September 12, 2023 (edited) 26 minutes ago, Peter Suh said: To me, it seems like the DSM is messed up rather than the disk being in an abnormal condition. It would be better if I had a side job, but I don’t think that’s the case. I recommend reinstalling DSM. This will prevent data partitions from being overwritten. Only the system partition will be initialized. Please enter “J” within 7 seconds during FRIEND boot. After a while, you will be able to reinstall DSN. Sent from my iPhone using Tapatalk Thanks alot and i apricate it . So when i use the WebUI it will and ask me to load again. I will do 7.2 Update 1 .pat that correct ? Hi @Peter Suh I am now getting a message No Disks Detected. Should i change to DS918 or something else that supports an HBA ? Edited September 12, 2023 by Vodka2014 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted September 12, 2023 Author Share #673 Posted September 12, 2023 26 minutes ago, Vodka2014 said: Thanks alot and i apricate it . So when i use the WebUI it will and ask me to load again. I will do 7.2 Update 1 .pat that correct ? Hi @Peter Suh I am now getting a message No Disks Detected. Should i change to DS918 or something else that supports an HBA ? In that state, reboot the loader and reattach the two logs you sent earlier. 1 Quote Link to comment Share on other sites More sharing options...
Vodka2014 Posted September 12, 2023 Share #674 Posted September 12, 2023 Hi @Peter Suh As requested. based on what you stated i did find this: modprobe: ERROR: could not insert 'mpt3sas': Exec format error Thanks again linuxrc.syno.log dmesg Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted September 13, 2023 Author Share #675 Posted September 13, 2023 (edited) 11 hours ago, Vodka2014 said: Hi @Peter Suh As requested. based on what you stated i did find this: modprobe: ERROR: could not insert 'mpt3sas': Exec format error Thanks again linuxrc.syno.log 7.24 kB · 0 downloads dmesg 56.59 kB · 0 downloads The following error was confirmed in dmesg. The module has been stopped due to an error while loading. [ 6.292765] mpt3sas version 41.00.00.00 loaded [ 6.292933] mpt3sas 0000:07:00.0: can't disable ASPM; OS doesn't have ASPM control [ 6.293178] mpt2sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (6096876 kB) [ 6.293360] mpt2sas_cm0: doorbell is in use (line=4858) [ 6.293475] mpt2sas_cm0: _base_get_ioc_facts: handshake failed (r=-14) [ 6.293616] mpt2sas_cm0: _base_unmap_resources [ 6.293734] mpt2sas_cm0: failure at /tmp/input/drivers/scsi/mpt3sas/mpt3sas_scsih.c:16235/_scsih_probe()! The same phenomenon was confirmed on H310 using the same mpt3sas module. I am checking this with @wjz304 of ARPL-i18n. This issue is partially written in Chinese, but please use a translator. https://github.com/wjz304/arpl-i18n/issues/209 Edited September 13, 2023 by Peter Suh Quote Link to comment Share on other sites More sharing options...
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.