totalnas

More drivers to this release: http://xpenology.com/forum/viewtopic.php?f=2&t=928#p4431

Hi, This is done for AX88179 in DSM 4.2 x64: http://xpenology.com/forum/viewtopic.php?f=2&t=928#p4431

Sure! Moreover: If you boot a recent Linux LiveCD (like Ubuntu) with all disks connected from a Synoly (aka XPEnology) unit, all volumes are automatically mounted at boot. SHR volumes are simple LVM over Linux-RAID.

Great news! Kernel module (driver) for external Gigabit USB 3.0 devices based on AX88179 for DSM 4.2 x64: ax88179_178a: http://pastebin.com/zr5jgd9N As usual, UUDECODE the file, decompress it, copy the ".ko" file to "/lib/modules/" and you can start working after: $ insmod /lib/modules/usbnet.ko $ insmod /lib/modules/ax88179_178a.ko I hope next binary releases will include this great driver!

Please, I need feedback to complete a virtual-SSD hack! TN

Hi, These drivers don't have collateral effects over your installation. Please, check your configuration. If you need to access to repair, you can use an Ubuntu LiveCD. All disks/LVM/RAID partitions will be detected! TN.

Great! I hope other releases of 4.2 will include them also. I suggest that ALL developers share the ".config" file of different releases. I feel that the community needs to try divide the efforts in: 1) Kernel patching: new drivers, USB VID:PID hack, etc. 2) BIOS hacking: SYNOBIOS modding. 3) Script improvements: like UPS, LVM, SSD hack or others. 4) Binary releases: boot IMG and PAT file for plainPC, Microserver, ESX, VirtualBOX, etc. Peharps, after this division someone can starting to compile non-x86 versions. TN.

Hi, I feel rigth if my info helps you! I hope that releasers of new binary XPEnology versions will include these fixes/improvements. If someone has new ideas I'll try to assists to you. TN

For a NAS your don't need a huge CPU. Best price/performance relation is: HP N54L + 2x8GB DDR3 + 4 SATA HD + 1 SSD + XPEnology

Hi, I use one HP N54L and it works! Please, revise that you COMMENT the three lines: chsum, vender and hw_model. And boot using SYNOLOGY_2 config, not fallback (SYNOLOGY_1). FYI, I use the release DSM 4.2 3211 x64

FYI, The releases 3202 and 3211 are BINARY COMPATIBLE. Both uses the same Linux kernel for x64: 3.2.30. You can mix modules from both sources, mainly because no modifications from 3202 to 3211 in the kernel.

UPDATE: (based partially on info from http://forum.synology.com/enu/viewtopic.php?f=39&t=17091) Problem: After rebooting your UPS ins't detected. How to fix it: Put a startup script that call to "ups.sh start-all". Here an example of "/usr/syno/etc/rc.d/S12UPS.sh" : #!/bin/sh case $1 in start) /usr/syno/bin/ups.sh start-all ;; stop) /usr/syno/bin/ups.sh stop ;; *) echo "Usage: $0 [start|stop]" ;; esac Moreover the file "/usr/syno/bin/ups.sh" has errors !!! (please, someone can report this to the Synoly team?): One error is in the "stop" command. It don't work because the IF SENTENCE is erroneous! Here the correct code: stop) # wait 1 sec to prevent instability leading to restart sleep 1 IsDevAlive if [ 1 -eq $? ]; then StopUps log logger -p err -- "$0 $1 invoked." echo "Stop UPS" echo "$0 $1 invoked." /usr/syno/bin/synosetkeyvalue /etc/synoinfo.conf upsmaster no fi ;; You need to execute the commands if "isDevAlive" is TRUE !!! The original code say " if [ 0 -eq $? ]; then" Please, fix this!

Hi, To fix your UPS problems, first read: http://xpenology.com/forum/viewtopic.php?f=2&t=917 Aditionally, check the UPS with a recent LiveCD distribution of Linux (like Ubuntu). If your UPS is detected/supported in Linux, you can enable it on the XPEnology!

Hi, To enable your UPS see: http://xpenology.com/forum/viewtopic.php?f=2&t=917

I like to confirm that this release works without problems in a Proliant Microserver M52L. Moreover, all kernel modules are binary compatible with the previous x64 release of DSM 4.2 (3202), so you can upgrade to this new release (3211) without problems. Good news!

Hi, The problem: You have attached an UPS to your XPEnology server but the web interface shows "no hardware found" in the UPS window. The solution: The support for UPS hardware is enabled in the Syno using the Linux package NUT (http://www.networkupstools.org/). If you can detect your UPS with a recent distribution of Linux (try with an Ubuntu LiveCD) you CAN use your UPS with XPEnology. 1) Check that the kernel has access to your UPS. For USB devices, execute "cat /proc/bus/usb/devices" and search for the VID:PID values of your device (in my case "P: Vendor=0001 ProdID=0000 Rev= 1.00", so "S: Product=STD UPS MON V1.0"). 2) Check if the NUT driver can speak with your device (you can copy the info detected by Ubuntu when you try the Linux support with the LiveCD distribution). My UPS uses the "blazer_usb" driver, so I check it with command "blazer_usb -u root -DDD -a ups" after editing the file "/usr/syno/etc/ups/ups.conf" and set the correct values for entry [ups]. Example: [ups] driver = blazer_usb langid_fix = 0x409 port = auto vendorid = 0001 productid = 0000 desc = "BLAZER_USB LANGID_FIX" #community = name #snmp_version = v2c If this check fails, you need to edit the "ups.conf" file. If the check goes right you only need to enable it in the Syno GUI. 3) How to enable the UPS in the Syno GUI? This is the trick: execute command "/usr/syno/bin/ups.sh start-all". This command starts all scripts related to UPS using your manual configuration of "ups.conf". Afer that you can show that the UPS monitor starts, and now you can show that in the GUI the UPS is detected. Good look!

Hi, I like to modigy the tool "/usr/syno/sbin/synodisk" to enable FAKE SSD disks. My idea is use XPEnoloy in a virtual environment and use virtual disks on SSD storage to enable the caching. The problem is that the virtual disks aren't detected as SSD. So, please, can you provide the output of the command (text and exit code) with a REAL SSD disk? $ synodisk --isssd /dev/sdX I'll apreciate the feedback! Thank you!

If you like to protect your work, you can do the suggested in this post: http://xpenology.com/forum/viewtopic.php?f=2&t=915#p4290 Please, when you release a new firmware include on it the "configs.ko" module for "/proc/config.gz" support. Please, when you create a patch for source code, use pastebin to share the patch. We need to protect our advances! Some git source repositories are removed!

Definitive solution to USB ports malfunction: See my post at: http://xpenology.com/forum/viewtopic.php?f=2&t=915&p=4292#p4292 You need to enable OHCI support! With DSM 3.2 (both revisions for 64bit, 3202 and 3211) you can download the correct drivers in this post. I hope developers will include this on new releases!

#4: OHCI support Current releases of the XPEnology lacks OHCI USB support (remember: USB 1.1 hardware has two different driver models, UHCI and OHCI; also all USB 2.0 hosts has two drivers, one for USB 2.0 protocol (EHCI) and one for USB 1.1 (UHCI or OHCI)). This is the reason because in the HP Microserver you lack USB support for low speed devices (like keyboard, mouse, UPS, etc.). The kernel loads the correct EHCI driver, but for USB 1.1 speeds only has the UHCI driver and the system can't comunicate with your devices. Here the solution: Add support for OHCI driver. You only need to modify the config file in the kernel with: CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_OHCI_HCD=m CONFIG_USB_OHCI_HCD_SSB=y And this will generate the correct "ohci-hcd.ko" module. This module will be automatically loaded at boot, so you only need to copy them to "/lib/modules/". WARNING: After recompiling this module the module "usbcore.ko" is different. If you try to load the "ohci-hcd.ko" in a system with the original "usbcore.ko" module already loaded you receive a kernel fault. You need to replace also the "usbcore.ko" module!!! FOR MICROSERVER USERS: If you like to complete your USB support in your machine: 1) Download the extended package of kernel modules (modules-4.2-02.05.2013.tar.gz ) and copy all of them in the directory "/lib/modules/": https://docs.google.com/file/d/0B5tpWhE ... _web&pli=1 2) Download the new "usbcore.ko" and "ohci-hcd.ko" modules and copy them to "/lib/modules/": http://pastebin.com/sH4RieEj / http://pastebin.com/4vL65THx 3) Reboot and you have full USB support (all ports, USB 1.1 and USB 2.0 speeds)!

#3: DM-Mirror support for LVM2 physical relocation One of the most limited functionality in the DSM firmware is the lack of RAID/Volume modification tools. For example, after you create one SHR raid volume you can't move/relocate/decrease/etc. disks. Nevertheless, the Linux kernel has functions to relocate LVM extends. Moreover, you can reduce logical volumes using resize2fs and you have the full power to modify your RAID. All tools are included in the firmware (mdadm, lvm, resize2fs, etc.) except the modules to migrate a LVM extend: dm-mirror.ko Here the modules that you need (for DSM 3.2 kernel 3.2.30 x64): DM-LOG: http://pastebin.com/RaVVpqMb DM-REGION-HASH: http://pastebin.com/Dj1Z69xy DM-MIRROR: http://pastebin.com/Jc32M86g You only need to load them in this order to enable the PVMOVE command in the LVM tool: $ insmod /lib/modules/dm-log.ko $ insmod /lib/modules/dm-region-hash.ko $ insmod /lib/modules/dm-mirror.ko The command is "lvm pvmove", or you can create the symlink with "ln -s lvm /sbin/pvmove" Moreover, if you like to load these modules at boot create a simple script file in "/usr/syno/etc/rc.d/" to load them (for example, "S15LoadModules.sh"). With this great tool I administrate all my RAID/LVM volumes without any limitation!

#2: Add "/proc/config.gz" as a module. For future support of XPEnology you can implement a simple way to continue with your work. The main changes in the kernel are "patches" and "config". Related to patches, you can publish them on this forum (or you can create a huge public source repository). Related to the config, you can INCLUDE THIS INFO in your release. Here the instructions: * When you compile a new kernel, the most relevant file is the ".config". This file can be included in the kernel and you can access to it in the "proc" pseudo-filesystem (as "/proc/config.gz"). This ins't set by default in any of the current releases of the XPEnology. But you can include it AS A MODULE. If your release has the module "configs.ko" (not "configfs.ko") you don't waste any memory space in the kernel. But at any time some user can execute the command "insmod /lib/modules/configs.ko" and can obtain the current kernel configuration with the command "zcat /proc/config.gz > ./.config". After that is VERY EASY to compile new kernel modules or continue your work improving new kernels. * You only need to set this values in the kernel config prior to compile it: CONFIG_IKCONFIG=m CONFIG_IKCONFIG_PROC=y The first value enables the module, the second one inserts the file in the "/proc" directory. * Remember to include the module "configs.ko" in your final release of the firmware! Your don't need to load this module at boot, only do manual loading for show the kernel configuration. Best!

#1: Command line boot parameters for set IS_SYNO_USBBOOT_ID_VENDOR & IS_SYNO_USBBOOT_ID_PRODUCT If you like to use the XPEnology on physical hardware with a USB flash drive for booting, you know that this boot drive is mounted and used as a standard USB drive. In the sources of the syno is the code to prevent this and hide the boot drive. The problem is that this code is based on USB VID:PID numbers. Here one definitive solution: The VID:PID values are store in the file "include/linux/syno.h" as values: #define IS_SYNO_USBBOOT_ID_VENDOR(VENDOR) (0x0DD8 == (VENDOR) || 0xD80D == (VENDOR)) #define IS_SYNO_USBBOOT_ID_PRODUCT(PRODUCT) (0x173C == (PRODUCT) || 0x3C17 == (PRODUCT)) And these constants are used in the file "/source/linux-XXXXX/drivers/scsi/sd.c". The main function "syno_disk_type_get()" has the code that uses this constants. You can change the values in the header file to target your pendrive and recompile the kernel... OR YOU CAN WRITE NEW CODE IN "/source/linux-XXXXX/drivers/scsi/sd.c" TO OVERRIDE THESE VALUE WITH BOOT VALUES, LIKE FOR EXAMPLE WITH "syno_hw_version". What needs to be modified? 1) Add one new value in "/linux-XXXXX/arch/x86/kernel/setup.c" for new VID:PID parameter (like extern char gszSynoHWRevision[]). 2) Modify the function "static SYNO_DISK_TYPE syno_disk_type_get(struct device *dev)" in "/source/linux-XXXXX/drivers/scsi/sd.c" to use boot values or the constants. 3) Add the new parameter to your "grub.conf" file with the VID:PID of your flash drive. That's all!

Hi to all, This thread is mainly for advanced uses that has tools to compile the kernel. The idea is share here tweaks, tricks and other things to improve the support of the XPEnology. Please, use one post for each topic! All contributions are welcome! TotalNAS