Jump to content
XPEnology Community

filippo333

Member
  • Posts

    156
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by filippo333

  1. On 9/24/2018 at 11:19 PM, dh22r said:

    nope ... on the migration/update page to DS918+, i  chose to keep my existing data & configs when asked.

     

    Currently using the DS918+ loader (was previously using the DS3615xs on my i3 baremetal) and so far it's a mixed bag. Windows 10 1809 installs fine, whereas Ubuntu and Xubuntu boot but won't install. I can see and format the disks without a problem, but as soon as I get to the disk selection step of the installer, the setup window goes into an infinite loading screen. It doesn't matter if I switch the disk mode from VirtIO to SATA or IDE the result is the same.

    CentOS has it the worst, using the minimal installation ISO I get a kernel panic and there is no way around it that I was able to see.

     

    The official compatibility list is quite out of date, I did try a certified build of CentOS but get the same problem. VMM might be putting some incompatible instruction in the Qemu VM config or maybe it's just really broken (which I find hard to believe). I'm lead to believe that this is the case as in my previous post I mentioned that enabling CPU compatibility mode with VMM Pro resolved the issue whilst on my DS3615xs loader (in which VMM was even more broken than it is on the loader I'm currently using ;) )

    • Sad 1
  2. 4 hours ago, dh22r said:

    just an update ...

     

    i'd forgotten to mention the above T30 issue was under DS3617sx.

    once i'd upgraded (sidegraded?) to DS918+, no issue running linux via VMM.

     

    weird?

     

    dhrr2

     

    Does changing model require a re-import of your data? It's possible VMM is fine tuned for the CPUs it's designed for. This is likely why people running as a DS3615xs and DS3617xs have no issues with VMM on enterprise Xeon hardware (as far as I know).

  3. 3 hours ago, filippo333 said:

    Yeah I'm getting the exact same thing, Windows also gives me a "kmode exception not handled" BSOD. It seems like some sort of Synology kernel incompatibility. Though the odd thing is the beta didn't have this problem when I was first testing it out on my bare-metal NAS.

     

    Update: After enabling Core 2 Duo CPU compatibility for the VM (only available with the pro version of VMM) it works perfectly. Unfortunately this isn't an option for most people (me included) as it requires a valid S/N and MAC combo to obtain a trial and or purchase a VMM pro license for $130.

     

    Maybe there's some way to force this instruction set in the hyper-visor without a license?

  4. 5 hours ago, Polanskiman said:

    If you are using 3615xs then keep using that. Don't really see the point in using 918+ unless you have a specific set of hardware which is close to the original ds918+

    I recommend you read the FAQs and have a look at the past tutorials I made. that should provide enough information on the DOs and DONTs.

     

    edit: I just realized there is no custom extra for 3615xs. Then yes you can try using ds918+ see if that works for you with the custom extra ramdisk.

     

    Agreed, it's worth pointing out that the DS3615xs is based off the regular consumer i3 architecture whereas the DS3617xs is Xeon based. Obviously if you're not using a Xeon of that generation then it's recommended not to use that specific config.

  5. 11 minutes ago, simoareva said:

    Tested on a VM on a ESXi 6.7 on a Gen8 with Xeon E3-1220 V2 and it is not working. It gets stuck on this screen (as expected) but the network interface is not recognized so i am not able to trigger the setup (and yes i selected the E1000 as network card). I think it's dependant on the instructions library missing on older CPU like someone said before.

    jun103a2.PNG

     

    Yeah I have the exact same problem when running the loader from VMware Workstation 12. No network or disk activity whatsoever, not tested on baremetal hardware myself.

  6. Because my NAS install DSM 6.2 automatically, it's not visible on my net, now :-(
    So, I'm very impatient to read about you !
    Thanks for your wonderful work !
    Best regards
    As far as I know your system is bricked. Major releases such as going from 6.1 to 6.2 almost always cause problems.

    Always check the forums before doing any updates. Thus far, we need a loader specifically for 6.2 compatibility.

    Sent from my ONEPLUS A5000 using Tapatalk

  7. That's a very good question, I'm sure there are many others including myself that have a dedicated Synology box. Anything that makes Xpenology more plug and play is certainly good news!

     

    I know DSDT patching is what is used in the Hackintosh world to make regular PCs more in-line with Apple hardware. I'd also be interested to know what validity checks exist on genuine Synology hardware. Although I'm pretty sure the devs would want to keep it under wraps to ensure Synology don't catch onto our patching ways!

  8. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.1.6-15266 Update 1
    - Loader version and model: Jun's Loader v1.02b - DS3615xs

    - Using custom extra.lzma: NO
    - Installation type: ASUS H110I-Plus (Skylake)
    - Additional comments: Reboot required, takes longer to install compared to previous updates ~3-4 mins.

  9. You can also get Intel X520-DA cards dirt cheap from China. If you don't mind waiting a few weeks for them to arrive, then they're literally 2-4 times cheaper than getting them locally.

     

    I've got two, one in my desktop and the other in my Xpenology box. Both work out of the box and I get around 400-450MB/s throughput copying files from a block-level formatted iSCSI connection (1x SSD drive). I also get just over 2x the performance out of my 3-drive SHR array (7200RPM drives) going from 110MB/s to around 240MB/s.

     

    I highly recommend the Intel cards as they "just work" with no configuration whatsoever.

  10. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.1.5 15254 - Update 1
    - Loader version and model: Jun's Loader v1.02b - DS3615xs

    - Using custom extra.lzma: NO
    - Installation type: ASUS H110I-Plus (Skylake)
    - Additional comments: Reboot required. Update resets synoinfo.conf!

  11. 41 minutes ago, IG-88 said:

    if its so easy to compile a new kernel why did jun made the effort to patch the running kernel, a newly compiled kernel could support amd and even hyper-v but we dont see this

    i'd expect some protections to preventing things like that and for 6.2, i would not think to much about it, we will see when it got officially released by synology

     

    Hmm good point, let's just hope that the reason for Synology doing this is purely for modernisation and not as an attack on Xpenology. As we are after all niche and hobbyists.

  12. beside this if i open the kernel modules in a hex editor there is the following at the and of each module
     
    "...Synology SDG kernel module signing key...~Module signature appended~"
     
    could mean the modules to load have to be signed and i dont expect the signig key to be part of a open source kernel release
    so this might be a additional hurdel for a using dsm with other hardware


    I’ve done a bit of research as to why Synology would be signing their kernel modules. Could it maybe be to allow for Secure Boot as it seems to be a requirement for using this feature?

    I’m not sure if this is relevant but disabling secure boot may invalidate the need for requiring signed modules?

    If so this PITA hardening feature can be disabled with a simple kernel flag when recompiling the Synology kernel from source.

    http:// https://askubuntu.com/questions/773734/how-to-install-module-ko-module-without-kernel-signature-or-kernel-rebuild-in-ub


    Sent from my iPad using Tapatalk
  13. Just now, George said:

    Question, if I build the XPEnology now using the Jun loader. how difficult is it, or is not to switch to Quicknic's loader. Is it simply a case of building a new USB, swapping and rebooting ?

     

     

    I don't think anyone can answer that question right now since the loader currently isn't available. In theory if you use the same serial number, mac address and Synology hardware model (ie DX 3615xs), you should be able to just import your drives into a new loader.

     

    I managed to successfully import drives from my Xpenology box to my genuine DS 1515+ when I had one, without issues.

  14. 3 hours ago, George said:

    I'm going to stick my hand up for releasing the DS3615xs loader now... It might be selfish, but thats all i need, and can say we can give feedback now,

     

    " the fact that Synology seems to be signing modules which means" this does not good at alllll.

     

    G

     

    Honestly if Synology play that game and make it harder and harder, I'll move to a different OS entirely. Most people with an Xpenology either:

     

    a) Can't afford a genuine Synology system.

    b) Have a more powerful system compared to most of Synology's product range (my case).

     

    Synology should be smart and offer their OS at a price for third party systems rather than piss off people that wouldn't/can't use their hardware for various reasons. I'd pay good money for DSM personally.

     

     

×
×
  • Create New...