cuspess

Members
  • Content Count

    45
  • Joined

  • Last visited

Everything posted by cuspess

  1. Sure enough if you already got Jun's 1.0.2a2 or 1.0.2a working with your machine, then you are safe. I personally encountered Error 13 with both loader and just couldn't get it working with my rig. And this post is about people like me not able to update to these 2 loader with bug free DSM 6.1 installed. Recommendation like Salah's is quite useful. There we have a hint what could be done if we could not upgrade to DSM 6.1.1-U4. Now if Salah can elaborate more this method, that would be great.
  2. It seems that Synology has released a security patch yesterday to address the potential vulnerability of DSM in relation to recent WannaCry attacks. Xpenology usually is quite stable once you got the bootloader all working bug free; but it is the time like these that could cause problem to xpenology users, just like synolock back in 2014. Xpenology users are limited to certain version, depends on the bootloader version they are using. For instance some user are still on DSM 5.x which their bootloader doesn't support further update or a complete upgrade of bootloader is require if to upgrade to DSM 6; same applies to those, and including myself, who yet to get the newer bootload which support DSM 6.1 to work with their machine. My queries, with the difficulties mentioned above, how do we protect ourselves from security vulnerability? Version: 6.1.1-15101-4 (2017/05/25) Important Note The update is expected to be available for all regions within the next few days, although the time of release in each region may vary slightly. Fixed Issues Fixed a security vulnerability regarding samba service (CVE-2017-7494).
  3. While I agree both points, I think whether to use DS3617xs or DS3615xs bootloader comes to trial & error more than anything. No doubt people with knowledge in these area could make a better judgement on which would suit them better, but because most hardware we use to run DSM here are unofficially supported, no guaranteed anything would work. So I think there is no harm trying both, with your testing environment at least, to find which suits your hardware best.
  4. I aint Rhubarb so maybe only he can answer exactly. But I am making a guess here that it really doesn't matter if you go for DS3615XS or DS3617XS because you need to create a new usb drive to boot the DSM 6.1 or later iteration anyway. Moreover latest Jun's loader for DS3615XS is v1.02a whereas the latest is v1.02a2 for DS3617XS, which is a later revised version. Although I remember v1.02a2 only contains very minor change, it still make sense to go for the later version if you were to try something new. Having said all above, neither of the two loader work for my setup with both error 13, which really is a bomber.
  5. cuspess

    DSM 6.1.x Loader

    Interesting. I am on Gen8 Microserver, ESXi 6.0, tried both DS3615xs 1.02a and DS3617xs 1.02a2, neither worked, both produce error 13.
  6. cuspess

    DSM 6.1.x Loader

    I got it back up and running few hours ago, then spent few hours working on all the settings to match mostly how I had it before. With the recent wannacry strikes around the globe, i also try to tighten my security such as setting more restrictive firewall rules and blocking unused ports, etc. I think my failure in upgrading to DSM 6.0.3 did indeed give me this great opportunity to do so. My DSM is running on a Gen8 Microserver under esxi 6, so it would be different experience to your mediasmart server setup i would imagine. From what you described if 6.0.2 rev8 did work flawlessly, you might want to download the .pat file of 6.0.2 rev8 and fresh install onto a spare Hard Drive, get over the initial setup, then plug in your original Hard Drive. DSM will then prompt your to repair your original Hard Drive. After the repair, you should be able to turn off the machine and unplug the spare Hard Drive, boot it up again with your original Disk. Down side is, you won't retrieve your DSM settings. But for me it is fine as I want to start over, but most importantly my data were kept intact this way.
  7. cuspess

    DSM 6.1.x Loader

    Hey, I am back to report I have revived my DSM and all data; only lost the DSM settings e.g. user, apps, backup schedules, etc. It was done with the method I mentioned in my previous post, by installing a new DSM on a spare disk to repair the corrupted system partition on my existing storage disks. I take it a opportunity to clear up some bloated and abandoned settings, so I am pleased with the result. And this is where I think the forum should evolve. I am sure there are plenty of users without much technical knowledge in coding programming but have some kind of idea how to get round things just like myself in this forum (obviously there are also many more with such knowledge and tinkering capability), but there are relative lot more of those who just don't know what they are doing yet want to grab a piece of this holy grail of xpenology, those who jump into it without knowing anything then only ask everything without even a look around. Thats what bloating the forum, together with a unorganised forum structure and buzzard searching engine made looking up useful information and write ups even more obscure. I still think there are good guys doing the community great here, I can tell by some of the search returned result. But why hiding them and requiring a search to reveal them? if you list them out clearly, with good layout and appropriate location, it will efficiently lower the bloat questions and threads and posts.
  8. btw I am using Gen8 too, though run DSM under esxi. Otherwise we had a very similar setup. One thing you got lucky, which is that DSM 6.1 actually works for you. Somehow I couldn't get it work. So I am recovering back to 6.0.2 using your above method.
  9. Good write up. I faced similar issue and had the same idea in my head to solve it. Great to see someone already come across this method and assure my thinking. Will try this now, hope it all works out.
  10. cuspess

    DSM 6.1.x Loader

    So I just saw the red text on the updated tutorial regarding shouldn't update to 6.0.3 on v1.01 when looking for solution to my situation. Damn. I wish any updated or important notes was made clear in the forum, like a specific headline in big text or a prompt note or something. Not to blame anyone but this forum is bloated with questions of outdated DSM5 and query of different issue, it is just so difficult to aware of any update, not to mention any important notice.
  11. cuspess

    DSM 6.1.x Loader

    Thank you IG-88 for your response. I am proceeding with my plan at the moment. Unfortunately I hit the wall already as we speak. I encountered the Error 13, which I expereienced previously when testing Jun's 1.02a DS3615xs loader on a separate testing vm. I wasn't running a passthrough back then so I thought the error was caused by that. Now with passthrough error 13 remains, that is tricky. Will need to see what I can do to work it.
  12. cuspess

    DSM 6.1.x Loader

    To add in some background, I am running ESXi 6 on a HP Microserver Gen8, with the built-in B120 controller run in ACHI mode and passthrough to the DSM virtual machine. Which means my production Hard Drives should technically plugged in and formatted just like a normal Synology NAS would be.
  13. cuspess

    DSM 6.1.x Loader

    I have been on Jun's 1.01 running with DSM 6.0.2 for ds3615xs for quite some time, runs stable and faultless for months. I have been notified a new update of DSM 6.0.3 is avaliable for weeks but reluctant to update until just now. I have always been able to update using the updater in control panel over the past few updates. But this time my dsm would not boot up. The local IP is changed and I got given the option to recover. Not hard to guess the recovery didn't work out. So I am going to try upgrading to Jun's v1.02a2 and hopefully by installing the new DSM 6.1, it will work again. One technical issue though. As the hard drives I am using is the main production drives with my important data, I have a thought of first unplug all the drives and install the DSM 6.1 with a spare hard drive. That should classify as a clean install, then I will plug back in my production drives; in theory I should then be able to "migrate" or "re-habit" my data back to the new DSM 6.1. Can anyone confirm this will work?? Will I be able to then transfer the DSM 6.1 settings and main system files back to my production drives from the spare, optimally unplug the spare drive to free up the bay again??? Kind of nervous because I didn't expect upgrading to 6.0.3 would go wrong, even I knew migrating to 6.1 would be more likely to fail and avoided it. So any help and advice would be deeply appreciated. Thank you
  14. Just tried creating a vm with 40GB virtual HDD on esxi 6.0, boot the loader v1.01a2 for DS3617xs of a USB flash drive. It boots into "Install DiskStation Manager (DSM)" alright, then when I try to start the installation by using "Manual Install" with "DSM_DS3617xs_15047.pat" or "Install the latest DSM", it both proceed to 54% and interrupted with error message "Failed to installthe file. The file is probably corrupted. (13)" Thinking it might be something to do with my virtual HDD, but the same method had been deployed successfully on my working xpenology, which is still on DS3615xs DSM 6.0. Not sure what's the problem is. Anyone with similar experience?
  15. cuspess

    DSM 6.1.x Loader

    Trying to understand the current situation here. Does the undefined instructions complain affect machines running e3-1230 v2 with esxi being the underlay OS?
  16. ah, with 16 cores and 32 threads, that is true that you got plenty to toss around. Actually envying you with such a powerful machine With only 8 total threads, I had no option other to optimize the best performance out of the limited resource, so my other 4 VMs could still have enough vcpu to run smoothly. Anyway, I am guessing your conclusion regarding difference between DS3615 vs DS3617 would only benfit if one is going to assign more than 4 vcpu to DSM?
  17. That's interesting. I am running DSM 6.0 on exsi 6.0 with HP MS Gen8 and E3 1240v2 (4 cores 8 threads). With some testing, I found that assigning 2 vcpu (core #0 & #2, which are the actual cores, not the associated thread of any core) is sufficient for Plex Server transcoding. H264 were transcoded without full cpu utilisation and even H265 were at full utilisation at 100% during playback, it has minimal to no impact to the smoothness of the displayed video. I also tried assigning 3 vcpu (core #0, #1 & #2 this time, which #1 being #0's associated thread) with even better performance for H265 transcoding. Such cpu utilisation would drop to average 80~90%. The point is, 3 vcpu for DSM seem sufficient for most of the task assuming transcoding is the most demanding task to run on DSM (that seem to be the case with my usage). Not to say it isn't great to be able to utilise more cpu power with DS3617 loader, just sharing my experience and hope to exchange for better effiecient setup.
  18. I am currently on esxi 6.0 and xpenology as a vm within it. I too suffer the high fan speed issue where ambient temp is 27c and fan spins no lower than 35% when idle. None of those reported success with the modded hp-ams mentioned they are on esxi 6.0 or baremetal, I assume they are on baremetal. Can someone advise will this hp-ams mod work for esxi 6.0? If it is esxi 6.0 that I am on, does it matter which modded version I choose? thanks
  19. cuspess

    DSM 6.1.x Loader

    You don't need to passthrough your usb controller to use it. Just go to your vm setting page, add a virtual usb controller to the config, click apply, then plug in your usb device, go back into your vm setting page, add a usb device and select that particular device from the list, click apply and you are done.
  20. cuspess

    DSM 6.1.x Loader

    Normally swaping out hard drives from one NAS box to another should work with an initial setup called migration. That should be the case as well in terms of Xpenology; that is if your new hardware is booting Xpenology correctly without any problem and with all the supported hardware and drivers. Unfortunately there is no gurentee in the world of Xpenology when it comes to list of supporting hardware or working drivers. For that reason I would suggest sticking with your current hardware if it is working flawlessly and stability is your priority. If you are adventurious, always remeber to have backup of your data before proceeding to the migration. You wouldn't want to risk all your data for the hardware upgrade.
  21. cuspess

    DSM 6.1.x Loader

    Glad to hear you have been able to get your system up and running again without losing any data. Would you say, from your experience under the currently known situation that a clean install is the only way to run DSM 6.1 without problems, by formating the first linus parition with gparted and install DSM again is effectively same as a clean install of DSM 6.1 but without losing any data? thus could be the way out for now aside from the migrating route.
  22. But if you update the loader the NAS won't boot if the NAS is stil on DSM 6.0.2-8451 Update 9 so I asked if you update DSM 6.0.2-8451 Update 9 to 6.1 and you replace the USB stick with new loader is that the correct way? Sure I will wait a little longer. Disclaimer: I have not done the migration myself, just take below a grain of salt. Imagine you own a physical 3615xs, like a real one not xpenology. Imagine it was on DSM 6 but died and you just received a replacement from the seller and it was pre-installed with DSM 6.1 So what you would do is just unplug all your HDDs from the old and slot them all into the new unit. Now DSM 6.1 is flashed in the DOM of the new unit (just like your new loader 1.02a) but all the system partition in your HDDs are on DSM 6. First boot up the new unit should prompt you to migrate your system partition to DSM 6.1, which then would allow you to use the NAS as you would before but now with DSM 6.1 This should be the same logic as getting xpenology DSM 6.1 work with migration from DSM 6
  23. cuspess

    DSM 6.1.x Loader

    Sonnyboy, did you migrate yours from DSM 6? What I mean is you replaced loader 1.01 with 1.02, then boot up with old hdd installed, go through the migration process? any error afterwards? I am on Gen8 with esxi, about to migrate as soon as someone succeed without the error. thanks
  24. cuspess

    DSM 6.1.x Loader

    What if I first remove existing HDDs (DSM 6) and USB drive (loader 6.01), create another USB drive with loader 6.02, plug it in with a spare HDD (not been used for xpenology), initialise all the setup, then plug back in all HDDs?? Would this method count as migrate? or fresh install?? If it works, I would want to unplug the spare HDD at the end, so to left with only those HDDs originally connected to my DSM 6 system.
  25. cuspess

    DSM 6.1.x Loader

    I am beginning to think case like this, if you still had your old loader 1.01 with you, you could still boot with 1.01 and have your DSM 6 working like before the upgrade. Someone please confirm if my thought is right, otherwise I think it is fair to say it is safe to try upgrading. cheers