Jump to content
XPEnology Community

Can I use a Dell R710 PowerEdge server to run XPEnology?


jgaltone

Recommended Posts

13 hours ago, jgaltone said:

Ugh...Jun's thread regarding his loader for DSM v6.x is up to 3,696 replies.

 

I am about to try and get DSM v6.x to work on one of our Dell R710's as a virtual machine running in ESXi. Can someone that has done this successfully (please provide links) to the exact installer or disk image you installed? If you used one of Jun's disk images can you please be very specific as to which one.

 

Can you also please share what updates you have been able to install after you got the initial installation up and running?

 

I see that the latest version of ESXi is no longer compatible with the Dell R710. It would also be great if you could tell us what version of firmware you are running on your R710 an which version of ESXi you have installed.

 

Thanks.

I'm running ESXI 6.5 on my R710 with no issues, the only warning I get is that this CPU might not get support for the next versions. I'm using loader Jun's 1.02b on DS3617, if you want to learn how to do it,  do some reading, search bar is very helpful...

Keep us updated... 

Link to comment
Share on other sites

On 8/30/2017 at 0:12 AM, painkiller895 said:

I'm running ESXI 6.5 on my R710 with no issues, the only warning I get is that this CPU might not get support for the next versions. I'm using loader Jun's 1.02b on DS3617, if you want to learn how to do it,  do some reading, search bar is very helpful...

Keep us updated... 

I am sorry if I overreacted to your comment. I was having a bad day and I took your comment about using the search bar as the the equivalent of telling me to got RTM when perhaps that wasn't your intention. Before asking my questions in this thread I had spent several hours reading through hundreds of posts in Jun's seemingly never ending thread.

 

I thought that it would serve the community better if the information specific to using Xpenology on the Dell R710 was consolidated into a single place that users could come to so they don't have to spend hours trying to pull the information from literally hundreds of comments that are not specifically relevant to them.  

Link to comment
Share on other sites

  • 2 weeks later...

It is just my own point of view. But unless you are a business there is no point to do a BARE METAL from Xpenology with a R710. BUT even if you are a business... you should stay away from Xpenology (and especially from Alpha & Beta test stuff). For business: Is it legal? Call in first Synology and ask their support for help on Xpenology. If they give you a award and say Yes then go head. And call me to get the award!! UNLESS it is a small config R710 like 1 Xeon and 16Gb or max 32Gb?

 

-Meaning is like using a BIG tractor (Power) to do your backyard where you will have a 12zn of flowers and plants.

-If you have Terabyte and Terabyte of data then you need more Hard Drive (Storage) than power.

-If you are transferring a lot of data between your computers and especially BIG FILES and it is slow then best to upgrade your network side or NIC card.

-If you are doing plex or Emby... transcoding then even in bare metal X penology will not be able to use 100% of your R710 dual Xeon totaling 8 cores (16 threads) or 12 cores (24 threads) with 8Gb, 16GbB, 32Gb, 64Gb maybe 128GB, 192Gb?. Synology DS3615xs is designed for Intel i3 2 cores with max 32Gb Ram (but come with 4Gb only). So your Xpenology DS3615xs can maybe see 4 cores and over 32Gb Ram... But for home or personal use, in that last case you will pay more the electricity bill than it is really useful.

 

Ok I believe most of you understand it. And less we talk about it better it is.

BUT I am more looking at experience and experimentation with R710 so go head more there is people doing different thing and more info we will have. If they are willing to post here for R710.

 

I have 2 Xpenology - DS3615 DSM 6.1.x & DS3617 DSM 6.1.x both with Jun 1.02b - running on my R710 under Esxi 6.0

- I have no issue with DS3615 even doing exotic upgrade from DSM 5.2 to DSM 6.1.X with keeping all setting and data and fixing/update package only got a stable DS3615 with Jun 1.02b.

- Is it just me or I have seen DS3617 got Frozen or need to be rebooted?? not stable. Or is it one of my package that make the system get cold?

The DS3617xs: I am using it especially for Emby and when it work... Work great!! For my use Emby is better. So if Emby is culprit and you have no such issues with Plex I might get a try?

 

thank for sharing your experience with DS3617xs with R710.

Link to comment
Share on other sites

On 3/22/2017 at 4:39 AM, fb_luc said:

 

I use Jun's Loader 1.01 (DSM 6.0.2)

 

You have to create an RAID volume at the (Hardware) RAID controller. (e.g. RAID 5)

 

Then the disk(s - all RAID disks you created in Hardware RAID config) will be detected from DSM and you can run the installation. In the DSM disk manager i choose not an RAID (because only one big disk will be shown). Use "basic" instead. The "failure security" will be handled from your Hardware RAID controller.

 

There you go.

 

 

It works! Very nice :smile:

 

Thank you very much @Salah @Polanskiman

I did this and got it working with that Loader 1.01 now can Loader 1.02b please be updated with the same drivers so we can update our DSM to the latest please....Also I would like to migrate from ds3615 to ds3617 with a new fresh updated loader. Hope I'm not asking for too much.  As always thank you very much for the hard work you guys have done!  

Edited by painkiller895
Link to comment
Share on other sites

On 8/30/2017 at 5:40 PM, jgaltone said:

I am sorry if I overreacted to your comment. I was having a bad day and I took your comment about using the search bar as the the equivalent of telling me to got RTM when perhaps that wasn't your intention. Before asking my questions in this thread I had spent several hours reading through hundreds of posts in Jun's seemingly never ending thread.

 

I thought that it would serve the community better if the information specific to using Xpenology on the Dell R710 was consolidated into a single place that users could come to so they don't have to spend hours trying to pull the information from literally hundreds of comments that are not specifically relevant to them.  

No problem, Did you get it working ???

 

Link to comment
Share on other sites

10 hours ago, painkiller895 said:

I did this and got it working with that Loader 1.01 now can Loader 1.02b please be updated with the same drivers so we can update our DSM to the latest please....Also I would like to migrate from ds3615 to ds3617 with a new fresh updated loader. Hope I'm not asking for too much.  As always thank you very much for the hard work you guys have done!  

 

Jun's loader v1.02b already contains the qlcnic.ko and megaraid_sas.ko modules which are the modules for the NetXtreme II 5709c Gigabit Ethernet NIC and Perc 6i Raid Controller respectively.

 

What is the problem?

Link to comment
Share on other sites

5 hours ago, Polanskiman said:

 

Jun's loader v1.02b already contains the qlcnic.ko and megaraid_sas.ko modules which are the modules for the NetXtreme II 5709c Gigabit Ethernet NIC and Perc 6i Raid Controller respectively.

 

What is the problem?

Thanks for the response,

The problem is I want to update the system.  I make the usb stick with bootloader 1.02b I boot it and I get the boot loader screen it loads up and I have no network connection and the hard drive lights all go off and never come back on.  So I guess the controller is not being detected also.  I using the same serial and mac number on both loaders and the same usb stick also.  That's the problem I have having...

BTW:  I'm using Loader Jun's-1.0.1     6.0.2.1-8451

 

Edited by painkiller895
to add
Link to comment
Share on other sites

11 hours ago, painkiller895 said:

Thanks for the response,

The problem is I want to update the system.  I make the usb stick with bootloader 1.02b I boot it and I get the boot loader screen it loads up and I have no network connection and the hard drive lights all go off and never come back on.  So I guess the controller is not being detected also.  I using the same serial and mac number on both loaders and the same usb stick also.  That's the problem I have having...

BTW:  I'm using Loader Jun's-1.0.1     6.0.2.1-8451

 

 

I'm using DS3615xs DSM 6.0.2-8451 Loader Jun's 1.0.1 This is working, Loader 1.0.2b is not....

root@Test220:~# dmesg | grep "eth"
[    2.905525] usbcore: registered new interface driver ethub
[   18.591159] jme: JMicron JMC2XX ethernet driver version 1.0.8
[   18.643805] bnx2 0000:01:00.0 eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem d6000000, IRQ 36, node addr 78:2b:cb:44:f6:cd
[   18.644462] bnx2 0000:01:00.1 eth1: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem d8000000, IRQ 48, node addr 78:2b:cb:44:f6:cf
[   18.645138] bnx2 0000:02:00.0 eth2: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem da000000, IRQ 32, node addr 78:2b:cb:44:f6:d1
[   18.645832] bnx2 0000:02:00.1 eth3: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem dc000000, IRQ 42, node addr 78:2b:cb:44:f6:d3
[   20.000263] bnx2 0000:01:00.0 eth0: using MSIX
[   20.000469] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   20.065864] bnx2 0000:01:00.1 eth1: using MSIX
[   20.065931] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   20.207771] bnx2 0000:02:00.0 eth2: using MSIX
[   20.207806] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[   20.760031] bnx2 0000:02:00.1 eth3: using MSIX
[   20.760070] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
[   22.769387] bnx2 0000:01:00.0 eth0: NIC Copper Link is Up, 1000 Mbps full duplex
[   22.769478] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
root@Test220:~# ^C
root@Test220:~#

 

Link to comment
Share on other sites

10 hours ago, painkiller895 said:

 

I'm using DS3615xs DSM 6.0.2-8451 Loader Jun's 1.0.1 This is working, Loader 1.0.2b is not....


root@Test220:~# dmesg | grep "eth"
[    2.905525] usbcore: registered new interface driver ethub
[   18.591159] jme: JMicron JMC2XX ethernet driver version 1.0.8
[   18.643805] bnx2 0000:01:00.0 eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem d6000000, IRQ 36, node addr 78:2b:cb:44:f6:cd
[   18.644462] bnx2 0000:01:00.1 eth1: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem d8000000, IRQ 48, node addr 78:2b:cb:44:f6:cf
[   18.645138] bnx2 0000:02:00.0 eth2: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem da000000, IRQ 32, node addr 78:2b:cb:44:f6:d1
[   18.645832] bnx2 0000:02:00.1 eth3: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem dc000000, IRQ 42, node addr 78:2b:cb:44:f6:d3
[   20.000263] bnx2 0000:01:00.0 eth0: using MSIX
[   20.000469] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   20.065864] bnx2 0000:01:00.1 eth1: using MSIX
[   20.065931] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   20.207771] bnx2 0000:02:00.0 eth2: using MSIX
[   20.207806] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[   20.760031] bnx2 0000:02:00.1 eth3: using MSIX
[   20.760070] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
[   22.769387] bnx2 0000:01:00.0 eth0: NIC Copper Link is Up, 1000 Mbps full duplex
[   22.769478] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
root@Test220:~# ^C
root@Test220:~#

 

 

You might boot with your 1.01 installation and check what modules are actually used/loaded for your hardware and then check if the modules are present in the extra.lzma you use for 1.02

 

in the case of nic its bnx2, i'n not shure but afair there where firmware files missing in jun's 1.02/a

not sure if its still the case with 1.02b, afair I added some in my extra.lzma (driver extension for 1.02)

 

edit: just checked i added bnx2-mips-09-6.2.1a.fw and bnx2-mips-06-6.2.1.fw and 1.02b does not have this files, the bnx2 seems to come with two different hardware versions and will need two kinds of firmware dedending on the chip/core on the nic?

if you use a serial cable to read the log of the 1.02 booting you might see more clearly what happens

Link to comment
Share on other sites

10 hours ago, IG-88 said:

 

You might boot with your 1.01 installation and check what modules are actually used/loaded for your hardware and then check if the modules are present in the extra.lzma you use for 1.02

 

in the case of nic its bnx2, i'n not shure but afair there where firmware files missing in jun's 1.02/a

not sure if its still the case with 1.02b, afair I added some in my extra.lzma (driver extension for 1.02)

 

edit: just checked i added bnx2-mips-09-6.2.1a.fw and bnx2-mips-06-6.2.1.fw and 1.02b does not have this files, the bnx2 seems to come with two different hardware versions and will need two kinds of firmware dedending on the chip/core on the nic?

if you use a serial cable to read the log of the 1.02 booting you might see more clearly what happens

 

Sorry but I don't have access to that at the moment...

Link to comment
Share on other sites

9 hours ago, IG-88 said:

i can try this extra.lzma for 1.02, the nic might work with this as it contains the two firmware files (but without log its just guessing and trying)

 

Where can i download this loader ?  Thanks for the help.

 

Edit: got it, going to try the 1.0.2a keep you updated ....

 

 

Edited by painkiller895
Link to comment
Share on other sites

17 hours ago, Polanskiman said:

 

Jun's loader v1.02b already contains the qlcnic.ko and megaraid_sas.ko modules which are the modules for the NetXtreme II 5709c Gigabit Ethernet NIC and Perc 6i Raid Controller respectively.

 

What is the problem?

10 hours ago, IG-88 said:

 

You might boot with your 1.01 installation and check what modules are actually used/loaded for your hardware and then check if the modules are present in the extra.lzma you use for 1.02

 

in the case of nic its bnx2, i'n not shure but afair there where firmware files missing in jun's 1.02/a

not sure if its still the case with 1.02b, afair I added some in my extra.lzma (driver extension for 1.02)

 

edit: just checked i added bnx2-mips-09-6.2.1a.fw and bnx2-mips-06-6.2.1.fw and 1.02b does not have this files, the bnx2 seems to come with two different hardware versions and will need two kinds of firmware dedending on the chip/core on the nic?

if you use a serial cable to read the log of the 1.02 booting you might see more clearly what happens

 

My bad. It's not the qlcnic.ko I mentioned but the bnx2.ko module. Sorry for the mislead. I recall some had a similar issue ion the past with the same NIC. Read here: https://xpenology.com/forum/topic/6253-dsm-6xx-loader/?do=findComment&comment=68044 and subsequent exchange between Salah and me.

 

In principale these are the following firmwares that should be present in the default loader:

 

bnx2-rv2p-09ax-6.0.17.fw

bnx2-rv2p-09-6.0.17.fw

bnx2-mips-09-6.2.1a.fw

bnx2-rv2p-06-6.0.15.fw

bnx2-mips-06-6.2.1.fw

 

But there seems to be several missing:

 

bnx2-mips-06-6.2.1.fw

bnx2-mips-09-6.2.1a.fw

bnx2-mips-09-6.2.1b.fw - This one being the one used by that NIC if I'm not mistaken.

 

@IG-88 I see you added the two first ones in your extra.lzma ramdisk namely 'bnx2-mips-06-6.2.1.fw' and 'bnx2-mips-09-6.2.1a.fw' but they are dated from 2013. Did you compile those firmwares yourself? In any case 'bnx2-mips-09-6.2.1b.fw' would also need to be added for that NIC to work in my opinion but I might be wrong.

Link to comment
Share on other sites

On 9/11/2017 at 9:35 AM, Polanskiman said:

@IG-88 I see you added the two first ones in your extra.lzma ramdisk namely 'bnx2-mips-06-6.2.1.fw' and 'bnx2-mips-09-6.2.1a.fw' but they are dated from 2013. Did you compile those firmwares yourself? In any case 'bnx2-mips-09-6.2.1b.fw' would also need to be added for that NIC to work in my opinion but I might be wrong.

the files are the ones that come with the kernel sources, jun only took the rv2p files for his package, there are only those 2 mips files with the kernel but i found bnx2 firmware deb packages containig more firmware files, i will put the "b" file within my next extra.lzma that will be out in a few hours

 

the best way is to look in the source what *.fw files are mentioned, i did it for bnx2 and it looks like this

#define FW_MIPS_FILE_06         "bnx2/bnx2-mips-06-6.2.3.fw"
#define FW_RV2P_FILE_06         "bnx2/bnx2-rv2p-06-6.0.15.fw"
#define FW_MIPS_FILE_09         "bnx2/bnx2-mips-09-6.2.1b.fw"
#define FW_RV2P_FILE_09_Ax      "bnx2/bnx2-rv2p-09ax-6.0.17.fw"
#define FW_RV2P_FILE_09         "bnx2/bnx2-rv2p-09-6.0.17.fw"

 

no mention of the "a" file, the "a" seems to be wrong with the 3.10.xxx kernel, a mistake from someone who placed the firmware files in the kernel, so i will delte the "a" file from the next extra.lzma

 

  • Like 1
Link to comment
Share on other sites

On 9/12/2017 at 0:25 AM, IG-88 said:

the files are the ones that come with the kernel sources, jun only took the rv2p files for his package, there are only those 2 mips files with the kernel but i found bnx2 firmware deb packages containig more firmware files, i will put the "b" file within my next extra.lzma that will be out in a few hours

 

the best way is to look in the source what *.fw files are mentioned, i did it for bnx2 and it looks like this


#define FW_MIPS_FILE_06         "bnx2/bnx2-mips-06-6.2.3.fw"
#define FW_RV2P_FILE_06         "bnx2/bnx2-rv2p-06-6.0.15.fw"
#define FW_MIPS_FILE_09         "bnx2/bnx2-mips-09-6.2.1b.fw"
#define FW_RV2P_FILE_09_Ax      "bnx2/bnx2-rv2p-09ax-6.0.17.fw"
#define FW_RV2P_FILE_09         "bnx2/bnx2-rv2p-09-6.0.17.fw"

 

no mention of the "a" file, the "a" seems to be wrong with the 3.10.xxx kernel, a mistake from someone who placed the firmware files in the kernel, so i will delte the "a" file from the next extra.lzma

 

ok let me know when it's done so I can try the Loader I'm not able to compile it myself.  I'll test what ever you can do and give you the results...

thanks again.  BTW I also tried it on a Dell 2950 with the same results...

root@192.168.1.20's password:
root@test2970-20:~# dmesg | grep "eth"
[    0.295201] ACPI Error: Method parse/execution failed [\_SB_._OSC] (Node ffff88043d863b50), AE_NOT_FOUND (20130328/psparse-537)
[    2.721664] usbcore: registered new interface driver ethub
[   15.431529] jme: JMicron JMC2XX ethernet driver version 1.0.8
[   15.495427] bnx2 0000:03:00.0 eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem f8000000, IRQ 16, node addr 00:1e:c9:53:1d:5b
[   15.498871] bnx2 0000:07:00.0 eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem f4000000, IRQ 16, node addr 00:1e:c9:53:1d:5d
[   17.017015] bnx2 0000:03:00.0 eth0: using MSI
[   17.017112] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   17.259014] bnx2 0000:07:00.0 eth1: using MSI
[   17.259060] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   20.245114] bnx2 0000:03:00.0 eth0: NIC Copper Link is Up, 1000 Mbps full duplex
[   20.245202] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
root@test2970-20:~#


This is on the Dell 2950

 

Link to comment
Share on other sites

On 9/12/2017 at 2:06 AM, painkiller895 said:

ok let me know when it's done so I can try the Loader I'm not able to compile it myself.  I'll test what ever you can do and give you the results...

thanks again.  BTW I also tried it on a Dell 2950 with the same results...


root@192.168.1.20's password:
root@test2970-20:~# dmesg | grep "eth"
[    0.295201] ACPI Error: Method parse/execution failed [\_SB_._OSC] (Node ffff88043d863b50), AE_NOT_FOUND (20130328/psparse-537)
[    2.721664] usbcore: registered new interface driver ethub
[   15.431529] jme: JMicron JMC2XX ethernet driver version 1.0.8
[   15.495427] bnx2 0000:03:00.0 eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem f8000000, IRQ 16, node addr 00:1e:c9:53:1d:5b
[   15.498871] bnx2 0000:07:00.0 eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem f4000000, IRQ 16, node addr 00:1e:c9:53:1d:5d
[   17.017015] bnx2 0000:03:00.0 eth0: using MSI
[   17.017112] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   17.259014] bnx2 0000:07:00.0 eth1: using MSI
[   17.259060] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   20.245114] bnx2 0000:03:00.0 eth0: NIC Copper Link is Up, 1000 Mbps full duplex
[   20.245202] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
root@test2970-20:~#


This is on the Dell 2950

 

 

Wow 5000 + views here impressive: Just an update guys with the new extra.lzma v3 I was able to update both machines to the latest 1.02b loader. Great work ! Thanks a million. Will keep you update if anything develops...

Thanks again...

Link to comment
Share on other sites

3 hours ago, painkiller895 said:

Oh BTW ramdisk for 3617 possible ?

 

possible, but not in the next x days, its kind of more importent to bring up more drivers for 3615 (the "unknown symbol syno_libata_index_get" thing is realy anoying)

from my point of view the 3617 does not offer much more then the 3615 (only more then 8 cores possible? maybe some processort features that you will not recoginse in real life situations?)

 

5 hours ago, painkiller895 said:

I was able to update both machines to the latest 1.02b loader

 

good to know i naild it this time (after checking the source what firmware is needed for bnx2 it should have)

maybe jun will put the 2 missing files (bnx2-mips-06-6.2.3.fw, bnx2-mips-09-6.2.1b.fw) into his next version and the case is permanently closed

Edited by IG-88
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...