• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Zackbum

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Have found out that the automount for USB is related to udev (/lib/udev/...). Further investigating in this area ... I would like to have it completely automatic ... in case you put in a SATA disk and turn the little power switch to on, it should get automatically mounted to /volumeSATA/whatever/here_is_the_content. It should also be umounted safely by a script to make it unplugable without rebooting the box. Probably someone has a good guide how the standard linux mechanism is included into the synology world and whether there is something to be added to the boot image
  2. I don't think that it is a matter of drivers. There is no "intelligence" in the device at all, just two SATA devices and 2 USB ports, that have to be cabled to some internal connectors. As far as I can remember some configuration regarding USB drives have to be done, but I do not know exactly what it was or probably I mix up some things. When I put a drive into the3.5" tray I have to mount it manually and it works quite good, but I hae no idea about plug/unplug mechanism. In earlier times I did it with the following scripts: plug: echo "- - -" > /sys/class/scsi_
  3. Just found the description of the bay tray. It is a Sharkoon Quick Port Internal Multi.
  4. HI everyone, I started with XPenology about 4 years ago using trantor's boot images on DSM4.x. At that time I've build an HP N54L with 16 GB RAM and 4*4TB WD RED (seems to be somewhat a standard package). After reading several articles I replaced the optical disk drive (ODD) by a "thing" (words are missing, sorry, no native speaker) containing 2 USB3 ports, 1 2.5" SSD SATA tray and 1 3,5" SATA tray (including power switch) for an additional standard HDD. In addition I installed a card for USB3 ports. I know this whole setup has been quite popular. In earlier times I use
  5. The different versions are related to the architecture: x86, x64. I've got it running ... my fault, I missed to copy the new busybox but made a symlink from the existing one to acpid ...
  6. I've seen there are several packages of NB5031 available. Probably I've got one without? Do you use the package from trantor or the one I mentioned in my initial question?
  7. Sorry, my fault: - HP Gen7 N54L - 16GB RAM - 1*2TB (to be replaced by 4TB)+3*4TB Syno Array, - ODD bay with "Sharkoon QuickPort intern multi" hotplug docking incl. 2*USB3 front panel ports - NEC chipset based USB3 PCI Xe card with 19pin connector and 2 additional rear ports ACPI is enabled in BIOS. But as I stated: For me it looks like nanoboot does not include the necessary acpi-enabled busybox, so the symlink to acpid does not lead to the expected result when starting the daemon.
  8. It depends on settings in synoinfo.cfg. I had a similar issue and got it managed by setting the following values: SYNONAS> grep portcfg /etc/synoinfo.conf esataportcfg="0x30" usbportcfg="0x1fc0" internalportcfg="0xf" SYNONAS> grep portcfg /etc.defaults/synoinfo.conf esataportcfg="0x30" usbportcfg="0x1fc0" internalportcfg="0xf" SYNONAS> The values are derived from a bitfield. eSata is plug'n play and ideal for my solution with a pluggable drive for backups of the NAS. If you want it being recognized as an internal drive, change the values for esataportcfg (0x20 or 0x10) a
  9. Sorry, but for me it is not working in I took the packages from the links suggested in the Howto guide: viewtopic.php?f=15&t=3666 Neither the load of button.ko was included in /etc/rc nor the other stuff has been in place (S30 start/stop, busybox-copy, ...) So when I try to enable everything that is needed, I get an "acpid: applet not found" in case I try to start the daemon. So I assume there is no acpid-enabled busybox in this distribution. Probably I've made a mistake, so correct me if I'm wrong. THanks in advance.
  10. It is just a matter of underlying virtualization in combination with the release to be used. I've found a hint that you have to have EHCI support for UPSes. This is available 3211, but not in 3202. So I dropped virtualbox as virtualizer for XPenology: Current releases do not support neither e1000 NIC nor AMD stuff. VMWare Player 6 officially also has only e1000 NIC, but you can patch the vmx file and enter vmxnet3 instead of e1000. And vmxnet3 is supported in 3211. After that I created a bootable ISO image ( so I will have s
  11. When you install xpenology in a virtualizer like virtualbox or vmware player, you will have to face the problem, that the boot image put on a flash drive will not be recognized by the virtualizer, since the underlying windows asks you to format the flash drive. The normal solution is to convert the IMG file to VDI (virtualbox) or to VMDK (vmware) with e.g. vmboxmanage or qemu. Unfortunatly to boot from these virtual drives they will have to be the first in the list of being examined. And so they will get formated as part of the installation process. I was looking for a different solution s
  12. vi /etc/rc.local and attach the insmod-lines to the end. Save. If you are not familiar with vi, do the following instead: echo "insmod /lib/modules/hid.ko" >> /etc/rc.local echo "insmod /lib/modules/usbhid.ko" >> /etc/rc.local echo "insmod /lib/modules/usb-storage.ko" >> /etc/rc.local Be aware! Do always use ">>" and NOT ">", since the second one will not append the line but replace the file's content by the line! No restart needed in case you have loaded the modules already by hand.
  13. Hi folks, for testing purposes I got an XPenology release installed in a virtual box, curently it is DSM4.2-3202 upgraded from 2668. I have an old UPS standing arround here, a Mustek PowerMust 800 USB. I tried it under Windows - works quite good. I'd like to connect it to the NAS server. Unfortunatly there are several issues, that hinder me from doing so: - only protocol usbhid-ups is supported, Blazer_usb is not. Checked the NUT sources, installed toolschain and optware-devel to recompile and install release 2.4.2. Solved - I realized, that there is only one device available in /pr