meimeiriver Posted January 19, 2017 Share #1801 Posted January 19, 2017 Yes, Update 9 totally hosed my machine. It won't reboot, and even after a hard reset won't come back. Quote Link to comment Share on other sites More sharing options...
meimeiriver Posted January 19, 2017 Share #1802 Posted January 19, 2017 C'mon, ppl, this is not the time to be silent! Please, tell me how to fix this. Is there a new image I need to download? P.S. I *knew* not having a terminal console would come to bite me in the ass one day! Quote Link to comment Share on other sites More sharing options...
dalin Posted January 19, 2017 Share #1803 Posted January 19, 2017 I installed update 9. But can't get the ip. i tried ifconfig eth0 up and it told me: eth0: ERROR while getting interface flags: No such device I tried to reboot and reboot, it doesn't work. I use KVM. Quote Link to comment Share on other sites More sharing options...
meimeiriver Posted January 19, 2017 Share #1804 Posted January 19, 2017 I installed update 9.But can't get the ip. i tried ifconfig eth0 up and it told me: eth0: ERROR while getting interface flags: No such device I tried to reboot and reboot, it doesn't work. I use KVM. And you're the lucky one! Me, I'm stuck with a VMware image that doesn't even have a console! Quote Link to comment Share on other sites More sharing options...
meimeiriver Posted January 19, 2017 Share #1805 Posted January 19, 2017 Using Juns pre-packaged Esxi vmdk I have ran into an issue on Esxi 6.2 patched all the way. (...) SCRATCH ALL THAT! I wan using jun 1.0 vmdk. no wonder I couldnt get it going. after loading correct boot 9 went on fine So, which image are you using now then?! Quote Link to comment Share on other sites More sharing options...
Polanskiman Posted January 19, 2017 Share #1806 Posted January 19, 2017 Using Juns pre-packaged Esxi vmdk I have ran into an issue on Esxi 6.2 patched all the way. (...) SCRATCH ALL THAT! I wan using jun 1.0 vmdk. no wonder I couldnt get it going. after loading correct boot 9 went on fine So, which image are you using now then?! v1.01 Quote Link to comment Share on other sites More sharing options...
meimeiriver Posted January 19, 2017 Share #1807 Posted January 19, 2017 Using Juns pre-packaged Esxi vmdk I have ran into an issue on Esxi 6.2 patched all the way. (...) SCRATCH ALL THAT! I wan using jun 1.0 vmdk. no wonder I couldnt get it going. after loading correct boot 9 went on fine So, which image are you using now then?! v1.01 Okay, thx. I'll give that a try. Quote Link to comment Share on other sites More sharing options...
Polanskiman Posted January 19, 2017 Share #1808 Posted January 19, 2017 C'mon, ppl, this is not the time to be silent! Please, tell me how to fix this. Is there a new image I need to download? P.S. I *knew* not having a terminal console would come to bite me in the ass one day! If you have a serial port on your machine then you have a console. It's just a matter of hooking up the machine with a serial cable to your PC (most probably with a converter serial-usb) and accessing consol through a serial consol. Don't waste your time if you don't know what I am talking about. Edit: just realised that you are on a VM. Quote Link to comment Share on other sites More sharing options...
mazay Posted January 19, 2017 Share #1809 Posted January 19, 2017 Give him a fiew minutes, i have the same problem.... Quote Link to comment Share on other sites More sharing options...
Polanskiman Posted January 19, 2017 Share #1810 Posted January 19, 2017 So, which image are you using now then?! v1.01 Okay, thx. I'll give that a try. Please report back once you update to v1.01. I am curious to know whether this could be due to people using V.1.0 Quote Link to comment Share on other sites More sharing options...
meimeiriver Posted January 19, 2017 Share #1811 Posted January 19, 2017 Please report back once you update to v1.01. I am curious to know whether this could be due to people using V.1.0 Yeah, this is not going well. When I try to intall the jun 1.1 version, ESXi 6.02 says: "failed to deploy ovf package", "error uploading synoboot.vmdk". Quote Link to comment Share on other sites More sharing options...
dutchnas Posted January 19, 2017 Share #1812 Posted January 19, 2017 (edited) I'm using the bootloader jun-amd-baremetal-hybrid-uefibios-arcao-v2 https://mega.nz/#F!Oc8TCLgD!IiullNuGs95RlelM9SKd5w!qJ9HSDIZ when i dismount all my disks the NAS is accessible from the assistent tool, when readding the disks it won't. Is this the correct version for bare metal setups with update 9? Edited January 19, 2017 by Guest Quote Link to comment Share on other sites More sharing options...
meimeiriver Posted January 19, 2017 Share #1813 Posted January 19, 2017 Please report back once you update to v1.01. I am curious to know whether this could be due to people using V.1.0 Yeah, this is not going well. When I try to intall the jun 1.1 version, ESXi 6.02 says: "failed to deploy ovf package", "error uploading synoboot.vmdk". Using this jun 1.1 image, btw, from the start post: "Updated loader by Arcao latest images (10-28-2016) : https://mega.nz/#F!Oc8TCLgD!IiullNuGs95RlelM9SKd5w" Quote Link to comment Share on other sites More sharing options...
Polanskiman Posted January 19, 2017 Share #1814 Posted January 19, 2017 Please report back once you update to v1.01. I am curious to know whether this could be due to people using V.1.0 Yeah, this is not going well. When I try to intall the jun 1.1 version, ESXi 6.02 says: "failed to deploy ovf package", "error uploading synoboot.vmdk". Using this jun 1.1 image, btw, from the start post: "Updated loader by Arcao latest images (10-28-2016) : https://mega.nz/#F!Oc8TCLgD!IiullNuGs95RlelM9SKd5w" That link is not V1.01. Here is the official link from the OP: https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA Quote Link to comment Share on other sites More sharing options...
meimeiriver Posted January 19, 2017 Share #1815 Posted January 19, 2017 Using this jun 1.1 image, btw, from the start post: "Updated loader by Arcao latest images (10-28-2016) : https://mega.nz/#F!Oc8TCLgD!IiullNuGs95RlelM9SKd5w" That link is not V1.01. Here is the official link from the OP: https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA The other link has a sub-dir with 'jun's images'. Just to be sure, I downloaded the one from your link, but it's the same, and won't install. Quote Link to comment Share on other sites More sharing options...
meimeiriver Posted January 19, 2017 Share #1816 Posted January 19, 2017 Using this jun 1.1 image, btw, from the start post: "Updated loader by Arcao latest images (10-28-2016) : https://mega.nz/#F!Oc8TCLgD!IiullNuGs95RlelM9SKd5w" That link is not V1.01. Here is the official link from the OP: https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA The other link has a sub-dir with 'jun's images'. Just to be sure, I downloaded the one from your link, but it's the same, and won't install. Anyone?! I'm using the latest ESXi 6.5.0 machine. This thing just won't upload. Sigh. When it rains, it pours. Quote Link to comment Share on other sites More sharing options...
dutchnas Posted January 19, 2017 Share #1817 Posted January 19, 2017 I'm using the bootloader jun-amd-baremetal-hybrid-uefibios-arcao-v2 https://mega.nz/#F!Oc8TCLgD!IiullNuGs95RlelM9SKd5w!qJ9HSDIZ when i dismount all my disks the NAS is accessible from the assistent tool, when readding the disks it won't.Is this the correct version for bare metal setups with update 9? Anybody has some tips for me? Quote Link to comment Share on other sites More sharing options...
maryanos Posted January 19, 2017 Share #1818 Posted January 19, 2017 C'mon, ppl, this is not the time to be silent! Please, tell me how to fix this. Is there a new image I need to download? P.S. I *knew* not having a terminal console would come to bite me in the ass one day! I think i've found a solution! I've changed NIC type in my ESXI vm from VMXNET 3 to E1000E and now DSM is accessible! Quote Link to comment Share on other sites More sharing options...
maryanos Posted January 19, 2017 Share #1819 Posted January 19, 2017 (edited) For all ESXI users: I've changed NIC type in my ESXI vm from VMXNET 3 to E1000E and now DSM is accessible after update 9 Edited January 19, 2017 by Guest Quote Link to comment Share on other sites More sharing options...
Eagle Posted January 19, 2017 Share #1820 Posted January 19, 2017 Hi! Is it possible to add own driver packages? howto? Regards Chris Quote Link to comment Share on other sites More sharing options...
meimeiriver Posted January 19, 2017 Share #1821 Posted January 19, 2017 For all ESXI users:I've changed NIC type in my ESXI vm from VMXNET 3 to E1000E and now DSM is accessible after update 9 It was already on E1000E for me (and still is). That link is not V1.01. Here is the official link from the OP: https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA And that jun 1.1 ovf package still won't load for me on ESXi 6.5.0. Can someone PLEASE tell me how they got it working?! Quote Link to comment Share on other sites More sharing options...
bchuter Posted January 19, 2017 Share #1822 Posted January 19, 2017 For all ESXI users:I've changed NIC type in my ESXI vm from VMXNET 3 to E1000E and now DSM is accessible after update 9 It was already on E1000E for me (and still is). That link is not V1.01. Here is the official link from the OP: https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA And that jun 1.1 ovf package still won't load for me on ESXi 6.5.0. Can someone PLEASE tell me how they got it working?! Try the following from Koroziv. Download his .ovf and import that into Esxi. This worked for me on Esxi 6.0 and i upgraded my Esxi to 6.5 yesterday and DSM is still running fine with this and Update 9 For esxi users : here you have an ovf vm export that will make the install easier:https://mega.nz/#!Vk40FCDT!r2ertz7Eyoeh ... W2p1GLgzfs All you need to do after import is to add your drives and edit ram/cpu to your needs (comes with 2x2cpu and 4 Gb ram), then start the vm and continue with the install process. It will start with the vmware boot option automatically, and after the install you will not see the 50mb boot drive. I didn't edit a thing in the cfg (vid or pid) This is the loader on the first page of this topic, latest version, I just made it more easy to use it for esxi users. Here is the process: I had to import the original vm in VMware Workstation Pro (I had errors at import in esxi 6.5), and chage to hw version 10, export to new ovf; imported the new ovf in esxi, edited a few things, start once to retain the vmware boot option, changed the boot drive to non-persistent (it's hidden in xpeno now) and exported again to the ovf in the link for easy future use. I hope it will be useful to others to; if I messed up something let me know, for me and a few others this worked nice. Edit: On my gen8 microserver I don't have and can't add an usb3 controller; this could be a poor choice at vm guest os version, I put "other 3.x or later linux x64", did not tried any other way yet. Edit 2: The usb3 issue is not present on the atached hw 10 ovf(the one in the link), you can add usb3 controller in it; my xpeno install is on a vm with hw 13 and that is why I can't add an usb3 controller. Quote Link to comment Share on other sites More sharing options...
meimeiriver Posted January 19, 2017 Share #1823 Posted January 19, 2017 For all ESXI users:I've changed NIC type in my ESXI vm from VMXNET 3 to E1000E and now DSM is accessible after update 9 It was already on E1000E for me (and still is). That link is not V1.01. Here is the official link from the OP: https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA And that jun 1.1 ovf package still won't load for me on ESXi 6.5.0. Can someone PLEASE tell me how they got it working?! Try the following from Koroziv. Download his .ovf and import that into Esxi. This worked for me on Esxi 6.0 and i upgraded my Esxi to 6.5 yesterday and DSM is still running fine with this and Update 9 For esxi users : here you have an ovf vm export that will make the install easier:https://mega.nz/#!Vk40FCDT!r2ertz7Eyoeh ... W2p1GLgzfs All you need to do after import is to add your drives and edit ram/cpu to your needs (comes with 2x2cpu and 4 Gb ram), then start the vm and continue with the install process. It will start with the vmware boot option automatically, and after the install you will not see the 50mb boot drive. I didn't edit a thing in the cfg (vid or pid) This is the loader on the first page of this topic, latest version, I just made it more easy to use it for esxi users. Here is the process: I had to import the original vm in VMware Workstation Pro (I had errors at import in esxi 6.5), and chage to hw version 10, export to new ovf; imported the new ovf in esxi, edited a few things, start once to retain the vmware boot option, changed the boot drive to non-persistent (it's hidden in xpeno now) and exported again to the ovf in the link for easy future use. I hope it will be useful to others to; if I messed up something let me know, for me and a few others this worked nice. Edit: On my gen8 microserver I don't have and can't add an usb3 controller; this could be a poor choice at vm guest os version, I put "other 3.x or later linux x64", did not tried any other way yet. Edit 2: The usb3 issue is not present on the atached hw 10 ovf(the one in the link), you can add usb3 controller in it; my xpeno install is on a vm with hw 13 and that is why I can't add an usb3 controller. Thank you very kindly!! That koroziv guy, and you, may yet save my day! P.S. Seems he had the same experience: "I had errors at import in esxi 6.5". So it wasn't just me. Quote Link to comment Share on other sites More sharing options...
vrm42 Posted January 19, 2017 Share #1824 Posted January 19, 2017 Jun's loader works fine with esx 6.0. I did the following: - open .vmx file with a text editor and change hw version from 12 to 11 - upload the files from the .zip to the datastore - don't deploy .ovf, instead, just open server IP in web browser and login to the esx web page - click on datastore and select register vm, select the .vmx file - now you can return to vsphere client, edit your vm as you like - I needed to remove nic and re-add a new one, don't forget to add an hdd - open console, start vm, select vmware install from boot menu (keep pressing down arrow from the start, loader is very fast) - open find.synology.com within your browser and install your nas (you need a dhcp server within the same ip segment) - after that you can update to update-9 directly I hope it helps... Quote Link to comment Share on other sites More sharing options...
audiophile20 Posted January 19, 2017 Share #1825 Posted January 19, 2017 Thanks to Jun for the v1 loader - I am running DSM6.0 and update 9 is running; build is stable on the test machine. The test machine is a bare metal install; Hardware - Dell Dimension (re-purposed to a test NAS). The production unit - NARCO 24 bay hot-swap 4U; w/ Supermicro mobo, Intel Xeon CPU and a LSI controller card; all my mobo controllers are disabled in BIOS + 2 1GB NICs running DSM5.0 and the machine is stable. 1. Now I would love to upgrade to DSM6.0 on the test machine. I think, I will have to wait for the DSM60 v2.xx loader to be available to make this transition. Am I correct in the assumption? 2. Can I use Jun's v1 loader and mod it to see 24 drives? I tried playing with the MaxDrive variable on the test bed and I am not seeing the 24-slot display in DSM60 on the test machine. Can someone please point me in the right direction with answers? My apologies if this has already been asked and answered. Thanks in advance! Again thanks to all the coders on this effort. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.