Hostilian

Sorry.. Which version are people testing here?? The problem for me was getting (6.0.2) 8451 working. Has that been resolved? 6.0.1 - 7393 works fine for me; both bare-metal and vmware (apart from BTRFS)..

Hi all.. Anyone managed to work around this error please? Working disks are kind of important! #H

So it's not just me then! Thanks for looking into it. Must UEFI boot be used for this? Would it be possible to go back to Legacy boot? #H

I'm getting errors on bare metal (using your disk image) though it's fine in Vmware. Error is 'We've detected errors on your hard drives (1,2) and the SATA ports have also been disabled. Please shut down or repace or remove the hard disks to continue." Any thoughts? I do have a previous install on them (7393), so maybe it needs them cleaned up first? Cheers #H

Sorry, slightly off topic.. What's your Brix like (Gigabyte yeah?)? I've been looking at them for a while now (as a replacement media PC beside my TV) - if this project is able to get me a working DSM 6.0 on my current media server (as a larger Synology NAS).. Can't comment on transcoding as I try to avoid it.. Cheers #H

Hardware and software details might be useful.. 5.x or 6.x? An actually Synology, VM or whitebox hardware? Do you have many tasks configured?

The only difference from the Boot.vmdk in the 'DSM 6.7z' Image (linked earlier in this thread) is the syslinux.cfg file (posted in above thread). Don't confuse the boot mode 'Install' (on the USB key at your server's console) with the 'Install' option on the synology NAS (when you connect via a web browser and apply the PAT file). Oh and I'm testing this with DSM 6 (as per this thread) not Xpenology 5.x. #H

I have used the Boot.vmdk file in the VM linked earlier in this thread. DSM 6.7z (and the one without Snapshots - No SS) work fine. All you need is Boot.vmdk and run VMDKtoPhys to convert it. ALWAYS run the USB boot drive in 'Install mode' (not Run), you know the Linux menu on your server, the one you get when booting to the USB drive - NOT the synology menu, where you apply the PAT file in your browser. When the USB drive has been first created, edit the syslinux.cfg file (it's just a text file in the syslinux folder on the USB drive) and change the timeout to 100 or more (to give you time to change it from the default, which is 'Run'). I'd say that if you don't have an Intel (or known compatible) NIC, disable it in the BIOS.. If you select 'Run' mode, it will likely keep rebooting! So don't.. Here's my syslinux.cfg file. It defaults to Install mode. If you replace yours, make sure you put in valid SN and MAC addresses.. UI menu.c32 PROMPT 0 TIMEOUT 100 DEFAULT Install MENU TITLE Synology LABEL Install MENU LABEL Install KERNEL ../XPEnoboot APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=SNHere mac1=mac1Here mac2=mac2Here mac3=mac3Here mac4=mac4Here mac4=0011430c30c0 vid=0x0EA0 pid=0x2168 console=ttyS0,115200 upgrade=6.0.1-7393 LABEL Run MENU LABEL Run KERNEL ../zImage INITRD ../rd.gz APPEND root=/dev/md0 ihd_num=0 syno_hw_version=DS3615xs custom_sn=SNHere mac1=mac1Here mac2=mac2Here mac3=mac3Here mac4=mac4Here console=ttyS0,115200 The first time you boot, it should ask you to Install the PAT image and set up your system. There is a link to an update 7393 pat file earlier in this thread. Not sure if that has been tweaked from the one from Synology? I used the one linked in the thread, not the one from Synology. Good luck! #H

Nice work! +1 for ISO. Would be handy, thanks!

Yep, read through that thread and tried everything. Not that fussed though as I won't be using the features that use it.. Thanks! edit.. Power management (timed shutdowns) working fine on Bare Metal!

I read that that wasn't correct (and safe to ignore).. Try the command I mentioned. #H

..Mine as well - if BTRFS works too! Cheers, #H

No worries. Works fine for me! Where are you seeing that on the console? Confirmed using SSH and 'more /proc/cpuinfo' that mine has 4 cores.. Cheers, #H

To get it working on bare metal, I first tried the install ISO and PAT file manually. No dice. I already had a VM working in VMWare workstation (downloaded earlier in this thread) and noticed the BOOT.vmdk (I knew this worked fine). Basically, I took a copy of Boot.vmdk and ran a great little tool called VMDKtoPhys to transfer it to a USB disk.. (simple, huh) Plugged the new USB Boot drive into my physical machine with my 2x 3TB drives, disabled the sound card in the BIOS (and sorted the boot order).. As it's a USB drive, it's easy to edit the Syslinux.cfg file. Add SN and MAC if you want (when plugged into your normal computer). I booted to the USB drive, selected 'Install' option. Followed the Wizard. Voila, working.. You need to keep booting in install mode (after you've set up the disks). I've set this to the default option now. Downloading the Update-1 and Update-2 files for 7393 manually and installing manually worked fine. Only thing that doesn't work is BTRFS (that I've tested so far) and I can't update to 8451. Oh and it's SERIOUSLY fast - compared to my little Synology 216j NAS.. #H

Yep (thanks though). Read through that and watched the video a couple of days ago (pretty useful). I'm getting caught up fast as I came to the party late! Oh.. I used a slightly different method to get DSM 6 onto my baremetal server.. Modifying the MAC address was the next thing I tried - though it didn't resolve the 'no serial number' issue.. I did use ones generated by the spreadsheet - though didn't try to register them. I 'found' a ds3615xs serial number - but couldnt find a MAC address for it. Is there a way to generate linked MAC's from a valid (It is, I've checked) serial number? Thanks #H

I get that error in a VM too.. I did notice that my bare-metal install doesn't have a serial number listed in the System Info section. It's blank.. Does the 6.02 update need a valid serial number or something, I wonder? I've wasted the last while trying to modify the serial number in the system using putty. I had already added it to my syslinux.cfg file (I generated it) but no dice! #H

i3 4330 ASUS H87i-Plus 16GB RAM (DDR3 1600) 2x WD RED 3TB 32GB Sandisk ultra fit flash drive I had 3 other drives in it - as it had Server 2012R2 installed - but I've disconnected the power cables while I muck around (so I don't need to reinstall anything).. I've managed to install the mini-updates. First to update 1 (just in case) and then to Update 2.. It's now on DSM 6.0.1-7393 Update 2 (BTRFS still fails when created). Next step is to try to go to 8451.. edit.. Trying to update to 8451 and it says 'the system is not compatible with the patch file'..... hmmm #H

Hmmm.. I seem to have DSM 6 (7393) working on my mini server - Bare metal, not in ESXi. I was using it as something else but had 2 new 3TB drives to do some tests - so that's what I left inside.. DSM 6 was installed onto a USB3 drive - and I booted from there.. Anyway.. Can logon fine, it's on the network etc.. It's still got the same issues with formatting the disks with BTRFS but can use ext4 in RAID 1 on the two 3TB drives (2.7TB usable). It creates shares etc fine and is browsable. It won't shut down when scheduled in a task - though clicking the button on the console works fine.. It installs apps fine (Hyperbackup, log station, Security camera stuff). Currently taking an image of the memory stick (wishing I hadn't used 32GB) so I can fiddle with it.. #H

Hi all, Stumbled across this project - and thread - whilst looking for a Freenas plugin (of all things). I have a Synology 216j (long term is to use this as a backup NAS) and I'm considering a new Synology NAS (916+ or 1516+/1517+ when they come out). However, I have a mini server that I've been 'testing' with Freenas. If I could get DSM6 to work on it, that would be amazing (medium term goal).. Anyway, thanks to oktisme for the initial DSM6 image - and everyone that has contributed so far (a big help). Few queries, if you don't mind! Apologies if I've missed the fixes in this thread. In the interim, I'd like to test it in VMWare Workstation. I've managed to get the downloadable (on this thread) VMWare image working. I've added extra drives and even got BTFRS working.. All good there. Problem is getting it to work when installed from 7393 ISO. I've got a VM with 2 disks (Sata) and mounted the ISO - then installed (using the 7393 PAT file). On reboot, I changed the boot sequence to have the ISO first, then selected RUN. It went to Booting the kernel so I went as normal to scan the subnet. This time it wasn't on the network. After a bit of fiddling, I noticed that the VMX file for the VM had e1000 against the network card. I changed this to "e1000e" and rebooted. Now I could get an IP address and connect to DSM.. Unfortunately it said that I had migrated a new disk and if I wanted to migrate or clean the disk. No amount of messing around in here seems to make a difference.. I have tried clean migrate using the earlier 7393 PAT file - it just goes back to the Migrate screen (after a reboot). Any thoughts?