boefje

Transition Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About boefje

  • Rank
    Newbie
  1. I'm thinking about upgrading my hardware and moving from VMware to Proxmox. It'll be a good exercise which I'll probably am going to regret when I'm half way the upgrade I'm looking for some help in the migration steps; Current setup: Hardware: i3 6100 8Gb 250Gb SSD + 4x3TB + 3x5TB+2x8TB VMWare ESXi 6.7.0 XpenologyA: Jun's Loader v1.04b - DS918 RDM 4x3TB - Photos, backups and document storage (The important stuff) XpenologyB: Jun's Loader v1.04b - DS918 RDM 3x5TB + 2x8TB - Home media server (The not so important stuff) XpenologyC: Jun's Loader v1.04b - DS918 No disks, upgrade/test purposes. I'd like to move to a Ryzen 7 1700 with the Asus Prime X370-PRO with 16Gb running ProxMox Installing Proxmox and Xpenology should not be a big problem. However, how am I going to migrate my data to the new installation without having to buy a sh*tload of drives? I know DSM allows you to migrate a set drives from one server to another. But, how does this work/apply (if at all) when you have a virtualized instance RDM and you want to change from VMWare to Proxmox?
  2. @shax I ditched the whole DS3615 and went with the 1.04b loader and DS918 pat file. That worked like a charm. I think I must have messed it somewhere up but I have no idea where. Thank you for responding to my question.
  3. I'm getting the error message: Failed to format the disk (35) after the discovery and upload of the PAT files. ESXi 6.7 fresh installation Loader 1.03b DSM_DS3615xs_23824.pat AND DSM_DS3615xs_23739.pat First drive to sata controller 1 on 0:0 2nd drive on sata controller 2 on 1:0 (16Gb) Tried 2 different hard disks Hitachi and Seagate but both gave the same error message. Any hints since I'm out of ideas?
  4. Make sure you're using a PS/2 keyboard. My USB keyboard didn't work either and I had to dig out my old and trusty PS/2 one.
  5. Check my post for the password viewtopic.php?f=2&t=12523&p=56459#p56459
  6. Give this a try http://xpenology.com/forum/viewtopic.php?f=2&t=12523
  7. I have no idea why the NIC didn't get an IP address. The bootlog was too quick to tell whether there was any error. After the first reboot during the install II had to give it again manually an IP address but after the installation was completed, Xpenology saw my 2 NIC's and I was able to reboot the machine from the menu without any problems. (I did give the system a fixed IP address in Xpenology)
  8. While running Xpenoboot, my bootlog said; eth0 not RUNNING eth1 not RUNNING My machine didn't get an IP address. A bit strange because one of my NIC's, an i219-V is apparently supported. After some searching in the forum and googling I was able to find a workaround. However it took me quite some time so I'm posting it as a stand alone thread so others can find it more easily. 1) After the Xpenoboot installation ran, you end up with a sign in prompt. Use user-id "root" and a password that changes every day. and here is how you can generate it; Go to http://www.codepad.org And past this piece of code in the editor and run the code in C. (more can be found here https://wrgms.com/synologys-secret-telnet-password/) #include #include #include void main() { struct timeval tvTime; struct tm tmOutput; gettimeofday(&tvTime, 0); localtime_r(&(tvTime.tv_sec), &tmOutput); tmOutput.tm_mon += 1; printf("password for today is: %x%02d-%02x%02d\n\n", tmOutput.tm_mon, tmOutput.tm_mon, tmOutput.tm_mday, gcd(tmOutput.tm_mon, tmOutput.tm_mday)); } int gcd(int a, int b) { return (b?gcd(b,a%b):a); } Once you're in, you need to manually assign an IP address , the subnet mask and the gateway. Assuming you have 1 NIC called eth0 I'm going to adding it with IP address 192.168.1.100 subnetmask 255.255.255.0 and default gateway 192.168.1.1 use the following 2 commands ifconfig eth0 192.168.1.100 netmask 255.255.255.0 route add default gw 192.168.1.1 eth0 Now your machine should have an IP address and you can continue to install Xpenology.