Gronaldo

Just tried this, see my posts above. Answer is No. This is Broadcom based, while you need Intel based.

Pfff...it is running now. After some tests, I updated my 6.1.7 version to manual 6.2.1 PAT, using the Intel server network card. It took machine more time than usual to become available again. I almost gave up and pull the plug... In the end machine rebooted a second time, while Assistant show 'Starting services'. After finally completing all, it now runs with upgrade 4, much to my surprise. But anyway, we're in business again! Thanks!

Thanks, I'll give that a try! Did come accross overview, but did not pick up this detail

Not in last attempts. Installed new network card, under 6.1.7, all okay. Then 1.03b loader and DS3617 PAT. Tried 3615 earlier, but without Intel network cards. Also no luck.

For some reason I cannot upgrade my Microserver G8 to 6.2.1, using loader 1.03b. I installed a Intel based Hp NC360T dual network card, disabling the onboard ones. Tried to manually upload .PAT files etc. However unit dissapears after migrate / repairs actions. No clues anymore. Could it be my processor, being an i3-3240T?

Just installed this 1.04b loader for DS918+ on Gigabyte GA-J3455N-D3H board, without apparent issues. Did notice no info is displayed at all on monitor output, not even nromal Xpenology boot menu. Is this as intended? Is DS918+ image now adviced for J3455 platforms? Feedback / comments welcome.

After more testing I found a reboot is required in order to work. Machine is usually off and active for making backups, as target for live Nas and creating secondary backup to USB drive. So after initial boot, no USB drive is detected, even after reconnecting a few times. After reboot, with drive connected, is works. Any suggestions how to resolve or what issue may be? Thanks for any assistance .

For a long time I am using a Seagate USB 3.0 drive for external backups. It seems starting with DSM 6.1.7-15284 the drive is no longer recognised. Test with other USB 3.0 drives have same results. On USB 2.0 all drives do work. I am using same hardware, same loader (Jun v.1.02b) as before, when all worked without any issues. Anybody any suggestions how to fix this? Many thanks!

Nevermind.

I always learned it is never to late to provide feedback. I appreciate the work done, don't get me wrong. But my experiences working for some time with current setup triggered me on this comment. It's easy to criticise, rather than to contribute or create, i know. Nevertheless i hope it may be of use for the future. Thanks.

A bit lost... Sorry to say that i am a bit lost on the new forum. So many categories, so may closed topics, so many branches... Really struggling to find info, and missing the easy to browse, or being updated after a quick visit... Surely it's difficult to accommodate everyone's preferences, but to me it seems a bit overdone.

Thanks, will take a look. Funny thing is; - Working bootdisks (created earlier or newly in VM with Win1703) cannot be read correctly - Same issues at 3 different PC's (new install 1709 or upgraded earlier versions) - Not USB drive dependent, preparation or partioning done as usual - Used to be able to read bootdisk and edit config files directly, not posible anymore, besides on older Win versions. Very strange....

Sure? Releases

All, after the Windows 1709 update I cannot successfully create or read the USB bootdisk loader, using Win32Imager 1.0. Somehow Windows seems to limit access to the USB device and partitions. Using a previous version of Windows, 1703, even as a VM on the same PC, works all fine. So i found my workaround, but i am surprised not to see any similar issues reported here?

After the 1709 update I cannot create or read the USB bootdisk loader, downgrading to 1703 works fine again. I use Win32imager and used to edit config files on desktop, after creating the USB stick. Still investigating what's going on, but any suggestions are welcome.