chege

Im not a guru, but as you figured it out it was mistake to upgrade from dsm 5.2 straight to 6.1. I think i saw somewhere Synology says that upgrade to dsm 6.1 can be make only from dsm 6. Now about questions. md0 and md1 are system partitions and im guessing one is with dsm 5.2 and the other is with dsm 6.1. One of them could be unmounted but due upgrade issues its still there. About 2nd question. You mentioned those 2 disks are eSATA, did you changed flags in configuration files in dsm 5.2 to make it visible as normal disks? If yes, check if those settings got no changed after upgrade. You can try to downgrade system to dsm 5.2 and from that point try to upgrade to dsm 6 and then to dsm 6.1. At least i would do those steps.

Then most probably is lack of nic drivers for one nic.

Do you run DSM on both mb at the same time? If yes then both has assigned the same mac and dhcp server can't assign IP. Ergo, you wo't find it. It's because loader has hardcoded mac for 4 nics.

I have questions to those who have issues with "disappearing" access to DSM. 1. As i understand its on migrated systems only, not on fresh installed DSM 6.1. Correct? 2. Old DSM was in version 6.02 for 3615x, and new version is 6.1 for 3617x? Correct? If both answers are true then it is possible that synology makes some procedure to check compatybility to prevent installing pat file for 3617x on older hardware.

We all can see some confusion when people try to deploy new version and can't find new DSM with find.synology.com or with assistant. In many cases its related with having few DSM systems runing on the same network. My sugestion is to add those lines to ESXI boot option: set mac1= set mac2= set mac3= set mac4= This will let ESXI users to run multiple DSM systems without need to edit grub.cfg and to control mac addresses from within VM settings. PS. Thank you guys for great work with loader.

Do you have more DSM OS's running in the same network? If yes, then most probably both system got the same MAC assigned by loader and DHCP cant assign IP. There is few solutions.

No, it wont write permamently. It was just to find out problem. You can try jun's xpenology tool to change grub settings. viewtopic.php?f=2&t=24308 I've read the topic: viewtopic.php?f=2&t=24308, but I am not clear over if you can remove grub setting MAC completely? I understand that you can change the MAC with Jun's Xpenology tool, but can you unset it and let it take the MAC of the virtual VM LAN in ESXi ? Im not sure because i dont use it, but this is how i think: - if i do: set MAC1= , and leave it empty then this will override settings from grub.cfg, - if this overrides settings in grub.cfg with empty string and at the same time it takes mac from VM settings, then my best guess is yes, when you change grub.cfg with jun's tool then you can control mac from esxi. But like i said, i dont use it myself and this is only deduction from overriding settings during startup. Best option is to create test vm and try it, it cost nothing but some time, but gives you great experience.

Its good start: viewtopic.php?f=2&t=20216&hilit=qnap&start=1060#p77590

No, it wont write permamently. It was just to find out problem. You can try jun's xpenology tool to change grub settings. viewtopic.php?f=2&t=24308

Its exactly what i told you. If you would try my solution you would know where the problem is. If you use command set MAC1= , then mac from esxi VM will be used instead. btw. MAC is hardcoded in grub.cfg in jun's loader.

I connected a serial console using named pipe from the DSM 6.1 to my Ubuntu VM on the same host, as you you see the nic is not requesting an ip from the dhcp server (checked the logs in pfsense dhcp client list also). root@ubuntu-server:/home/donald# screen /dev/ttyS0 115200 :: Loading module cnic ... [FAILED] :: Loading module r8169 ... [ OK ] :: Loading module tg3 ... [ OK ] :: Loading module usbnet ... [ OK ] :: Loading module ax88179_178a ... [ OK ] :: Loading module button ... [ OK ] mount: open failed, msg:No such file or directory mount: mounting /dev/bus/usb on /proc/bus/usb failed: No such device ln: /proc/bus/usb/devices: No such file or directory :: Loading module synobios ... [ OK ] udhcpc (v1.16.1) started eth0 Link encap:Ethernet HWaddr 00:11:32:2C:A7:85 inet addr:169.254.58.122 Bcast:169.254.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:890 (890.0 B) Interrupt:19 Memory:fe120000-fe140000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) :: Starting syslogd ... [ OK ] :: Starting scemd :: Starting services in background Starting findhostd in flash_rd... Starting services in flash_rd... Running /usr/syno/etc/rc.d/J01httpd.sh... Starting httpd:80 in flash_rd... Starting httpd:5000 in flash_rd... Running /usr/syno/etc/rc.d/J03ssdpd.sh... /usr/bin/minissdpd -i eth0 (15): upnp:rootdevice (51): uuid:upnp_SynologyNAS-0011322ca785::upnp:rootdevice (58): Synology/synology_bromolow_3615xs/6.1-15047/169.254.58.122 (47): http://169.254.58.122:5000/description-eth0.xml Connected. done. /usr/syno/bin/reg_ssdp_service 169.254.58.122 0011322ca785 6.1-15047 synology_bromolow_3615xs eth0 Running /usr/syno/etc/rc.d/J04synoagentregisterd.sh... Starting synoagentregisterd... Running /usr/syno/etc/rc.d/J30DisableNCQ.sh... Running /usr/syno/etc/rc.d/J80ADTFanControl.sh... Running /usr/syno/etc/rc.d/J98nbnsd.sh... Starting nbnsd... Running /usr/syno/etc/rc.d/J99avahi.sh... Starting Avahi mDNS/DNS-SD Daemon cname_load_conf failed:/var/tmp/nginx/avahi-aliases.conf :: Loading module hid ... [ OK ] :: Loading module usbhid ... [ OK ] ============ Date ============ Wed Mar 1 12:24:53 UTC 2017 ============================== starting pid 5897, tty '': '/sbin/getty 115200 console' Wed Mar 1 12:24:54 2017 DiskStation login: edit: Nevermind, finally found the problem. You can't change change the MAC from the VM in vmware, the mac 00:11:32:2C:A7:85 is somewhere hardcoded in the loader, so you MUST use that one. Changed it to 00:11:32:2C:A7:85 in the .vmx file (or using vCenter or UI from host) and now requesting IP now... Regards, Donald. Its exactly what i told you. If you would try my solution you would know where the problem is. btw. MAC is hardcoded in grub.cfg in jun's loader.

Its possible that other DSM VM you have running has the same MAC as the new one you try to run with DSM 6.1. That way one VM wont be found by find.synology.com. Try this: - VM settings: in options set boot time to few seconds, - when you start new VM, with DSM 6.1, in grub options click 'e', - edit command by adding: set mac1= - F10 to start VM.

I've got problem with importing ovf then i choosed simplest possible solution. Create new VM as usual, linux - other 64 bit, etc. Then add 1st hdd from jun's package and add other hhd's tocreate volumes. Thats all. DSM 6.1 works with no problem. Im having ESXI 6.

Just create standard linux VM and add synology.vmdk as 1st hdd. I had to do nothing more than that to run it on ESXI 6. On VM start you need to choose ESXI option from grub

Im not 100% sure but as i remember some people got this problem before. Try with different pendrive

Its because in DSM6 there is no ntfs-3g driver installed. Im not sure if this gonna to work but you can try to mount this USB drive with this command from CLI(* is drive number): mount -o rw,mount,rw -t ntfs /dev/sdc* /mnt/ntfs/

Dont know why youre having issues with iscsi target. Im having up and running dsm 6.0 on iscsi target under esxi 6. iscsi lun is from baremetal dsm 5.2.

You dont have to set vid/pid under esxi. You have to setup all drive but boot drive as SATA drive.

If you are using DSM to storage and copy files then you are right. For me ie there is a lot new features like: - letsencrypt - web server with option to choose you want to use apache or nginx - option to create and edit spreedshets and microsoft files - mailplus server and station - for many users most wanted btrfs - nodejs version 4 - reverse proxy - many more new features

https://forums.verizon.com/t5/Fios-Inte ... d-p/803509 This is all you need to do. With no-ip you will have access to nas from internet Thanks, that's what I did try before but had no luck. I set 192.168.1.xxx tcp any -> "the port number" udp any -> "the port number" with 192.168.1.xxx is my Nas IP address. The problem is I really don't know what is "the port number" here to enter in the port field to see my XPEno from internet. I tried port "9" and somebody told me to try port "22" but got no luck either. We here encourage people to use DDNS instead of QuickConnect. That's fine and great, but in fact, there is no instruction in the forum to guide people how use it properly. I'm using 30-days trial of No-ip and plan to buy a 12-months plan. But I may change my mind unless I find out the way to setup port forwarding correctly. Port 22 is for ssh, in most cases you dont need it to open in router. Standard ports to access DSM are 5000 for http and 5001 for https, but DSM has pretty nice tool which is port forwarding. You can forward only port 80 and/or 443 to your NAS and with port forwarding on NAS and subdomains you can access DSM, audiostation, videostation, download station etc thru subdomains. Its really very simple. Of course you can simply open port 5000 or 5001 on router. In my case im using twoDNS. Its free ddns with wildcard option. FreeDNS also is nice to use with subdomains.

Your router wont let you to open port 80/443? I'm using Verizon FIOS-G1100 and need a port forwarding rule to forward port 22 to my XPEno Nas but I couldn't. BTW, I'm using No-IP. https://forums.verizon.com/t5/Fios-Inte ... d-p/803509 This is all you need to do. With no-ip you will have access to nas from internet

Yes

This is all what you will see. Now open browser and find server thru http://find.synology.com or with synology assistant.

Your router wont let you to open port 80/443? Yes, its fair because using quickconnect you will use not only DSM system but also synology's servers without fees. Is it fair enough for you to do that?

As for now its only possible thru virtualDSM on DSM 6.0. Synology always is messing with beta update and always is problem with volumes/drives on clean or upgraded system.