marc_al

Hello, I managed to do it like that : 1) Create a new vdi file and mount it (Temp HDD). 2) Create a new volume (volume2) and move all shares in it. 3) Move (cp -R all files from /volume1 to /volume2 4) Remove the old HDD and add a new one (New Volume1HDD that will be smaller). 5) Move all shares from the old volume2 (temp HDD) to /volume1 6) Copy all the applications from /volume2 to /volume1 7) Remove the temp HDD Marc

Hello, Can you please tell le if it is possible to resize a VDI file (virtualbox) that contains the OS (Volume1). I can't manage to do it. I have one HDD with only 1 GB used and it uses 34 Go. Here is what I have done at the moment 1) Empty the HDD (with the dd /dev/zero.....) Then Vboxmanage to compress (or VBoxmanage to clone and then compress). I still keep all my GB. 2) Use Clonezilla (but is says partitions unknown so the clone has exactly the same size as the original. Is there another method that would work? Thank you Marc

Hello, Personally I like the snapshot feature of ZFS. The only thing I use from synology is the download station (rarely) and vpn center (even less then the download station). Plex runs directly on Freenas... ZFS is supposed to be safer for the security of the datas.(I have copied a few TB from a synology (true Syno hardware) to my PC and I sometimes had a failure in a transfer (one or two files were wrong with the verification after the copy) and I never had the problem with the Freenas box. That is why I have chosen Freenas instead of Nanoboot on bare metal. (You also have the possibility to use Nanoboot in a virtual machine that will connects with iscsi to the Freenas and have the advantage of both worlds (but you lose the zfs snapshot for files) Marc

Hello, I have installed Nanoboot on a jail in a virtualbox jail (in Freenas). I can install Nanoboot and it runs perfectly, but I have seen that the ACPI shutdown doesn't work. Is a driver missing for the ACPI shutdown? Am I doing something wrong? Thank you Marc

Hello, I have managed to mount a ISCSI target but I have one problem The ISCSI share doesn't appear on the storage management as a normal hard drive. Is it possible to make it or am I missing something? Thank you Marc Here is what I did Modify the line node.startup vi /etc/iscsi/iscsid.conf node.startup = automatic 1) Start he daemon /usr/syno/etc/rc.iscsi start 2) Find the name of the target (192.168.1.4 : IP of the Iscsi target)- iscsiadm -m discovery -t sendtargets -p 192.168.1.4 Returns the value iqn.2007-09.jp.ne.peach.istgt:disk0 (name of the target) 3) Connect the target iscsiadm --mode node --targetname iqn.2007-09.jp.ne.peach.istgt:disk0 --portal 192.168.1.4:3260 --login This will create a device /dev/isda 4) Create a partition (with sfdisk so it will be GPT and more than 2To will be possible) sfdisk -N1 -z-1 -o8 -t83 /dev/isda 5) Format the partition mkfs.ext4 /dev/isda1 6) Mount in volume1 mount /dev/isda1 /volume1 When the syno restarts you must mount again the ISCSI drive so I have created a file /usr/syno/etc.defaults/rc.d/S99SynoISCSI.sh and I have put the lines /usr/syno/etc/rc.iscsi start iscsiadm --mode node --targetname iqn.2007-09.jp.ne.peach.istgt:disk0 --portal 192.168.1.4:3260 --login mount /dev/isda1 /volume1 so when the syno starts the ISCSI is auto mounted EDIT : Solved the problem with the 2Go partition

Hello, I managed to apply the update using the following method Download the update (but do not apply) is a SSH : sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1 mv /autoupd@te.info1 /autoupd@te.info Go back to the DSM Gui and click the Update button. For the insmod : I boot normally (no change in grub) and then I open a putty session and when I do the following command insmod /lib/modules/synoacl*.ko I receive the error insmod: can't insert '/lib/modules/synoacl_ext4.ko': unknown symbol in module, or unknown parameter For the ISCSI, I am looking for a guide (I will try http://www.cyberciti.biz/faq/howto-setu ... initiator/) as open iscsi is already installed and post if it is working (or not working). Thank you Marc

Hello, I have downloaded your image (it is really impressive because the pat from Synology works immediately ), and I have some problems there is no ACL on windows (right click on a file / directory and Properties there is ne Security page). You say do do that Try to insmod GRUB option synoacl_ext4.ko and synoacl_vfs.ko in 10.4. I have made a insmod in a putty session but is not working. I don't understand the method you recommend kernel /zImage insmod=vmxnet3 # cat > /etc/rc.local << EOF #!/bin/sh source /etc/rc.subr source /.gnoboot/modules.d/99-install.conf source /.gnoboot/modules.d/05-media.conf source /.gnoboot/modules.d/04-virt.conf source /.gnoboot/modules.d/03-wifi.conf SYNOLoadModules \$MEDIA_MOD SYNOLoadModules \$VMWARE SYNOLoadModules \$HYPERV EOF # chmod 755 /etc/rc.local What must I do ? I add a line (before the EOF) with the insmod ? Doing the insmod directly doesn't work. Also is it possible to mount a ISCSI target from another computer with your image ? For example I create a ISCSI share from my own server and I mount it as normal drive for the GNOBoot? Also I can't manage to apply the last update from synology (I downlaoded the last file and installed normally but there is a Update1 file that can only be applied from inside the DSM). Thank you for your time (I have clicked on every banner I was able to find on your web site). Marc

Hello, Thank you for your answer. I didn't think about it Marc

Hello, I would like to know how I can identify a drive that has failed with xpenology. For example if I have a raid 5 and one of the 4 HDD fails, (HD3 on the motherboard). What is the best way to find the failing one? (if I remove the wrong one I guess I will kill the complete volume)? Thank you Marc

Hello, You are right, the 4.1 won't work with the 4.2 (I tried and all the modules have a wrong version). The link I gave had the 4.2 that I used before but now the project has disappeared (error 404). Marc

Hello, I am sorry i didn't explain myself correctly. I am looking for the XPEnology files (and not the Synology files). Thank you Marc

Hello, I am trying to compile a new kernel for the 4.2 (I am still looking for what I am missing to make a kernel myself) and I have seen that the 4.2 source is not available anymore in github. https://github.com/nighthawk149/xpenology-4.2-kernel Can someone please tell me if it is removed or if it has been renamed? (I have an error 404). I have seen the project git://github.com/Vincentxiaojie/xpenolo ... usybox.git but it is for the tools and not the kernel. Thank you Marc

Hello, Thank you for your great guide. You should thank grayer that compiled the kernel. On the kernel I made myself the HDD must be in IDE and It seems that when you put one HDD you will see 2 of them in the syno assistant (the source code part for Hyper-v is not working correctly in the source code so you must merge the Hyper-v files with the files from a more recent kernel where Hyper-V is working but it seems I am missing something so I took the kernel from Grayer.. Marc

Hello, After the installation, if you have the error 22 you must put back the original vhd. You will see no error at all after that. You can also put the data disk in the IDE port for the installation and you won't have the error 22. I have no problem since the image has been created on my computer. The virtual machine is working since I posted the zip file and I have seen no error at all (I don't use it a lot because I am using a DS 210J ). I use XPEnology for testing only. Marc

For Hyper-v you must use a kernel that has support for the network adapter (as the image I put before) For all the machines you must put a correct MAC adress. (see the first port installing on Virtual box)

Hello, Personally I have this error too and I can't connect (DS Assistant) only if the MAC address has not been set correctly in the network adapter of VirtualBox. If you have this message it means that the network adapter is working. The MAC MUST be 00113208D62A

Hello, Here is what I did : I am working with Hyper-v and I have converted an existing img file to vhd. After that I mount the vhd with another linux (the Ubuntu that I used to make a new kernel) and I do the copy normally (with sudo cp when I don't have the rights because some files are protected). To see the checksum for grub, I simply boot normally and Grub complains about a checksum error (I do a print screen) and Grub says what ckecksum it expects to see so I modify it in the file (to be the same as the one in my print screen. The only problem I have at the moment is that when I put 2 HDD (the img loader file and a data vhd), xpenology sees 4 HDD when I compile the kernel myself. That is why I don't use my image but another one for Hyper-v. Marc

Hello, To make the boot file, personally, I take an existing one and then I replace the files in it by the ones I created before (for the Pat file). (so I take the kernel file, the grub file with the checksum and the syno checksum file. For the upgrade 4.1 --> 4.2 I can't help you I have no idea about it. Normally you can put the new img file as first boot drive instead of the old one (DSM4.1) and when you boot the syno and go to the IP address (DS Assistant can help) you will have a web site to do the upgrade instead of the login page. There you can choose the new pat and the upgrade will be done. I haven't tested it with data so I can't say if the data will stay or not. Marc

Hello, The main disk always need to be in IDE. This is necessary. You should use the old file I provided before. The new kernel I compiled myself has nothing better than the one from Grayer (OP). I only try by myself to understand how to compile a kernel. With the old version you can have the second HDD in IDE or SCSI (your choice). With the new kernel I made myself, the second HDD can only be in IDE (on SCSI it doesn't work), but the other drives can be SCSI. My version seems to see 4 HDD when there are only two. I can't compile the kernel source from Grayer (there are missing functions so I guess something is missing). Marc

Hello, I have managed to create a kernel by doing changes to the kernel source code but it seems that the SCSI driver is not working. When the new HDD is in the SCSI card the configuration doesn't work, if I put the HDD in the IDE port it is fine. A second HDD in SCSI is working perfectly too but the first installed HDD has to be in IDE (so 2 in IDE and one in SCSI) Marc

Hello, This image is nearly the same as the one with virtual box (viewtopic.php?f=2&t=3) The important thing is to put the MAC address (00113208D62A) You must create a PC with the first HDD that is in the image. After that you create a second HDD where you will put the data (it can be SCSI or secondary master). In the network you use the external network adapter (MAC 00113208D62A) it is very important or it won't work. You boot then with the DS Assistant you will see the synology (wait a moment to be sure the image is correctly booted). After that you can do a right click and choose Install then you choose the PAT file in the 7zip file. After that the syno will reboot. If you see a grub error 22 you put the vhd file from the archive again (as the first vhd) and you restart the virtual machine. the installer will continue the installation normally. For the SSD caching I have no idea. This image is only interesting for Hyper-V and I have ni idea if it is possible to use a SSD cache. Perhaps if you can make it work in Windows it will work but I am not sure. Marc

Hello, Thank you for the files. I have already made a new image file and Pat file to install on a new Hyper-v (with your zImage). Here is a file (7zip) with a vhd file and a Pat file). If you create a vhd file as secondary slave there is no problem. Il the hvd is as SCSI you will have an error 22 and after that you must restore the vhd from the zip file and reboot the machine. Thank you again for your time Marc Here are the files to use DSM 4.2 with Hyper-v https://mega.co.nz/#!bYZmGAZS!AgDSqhlmm ... ZQFpLtqa4Y

Hello, I will try by myself to add the 3.4 (and perhaps put the changes in git (I have no idea about how to do it but there is probably a way . If you have the zImage for the DSM 4.2, it would be great if you can put it here so I will be able to make the image for 4.2 (in case I have a problem doing the merge).. Marc

Hello, Since the 3.2 kernel (of linux), the hyper-v drivers have been changed by MS and they have left the staging area. Perhaps that is why they are unstable? How can you patch the kernel with the 3.4 (or even better 3.8 version of the drivers?) Do you simply copy the files in the directory you specified into the xpenology drivers? Do you have to change something in the Makefile? And after that you compile the kernel? Thank you Marc

Hello, I have managed to compile a DSM 4.2 In fact I used the git from the 4.1 with the 4.2 from syno. I have been able to mahe the img file (vhd format), but I have the same problem as you had : The DEC driver works but after a moment it is stopped and there is no network access. I have also seen that the hyper-v drivers are not working. A HDD in SCSI is not working and the network driver is not working too (the same problem as the one you had in the original post). I have selected Hyper-v and all the hyper-v options (network, scsi and the thitd one). Can you please tell me what I am missing? Did I miss one driver for hyper-v somewhere? Do I have to remove something for the Hyper-v driver to work? You have managed to solve the problem in your image Thank you Marc