qwert_wayne

Ich habe DSM bei netcup mit kostenpflichtigem vmx flag am laufen. Vmx lassen die sich allerdings mit 2€ pro Kern auch sehr gut bezahlen. Das Problem mit juns Patch ist, dass 2 Images geladen werden müssen, wie hier auch schon gesagt wurde. Das Image mit dem Patch und ein Image mit den Daten. Bei netcup lässt sich aber leider nur ein qcow Image Laden. Hätte noch jemand eine Idee wie man das Problem lösen könnte? Zum basteln wäre ich bereit, aber ich sehe leider keine Möglichkeit. DSM möchte sich ja auf einem blockdevice installieren und das kann eben nicht dasselbe sein wie das System, das in /Dev/synoboot steckt. Ich würde mir sehr gerne das Geld für vmx sparen...

Thank you very much! I didn't think of extracting it twice. I suppose there are some uboot files in the first archive. Does anybody know how to extract the remaining part? I looked into jun's hack and found (as was mentioned somewhere in the forums) that he replaces modprobe. I guess he creates virtual devices to imitate a real synology hardware...? I will try to get to the point where DSM stops working on an unmodified system.

I'm trying to find out something about the inner workings of the DSM software and how jun's hack works. I extracted the pat file of a 918+ and looking around. There is a rd.gz file, which should be the ramdisk and the tool binwalker says that it is LZMA compressed. However, I cannot unpack the ramdisk neither can I mount it. Can someone tell me how I can open the file? And while I'm at it: Is there any website or post that explains how the boot process of the filestation works? Thank you for your help!

If anybody else ever comes across the same problem: I don't understand why, but v1.02b works with "-cpu Nehalem -enable-kvm" on my virtual server.

I found out that DSM works on the server if I disable kvm. Loading DSM -cpu Nehalem <- works -cpu Nehalem -enable-kvm <- does not work Loading debian image -cpu Nehalem <- works -cpu Nehalem -enable-kvm <- works How is that possible?

Could you please point out for me what that means? I have the same problem. 1.03 works, but in 1.04 the serial ouput is blank. Do I have to enable UEFI boot for the virtual machine?

Hello there, I successfully installed DSM 6.2 (loader 1.03b) on qemu on my laptop. I use the following line to start the virtual machine: qemu-system-x86_64 -drive if=none,id=stick,file=synoboot1.qcow2,format=qcow2 -device nec-usb-xhci,id=xhci -device usb-storage,bus=xhci.0,drive=stick,bootindex=1 -drive id=disk,file=system1.qcow2,format=qcow2,if=none -device ich9-ahci,id=ahci -device ide-drive,drive=disk,bus=ahci.0 -m 512 -device e1000,netdev=network0,mac=00:11:32:2C:A7:85 -netdev user,id=network0,net=172.20.0.0/16,dhcpstart=172.20.246.57,hostfwd=tcp::5001-172.20.246.57:5000 -smp cpus=2,cores=1 -enable-kvm -nographic Everything works fine. My goal is to get this running on a virtual server. It has nested kvm enabled and I can run other linux images (like debian or ubuntu) on qemu/kvm on the virtual server. DSM with the line shown above does not work though. I can see the menu showing up with the three boot options, and the happy hacking text shows up (i think at least) for an instance, but then the system hangs and I do not get any serial output (with the command as shown above, the serial output is dumped into the console). CPU utilization then stays near 100%. The only difference between the two systems is that I'm running antergos (arch) linux on my laptop and ubuntu 18.04 (also tried centos 7) on the server. Is there anything besides nested kvm that the virtual server has to support? Thank's for any help on this topic!