Hello,
Yesterday I updated my NAS F2.223 from 5.1.100 to 5.1.123.
Since restarting the NAS I can no longer access the webgui. The page does not load. The website is not accessible.
I have access via SSh and SMB. Docker is also still running in the background.
The support said only a new installation would help. It really has to be. Is there no other possibility. I'm afraid that my data will be lost.
The reinstall post says yes, remove all hard drives. I have 2 M2.NVME in there. How should I clean it during operation?
Please help.
Sorry for the bad English. Has been translated from German to English.
After updating to 5.1.123, WebGui cannot be accessed
- fmonster1283
- Posts: 5
- Joined: 20 Mar 2024, 21:49
Re: After updating to 5.1.123, WebGui cannot be accessed
We did not release TOS 5.1.100.
It may be due to incorrect version causing configuration issues.
Regarding this issue, we can only guess that there may be a library file error.
Please enter the following command and provide us with the output information:
It may be due to incorrect version causing configuration issues.
Regarding this issue, we can only guess that there may be a library file error.
Please enter the following command and provide us with the output information:
Code: Select all
ldd /usr/sbin/nginx
ldd /usr/sbin/php=fpm
ldd /usr/sbin/TOSDaemon
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
- fmonster1283
- Posts: 5
- Joined: 20 Mar 2024, 21:49
Re: After updating to 5.1.123, WebGui cannot be accessed
ldd /usr/sbin/nginx
linux-vdso.so.1 (0x00007ffcd8564000)
libdl.so.2 => /lib/libdl.so.2 (0x00007f49806ef000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f49804d1000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007f498029a000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f4980af0000)
libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007f4980060000)
libssl.so.1.1 => /usr/lib/libssl.so.1.1 (0x00007f497fde2000)
libcrypto.so.1.1 => /usr/lib/libcrypto.so.1.1 (0x00007f497f964000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f497f751000)
libgd.so.3 => /usr/lib/libgd.so.3 (0x00007f497f4e2000)
libGeoIP.so.1 => /usr/lib/libGeoIP.so.1 (0x00007f497f2ae000)
libc.so.6 => /lib/libc.so.6 (0x00007f497eefd000)
/lib64/ld-linux-x86-64.so.2 (0x00007f49808f3000)
libm.so.6 => /lib/libm.so.6 (0x00007f497ebb6000)
libatomic.so.1 => /lib/libatomic.so.1 (0x00007f497e9af000)
libiconv.so.2 => /usr/lib/libiconv.so.2 (0x00007f497e6cf000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f497e445000)
libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f497e239000)
libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f497e00f000)
libtiff.so.5 => /usr/lib/libtiff.so.5 (0x00007f497ddaa000)
liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f497db8a000)
libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0x00007f497d92c000)
libwebp.so.7 => /usr/lib/libwebp.so.7 (0x00007f497d67f000)
libmvec.so.1 => /lib/libmvec.so.1 (0x00007f497d455000)
linux-vdso.so.1 (0x00007ffcd8564000)
libdl.so.2 => /lib/libdl.so.2 (0x00007f49806ef000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f49804d1000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007f498029a000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f4980af0000)
libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007f4980060000)
libssl.so.1.1 => /usr/lib/libssl.so.1.1 (0x00007f497fde2000)
libcrypto.so.1.1 => /usr/lib/libcrypto.so.1.1 (0x00007f497f964000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f497f751000)
libgd.so.3 => /usr/lib/libgd.so.3 (0x00007f497f4e2000)
libGeoIP.so.1 => /usr/lib/libGeoIP.so.1 (0x00007f497f2ae000)
libc.so.6 => /lib/libc.so.6 (0x00007f497eefd000)
/lib64/ld-linux-x86-64.so.2 (0x00007f49808f3000)
libm.so.6 => /lib/libm.so.6 (0x00007f497ebb6000)
libatomic.so.1 => /lib/libatomic.so.1 (0x00007f497e9af000)
libiconv.so.2 => /usr/lib/libiconv.so.2 (0x00007f497e6cf000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f497e445000)
libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f497e239000)
libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f497e00f000)
libtiff.so.5 => /usr/lib/libtiff.so.5 (0x00007f497ddaa000)
liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f497db8a000)
libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0x00007f497d92c000)
libwebp.so.7 => /usr/lib/libwebp.so.7 (0x00007f497d67f000)
libmvec.so.1 => /lib/libmvec.so.1 (0x00007f497d455000)
- fmonster1283
- Posts: 5
- Joined: 20 Mar 2024, 21:49
Re: After updating to 5.1.123, WebGui cannot be accessed
ldd /usr/sbin/php=fpm
ldd: /usr/sbin/php=fpm: No such file or directory
ldd /usr/sbin/TOSDaemon
linux-vdso.so.1 (0x00007ffc36c93000)
libresolv.so.2 => /lib/libresolv.so.2 (0x00007fc66e4e0000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007fc66e2c2000)
libpam.so.0 => /lib/libpam.so.0 (0x00007fc66e0b6000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007fc66de7f000)
libdl.so.2 => /lib/libdl.so.2 (0x00007fc66dc79000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007fc66d93f000)
libm.so.6 => /lib/libm.so.6 (0x00007fc66d316000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007fc66d104000)
libc.so.6 => /lib/libc.so.6 (0x00007fc66cd53000)
/lib64/ld-linux-x86-64.so.2 (0x00007fc66d65e000)
ldd: /usr/sbin/php=fpm: No such file or directory
ldd /usr/sbin/TOSDaemon
linux-vdso.so.1 (0x00007ffc36c93000)
libresolv.so.2 => /lib/libresolv.so.2 (0x00007fc66e4e0000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007fc66e2c2000)
libpam.so.0 => /lib/libpam.so.0 (0x00007fc66e0b6000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007fc66de7f000)
libdl.so.2 => /lib/libdl.so.2 (0x00007fc66dc79000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007fc66d93f000)
libm.so.6 => /lib/libm.so.6 (0x00007fc66d316000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007fc66d104000)
libc.so.6 => /lib/libc.so.6 (0x00007fc66cd53000)
/lib64/ld-linux-x86-64.so.2 (0x00007fc66d65e000)
Re: After updating to 5.1.123, WebGui cannot be accessed
Sorry, I made a mistake.
It's not "php=fpm" but "php-fpm".
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
- fmonster1283
- Posts: 5
- Joined: 20 Mar 2024, 21:49
Re: After updating to 5.1.123, WebGui cannot be accessed
ldd /usr/sbin/php-fpm
linux-vdso.so.1 (0x00007fffed9f3000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007f35e25cf000)
libreadline.so.8 => /usr/lib/libreadline.so.8 (0x00007f35e2387000)
libncurses.so.6 => /usr/lib/libncurses.so.6 (0x00007f35e2146000)
libpq.so.5 => /usr/lib/libpq.so.5 (0x00007f35e1f01000)
libssl.so.1.1 => /usr/lib/libssl.so.1.1 (0x00007f35e1c83000)
libcrypto.so.1.1 => /usr/lib/libcrypto.so.1.1 (0x00007f35e1805000)
libiconv.so.2 => /usr/lib/libiconv.so.2 (0x00007f35e1525000)
libgmp.so.10 => /usr/lib/libgmp.so.10 (0x00007f35e12c4000)
libdb-5.3.so => /usr/lib/libdb-5.3.so (0x00007f35e0f61000)
libm.so.6 => /lib/libm.so.6 (0x00007f35e0c1a000)
libpcre2-8.so.0 => /usr/lib/libpcre2-8.so.0 (0x00007f35e09cc000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f35e07b9000)
libcurl.so.4 => /usr/lib/libcurl.so.4 (0x00007f35e0551000)
libldap-2.4.so.2 => /usr/lib/libldap-2.4.so.2 (0x00007f35e0311000)
liblber-2.4.so.2 => /usr/lib/liblber-2.4.so.2 (0x00007f35e0104000)
libresolv.so.2 => /lib/libresolv.so.2 (0x00007f35dfeee000)
libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0x00007f35dfc90000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f35dfa06000)
libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f35df7fa000)
libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f35df5d0000)
libonig.so.5 => /usr/lib/libonig.so.5 (0x00007f35df34a000)
libodbc.so.2 => /usr/lib/libodbc.so.2 (0x00007f35df0e9000)
libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x00007f35dee07000)
libnetsnmp.so.40 => /usr/lib/libnetsnmp.so.40 (0x00007f35deb83000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f35e29fb000)
libexslt.so.0 => /usr/lib/libexslt.so.0 (0x00007f35de970000)
libxslt.so.1 => /usr/lib/libxslt.so.1 (0x00007f35de73d000)
libgcrypt.so.20 => /usr/lib/libgcrypt.so.20 (0x00007f35de42e000)
libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x00007f35de21d000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0x00007f35ddefd000)
libdl.so.2 => /lib/libdl.so.2 (0x00007f35ddcf9000)
liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f35ddad9000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f35dd8bb000)
libc.so.6 => /lib/libc.so.6 (0x00007f35dd50a000)
/lib64/ld-linux-x86-64.so.2 (0x00007f35e2806000)
libldap_r-2.4.so.2 => /usr/lib/libldap_r-2.4.so.2 (0x00007f35dd2c3000)
libatomic.so.1 => /lib/libatomic.so.1 (0x00007f35dd0bc000)
libsasl2.so.3 => /usr/lib/libsasl2.so.3 (0x00007f35dcea4000)
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00007f35dcc60000)
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00007f35dc9a1000)
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00007f35dc778000)
libcom_err.so.3 => /usr/lib/libcom_err.so.3 (0x00007f35dc574000)
libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00007f35dc369000)
libkeyutils.so.1 => /usr/lib/libkeyutils.so.1 (0x00007f35dc165000)
linux-vdso.so.1 (0x00007fffed9f3000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007f35e25cf000)
libreadline.so.8 => /usr/lib/libreadline.so.8 (0x00007f35e2387000)
libncurses.so.6 => /usr/lib/libncurses.so.6 (0x00007f35e2146000)
libpq.so.5 => /usr/lib/libpq.so.5 (0x00007f35e1f01000)
libssl.so.1.1 => /usr/lib/libssl.so.1.1 (0x00007f35e1c83000)
libcrypto.so.1.1 => /usr/lib/libcrypto.so.1.1 (0x00007f35e1805000)
libiconv.so.2 => /usr/lib/libiconv.so.2 (0x00007f35e1525000)
libgmp.so.10 => /usr/lib/libgmp.so.10 (0x00007f35e12c4000)
libdb-5.3.so => /usr/lib/libdb-5.3.so (0x00007f35e0f61000)
libm.so.6 => /lib/libm.so.6 (0x00007f35e0c1a000)
libpcre2-8.so.0 => /usr/lib/libpcre2-8.so.0 (0x00007f35e09cc000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f35e07b9000)
libcurl.so.4 => /usr/lib/libcurl.so.4 (0x00007f35e0551000)
libldap-2.4.so.2 => /usr/lib/libldap-2.4.so.2 (0x00007f35e0311000)
liblber-2.4.so.2 => /usr/lib/liblber-2.4.so.2 (0x00007f35e0104000)
libresolv.so.2 => /lib/libresolv.so.2 (0x00007f35dfeee000)
libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0x00007f35dfc90000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f35dfa06000)
libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f35df7fa000)
libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f35df5d0000)
libonig.so.5 => /usr/lib/libonig.so.5 (0x00007f35df34a000)
libodbc.so.2 => /usr/lib/libodbc.so.2 (0x00007f35df0e9000)
libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x00007f35dee07000)
libnetsnmp.so.40 => /usr/lib/libnetsnmp.so.40 (0x00007f35deb83000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f35e29fb000)
libexslt.so.0 => /usr/lib/libexslt.so.0 (0x00007f35de970000)
libxslt.so.1 => /usr/lib/libxslt.so.1 (0x00007f35de73d000)
libgcrypt.so.20 => /usr/lib/libgcrypt.so.20 (0x00007f35de42e000)
libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x00007f35de21d000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0x00007f35ddefd000)
libdl.so.2 => /lib/libdl.so.2 (0x00007f35ddcf9000)
liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f35ddad9000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f35dd8bb000)
libc.so.6 => /lib/libc.so.6 (0x00007f35dd50a000)
/lib64/ld-linux-x86-64.so.2 (0x00007f35e2806000)
libldap_r-2.4.so.2 => /usr/lib/libldap_r-2.4.so.2 (0x00007f35dd2c3000)
libatomic.so.1 => /lib/libatomic.so.1 (0x00007f35dd0bc000)
libsasl2.so.3 => /usr/lib/libsasl2.so.3 (0x00007f35dcea4000)
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00007f35dcc60000)
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00007f35dc9a1000)
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00007f35dc778000)
libcom_err.so.3 => /usr/lib/libcom_err.so.3 (0x00007f35dc574000)
libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00007f35dc369000)
libkeyutils.so.1 => /usr/lib/libkeyutils.so.1 (0x00007f35dc165000)
Re: After updating to 5.1.123, WebGui cannot be accessed
It appears that the library is complete, possibly due to the influence of other unknown reasons.
Perhaps you could consider reinstalling TOS to restore use:
viewtopic.php?t=423
Perhaps you could consider reinstalling TOS to restore use:
viewtopic.php?t=423
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
- fmonster1283
- Posts: 5
- Joined: 20 Mar 2024, 21:49
Re: After updating to 5.1.123, WebGui cannot be accessed
Ok. Then I'll try it.
Can you use the M2 SSD during operation?
I installed 2 M2 SSDs where the system is installed.
Can you use the M2 SSD during operation?
I installed 2 M2 SSDs where the system is installed.
Re: After updating to 5.1.123, WebGui cannot be accessed
Perhaps you are talking about how to handle SSDs.
If you are using SSD as a cache for a volume, it is recommended that you cancel the cache before reinstalling TOS.
If you use the SSD as the system installation location or storage, you need to select "Restore Factory Settings" in the Control Panel System interface to reset the SSD's system partition. Then you can reinstall TOS.
Please note that if there is a prompt to "format/delete" the disk during the installation process, please confirm if there is any data on this disk. If there is any necessary data, please do not continue. Contact the technical support email or customer service window on the official website.
If you are using SSD as a cache for a volume, it is recommended that you cancel the cache before reinstalling TOS.
If you use the SSD as the system installation location or storage, you need to select "Restore Factory Settings" in the Control Panel System interface to reset the SSD's system partition. Then you can reinstall TOS.
Please note that if there is a prompt to "format/delete" the disk during the installation process, please confirm if there is any data on this disk. If there is any necessary data, please do not continue. Contact the technical support email or customer service window on the official website.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)