Schnapps
-
Posts
603 -
Joined
-
Last visited
-
Days Won
1
Posts posted by Schnapps
-
-
No offense but if you guys can't figure out where to download the .pat file from the Synology website, you shouldn't try xpenology.
-
Yes! I have wrote those lines and did the upgrade several times for several colleagues
Sent from my iPhone using Tapatalk
Thanks for the confirmation.
One more question if I may, which PAT file do I use?
Looking at my old installation for 4.2 I used the DS3612 file, but I can't seem to locate the equivalent for version 5.
Use the DS3612xs pat file. All xpenology work is based mainly on that version.
-
Yes
The data won't be wiped but a backup is welcome
-
If the disks are RDMed in ESX, you can do a pass through in hyperv
-
Hi everyone,
After struggling a lot with Xenserver 6.2 and DSM (im not much of a linux user and i couldnt follow the command line instruccions in the post)
I manage to make it work!!
I was determined to test the HA feature in the DSM, and for that i needed 2 VMs with DSM, 1 in each XenServer in my lab enviroment. (2 Xenservers 6.2 with High Avaiavility). What i really like from Xenserver over ESXi is that for this HA feature in an ESXi enviroment i needed and extra VM o PC for the vCenter, and for XenCenter theres no need. But to the HA to be full, i wanted a HA storage too, without the need of extra phisical hardware, so i desperated wanted to DSM to work in a XenServer.
Said that, here is what i did (maybe is not the better way but it worked):
- 1. Download gnoboot_105_xpenology_5.0-4458_bootloader_X64_by_Poechi.iso from the
2. Download the DSM 5.0-4458 .pat file from Synology
3. Create a VM in XenServer, with a 100GB Disk, 512 Mb RAM, 1 vCore. DO NOT start the VM yet!
4. Mount the ISO Image in the VM's CDRom and configure CDRom as the first boot device
5. Start the VM
6. Choose the first option (not the option to install/upgrade) and everything should be looking good
7. Use Synology Assisstant to search for the new VM DSM
8. After finding the new VM DSM, right click and connect (it would open a browser to the IP of the DSM) or just use the Assitant's native Installation
9. In the installation menu DSM should see a vDisk connected (usually in that step appears that no disk was connected)
10. Follow the wizard to install the DSM, and everything should work like a charm
11. Reboot and let the boot process of Gnoboot to start with the first option
12. Continue DSM configuration
The only thing that might not be perfect is that in the VM should be always mounted the ISO image in the CDRom, but honestly, at that point for me it didnt matter.I hope this would help someone.
Regards.
Cae
PS=Excuse my english
Hi cae,
Thanks for this GREAT guide. I edited it a bit and made it a bit more user friendly.
Cheers mate!
-
Thank god its not effecting DSM 5. At least this has caused be to review my security settings on my NAS's. I will get my last 4.3 box updated soon, for now I have removed web/https access from the internet.
Useless mate! But good choice.
My suggestion is to block 5000 5001 ports in your firewall/cancel port forwards.
It's enough that the system is pingable on the internet the exploit just gets root permissions for the attacker and everything is installed automatically.
-
FreeNAS needs also a bunch of RAM to work (at least in the recommendation).
Didn't like it too much...
-
Hi,
Thanks to this guide, I'm now running nanoboot on my ESXi 5.1 perfectly.
Just one point is frustrating me: the vm is consuming around 500MHz of CPU all the time.
I can see that on vsphere client, even the guest system is idle (99,6% idle from a “top” command in the console), there is still 500MHz on the host. This is even more than a windows guest (around 100MHz on idle) 
Actually, I noticed this behavior at the end of the step 4, before installing DSM 5.0. So I guess something in nanoboot is over consuming CPU.
My host CPU is a “old” Intel Core 2 Duo. Do you think it can be relate to missing instructions or something?
I think 400MHz is default minimal usage in ESX
-
There will be always, something...
-
If you're using both v5 or v4 updated to the latest version, you're safe.
You could just isolate it from the internet and you'll be safe.
-
I think Xpenology will still use all cores, just the display is wrong.
Just check it
That's 100% corect!
You could check it by ssh-ing your nas and by running cat /proc/cpuinfo
-
Damn lucky chumps!
You managed to do this the elite geeky way: Fixing the client's issue and getting a perfect SMB NAS for free
Good luck in using it in the future guys and thanks for sharing this sweet stuff with us!
Cheers!
-
What do you mean by "you don't need it"? I wonder if this fonctionnality works or not, not your point of view about it.
Well the SSDs are welcome when you have more than 12HDDs or lots of users accessing that NAS. Bloody hell! You actually don't need SATA III if you have only HDDs.
SSDs are used for caching files in transfer. For a home NAS you don't need to spend 200$ for something you like but don't use
Cheers
-
F5BJR, you're also right but this process needs some Linux skills, something that this community lacks at a large scale.
-
It sucks to be 1st (in this case)
But tell us more. Is all your data encrypted?
-
No offense but if you're not on the latest version and you keep your box on the internet, hacking like this is gonna happen all the time and you're kinda' asking for it.
-
Dude, your English sucks pretty big. I barely understand what's the problem.
Can you please rephrase a bit and type the full words? I don't think you'll do anything with the time you save by using sick acronyms.
Thanks
-
You don't need it and you'll need 2 SSDs of the same type
-
Try to update to nanoboot and latest DSM or keep your machine off the internet by deleting all port forwarding.
If this is true, it's pretty big shit!
-
It will take a while... Trantor is a bit away. You should do it yourself or find another way to compile those modules
-
NOPE, it didn't
-
This is what i have as an SSD: http://www.thessdreview.com/our-reviews ... sd-review/ and it doesn't work as it's full size SSD but the pins match. You can't mount a full size SSD due some stuff laying around and blocking the SSD
-
Still, i couldn't make USB working but that's anyhow nothing bad for me. I'm not using it
-
It seems for me that the Future of XPEnology/Nanoboot/Gnoboot probably looks dark...
I don't know why you're spreading rumors like this but currently i don't think you're doing any good. Currently Xpenology "is supporting" the last DSM and updates so I don't see any issues with it.
On a certain thing you're right, people are a bit more silent because everything is working.
XPenology is acting like any kind of community (physical or virtual). When everything is working fine, nobody really contribute a lot. When an issue appears and affects the community, everyone is trying to do something to help the community. I've been an active member of this forum since more than 1 year and I saw a lot of "external interference" but also people sticking to some ideas and making them work.
I know nothing about sancome but his work can be found originally at http://www.colafile.com/u/sancome. nanoboot.tk was his gift for europeans as colafile was slow as hell due to the fact it was hosted (somewhere far away) on the Asian continent.
Trantor is a bit busy, he is apparently building a house (yes he's human!
) and he has a lot of work to do. I guess once winter will come or the house will be finished he could be a bit more activeGnoBoot is probably watching silently xpenology. Nobody actually knows who was it (not he or she yet
)Andy is also silently watching over xpenology and as long as the community is active and we're not stuck to any kind of ancient 4.ish DSM version, he's also ok.
Cheers!
DSM 5.0-4458 to 5.0-4493
in Archives
Posted
Yes it is. C'mon guys, use the damn search!