stanza Posted February 21, 2014 Author Share #101 Posted February 21, 2014 Have you tried to do a reboot after your update procedure?From which version are you trying to update? I suppose you're trying to apply over the 4.3 build 3810 my offline package of v4 update. Try again my offline method but without connection to internet. I did a fresh install on a new Microserver today Noticed when using the offline update there was a couple of segfaults happen when the control panel DSM update is selected Might have to install again and see if I can catch them . Quote Link to comment Share on other sites More sharing options...
djelusion Posted February 21, 2014 Share #102 Posted February 21, 2014 How would I go about upgrading to update 4 now that 4.3-3827 is available? I'm switching the update 4 file in but it won't install them as it see's the newer version is available.. quite frustrating! I managed to update by disconnecting from the internet and using the manual method. After you goto DMS update, it will say disconnected etc. I clicked manual DSM update then cancel and it somehow refreshed and used the local files. If you have problems updating because you have been infected (like i had), login via ssh and edit /usr/syno/synoman/webman/modules/ControlPanel/modules/upgrade.cgi then remove pipe '|' and the sed part off the file and save. what local files? and what dafuq does this mean??? then remove pipe '|' and the sed part off the file and save I opened the upgrade.cgi file in editor and nothing with sed and pipe | shows up, however a bunch of gibrish and other stuff appears. So far within the dsm gui i can download the 3827, but installing is another question.. so should I just do the download from the gui unplug it and cross my fingers?. Quote Link to comment Share on other sites More sharing options...
cqoute Posted February 22, 2014 Share #103 Posted February 22, 2014 Read the first post! the local files downloaded to do the update. "If you have problems updating because you have been infected (like i had)" means exactly that, if you had the same virus as me and couldn't update. then follow my instruction to fix it. If you don't see it, then most likely your not infected or you don't have the same virus/problem I had etc. in which case you don't need to do anything... simple as that. btw you can't update to 3827 from the gui and this has been mention a few times in this thread, you can only update to 3810 v4. Quote Link to comment Share on other sites More sharing options...
stanza Posted February 22, 2014 Author Share #104 Posted February 22, 2014 Ok the seg fault is to do with the cgi script of the update panel Something to do with libstc** Will have another go at trying to catch the actual output later As it only lasts a short time until the box reboots Can see it on console output eg monitor connected, but doesn't show on sash console output.... So copying the error and pasting it is hard. . Quote Link to comment Share on other sites More sharing options...
mackevin11 Posted February 23, 2014 Share #105 Posted February 23, 2014 btw you can't update to 3827 from the gui and this has been mention a few times in this thread, you can only update to 3810 v4. 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... Quote Link to comment Share on other sites More sharing options...
disruptorx Posted February 28, 2014 Share #106 Posted February 28, 2014 Its no only 4.2..I got infected and now have to upgrade to 4.3 3827. malware now runs httpd-log.pid and overwrites some core command modules (top,ls) with /lolz/jynx2.so. or atleast thats what im getting when I try to run ls or top Quote Link to comment Share on other sites More sharing options...
andyrav Posted February 28, 2014 Share #107 Posted February 28, 2014 Can someone please tell me how to Upgrade from 4.2 to 4.3 i have downloaded "XPEnology_3827-pre-v1.1_beta7.7z" does this include the fix? just dont know what to do next. HELP keep getting the following msg so might have been hacked DiskStation> top ERROR: ld.so: object '/lolz/jynx2.so' from LD_PRELOAD cannot be preloaded: ignored. top: error while loading shared libraries: libproc-3.2.8.so: cannot open shared object file: No such file or directory cheers Quote Link to comment Share on other sites More sharing options...
stanza Posted February 28, 2014 Author Share #108 Posted February 28, 2014 Can someone please tell me how to Upgrade from 4.2 to 4.3 i have downloaded "XPEnology_3827-pre-v1.1_beta7.7z" does this include the fix? just dont know what to do next. HELP keep getting the following msg so might have been hacked DiskStation> top ERROR: ld.so: object '/lolz/jynx2.so' from LD_PRELOAD cannot be preloaded: ignored. top: error while loading shared libraries: libproc-3.2.8.so: cannot open shared object file: No such file or directory cheers unpack the three files inside write synoboot-3827-pre-v1.1_v7.img to a usb stick boot from this new usb stick connect either by synologyassistant or try find.synology.com choose migrate choose 3rd option and feed it the beta7.pat file give new passwords and server name pray when it reboots, connect again and you might have to reinstall applications and users / settings etc. good luck . Quote Link to comment Share on other sites More sharing options...
nick w Posted February 28, 2014 Share #109 Posted February 28, 2014 God, is anyone able to help me So i followed this simple guide a page back: 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. CODE: SELECT ALL 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 I even had to sort these files out: 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 These steps below didnt seem to help so i had to revert these changes 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 It looks like i got the LOL virus, and now i am struggling to update I have follow the guide to the T, but when i get to the update screen, i cant for the life of me get the update button. Its getting to the point where im thinking of buying 2x 4tb drives to migrate off, to re-install DSM 4.3 to then migrate back.... Any help, i would be happy to throw some beer tokens your way! Quote Link to comment Share on other sites More sharing options...
stanza Posted February 28, 2014 Author Share #110 Posted February 28, 2014 I found the tricks to get it to work are Copy files to relevant places Check for update Select manual Cancel Go to your routers interface and disconnect from internet.... But leave router running so it gives out dhcp ip addresses etc Reboot xpenology box Log back into xpenology box and check for update again.... Wait It should now appear Run update and reboot When it comes back alive, log into router and re connect to internet Quote Link to comment Share on other sites More sharing options...
nick w Posted February 28, 2014 Share #111 Posted February 28, 2014 I found the tricks to get it to work are Copy files to relevant places Check for update Select manual Cancel Go to your routers interface and disconnect from internet.... But leave router running so it gives out dhcp ip addresses etc Reboot xpenology box Log back into xpenology box and check for update again.... Wait It should now appear Run update and reboot When it comes back alive, log into router and re connect to internet Thanks for the reply but i think i may be in a worse state since tinkering... Still my resource monitor is broken, think thats from the LOL Virus Now when i click updateDSM in control panel, it says no internet connected, you select ok, then the update window goes. BAD TIMES Quote Link to comment Share on other sites More sharing options...
stanza Posted March 1, 2014 Author Share #112 Posted March 1, 2014 If your going to blow it away, Might as well download 3827 beta7 and try updating that way (choose migrate) . Quote Link to comment Share on other sites More sharing options...
nick w Posted March 1, 2014 Share #113 Posted March 1, 2014 Will the keep the data on my volume (8tb = 2x 4TB drives). What would you suggest? Thanks N Quote Link to comment Share on other sites More sharing options...
stanza Posted March 1, 2014 Author Share #114 Posted March 1, 2014 Should do of you select migrate... But as always.... Backup 1st just in case . Quote Link to comment Share on other sites More sharing options...
cliffordsimak Posted March 6, 2014 Share #115 Posted March 6, 2014 Hello! Sorry for the english I'm using google translate. Yesterday I installed DSM 5 beta on DS713 +, this turned into another, much better! But appeared a problem, searching the internet I found that it was a virus, this must have been on DS for long. After the update it started to present an error message every command, to remove the problem I did the following: Login as root, put a # before the export LD_PRELOAD .... DiskStation> cd / volume1/homes/admin / DiskStation> vi. Profile # export LD_PRELOAD = / lolz/jynx2.so export PATH=/opt/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin ~ Quote Link to comment Share on other sites More sharing options...
samtch Posted April 7, 2014 Share #116 Posted April 7, 2014 Hello, I have successfully updated but , after reboot the virus still runniung. Do i need to delete the file myself? Or the system will do this automatically? Quote Link to comment Share on other sites More sharing options...
andywhit Posted April 8, 2014 Share #117 Posted April 8, 2014 You will need to remove the virus yourself. Have a look here for some clues -> http://blog.jandorsman.com/blog/synolog ... -preloaded The author of that article doesn't seem to edit the rc.local file to remove the creation of a bitcoin mining process so check that also. Quote Link to comment Share on other sites More sharing options...
TiNuuZzz Posted May 10, 2014 Share #118 Posted May 10, 2014 Hello, I running 4.3-3810 on a HP NL36 Microserver. After a power outage, I can't access any service on the station except couchpotato, the default landing page of the webserver and the personal photostation. SSH doesn't work, Management Web on both port 5000 and 5001 don't work, also SMB shares are not accessible. Is this also the result of the virus ? I also tried to connect to the console with a Logitech S510 wireless keyboard, but no reaction on keyboard trikes. Is this a comparability issue with the keyboard or also the virus at work. Quote Link to comment Share on other sites More sharing options...
athlonit Posted May 16, 2014 Share #119 Posted May 16, 2014 This virus, at least the one I encountered was very nice and made me some backups. The original upgrade.cgi was renamed to upgrade2.cgi. so: cd /usr/syno/synoman/webman/modules/ControlPanel/modules/ mv upgrade.cgi upgrade.cgi.bad mv upgrade2.cgi upgrade.cgi This restored update capability. Quote Link to comment Share on other sites More sharing options...
CorzD Posted September 23, 2016 Share #120 Posted September 23, 2016 Bloody champion!! Sorted, although the Select All link puts in your server name 'MicroDS2' in the string. That confuses it 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.