gnoboot

i think the GW is the firewall filter by keywords, dns and etc. more info: en.wikipedia.org/wiki/Golden_Shield_Project I found a very inconsistent transfer speeds on the cifs. speeds between 10mb ~ 110mb my test env: esxi 5.5, DSM 4.3 with A9 boot, vRAM 8GB. E1230 16GB RAM, 256GB SSD (data storage), WD 4TB disk (VMFS), WD 2TB(RDM), again thank you for your awesome job. Good for you! I'm getting 1mb flat using mpt2sas driver + lsi 9211-8i (IR RAID0) + SSD on alpha10.2. What version are you using?

You can send me Amazon gift card if you want. Does GW filter by IP or domain name? BTW, have you read my last post

[spoiler=] Though, I'm running AMD Turion X2.

Copy the new VERSION file to /etc and /etc.defaults in rd.gz, it should work I guess.

[spoiler=]Click the ADs on my blog or email me for donation;) Enjoy

It should be the same unless the vendor put another security checks on DSM... I'm compiling a dsgpl-5.0 kernel right now, and upload later. But it won't work until someone hexed synobios.

You have to `rm -f /lib/modules/*.ko` when upgrading to latest version.

may be the network drivers is not load. please check it! I replied to you on my blog, 10.x will not work either unless you provide the relevant information. Try alpha8, pm me if you don't have a copy.

Is your Ubuntu using MD Raid and LVM as well? Did you change its IO scheduler to noop? The vendor has customized a lot of underlying kernel subsystem for their product. It might be the reason (BUGS???) why we're not getting the same performance results from other Linux distro. DSM disk power saving feature will also contribute to performance degradation to other drivers (e.g. pvscsi, etc) that doesn't have this feature. Do you have other copies of older boot image? You might as well compare their results if it's ok with you.

I just tried 10.2, and Syno Assistant sucessfully installs DSM (disks recognized), however after final reboot, on :5000 there is still Syno Web Assistant with message "configuration lost" , am I doing anything wrong? (I set custom SN, tried booting/installing with menu_alpha.lst and menu_me.lst using DSM43. In last effort I tried even DSM5, however Syno Assistant failed with message I should install DSM43). If I will make at least this work I will give paravirtualization another shot... it is quite interesting by it self and at least I will learn something new Thanks for help First, you have to setup serial logging in XEN, and then boot to GRUB's debug option and send me the output. If that doesn't work for you, simply send me `dmesg` output or /.gnoboot/debug.log with debug enabled. Take note, you won't be able to see any console messages while doing this, add "console=tty0" at the end of GRUB kernel option to enable it. Do the same as mentioned above. Again, check the ADs on my blog or email me for donations.

Try using other controller, I was able to saturate 1Gb network link using virtual LSI parallel controller on alpha5. My worst was 1MB CIFS transfer using LSI 9211-8i VTd on alpha10.2. It should be getting more than that considering its SSD, will do more tests next week.

Will try to fix missing multimedia support in the next releases. I'm currently fixing reported kernel bugs. Thanks for testing XEN support in gnoBoot! I thought making disks appear /dev/sdxX would allow you to install it. Anyway, I'll fix that issue for you and you don't need to specify pygrub initrd option (its embedded in the kernel).

You need at least 2 disk to install DSM, disk1 (32MB+) and disk2 (8GB+). If you go below 8GB for disk2 (sda1) then you'll never proceed with the installation.

gnoboot-openvmtools-v5 available for download at my blog. Check out the ADs or email me for donations to continue gnoBoot development. Enjoy!

If you trust the developers/repackers here then its secure. That was the reason I went over and build my own kernel that can be installed using official pat file(installer) from the vendor. [spoiler=]My porns are very valuable to me and I don't want anybody to look at it. Kidding aside, just always keep a backup or have a test machine before you upgrade to another version.

My build and trantor's is still using the same dsgpl 4.3 kernel . So even if you install 5.0 it will never work because kernel doesn't support online resizing. You need at least kernel 3.3 and above to make it work. gnoboot> cat /etc/VERSION majorversion="5" minorversion="0" buildphase="beta" buildnumber="4418" smallfixnumber="0" builddate="2014/01/20" gnoboot> resize2fs resize2fs 1.42.6 (21-Sep-2012) Usage: resize2fs [-d debug_flags] [-f] [-F] [-M] [-P] [-p] device [new_size]

Sometimes, shutdown/reboot doesn't work from DSM. What I do is force it from command line. You're using an old kernel. You should be getting like below, get the latest zImage from my drive. gnoboot> uname -a Linux gnoboot 3.2.40 #1 SMP Wed Mar 5 18:05:38 CST 2014 x86_64 GNU/Linux synology_bromolow_3612xs kexec-tool is not a daemon (service). If you want to get rid of that messages, I think you need to install it on a baremetal.

Upgrading to 5.0 will not also work.

Nope, it has nothing to do with ffmpeg.

that's a known issue.

Use sfdisk that's also being use by DSM to install.

Subject: XPEnology gnoBoot run `cat /proc/mdstat` to see the raid rebuild status, it may take few hours/days to complete. How big is your volume? Are you using disk group?

I had similar problem with expanding volume of 7 4TB hdd-s in SHR with the 8th one. After much googling I decided that it is a problem of current DSM version (as it was also reported on original synology forums). Especially the version of e2fsprogs package with resize2fs in it which does not support FS resize above 16TB. It can make volume above 16TB, but not resize above this value. Here is its version info: XPEnology> resize2fs resize2fs 1.42.6 (21-Sep-2012) Usage: resize2fs [-d debug_flags] [-f] [-F] [-M] [-P] [-p] device [new_size] It is for DSM 4.3, latest releases. Did not checked om DSM 5.0 (as it happened 3 months ago). This version already supports online resize above 16TB. I think there's no need to update it. But a patch is needed to enable this feature in ext4 filesystem.

This should be fixed in the next release, removed the offending patch.