Jump to content
XPEnology Community

ilovepancakes

Member
  • Posts

    175
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by ilovepancakes

  1. 8 hours ago, mcdull said:

    Mine will not tag subject "other than" Children.  Facial recognition and geotagging works.

     

    Geotagging I would expect to work on any CPU since it is just reading the metadata of the image file. Confirmed subject tagging seems to be working for me. I only uploaded 18 pictures to a test DSM VM but it tagged 4 of them as selfies and 1 of them (a picture of brownies) as "dessert". Can upload more later to continue testing.

  2. 9 hours ago, mcdull said:

    me 2 having the same issue.  My E3 1200v2 cpu would not boot the 918 image with network. 

    I am running 3615 fine but the moments app does not behave correctly because lacking of Intel CV feature in ESXi.  I am trying to switch to another image to see if it will fix this one.

     Confirmed that Moments app and face discovery/tagging seems to work correctly for me on 3615xs image with DSM 6.2 installed as VM on ESXi 6.7u1. Intel Xeon E5-2630 v2.

  3. 1 minute ago, mcdull said:

    me 2 having the same issue.  My E3 1200v2 cpu would not boot the 918 image with network. 

    I am running 3615 fine but the moments app does not behave correctly because lacking of Intel CV feature in ESXi.  I am trying to switch to another image to see if it will fix this one.

     

    Hmm, wonder if E5-2630 v2 will work right with Moments on 3615 image. I'll have to try, although I need to find a way to change the mac in grub.cfg so it doesn't conflict with my already running baremetal 3615 image. I can only get the 3615 to get an IP on ESXi if I don't change the mac in grub.cfg. Leaving all files as is works but then it conflicts with my other machine if both are turned on at same time.

  4. 1 minute ago, NeoID said:

    Pretty sure, I'm also running the 3615 image without issues, but I couldn't get the DS918 image to work until I tried it on a 6.gen intel CPU. I guess the boot image requires instructions that aren't present on earlier processors.

     

    Interesting, I never considered 5 years old to be too bad especially since 6.2 on 1.03 works. Would assume CPUs would be ruled out on a major release or something. Ahh well...

  5. 2 minutes ago, NeoID said:

    I could be wrong, but I think you'll need a newer CPU. Something from the same generation (or newer) as Intel Celeron J3455.

     

    Because the boot is based on the 918 you think so? I was able to get jun's 1.03b 3615 image to boot correctly on ESXi 6.7u1 and get an IP. So wondering what changed from 1.03b running 6.2 to 1.04 for running 6.2.1.

  6. 3 hours ago, NeoID said:

     

    What CPU do you have? Doesn't show up on the network on my i7-4770, but it works on a later 6.gen CPU from Intel.

     

    I have 2 Intel Xeon E5-2630 v2 @2.6 Ghz.

  7. I'm on ESXi 6.7u1 and can't get 1.04b 918 synoboot image to get an IP and show on network for install of PAT file. Synology assistant does not find the VM. And, my router is not seeing the MAC address hit the DHCP server. I have manually set the MAC of the VM to match the MAC shown in the grub.cfg file. I am on EFI boot, and I tried VMXNET3 and E1000e network adapters with same result, VM just doesn't get IP. Tried BIOS boot too just for kicks.

     

    Any ideas on how to get the network adapter working?

  8. On 8/12/2018 at 7:53 PM, flyingtrapeze said:

    a slightly different in details but in principle much much the same here.

     

    download ds3615 synoboot.img 1.03b using existing synoboot.vmdk from other posts.

    upload these 2 files into the datastore in ESXi 6.5 datastore where the new Xpenology vm will be created

    create a new vm using OS as Other, FreeBSD 64 Bit (this gives the choice of VMnet3 in nic later)

    remove the harddisk that get automatically put in by the template

    add a harddisk, SATA controller 0 slot 0 using synoboot.vmdk (which points to synoboot.img by reference), either dependent or persisent doesn't seem to make a difference

    add SCSI harddisks for NAS data

    nic get its mac address from synoboot.img so if you need to change the licence or mac, then editing this img file has to be done

    set the nic to vmnet3

    complete and power up

    using synology assistant to discover the vm

    connect and when prompt to install DSM, choose auto install from internet and 6.2 (without update x) will be installed

    after reboot etc etc, 6.2 update x can be installed.

    note: could not get the various 6.1 pat files to work, downloading directly from the internet worked a treat. success with both HP N36L and N54L

    can post screenshots if others are interested

     

    Followed this exactly but when the VM starts up I can't seem to find the DSM with find.synology.com or the Synology Assistant... I checked my DHCP server and the synoboot is not even getting an IP it seems... I do have VMXNET3 as network adapter and other VMs on the same port group and vSwitch work fine so I don't think it is my ESXi config... Any ideas?

  9. 19 minutes ago, MGD9000 said:

    I think you would be a lot better off running ESXI 6.7 you can run all the vms you want. But I'll still do the test for you.


    Sent from my VS501 using Tapatalk
     

    Haha, I had guessed you might say that. I am scared to admit, I know not much at ESXi. Never had a use for it, maybe up until now. Not that this is the exact proper place to ask, but I am assuming I can take two R710s and run them in some sort of HA with ESXi? So if one fails it switches over to the other and has everything backed up and stored on there?

     

    I guess I'm lazy because I wish I could just do this with Synology HA and still use VMM. So easy just to slap it all together and keep running. But I'm willing to learn ESXi.

  10. 2 hours ago, MGD9000 said:

    I have a Dell R710 coming in next Monday. I will test a bare metal install for you.


    Sent from my VS501 using Tapatalk
     

    Thanks that would be great! I am considering buying 2 and running it in Synology HA cluster. But I found out that while running HA you can't install and use Virtual Machine Manager, even if you don't want to use the HA features of that. You simply cannot backup your VMs through HyperBackup or regular HA cluster unless you have VMM Pro. But it's in beta and Synology says after Beta it will cost money... So on Xpenology it won't work because you need Synology account linked to buy a license. So that plane went out the door.

     

    Figured if the R710 works bare metal anyway I can just use it HA and forget VMM.

  11. 1 minute ago, IG-88 said:

    good to see that there are no new problems with this driver (there would be still the option to compile a new driver from external source i have laying around)

     

     

     

     

    thats why there is a comment at the end of the first psoting

     

     

    i can now edit the first post and on next release i will rewrite the first post and provide more information about the actual state in the first post of the thread

     

    Thanks for all your work here, it is greatly appreciated! Have another nice server now up and going.

     

    -Chris

  12. 22 hours ago, IG-88 said:

    did you try to insert my extra.lzma (v3.2)? you dont write that you have tryed

     

     

    I managed to get it to work with this version 3.2, I don't know why I thought I had an old version (3, maybe) and couldn't find 3.2. The system can use the cards now, but at first one port was only connecting at 100M speed but couldn't do 1000M. Since the other port was doing 1000M figured it can't be a driver issue and after fiddling with it and rebooting a bunch it started working stably at 1000M on both ports.

     

    All seems good now! Thank you.

     

    -C

  13. @IG-88

    Using a Dell PowerEdge 2900 III. Has Dual embedded Broadcom NetXtreme II 5708 Gigabit Ethernet NICs. Using Jun 1.02b loader the boot seems ok but cannot find NAS with http://find.synology.com or the downloadable synology assistant. Furthermore I don't see those NIC's MACs on network when doing a scan. And, they don't get IPs from DHCP server. Guessing the NICs are not compatible with this loader. Do any of your ramdisk mods or other mods support this NIC maybe? I couldn't find anything explicitly saying so.

×
×
  • Create New...