• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About marc_al

  • Rank
    Junior Member
  1. 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
  2. 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
  3. 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 possibi
  4. 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
  5. 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 ( : IP of the Iscsi target)- iscsiadm -m discovery -t sendtargets -p Returns the value (name of the target) 3) C
  6. 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.info1 mv /autoupd@te.info1 / 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
  7. 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 so
  8. Hello, Thank you for your answer. I didn't think about it Marc
  9. 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
  10. marc_al

    XPEnology 4.2

    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
  11. marc_al

    XPEnology 4.2

    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
  12. marc_al

    XPEnology 4.2

    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. 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:// ... usybox.git but it is for the tools and not the kernel. Thank you Marc
  13. 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
  14. 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
  15. 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)