Jump to content
XPEnology Community

stanza

Members
  • Posts

    288
  • Joined

  • Last visited

Everything posted by stanza

  1. stanza

    LSI Cachecade

    try it and see. I am guessing it should work... Drivers for the Card should be there, xpenology should see one large drive. which you can then setup and a single volume. Only issue I can think of is if the volume is too large eg greter than 16tb problem for ext4.... the fix would be to make multiple less than 16tb volumes. Let me know if you get stuck
  2. if it's an intel chipset it will just work. if it's a broadcom chipset you will need to add the firmware files (drivers) in the correct places for it to work.
  3. Gday philsrb. Not looked at 5.1 as yet myself. Have you done a search thru the file system for similar lines? eg are they moved / hiding elsewhere? find /* | grep "internalportcfg" etc?
  4. Read this thread http://xpenology.com/forum/viewtopic.php?f=2&t=3298 .
  5. Your lacking some info. Your Games n Stuff PC......what OS is that running? It's easy enough to get decent speeds from Xpenology's networking. If your OS for games n stuff is Linux / BSD / Unix etc then bonding multiple cards can be the cheapest way to go (no switch needed if direct connecting) else cheapest is to grab some old 10Gb Fibre cards, and a length of fibre cable should see you getting an easy 9.90 Gbits/sec Way more than a bunch of HDD's raided together will give you. Emulex 10GbE Virtual Fabric Adapters work perfectly, and can be found cheap on eBay... if your lucky they will come with transceivers. Then all you need is a cheap LC to LC 50/125 cable to connect them together if you need more speed, buy dual port cards and then bond both of those ports together quick guide on how to bond gigabit cards here http://xpenology.com/forum/viewtopic.php?f=2&t=2476 .
  6. Think from memory I gave more than 26 a whirl once. Had to change the maxdisks setting but it seemed fine. MDADM has a limit on the max drives in a mirror set.... so that might be the limitation... eg /dev/md0 and /dev/md1 (OS and swap space) are mirror sets which go across all drives...... .
  7. MD0 = Mirror raid where the OS resides MD1 = Mirror Raid where the swap files lives MD2 = Raid 5 Array where your volume lives No somethings gone amiss there I would guess, and as such the reason you have such slow access times. I would wipe the drives completely and start again..... were these drives previously used in a mdadm array in another OS??
  8. t's a known problem sadly. Drives jump around all over the place.... but dont actually cause any issues.......as mdadm uses the uuid of the drives to assemle the arrays....but yes makes identifiying drives a little messy .
  9. maybe you need better lan cards? ie ones with tcpip offload etc to relieve the cpu load?
  10. Glad it helped. Was a fair while ago I did it myself......so yeah... just have to to find the right files and watch dmesg as to where to place them and it all works. .
  11. Broadcom cards need you to add the firmware into the correct folder. Tho, you might have to temporarily add another lan card into the system to get xpenology installed. EG grab a cheap intel e1000 card etc to get you going.... then you can download and fiddle with the correct firmware file and as to where it need to be placed. dmesg outputs can help you find where the driver is expecting to find the firmware files. For a 10/100 Broadcom card I have my notes ============= Download these files (will put them up somewhere for you) http://stanzabike.net/images/xpenology/versions/Nanoboot/bnx2-mips-09-6.2.1a.fw http://stanzabike.net/images/xpenology/versions/Nanoboot/bnx2-rv2p-09-6.0.17.fw copy them both to /usr/syno/hotplug/firmware /usr/syno/hotplug/firmware/bnx2 reboot should get it working for you......
  12. I would disable as much ports (usb and onboard SATA) as you can. then work from there 1st set the SATA / SAS / msata ports....eg work out how many and convert to hex 2nd then E-SATA if you need it. 3rd then usb ports if there is just one esata port use 0x1xxxxx, that is 1 x esata port and the xxxxx are the hex code you used for the SATA etc. it's confusing and complicated fudge.... but once you get it right will work fine. also I would suggest not hiding the usb stick (eg entering PID and VID in menu_nano.lst file) until you have sorted the above out. as then you can see in storage manager if the usb port is getting detected as a SATA port with you hex codes. once sorted, then go back and hide the usb stick
  13. http://xpenology.com/forum/viewtopic.php?f=2&t=2028
  14. yes speed of SMB copy from one Xpenology to another is pretty bad. I work around it by using the backup and replication app backup from one box to another, then just move the folders / files you will get full speed of the network this way. eg SMB copy = approx 50-60mb/s backup (which is really rsync) = 115-120mb/s .
  15. Unless you have pretty much nothing running or installed on the system HDD spindown is a waste of time trying to chase. There are way way way to many things that wake the drives back up or prevent them from sleeping eg, just enabling SMB sharing, and setting the box to become the master browser..... then enables the guest account..... which in turn either keeps the drives awake, or wakes them backup from sleep every 20mins. .
  16. stanza

    Power wattage

    No need for a video card.....remove it change ram.... less sticks = less power usage change HDD's to slower spinners Change fans, to lower power ones. .
  17. edit /etc.defaults/synoinfo.conf and /etc/synoinfo.conf change the section # service limitations maxaccounts="16000" maxgroups="512" maxshares="512" maxdisks="16" <<<<<<<<<<<<<<<<<<< maxprinters="2" maxlogsize="64" maxvhost="30" save both files, go back to storage manager and wait a minute or two... it should then automagically change. If it does't refresh (which it doesn't seem to do on stupid internet explorer) try a different browser. . .
  18. Some realtek are fine, some are bad. I have a HP Mediasmart EX490 which has a Realtek 8168c onboard EX490-1> dmesg | grep "eth" [ 8.191947] b44: Unknown symbol phy_ethtool_sset (err 0) [ 8.192037] b44: Unknown symbol phy_ethtool_gset (err 0) [ 8.219545] r8169 0000:03:00.0: eth0: RTL8168c/8111c at 0xffffc900100fe000, 00:26:2d:01:f9:32, XID 1c4000c0 IRQ 44 [ 8.219549] r8169 0000:03:00.0: eth0: jumbo features [frames: 6128 bytes, tx checksumming: ko] [ 16.020600] usbcore: registered new interface driver ethub [ 16.871388] r8169 0000:03:00.0: eth0: link down [ 16.871396] r8169 0000:03:00.0: eth0: link down [ 16.871798] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 19.671905] r8169 0000:03:00.0: eth0: link up [ 19.672398] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready I can easily saturate the network with it. I would suspect maybe there is something else going on with your system eg IRQ clash etc. When you say " the other has one onboard realtek 8111e and a second one mounted" What does that actually mean? does it mean you have added in a second Realtek card? if so where is it mounted? PCI or PCI-E slot etc What else is in the system? have you tried to disable anything in the BIOS you do not require, eg Serial ports... Printer Port etc to release IRQ's ? tried it with only one Lan port? eg disable the onboard and just use the add in card? .
  19. Microservers do not have Proprietary PSU's They use FlexATX PSU's and can be obtained cheaply on ebay any size wattage up to 350w are cheap and can be had in many different configurations eg power plugs in .....all molex, all SATA, or combinations of the two. etc .
  20. If your BIOS / Lan card are enabled to allow WOL. "Be aware that not all lan cards / computers can be awoken this way." Then you can as above, change the settings manually to reflect a working setup eg changing "d" to "g" etc To test shutdown your xpenology box and test if you can wake it back up by sending the "magic packet" to the mac address. eg for me I use Linux, and I use a little program called gwakeonlan (you will have to source one that suits yourself and Operating System) then I simply select which Xpenology to boot and press Turn On Button oh and djelusion, not sure about the ex490 having WOL or not.... I believe it does... but on mine I have change the BIOs settings around so much that I don't know what are the original settings anymore
  21. You can always just buy a case that will take more drives and transplant the Microserver innards into it. http://forums.overclockers.com.au/showthread.php?t=1081502
  22. Bad disc, bad sas cable, or not enough power I suspect. .
  23. SMB Mounts from 1 box to another are pityfully slow. to test the real speed of your boxes I suggest Set one box as a network backup target, then have the other do a network backup to it. (eg an RSYNC) you will probably find it will use the full bandwidth and easily saturate your network. SMB from another box to / from your xpenology will be fine. Just SMB from one to another is pretty sad. .
  24. for nanoboot I dont believe you need the mac1= parameter in the menu_nano.lst file nanoboot automatically finds the correct MAC Address (unlike older versions) though you can change the netif_num=4 down to netif_num=1 if you only have one lan port then if you have edited both /etc.defaults/synoinfo.conf and /etc/synoinfo.conf files, with the correct "g" settings (make sure both are the same) double check what MAC address the system is recognising at a command prompt (SSH) run dmesg | grep "eth" should show something like EX490-1> dmesg | grep "eth" [ 8.193093] b44: Unknown symbol phy_ethtool_sset (err 0) [ 8.193178] b44: Unknown symbol phy_ethtool_gset (err 0) [ 8.220657] r8169 0000:03:00.0: eth0: RTL8168c/8111c at 0xffffc900100fe000, 00:26:2d:01:f9:32, XID 1c4000c0 IRQ 44 [ 8.220660] r8169 0000:03:00.0: eth0: jumbo features [frames: 6128 bytes, tx checksumming: ko] [ 14.472234] usbcore: registered new interface driver ethub [ 15.436686] r8169 0000:03:00.0: eth0: link down [ 15.436693] r8169 0000:03:00.0: eth0: link down [ 15.437154] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 18.237214] r8169 0000:03:00.0: eth0: link up [ 18.237674] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready then your wake on lan application should work. Be aware that wake on lan doesn't like to transverse wireless networks.( if your trying to wake the box from a phone etc) .
  25. maxdisks setting is only for the display of bays in the storage manager. And also for the amount of disks that will be mirrored (for the OS and swap partition) you need to edit both files /etc.defaults/synoinfo.conf and /etc/synoinfo.conf to figure out what hex parameters you need you get everything recognised correctly read my thread here http://xpenology.com/forum/viewtopic.php?f=2&t=2028
×
×
  • Create New...