mervincm
-
Posts
193 -
Joined
-
Last visited
-
Days Won
4
Posts posted by mervincm
-
-
Hello,
I just set it up on a bare-metal Supermicro X9SCL-F-O with a Xeon E3-1230V2, 16GB ram and 6x 2TB WD Green drives (various models)
DSM is reporting my 4-core (8-thread) E3-1230V2 as an i3-4130 2-core. GHz are the same (3.3).
Does anyone know why it's doing this, and is it normal?
Is it not utilizing the other 2 cores of the processor? (or does this really make a difference?)
Thanks!
This is a long term problem, but only a cosmetic one. The OS is able to correctly ID the CPU and use all available cores, so while it is a bit disconcerting, it does not actually have a negative impact.
PS with WD green drives make sure to adjust tler value to max
-
on my Xpenology NAS (5x2TB HDD)
hdparm -Tt /dev/md2 gets me
/dev/md2:
Timing cached reads: 30620 MB in 2.00 seconds = 15334.99 MB/sec
Timing buffered disk reads: 1478 MB in 3.00 seconds = 492.17 MB/sec
or something very close to it each time
Yet I am restricted to 180MB/sec over 10gig (10gig nic in PC and in Xpenology system, direct connected over fiber)
-
I don't like any MB with only 2 slots for RAM, although it will be fine for Xpenology. i3 is still a lot of CPU for just NAS. if you buy ECC, then i3 is a good choice. otherwise cheaper Pentiums are still more than enough. I don't know if you plan on usingthe wifi with xpenology or not, or if that wireless nic is supported, maybe check it out. H97 is also fairly overkill for what xpenology needs. 2 NICS are not the benefit you might think, unless your switch supports dynamic LACP AND you will have multiple folks hitting the NAS at the same moment with sequential reads / writes.
-
Adding an SSD r/w cache dropped my sequential read/write from a solid 110-113 (max of gigabit link) to in the 90's
I am not sure how you can get numbers like that, even on my 24GB RAM quad haswell xeon based xpenology with 10gig ethernet and 5x 7200 hitachi ent drives and jumbo frames, I max at about 180MB / sec sequential.
-
I have a real Synology 1813+ w 4GB RAM. I had a single raid of 6x3TB REDA and 2 SSD acting as read write cache. My sequential read and write for large files was actually 10-15% worse with 2 SSD in cache mode than without. I didn't notice a lot of random access improvement, but I wouldn't be shocked if it was there, it is hard to easily measure. I instead created a 2 SSD volume and that works wonderfully.
-
RAID performance is fine, almost any system you will get your hands on will be limited by Ethernet( large files) or disk IO (small files) and not by your CPU doing RAID calculations.
RAID is not about Backup, Backup is always required, RAID only sometimes is required.
-
baremetal install (USB) gives you easy access to smart data and all of you HDD ports, It's a great option.
-
It didn't
I tried with your latest bootable image, and the files are not there.
To be clear I got it working like this
1) I installed latest USB stick and booted from it, use an intel NIC for install, installed latest DSM and update 2
2) copy bnx2x-e1-7.0.29.0.fw into /lib/firmware/bnx2x
reboot
Is there a way to add this to the USB stick to have it work automatically?
PS I just sent you 25 US$ donation for the help and good work you do.
-
Start with finding the name of the driver with your specific card. does it work under a regular linux install or live boot? Is so you can dmesg from the terminal and look through it for lines that have to do with the NIC driver loading. once you have that string, you can install xpenology on your box and look for that preface in dmesg under xpenology. you will usually see some error messages there.
PS this card is known very picky with transcievers and twin ax DAC. make sure it works in your hardware/cable/switch combo under something like windows/ubuntu before you spend too much time working on xpenology testing.
-
I found a folder that looked good
lib/firmware/bnx2x
and put it in there as well, same permissions as the other fw files.
IT WORKED
IT WORKED
IT WORKED
The NICS are seen in syno portal!!!!!!!!!!!
Thanks so much, I am really a linux noob, I just really needed a starting point.
-
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......
forgive my lack of linux skills here, but I quickly got stuck
1) made USB with XPEboot, installed a pair of disks, installed 5022 update 2 - so far so good
2) downloaded the files you hosted, enabled SSH, used winscp and logon using the root id and the admin password - still looking good
3) traversed to /usr/syno/hotplug and created firmware (777 permissions) and put these two firmware files in (again 777 permissions)
4) traversed to /usr/syno/hotplug/firmware and created bnx2 (777 permissions) and put these two firmware files in (again 777 permissions)
restarted
still cant see the nics in the diskstation interface
dmesg through winscp console
[ 4.321900] bnx2x: Broadcom NetXtreme II 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.70.30-0 (2011/10/25) [ 4.322044] bnx2x 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 4.322051] bnx2x 0000:01:00.0: setting latency timer to 64 [ 4.322849] bnx2x 0000:01:00.0: part number 394D4342-31373735-30314130-473032 [ 4.323778] bnx2x 0000:01:00.0: irq 60 for MSI/MSI-X [ 4.323783] bnx2x 0000:01:00.0: irq 61 for MSI/MSI-X [ 4.323788] bnx2x 0000:01:00.0: irq 62 for MSI/MSI-X [ 4.323792] bnx2x 0000:01:00.0: irq 63 for MSI/MSI-X [ 4.323801] bnx2x 0000:01:00.0: irq 64 for MSI/MSI-X [ 4.323806] bnx2x 0000:01:00.0: irq 65 for MSI/MSI-X [ 4.323811] bnx2x 0000:01:00.0: irq 66 for MSI/MSI-X [ 4.323815] bnx2x 0000:01:00.0: irq 67 for MSI/MSI-X [ 4.323820] bnx2x 0000:01:00.0: irq 68 for MSI/MSI-X [ 4.323825] bnx2x 0000:01:00.0: irq 69 for MSI/MSI-X [ 4.332669] bnx2x 0000:01:00.0: eth2: Broadcom NetXtreme II BCM57710 10 Gigabit PCIe [Everest] (A1) PCI-E x8 2.5GHz found at mem f9000000, IRQ 16, node addr 00:10:18:46:ac:2c [ 4.332713] bnx2x 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 4.332721] bnx2x 0000:02:00.0: setting latency timer to 64 [ 4.333609] bnx2x 0000:02:00.0: part number 394D4342-31373735-30314130-473032 [ 4.334607] bnx2x 0000:02:00.0: irq 70 for MSI/MSI-X [ 4.334612] bnx2x 0000:02:00.0: irq 71 for MSI/MSI-X [ 4.334617] bnx2x 0000:02:00.0: irq 72 for MSI/MSI-X [ 4.334622] bnx2x 0000:02:00.0: irq 73 for MSI/MSI-X [ 4.334628] bnx2x 0000:02:00.0: irq 74 for MSI/MSI-X [ 4.334632] bnx2x 0000:02:00.0: irq 75 for MSI/MSI-X [ 4.334637] bnx2x 0000:02:00.0: irq 76 for MSI/MSI-X [ 4.334642] bnx2x 0000:02:00.0: irq 77 for MSI/MSI-X [ 4.334647] bnx2x 0000:02:00.0: irq 78 for MSI/MSI-X [ 4.334652] bnx2x 0000:02:00.0: irq 79 for MSI/MSI-X [ 4.343092] bnx2x 0000:02:00.0: eth3: Broadcom NetXtreme II BCM57710 10 Gigabit PCIe [Everest] (A1) PCI-E x8 2.5GHz found at mem fa000000, IRQ 16, node addr 00:10:18:46:ac:82 [ 4.352509] NET: Registered protocol family 10 7.142616] bnx2x: [bnx2x_init_firmware:10574(eth0)]Can't load firmware file bnx2x/bnx2x-e1-7.0.29.0.fw [ 17.142619] bnx2x: [bnx2x_func_hw_init:5382(eth0)]Error loading firmware [ 17.142625] bnx2x: [bnx2x_nic_load:1847(eth0)]HW init failed, aborting [ 17.179228] init: dhcp-client (eth0) pre-start process (14459) terminated with status 1 [ 17.206383] bnx2x: [bnx2x_init_firmware:10574(eth1)]Can't load firmware file bnx2x/bnx2x-e1-7.0.29.0.fw [ 17.206387] bnx2x: [bnx2x_func_hw_init:5382(eth1)]Error loading firmware [ 17.206393] bnx2x: [bnx2x_nic_load:1847(eth1)]HW init failed, aborting
it looks like syno sees it as bnx2x??
so I googled bnx2x-e1-7.0.29.0.fw
and I got a hit on
https://packages.debian.org/wheezy/all/firmware-bnx2x/download
I figured what the heck and tried dl it and extracted the fw bits
put bnx2x-e1-5.0.21.0.fw and bnx2x-e1h-5.0.21.0.fw into /usr/syno/hotplug/firmware and bnx2x-e1-7.0.29.0.fw, bnx2x-e1h-7.0.29.0.fw, and bnx2x-e2-7.0.29.0.fw into /usr/syno/hotplug/bnx2x
then rebooted
nuthing
so then I coped the three from bnx2x folder into the firmware folder, and rebooted
no change, still no nics in syno portal
from the dmesg I think I really only need bnx2x-e1-7.0.29.0.fw and I have that file (from debian package) in /usr/syno/hotplug/firmware/bnx2x folder
dmesg says this
[ 17.141861] bnx2x: [bnx2x_init_firmware:10574(eth0)]Can't load firmware file bnx2x/bnx2x-e1-7.0.29.0.fw
[ 17.141864] bnx2x: [bnx2x_func_hw_init:5382(eth0)]Error loading firmware
[ 17.141871] bnx2x: [bnx2x_nic_load:1847(eth0)]HW init failed, aborting
[ 17.178009] init: dhcp-client (eth0) pre-start process (14461) terminated with status 1
[ 17.205169] bnx2x: [bnx2x_init_firmware:10574(eth1)]Can't load firmware file bnx2x/bnx2x-e1-7.0.29.0.fw
[ 17.205174] bnx2x: [bnx2x_func_hw_init:5382(eth1)]Error loading firmware
[ 17.205180] bnx2x: [bnx2x_nic_load:1847(eth1)]HW init failed, aborting
might it be permissions? maybe debian version is no good? maybe need it somewhere else?
-
Thank you for the helpful response! Since the system board has two intel integrated gig NICS, It's no problem at all getting XPenology installed and running.
-
If I boot the system under ubuntu the 10 gig nix are listed as bnx2x
-
Does anyone have a copy of the file linked by Trantor?
I somehow missed this response and desperate to get mine working!
-
inexpensive switch is mikrotik
http://routerboard.com/CRS226-24G-2SplusIN
only big problem for me with this switch is it does NOT support LACP dynamic LAG
I have Broadcom 10Gig Cards, and dispite efforts from folks like sancome, they do NOT work in xpenology. I tried an older intel card and it worked fine (sorry but I didnt record the part number)
bonding in xpenology works, but by design is hardly helpful. VERY rarely do you see more that 1 GBE of traffic at a time. the requirements to acheive it are simply not easy to acheive , especially in the home.
10GiG E provides instant EASY to take advantage of benefits.
-
I would never suggest an upgrade without a complete backup, but mine proceeded without issue, all data and virtually all settings survived.
-
did you try an old tiny USB stick? I have seen some systems that won't boot on sticks larger than 1 GB, but boot fine from the older ones. Not sure what the minimum size is for xpenology, but 1GB should be more than enough.
-
I recently built an Xpenology system from an older Core 2 Quad 2.83Ghz system with 8GB RAM. When transcoding Audio and Video (confirmed) on my largest MKV (22GB) it was hitting 80-90% but working well. I would not bother with the atom, especially since with plex's shared nature, you may have to run 2 simultaneous transcodes.
Also TDP is maximum power to be dissipated, not the minimum nor typical consumed. Add in the chipset and HDD's, I don't think your real world power consumption will differ much.
-
just created a new Xpenology NAS from this latest boot image. structure is a bit different on the boot image, but easy enough to find / exit the serial number etc. installed 5028 directly then update 2.
-
Can you play those same files from a local HDD connected to those media players? What about to a PC across an Ethernet cable? If you can you can rule out your NAS and wired network performance. If you are accessing the media as files on a share, you should be fine on the NAS side, but if you are using something like plex to present the media, maybe it is doing server side transcoding and just running out of CPU on your NAS side?
-
Teaming is possible, but it does not help in the way people usually think it does. Once most understand what benefit it does offer, folks don't usually bother.
Teaming helps up-time (theoretically , a little bit maybe) If you were to lose a port on your NAS, or a port on your switch, or accidentally unplug the cable, you might not have any downtime.
Teaming helps performance when you have two or more simultaneous loads FROM DIFFERENT SYSTEMS performing sequential transfers AND you have the disks in place in your NAS to support that extra performance. For Example say you had a 4/5 volume on your NAS, and it was used to store many large files. If you wanted to do both a Copy to a Second NAS (say a backup) and a copy of a single large file to your desktop, you could exceed what a single GB ethernet link could have done. Hower all you need to do is add in some random disk activity, or some write activity, and 9/10 times your real world performance is not going to reach a single link any way.
if you are looking for more uptime you can create a redundant link in the network section. if you are looking for more performance, make sure you create one of the Dynamic LACP type. your switch will also have to support 802.3ad dynamic LACP bonded channel as well.
don't use quick connect, but external access can be done manually in synology, plus your router.
-
I believe It's a 36 disk build. the last 2 digits are the series, the year that it was released.
-
I have a 10g netextreme 11 57710 NIC I would love to be able to us, please keep us up to dae if you find a way!
-
bnx2x
I believe what you are asking for is all contained in the code section I have above.
It tries to load but complains and aborts! I really need to get this working as the performance with iSCSI on 10gig is looking really good!
[ 6.530140] bnx2x: [bnx2x_init_firmware:10574(eth2)]Can't load firmware file bnx2x/bnx2x-e1-7.0.29.0.fw
[ 6.530143] bnx2x: [bnx2x_func_hw_init:5382(eth2)]Error loading firmware
[ 6.530148] bnx2x: [bnx2x_nic_load:1841(eth2)]HW init failed, aborting
[ 6.579559] bnx2x: [bnx2x_init_firmware:10574(eth2)]Can't load firmware file bnx2x/bnx2x-e1-7.0.29.0.fw
[ 6.579562] bnx2x: [bnx2x_func_hw_init:5382(eth2)]Error loading firmware
[ 6.579566] bnx2x: [bnx2x_nic_load:1841(eth2)]HW init failed, aborting
Wrong CPU reported by DSM
in Archives
Posted
I don't actually own any WD green drives, so I don't have the first hand experience, but the information is all over the place on WD Green drives having problems in RAID unless you use the WD IDLE utility to adjust the TLER value to minimize hard parks. just search and I am sure you can find it , if not I would start an appropriately titled new post.