tontounest

Yes, the Xpenology is really only the Linux kernel with some mechanisms in-place to combat the checks done by the Synology OS, extra drivers and it emulates the device that has serial number. But the real problem starts when you download the PAT file and use the proprietary parts of the Synology OS on the box that wasn't licensed for it. Technically, in some countries its illegal to bypath the mechanisms that prevent you from running on a non-licensed hardware, so the bootloader would also be illegal.

Maybe. To be honest i dont know. My point is, is it worth to buy extra license and maybe one day lose it? No, it is not worth it to buy it for the pirated copy of Synology. Either go fully licensed or fully pirated.

There already is a bootloader for 6.1 -> 1.02a

Do you compile using their scripts/tools? It would've being great if you could write some instructions on what is needed to compile the kernel from source. I will arrange a Howto in the afternoon Much appreciated.

Do you compile using their scripts/tools? It would've being great if you could write some instructions on what is needed to compile the kernel from source.

bump

Some of us have Windows Server as the hosting server OS for one reason or another. I guess the alternative would be to run VMware workstation which would be extra.(unless pirated of course). Hyper-v comes free though and integrates nicely with the Windows ecosystem.

From what I understand you don't actually need any link aggregation for the SMB multichannel. It should work by simply having x2 or more network cards on your server and PC with different IPs for each nic.

It will not work! Don't attempt to upgrade to 6.1

Does your motherboard have a serial port?

Yes the router is in between and it doesn't allow to change the MTU. Direct access isn't possible, because I've configured the network settings manually Sure it is. You just need to match the subnet on your PC. For example if you set your NAS to 192.168.1.2, then simply set your PC to 192.168.1.3. No gateway or DNS ip is necessary for this.

I'd already change the MTU on my PC, but my router Fritzbox 7490 FW 6.80 doesn't seem to support this high MTU rate. SSH is not enabled I'll try to get a 2nd network adapter and hopefully this will allow me to access again. Thx wgk Is there a router in between pc and xpenology? Try also changing MTU on a router. Or try connecting directly to nas.

Change MTU on your PC to 9k or connect via ssh and type ifconfig eth0 mtu 1500 up

Линк убрали так как автором были замечены ошибки в 2.2.

Its only the sourcecode for some of the opensource packages, but not the kernel... I think what we are looking for is a HUGE txz file that is usually about ~1GB in size. That's the source for the kernel.

Has anyone had success with HP N54L and the AMD CPU? What error gives with build volume? Are you trying to build the volume as EXT4 or BTRFS? I have not seen BTRFS work yet in either a VM or a physical using DSM6. EXT4 works fine. Btrfs seems to work fine for me. I am running it inside vmware. http://imgur.com/a/ep6Ru

I don't think you can reduce number of disks in your setup, but you might be able to replace your 2TB drives with 4TB one at a time, rebuilding array each time you swap disks. However, it won't give you extra space. (You could probably extend your array if you replace all 2TB with 4TB though) The best way would be to backup data, build new array using 4x 4TB and move new data there. As far as I know, settings are stored on all hard drives that you initialize on Synology, so just initialize some old hard drive while x6 array is still plugged in. Remove x6 array, keep old hard drive, insert x4 disk to create new array, remove old hard drive. SSD caching works for me on a barebone setup with 1 and 2 ssds. Can't say I notice much of a difference though... maybe a little more snappy. You might notice better performance if you have multiple people download the same file that was already cached and you have LACP or 10 Gb to your switch.

Здравствуйте! Подскажите как решили свою проблему? Буквально вчера поменял настройки, и сегодня пропал вход на DS.И смотрю в сети его нет... Переустанавливать? Или есть другая возможность? Просто вернул на стандартное 1500. Менял обратно с другого компьютера. Через SSH/консоль можно поменять в /etc/synoinfo.conf и /etc.defaults/synoinfo.conf. Или временно поменять на 1500 ifconfig eth0 mtu 1500 и потом через веб морду изменить значение. Самое странное что на том компе где стоит хренология, нет галки для настройки jumbo frame и mtu и я точно их не менял со стандартных. В локалке хренология доступна, из вне на мобильных устройствах и других компах доступна Только вот один комп кочевряжиться и без прокси никак не хочет открывать страницу входе в DSM. А на том компе какой MTU выставлен ?

У меня что то похожее было после того как поменял значение MTU Jumbo Frames. Но проблема проявлялась внутри сети, а не извне как у вас.

all the details are back in the previous page viewtopic.php?f=2&t=15341#p63644 Yea, I read your previous posts. As far as I know iSCSI cannot take advantage of using load balancing, you need to setup MPIO to use multiple links to increase the throughput. The current SMB protocol used by Synology also cannot take advantage of load balancing(except for mode 0) because it doesn't support multi-threading.(Windows Server does though). So, the way I see it you are still getting 1Gbps throughput. Or, perhaps, you are using something else? Are you running tasks in parallel to max out the links? Not really an overkill anymore with ssd transfer speeds and all. I desperately need it for my network as my ssd raid0 can push 1600MB/500MB Read/Write and I am bottlenecked by the network.

Ok, but what protocols are you using to take advantage of all 4 pipes?

balance-rr mode wants to disagree with you. Also, technically, teaming does give you more speed in other modes as well. Problem is not many protocols are multithreaded . Balance-rr mode just splits packets between network cards no matter if protocol is single or multi-threaded.

What load-balancing mode are you using? Also, what protocol were you using between Syno and Windows Server to utilize 4 ports. Afaik, there is currently no support for multi threaded smb in syno. Did you have to do anything special for iSCSI? Thanks.