billat29

You'll need to follow the instructions in this ====> viewtopic.php?f=2&t=13288

I suspect that the BIOS error is due to the power outage. Have you been into the BIOS settings, checked that all the settings are still how you want them and saved it?

Of course people are going to report back DSM6 can't be (fully?) upgraded yet. And of course they are going to express the wish it could be. I have yet to see anyone being unappreciative of the work of those who made a provisionary DSM 6 available, though. As for 'wait[ing] for an offical XPE version that supports DSM6,' I haven't heard anything from the 'official' team in ages. In fact, ironicially, this very thread has sprung from the deafening silence on their end. A word or two, every once in a while, wouldn't hurt either. I would just like to add my thanks to those who got a flavour of DSM6 running. However, I regard it as strictly experimental and I wouldn't entrust my valuable data to it at this point. As for the regular devs, there is nothing they can say or do until Synology release source. We know they are still around as they produced 5967 but I suspect that they are getting on with their lives and will get back to it once there is something to do. I agree that if you really want the features of DSM6 now, then it's time to put hands in pockets and buy a real device. And if you are genuinely running production for business critical work, then I would say you are being unwise to rely on XPE anyway. You should go for the fully supported Synology solution.

In principle you can follow the same method as outlined in the "downgrade from DSM 6.0" thread but putting in an earlier release of DSM5.2 than the one you want to go to. The idea is that you fool XPEnology into thinking it is running an earlier release so that you can "upgrade" it to the release you want. I have used this technique successfully. BUT! No guarantees though. Back up your data as it might all go horribly wrong.

XPEnology supports DSM 5.2. If Synology release more builds for this version, then I expect that the devs will update the XPEnology bootloader if needed. XPEnology does not support DSM 6. The devs are waiting for Synology to release the source code as they are obligated to (there's another thread on that) and then they can start to work on that version. I expect that Synology will delay release as long as they can. oktisme patched the Synology bootloader to work around Synology's security check. The check was basic and it is quite probable that they have changed it to something more advanced and this might be the reason why the latest DSM won't install.

One way to look at it is that "install" is basically Xpenoboot for 5.2 and has support for non-synology hardware but not all the new stuff in V6 (eg btrfs). "run" is the V6 synology bootloader with a mod to disable the security check. If you have compatible hardware, you can load the "synology bootloader" and get access to the features of V6. If you run with "install", then you are trying to run V6 on the V5.2 bootloader and that's not really a good idea as oktisme said somewhere near the beginning when I said I was doing it.

You can follow the first few steps of this https://xpenology.us/node/401 First download the correct version of xpenoboot from here https://xpenology.us/downloads/xpenoboot You need the one that matches the version displayed on your screenshot. Then, as the tutorial says, use win2diskimager to create the new usb. replace the old USB in the N54l with the new one and boot. You want to select "normal" boot as you already have DSM installed on your disks. Now either it all works or we find that unfortunately the problem is somewhere else.

I would use the same version that you have now. If we are fault finding then we should only change one thing at a time. And, unless you plan to also upgrade DSM itself (a much longer job), you don't need a later version of the bootloader on USB. One other thing. If you made any changes to the config files on the original USB, you need to make the same changes to the new stick.

Better than my French : There are guys on here who know much, much more than me I think your USB stick with the bootloader on it may be the problem. I would get another USB stick, install a new copy of XPEnoboot on it and try to boot my server with it.

I can see that. The problem was that that I couldn't get the zimage you made to work and this "works" to an extent - at least to load and test apps and to migrate data.

If you have used the ISO file to do this, then you need to make some modifications to the ISO to enable "run" to work. I have got as far as using this to create a VMWare machine from scratch and I have been able to migrate data (but not settings or users) from 5.2. You need to use a utility like winiso to edit the isolinux/isolinux.cfg file to look like this: UI menu.c32 PROMPT 0 TIMEOUT 50 DEFAULT run MENU TITLE Synology LABEL run MENU LABEL Run KERNEL ../XPEnoboot APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 vga=0x305 LABEL install MENU LABEL Install KERNEL ../XPEnoboot APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 console=ttyS0,115200 upgrade=6.0.1-7393 This also gives you the console listing.

I would be happy to pay around £50 for an entry level. A few things come to mind, though. Looking at the retail prices, I reckon that Synology would want to price it a bit higher to avoid cannibalising sales of their low end boxes - no "freeware" version, then - and also I believe we are using a number of the "enterprise" features for which they would expect a premium. And then, if you buy a Synology box, you only get new versions for a limited period of time - either your box breaks and you buy a new one or they stop supporting your model. So they have a way of getting a continuing revenue stream from their existing customers. If they were, say, to produce a VMWare solution, then it would have to be time or version limited. Finally, if I just want a simple NAS solution and I don't want to "play", then I would be better off buying one of the low end boxes, putting a couple of 4Tb drives in it and forgetting it.

When you buy a Synology device, you're buying hardware, software and warranty support. The hardware appears overpriced because you can get the software and 'support' from here for free. Essentially, you're assigning 0 values to software and support in the cost = hardware + software + support equation. Well said

This is just my theory. I am more than happy for someone with greater knowledge to stop by.... There is some stuff on the Synology forum about printing and trying to add support for various printers but it became too complex for me, I'm afraid...

It's a long, long time since I played printers and print languages but I think we have a driver problem. I can print from Windows, where I have installed the Samsung printer driver. As it is a GDI printer, I am expecting the Windows PC to do the heavy lifting of rasterising the image. From Google Cloud Print, the job, as you say, gets printed according to GCP but no paper appears. However, the printer powers up and the data light flashes which makes me think that the print job is actually sent to the printer but the printer does not know what to do with it. I also tried the "Print Test Page" from the Printer Manager in DSM control panel and nothing comes out there. I have tried a few values for the printer model, including what I now think should be the best fit - 1650 - but no joy. However, it depends on what you are trying to do, I did manage to print a couple of documents from my Android phone using Samsung Mobile Print.... but it takes an awfully long time on the phone.

Might be worth a try. On DSM, I have it defined as a network printer and it shows up in External Devices / Printer as name: usbprinter1. Mfr: Samsung ML-1660 series with a command set of GDI, FWV, EXT. On windows 7, I have it defined via a standard TCP/IP port, with IP address = IP of diskstation, Q as usbprinter1 (same name as shown in DSM), LPR and with LPR byte counting enabled. I'm using the ML-1660 driver which I installed separately and RAW output. And that's it. If yours looks like that, then I am a bit stuck too.

I have this printer connected to a N54L bare metal (and under ESXi at one point). It mainly works but sometimes my wireless connected laptop sends prints to it and they just vanish into the ether. My wired PC always works. I think you are saying that the microserver is connected via wireless so even though I can't think of a good explanation for doing this, how about trying it all on a fully wired connection. If that fails, we could compare our two setups.

DSM 6 does not work on Xpenology. The tutorials you have seen are for those people who left their update settings to default with the result that their machines updated to DSM6 - at which point they lose access to their data. The tutorials show how to downgrade to a supported version so that they can get their data back. There is no date as to when (or if) the devs will be able to get DSM6 to work. they are dependent on Synology releasing source code and then working out whether they can get it to run.

Ah! I'm with you. The first drive is your boot drive not a DSM volume.My mistake. You want to stop DSM seeing your IDE drives. You have to modify the boot image to do this. Have a look at this thread, it shows you which parameter to add and points you to a video which show explain how to do that. viewtopic.php?f=2&t=10774&p=52030&hilit=remove+ide#p52030

I think the missing piece is what else you are going to use your ESXi server for. The other VMs you intend to create may affect how you configure your server. ESXi will quite happily boot from a USB drive and that will save you trying to partition your SSD. I am assuming that you will connect your HDDs via RDM and so, as far as DSM is concerned, the datastore doesn't need to be on anything particularly fast as the virtual machine folder will only contain configuration and the xpenology virtual disk (or .iso file). This is only read at boot time, the DSM system itself will be on your HDDs. So I have: USB with ESXi 1 small HDD with a datastore containing the DSM VM and others 3 x HDD for DSM.

You have disk 1 on IDE(0:0) and disk 2 on SCSI(0:0). Not sure why you have done this. I guess the disk in between is IDE(0:1). I suggest that you reallocate them on the same SCSI channel as (0:0) and (0:1)

If you load the same version that you broke and you hadn't modified the image - say to change mac address etc, then it should boot and DSM should come up OK. DSM, your applications and their settings (such as Plex) are installed onto the HDDs so I would expect them still to be there.

Player behaves as I described. My test system has a 100Gb disk occupying 10.2Gb of disk space. I suspect workstation is the same.

Try 20Gb. If you are short of real disk space and you keep the option not to allocate the disk space "now" then it will only allocate enough for the install. I tend to create the disk as a single file - but I have no idea whether that makes any difference.

I did have that problem once and it was because the virtual disks I was trying to install DSM on were too small. What size have you used?