jokies
-
Posts
76 -
Joined
-
Last visited
Posts posted by jokies
-
-
Cheers, many thanks. Is gnoBoot the recommended pathway to 5 then, rather than Trantors release?
I can't say which is better since I tried only gnoBoot myself, but gnoBoot is updating very fast and many small glitches were eliminated.
Trantor's release is currently on DSM 5.0 beta, I don't know whether you can update it to stable DSM 5.0 release.
If you prefer Trantor's release, you may want to wait, since Trantor said he will release a newer version soon.
-
DSM is loaded into memory and very little IOPS was used after fully boot up because only if you change the configuration will the I/O happen.
Meanwhile I believe DSM was installed on every HDD initialized to avoid one HDD crashing cause system not booting up any more, that was how it was design and no you cannot choose which storage to install DSM on.
If you mean the bootable device you are using, that is just some Linux kernel DSM rely on, no I/O happen to it after DSM was initialized, put it on SSD won't boost your system speed.
Unlike ESXi and some other Server OS, since DSM is very small, most of the time it was fully loaded into your memory, you can even remove the bootable device after you fully boot your XPEnology if you wish.
-
So....
What with the fact that my DSM install has been misbehaving, and the recent Heartbleed issue, I figure now is a good time to update.
So first things first, I take a full backup of my data drive.
Then what? I'm presuming there isn't an 'upgrade path' as such, so which DSM5 install should I go for?
Trantor: viewtopic.php?f=14&t=2219
or:
gnoBoot: http://cyanlabs.co.uk/news/install-xpen ... thout-esxi
??
It 'looks' like the gnoBoot uses a later version of the pat file, but I'm unsure. I just want to update my server, but keep my current MAC addresses AND SERIAL number, or at least know how to change them back to what I am currently using after the install finishes.
If someone can guide me as to which install I am supposed to use these days I'll get on with it
Many thanks!
I never tried Trantor's DSM 5.0 but I can assure you Gnoboot's DSM 5.0 can update to the latest version of DSM (At the time of this post, it is DSM 5.0 update 2).
Gnoboot accept original pat file from Synology, if that is what you're trying to point out. Meanwhile Gnoboot use real MAC address and I myself do not know a way to change it. The serial number can be changed to whatever you like, Cyanlab already written a guide, you should read it.
Migrating to newer version using Gnoboot is a little tricky, you need to connect your XPEnology to a display in order to choose "gnoboot.me" while grub is counting (when u boot up use the new boot device), then choose "Install/upgrade DSM 5.0", then run your Synology assistant you will see your box showed up as "migratable", simply feed it with DSM 5.0 DS3612xs pat file from Synology official website and wait it to finish.
Then you can update it to DSM 5.0 update 2 from your Web UI, information about how to achieve this can be found within this forum.
Be warned! There are still chance you screwed up and see "DSM not installed" in your Synology assistant instead, proceed at your own risk.
-
That is loads of money...
I would suggest you go straight for some more professional solutions provided by DELL, HP, VMWARE or Oracle, you can obviously afford one of them, maybe even still get some money to spare.
With one of these enterprise grade server, man you can run almost dozens of DSM virtual machines or several linux server providing you jaw falling performance. DSM won't even be able to compare with it. On the other hand if you run DSM on it only, it's like bombing a fly with a nuclear.
-
I thought that the bitcoin problem was with 4.3 but NOT with 4.2 ?!
If I do update I think I might be worth me just going straight to DSM 5...
Of course if you wish you should go straight to DSM 5.0 because up to now DSM 5.0 update 2 is the only known version that is patched against miner and heartbleed security problems.
Yes, Synology is obviously not so good at making things secured, instead they made DSM 5.0 looked better...
----Update----
I realized that I should explain how miner and heartbleed would happen and in which situation should you seek for a way to solve them.
First of all, if your XPEnology's main ports are not exposed to the Internet, you do not need to worry at all. Here by main ports stand for 5000 and 5001 if you didn't changed them (If you enabled web station and yes, your port 80 and port 443 is also considered main ports), these ports provide access to the DSM Web UI. You need to be careful if you are using upnp or manual firewall policies to forward them to Internet.
Secondly, up to now, nobody reported any data lose because of these security problems, so you do not need to panic, although it might cause data leak, if your data interested hackers. Stop forwarding main ports to Internet and take your time to think about your next step. For example you may stay on/migrate to DSM 4.3 3827 update 1 with main ports blocked from Internet and wait for Synology to release heartbleed patch for it, this version is already patched against miner security problem.
Thirdly, as I had mentioned, the only version known that is patched against these problems is DSM 5.0 update 2, if you decided to migrate, read gnoboot's post carefully, make a new boot device using his *.img file and boot up, choose "gnoBoot.me" and then "Install/upgrade DSM 5" when grub is counting (connect a display to see them), run your Synology assistant and use unmodified DSM 5.0 DS3612xs *.pat file from Synology to proceed.
You will also find necessary information about how to upgrade to "DSM 5.0 Update 2" in this forum, use search function.
Good luck.
-
Thank you very much.
-
Damn... I thought the problem is gone but it is still there. It worked for the last two days but now it's gone again. Is it possible to do that by scripting or hardcoded in a file?
That sucks
The settings page are simply gone or they are greyed out?
The ShutDown and WakeUp settings are gone, like I never set up.
It seemed to be motherboard related, a few people reported their XPEnology can use this function without a glitch.
Most of them are using old motherboards with 965 chipsets with core 2 CPU on it.
Take a look at where the power plan settings file is located may help.
-
Sorry for the noob question.
Once SSH'ed into Disk Station as root, I was able to locate the VOLUME file. What is the syntax (how do you edit the value) to 1.
Thanks
After SSH to your diskstation, put in the following command exactly and press ENTER to enter text edit mode:
vi /etc.defaults/VERSION
move your cursor around until you find the row start with "smallfixnumber".
Then press "i" on your keyboard. Use backspace to delete "2", and press "1" on your keyboard. Now you finished modifying the file.
Press "ESC" and then press ":", "w" and "q" on your keyboard, followed by ENTER, the file is now saved with the change.
Go to your diskstation web UI, you should see it now display "Update 1" instead of "Update 2", otherwise something went wrong, try again.
-
Hi all,
I'm trying to update Transtor DSM 5.0-4418 Beta to 4458, I could not go thru the shell connection using Putty. When I execute the first command "sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1", I get the message "sed: /autoupd@te.info: No such file or directory"
So if I go back to the DSM GUI to install the update, I keep getting error that it can not access the temp directory (2). Please tell me what I'm doing wrong?
Thanks
The patch need to be downloaded first, then when it ask you whether you want to proceed and while updating do not power off your device, you ssh to your device, execute these command then go back to web UI, press "yes".
-
Damn... I thought the problem is gone but it is still there. It worked for the last two days but now it's gone again. Is it possible to do that by scripting or hardcoded in a file?
That sucks
The settings page are simply gone or they are greyed out?
-
i am having problems with access to nas using \\diskstation, after updating to dsm 5.0 gnoboot.
there are no problems using the ip directly, only \\diskstation.
do anyone have an idea to what is wrong?
Did you set custom netbios name?
Try set one.
-
Does 4.2 / 4.3 have an update to patch against HeartBleed, or is it only 5 that is getting patched?
Synology said later the patch for 4.3 will be released. Not sure whether it will be available for 4.2.
Since 4.2 there is already a security problem that hackers can easily turn your machine into a miner of Bitcoins, you should upgrade to 4.3 as soon as possible.
-
To those who had previously updated DSM 5.0 to update 2 before GMT Apr 9, your DSM is still affected by the heartbleed security problem.
In order to apply the newer version of the update, you need to edit /etc.defaults/VERSION via ssh, change "smallfixnumber" value from "2" to "1" and redownload the patch.
You can also see builddate here, if it is not "2014/04/09", then you need to take action immediately.
In order to apply the patch, you still need the magic small script to be runned after you download the patch and before you proceed.
Good luck.
The earlier DSM 5.0 update 2 is released Apr 3, which does not include the fix.
Don't forget to regenerate your SSL certificate, otherwise you're still threatened.
-
A few people said replacing original ones with proper S/N and MAC will get the DS cloud, myds DDNS and other cloud services to work, but I strongly don't recommend so.
On one hand, such action will open your XPEnology to the Synology server and sooner or later they will find out you're not a genuine Synology owner.
On the other hand, Synology cloud server will be overloaded thanks to XPEnology can be installed on almost any x86 hardware, and genuine Synology owner will not be happy, then they stop buying Synology devices, which finally result in Synology bankrupt.
Both are not something I would like to see.
So, please be kind and use some third party solution instead of quick connect and myds services.
-
Hi, Need some urgent help please
I have replace a faulty disk with a new one and after it has finished its repair/ parity checks etc is returns too
The Space is Degraded.
All my drives status say Normal and the smart check are ok.
It then does not have the option to repair again as Managed is grayed out.
running on a hp N54L
any ideas?
cheers
XPEnology is always having difficulty sorting out the proper disk slot, take look at them, but proceed with caution since rearranging your disks may result in DATA not accessible at all.
Also bear in your mind that the new disk have to be bigger or equal size to the old one.
It can also be possible another old disk is not stable, run full smart test one by one may reveal the problem.
-
Hi @ all,
my system was working great until yesterday. Referring to my pllan the system shutdown correctly yesterday evening. After I left my house today I was checking the cloud for a file but the system was down.
After I was back home I checked the system and after the reboot the energy saving plan settings were gone. No problem I thought and created a new plan. But after a reboot this plan was gone too. I've done nothing yesterday but the problem is still there. Could please anybody help me?
System: DSM 5-4458 update 2 / gnoboot 10.5
Greetz
Power plan obviously need some hardware support. I never tested on my DS713+ so I don't know what exactly hardware is needed. Maybe BIOS should be able to be modified within the DSM to support the function? Not quite sure.
But power plan obviously won't be supported if you are using virtual machine. Since they don't actually have a timer inside their emulated BIOS.
-
Thanks CtrlAltDel, whats the safest way to protect my data while doing the upgrade?
Back it up
I second this. If you made the new boot device, boot up and failed to see "migrate", instead "DSM not installed" showed up then you know you are screwed.
-
Why Synology have better interface while QNAP sales better? I think now we know why.
QNAP QTS is not affected, for your information.
-
Hibernating HDDs intend to make your HDDs live longer.
Hibernating the whole machine saves power.
However, hibernating the whole machine is not available for most 4 bays or more NAS models, since most of these are designed for enterprise use and should be powered on all the time.
-
No. Read the pinned threads carefully about how to make a newer boot device and migrate your data.
-
*bump*
anyone?
I don't think such function is even available on real Synology machines.
And it seemed having something to do with CPU functionality, what you said is very similar with how Intel describe their "S3" system state.
-
first, good idea CtrAltDel
after...
1 - Download update DSM 4.3-3827 from GUI
2 - sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1
3 - mv /autoupd@te.info1 /autoupd@te.info
4 - Update from GUI
and.... Same issue
No real error message but always in DSM 4.3-3810
I don't understand
You need to upgrade to trantor's DSM_4.3_3827 boot img first then you can apply small fix from web console other wise it won't work because your machine isn't a Synology and the boot img update won't apply.
-
you can do a robocopy within windows, or use a script in powershell for windows.
Never thought of pulling it from Diskstation to windows, Was thinking DSM pushing to Windows. Ill look into that. Any hints?
Enable SMB on your windows and mount it inside DSM to copy?
Or setup rsync on your windows. Too many ways. Since windows is almostly capable of any kind of server softwares.
I myself recommend robocopy or something likes that because it is always easier to config on a desktop environment.
-
Clearly this forum is growing- I see many posts of people asking if their system is compatible.
Can anyone help point me how to determine if a particular system will work?
Any help at all?
Probably works if the network card is from intel.
Upgrade possible from 4.3 3810++ (trantor) to 5.0 gnoboot
in Archives
Posted
Please refer to viewtopic.php?f=2&t=2863
The bootstrap will remain there, if I'm not making a mistake. Better ask others about it.