R0KH

It seems I had some trouble getting SMB to work with Kodi aswell, but the problem was solved when changing the settings in DSM to allow for SMB1 to be the minimum required version. When you set it higher SMB shares won't work with Kodi, tried with latest versions on both Android and LibreElec, so I gues they don't support newer versions of SMB.

Using the DS3617xs image on my system in the signature below, works fine, however many synocommunity packages aren't available. Not sure if they are on a 3615xs which I used when on DSM 5.2 where these packages were available. So it could be DSM 6.1 or the 'hardware' version you run, not sure... Currently I'm using Docker to run apps like Sabnzbd and Sonarr which is working quite well I must say, I might even like this better than running these apps natively on DSM (if it were possible). There's some discussion about using hardware transcoding on DSM with apps like Plex. I can only guess that's what you want to use quicksync for, but it's unclear to me whether it works and it depends on the exact hardware configuration, especially with Xeon CPU's.

After installing everything fresh, which went pretty much flawlessly btw, I didn't see any issues with samba on my Windows PC. I did however have issues trying to mount a folder through CIFS in a real Synology from my baremetal system. It just failed all the time so I went on using a FTP share to copy back my data.

Thx! Results will be shared...

I'm probably not really upgrading from DSM 5.2 which I'm currently running on and will clean install the whole thing. I will go straight to the most recent version 6.1.3 build 15152 as I see several positive reports already about upgrading to this version, so a clean install shouldn't be a problem either. System is baremetal, so no ESXi.

Time for upgrading to DSM 6 is at hand (for me)! Currently backing up data and then some hard- and software upgrades, probably a clean install rebuilding arrays, so will post my findings after everything is done.

I see that things are becoming interesting now for upgrading to DSM 6. It took a while, but I'm happy things haven't bled out here at the XPenology community and things are even progressing thanks to you quicknick. That said, I see that there isn't any guide for upgrading from DSM 5 as of yet. Are there any special steps to follow for doing this and is there a guide still in the making or do we have to wait for the 2.3 release.

Yes it can! viewtopic.php?f=2&t=3529

This is a normal message if no hard disks are connected to the SCSI bus. The boot ROM on the SCSI adapters can be disabled within the setup which can be entered right before you receive this message if you do not intend to boot from any device connected to the SCSI bus. You should see a message that says "Press Control-C to start LSI Logic Configuration Utility...". Once in there, select an adapter and look for "Boot Support" and turn it off. You should also check the BIOS settings for the boot order, but you may have to remove the card first to get in your mainboard's BIOS. Some more info and links to EFI shell files for different EFI versions (this is what makes it a pain to get the shell to function properly as you need the same version as your mainboard's EFI version): http://forums.tweaktown.com/asus/52327- ... evice.html You can also try the Shellx64.efi which I used, though I'm not sure if it will work for you: http://1drv.ms/1TUYc7s It's quite some time ago since I did this on my HBA so I'm not entirely sure how I got it working eventually, but I do remember it taking me some time (thanks to the annoying EFI shell). Also, I wouldn't have got it to work if I gave up on it and you shouldn't either (otherwise send me your HBA please)...

EDIT: Lol, I see now that you have an old mainboard with a BIOS so everything below is not entirely relevant for your case, however I do believe the commands for flashing the LSI controller are the same, but you can do them from a DOS prompt. Well, it kind of depends if your mainboard has a UEFI or a BIOS. Most systems nowadays use UEFI and this is quite a bit different than flashing firmware from DOS command prompt. I have a UEFI mainboard so I launched a UEFI shell. You will have to look up how to do this yourself as it can be different for each mainboard, you often need a shellx64.efi file and put this together with the firmware files on a FAT32 formatted USB stick and figure out how to boot from this stick, sometimes you can do it from the UEFI 'BIOS', but it's not always the same. It took me quite some time to figure it out, but if you have a UEFI mainboard you have to do it this way as you can't do it from a DOS prompt as far as I can remember. Once you're in the UEFI shell you can do the following (remember that this is all at your own risk!): type: map to list all available filesystems mount fs*: * = number of filesystem to mount use command To open filesystem type: fs1: Type: ls to list contents of the filesystem. --- Commands to flash LSI controller: This command puts the sas2flsh command into advanced mode (-o) and then erases the flash (-e 6) firmware and BIOS: sas2flash.efi -o -e 6 Rebooting at this point would cause the HBA to cease functioning as the article warns: DO NOT REBOOT. If you do reboot, or if you attempt to flash the firmware and/or BIOS image and it does not flash correctly, you will have to RMA the controller. The following command will flash the controller: sas2flash.efi -o -f [filename of firmware].bin -b mptsas2.rom Use this command to check the firmware version of the controller: sas2flsh -listall If it's all good you can safely reboot your machine.

I have the same card and it works in 5.1 (not yet upgraded to 5.2). You need to flash the right firmware to the SAS card before using it and there were also some issues with a specific version of firmware for this card. Ah, here it is: viewtopic.php?f=2&t=4985 P20 firmware is bad, P19 is ok as I have this one aswell.

For the people who don't know exactly how to do this.... The contents of the file should look something like this: #!/bin/sh echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo conservative > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor echo conservative > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor echo conservative > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor It can be simply made with a text editor. Above is how I did it and it works, finally I don't have to do it by hand anymore every time the server is rebooted. What about the "insmod" command? shouldnt it be in the script too? or is there a better place to put that into? (Sorry to ask, iam a linux newbie) I have a Intel CPU and the scaling governor works fine already, so I don't need the 'insmod' command. In my case with above script it works perfectly, also after reboot, which was the part I never got to work properly. I always had to change the governor manually by executing a task with the same commands as in the script after a reboot and now I don't need to anymore which is great!

You can easily find how to do this if you just Google it... To make it extra easy for you check this link: http://blog.michael.kuron-germany.de/20 ... nt-page-1/

For the people who don't know exactly how to do this.... The contents of the file should look something like this: #!/bin/sh echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo conservative > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor echo conservative > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor echo conservative > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor It can be simply made with a text editor. Above is how I did it and it works, finally I don't have to do it by hand anymore every time the server is rebooted.

I think video transcoding is something only the 'Play' versions of Synology NAS's are able to do and as Xpenology is based on the DSM from a 3614/15xs, which don't have the video transcoding options, this will most likely not be possible.