mackevin11

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mackevin11

  • Rank
    Newbie
  1. DSM 5.0-4458 Update 2 works perfectly here! First used trantor, now using gnoBoot, works pretty nice actually:D
  2. When I do ip.adr.ess.ss:port (replaced by my ip/port ofcourse) I got: Uh-oh, something went wrong: tls: oversized record received with length 20291 And without the portnr: dial tcp ip.adr.ess.ss:443: i/o timeout
  3. Yes, but popular 'good' sites, like YouTube, Facebook, Apple, ect are not affected. I was planning to do an upgrade to DSM5.1 and this doesn't stop me from doing that. Now I use an http connection which isn't encrypted at all, no problems so far. I think there will maybe be an update soon (DSM5.2 or so?) which will probably fix the 'bug'.
  4. Hi guys, My HDD doesn't want to sleep anymore. I tried a lot of things (removing packages, change configurations, change settings) nothing worked. Even with the internet cable unplugged it won't sleep anymore. I want to reset the OS, in other words, reinstall the software but without losing data. I searched the internet, but I can only find that I've to press the reset-button on my Synology NAS. Ofcourse I don't have a reset-button on my custom-build XPEnology NAS. How can I reset it then?
  5. Ohw, sorry then... But can you tell me if 3810 v4 is safe to use now, or does it have the same bug? I get 3-5 different people that are trying to connect via SSH every day... The log tells me 'login fail' so at least they fail, but I'm still worried about it...
  6. A week ago, I was running DSM4.3-3810 v1 but then I got that stupid 'lolz' virus (similar to the PWNED virus). I've successfully removed it and have updated my DS to DSM4.3-3810 v4. The security fix is only available in 4.3-3827, or not? Is there already a trantor 4.3-3827 version for my XPEnology NAS?
  7. I finally succeed to update to 4.3-3810 v4. Is this version safe or do I need to update to 4.3-3827? I do not want that virus again on my NAS! What I did (for other people having issues, its already described in parts in this thread, but again:) - Download the DSM 4.3-3810 v4 package from Trantor (see first post). - Unzip it (Mac: Stuffit Expander, Windows: WinRAR) - Make a directory on volume 1, called 'public' (as described) You can do this with SSH or in the GUI SSH: mkdir /volume1/public GUI: >ControlCenter >SharedFolders >Create (name it public, give at least the admin read/write permissions) - Copy the files 'autoupd@te.info' (<- thats a file) and '@smallupd@te.deb' (<- thats a folder) to /volume1/public by afp (or ftp) (just simply drag and drop it) Mac: Use AFP, Windows: use FTP - Move the files to their new location. cp /volume1/public/autoupd@te.info / cp -a /volume1/public/@smallupd@te_deb/ /volume1/ - DISCONNECT YOUR ROUTER (or switch) FROM THE INTERNET - REBOOT THE NAS You can do this with the SSH or in the GUI SSH: reboot GUI: >reboot - Use the GUI: go to >ControlPanel >DSMUpdate - Click 'manual update' - Click 'cancel' (Now you need to see the 'update now' button) - Click that button It tells you the update would take 10 - 20 minutes, well, mine was finished in 2 minutes... Just click 'ok' and wait a few minutes. When de update is finished the GUI will automatically refresh and your NAS is ready to use again. (You can check what version you have on the systeminfo page). Do not forget to reconnect your router again:D
  8. Successfully stopped all process called lolzm, lolzb, synolog (killall lolzm lolzb synolog) Successfully deleted S99p.sh (main script that start 'lolzm' 'lolzb' and 'synolog' when booting) Successfully located and deleted the /lolz folder and its contents. Successfully deleted /opt/bin (where some modified versions of ls kill top ps where located) Successfully deleted /etc/ld.so.preload Successfully moved /usr/syno/synoman/webman/modules/ControlPanel/modules/upgrade2.cgi Successfully moved /usr/syno/synoman/webman/modules/ResourceMonitor/rsrcmonitor3.cgi Successfully moved /usr/syno/synoman/webman/modules/ResourceMonitor/top2.cgi Now trying to update, but I don't know how to? I can't just use the Synology software can I? (downloaded with 'DSM update' in the menu) I downloaded it, but I'm not sure to install it. I'm still running 4.3-3810 (v3?)
  9. Successfully stopped all process called lolzm, lolzb, synolog (killall lolzm lolzb synolog) Successfully deleted S99p.sh (main script that start 'lolzm' 'lolzb' and 'synolog' when booting) Successfully located and deleted the /lolz folder and its contents. Successfully deleted /opt/bin (where some modified versions of ls kill top ps where located) Successfully deleted /etc/ld.so.preload Successfully moved /usr/syno/synoman/webman/modules/ControlPanel/modules/upgrade2.cgi Successfully moved /usr/syno/synoman/webman/modules/ResourceMonitor/rsrcmonitor3.cgi Successfully moved /usr/syno/synoman/webman/modules/ResourceMonitor/top2.cgi Now trying to update, but I don't know how to? I can't just use the Synology software can I? (downloaded with 'DSM update' in the menu) I downloaded it, but I'm not sure to install it. I'm still running 4.3-3810 (v3?)
  10. @cquote I can not find the lolz folder. It seems like there is no lolz folder. Appelboom> ls / bin etc.defaults lib64 opt sbin tmp var.defaults volumeUSB1 dev initrd lost+found proc scripts usr volume1 etc lib mnt root sys var volume2 Appelboom> ls -lha /proc/11073 | grep exe lrwxrwxrwx 1 root root 0 Feb 18 12:03 exe -> /lolz/lolzm Appelboom> ls -lha /proc/11073/exe/ ls: cannot access /proc/11073/exe/: Not a directory Appelboom> whereis lolzm -ash: whereis: not found The process is coming from a folder that doesn't exist. I tried to start the S97, as you suggested, but with no results:( Appelboom> /usr/syno/etc/rc.d/S97apache-sys.sh start Start System Apache Server ..... -f /usr/syno/apache/conf/httpd.conf-sys (98)Address already in use: make_sock: could not bind to address [::]:5000 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:5000 no listening sockets available, shutting down Unable to open logs (98)Address already in use: make_sock: could not bind to address [::]:5000 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:5000 no listening sockets available, shutting down Unable to open logs (98)Address already in use: make_sock: could not bind to address [::]:5000 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:5000 no listening sockets available, shutting down Unable to open logs Recover to default setting (98)Address already in use: make_sock: could not bind to address [::]:5000 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:5000 no listening sockets available, shutting down Unable to open logs /usr/syno/etc/rc.d/S97apache-sys.sh: system httpd could not be started By the way, it seems like the ps-command is also blocked. Appelboom> ps ps: error while loading shared libraries: libproc-3.2.8.so: cannot open shared object file: No such file or directory Appelboom> readelf /bin/ps -ash: readelf: not found Appelboom> readelf /usr/bin/ps -ash: readelf: not found It just seems to me that I've got a much worse virus than the 'PWNED' virus where everyone is talking about.
  11. @cquote I can not find the lolz folder. It seems like there is no lolz folder. Appelboom> ls / bin etc.defaults lib64 opt sbin tmp var.defaults volumeUSB1 dev initrd lost+found proc scripts usr volume1 etc lib mnt root sys var volume2 Appelboom> ls -lha /proc/11073 | grep exe lrwxrwxrwx 1 root root 0 Feb 18 12:03 exe -> /lolz/lolzm Appelboom> ls -lha /proc/11073/exe/ ls: cannot access /proc/11073/exe/: Not a directory Appelboom> whereis lolzm -ash: whereis: not found The process is coming from a folder that doesn't exist. I tried to start the S97, as you suggested, but with no results:( Appelboom> /usr/syno/etc/rc.d/S97apache-sys.sh start Start System Apache Server ..... -f /usr/syno/apache/conf/httpd.conf-sys (98)Address already in use: make_sock: could not bind to address [::]:5000 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:5000 no listening sockets available, shutting down Unable to open logs (98)Address already in use: make_sock: could not bind to address [::]:5000 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:5000 no listening sockets available, shutting down Unable to open logs (98)Address already in use: make_sock: could not bind to address [::]:5000 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:5000 no listening sockets available, shutting down Unable to open logs Recover to default setting (98)Address already in use: make_sock: could not bind to address [::]:5000 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:5000 no listening sockets available, shutting down Unable to open logs /usr/syno/etc/rc.d/S97apache-sys.sh: system httpd could not be started By the way, it seems like the ps-command is also blocked. Appelboom> ps ps: error while loading shared libraries: libproc-3.2.8.so: cannot open shared object file: No such file or directory Appelboom> readelf /bin/ps -ash: readelf: not found Appelboom> readelf /usr/bin/ps -ash: readelf: not found It just seems to me that I've got a much worse virus than the 'PWNED' virus where everyone is talking about.
  12. I'm also infected by the virus. I've got the problem that when it slowed down, I thought about restarting the NAS. Now, when I want to login by web (port 5000, 5001), I can't... 'System is starting services, please wait.'. After 8 hours still the same message. I've read threads on the internet about it, it seems to be a mining-virus. It is not the 'PWNED' virus, but, similar, the 'lolz' virus. Got three different processes (or maybe even more); synolog, lolzm, lolzb I've tried to trace & delete the virus, but I can't even trace it:( Appelboom> pidof lolzm 11073 11072 11071 11070 11069 11068 Appelboom> ls -lha /proc/11073 | grep exe lrwxrwxrwx 1 root root 0 Feb 18 12:03 exe -> /lolz/lolzm Appelboom> ls -lha /proc/11073/exe/ ls: cannot access /proc/11073/exe/: Not a directory Well, I'm trying to reinstall my NAS (and keep my data (such as movies, music, documents, ect.!)) but since I can not login by web, I don't know how. The Synology solution for this problem is reinstall it after pressing the 'reset button'. But my custom-made NAS doesn't have a reset button What can I do now? Or is there a simple command for resetting the NAS? Are there other things I may have to try?
  13. I'm also infected by the virus. I've got the problem that when it slowed down, I thought about restarting the NAS. Now, when I want to login by web (port 5000, 5001), I can't... 'System is starting services, please wait.'. After 8 hours still the same message. I've read threads on the internet about it, it seems to be a mining-virus. It is not the 'PWNED' virus, but, similar, the 'lolz' virus. Got three different processes (or maybe even more); synolog, lolzm, lolzb I've tried to trace & delete the virus, but I can't even trace it:( Appelboom> pidof lolzm 11073 11072 11071 11070 11069 11068 Appelboom> ls -lha /proc/11073 | grep exe lrwxrwxrwx 1 root root 0 Feb 18 12:03 exe -> /lolz/lolzm Appelboom> ls -lha /proc/11073/exe/ ls: cannot access /proc/11073/exe/: Not a directory Well, I'm trying to reinstall my NAS (and keep my data (such as movies, music, documents, ect.!)) but since I can not login by web, I don't know how. The Synology solution for this problem is reinstall it after pressing the 'reset button'. But my custom-made NAS doesn't have a reset button What can I do now? Or is there a simple command for resetting the NAS? Are there other things I may have to try?