Jump to content
XPEnology Community

HP Microservers above 6.2


blue max

Recommended Posts

7 minutes ago, flyride said:

Nothing special.

 

Haswell or later processor is required in order to run DS918.  VM standard install, add 2nd SATA to connect vdisks or RDM devices, or alternatively passthrough a controller

 

On my test instance, I need DiskIdxMap=0C00 to hide the boot loader and get the SATA vdisks to show up in the right place.

 

Humm so i thinnk e can not run that.. i have the gen8 with the default cpu GT.. maybe i will upgrade but for the xen 1625 😕

Edited by codedmind
Link to comment
Share on other sites

@flyride I checked the ID of my Intel 1000 CT an it is on the List: 10D3. I used it today on my Intel Test System and it worked directly without any stupid errors. So there was an issue with the following combination: HP Microserver Gen10 (X3216), Loader 1.03b for DS3617xs an DSM 6.2.1 with or without the dedicated Intel NIC. Thanks to @bearcat i made one more try with Loader 1.03b for DS3615xs and tadaa: The HP Death Star is fully operational with DSM 6.2.1. I still have to migrate my existing data from 3617xs, but this should work.

 

To complete my list from here:  

 

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: Baremetal - HP Microserver Gen10

- Additional comments: Intel 1000 CT Desktop Adapter / Deactivated internal NIC's

 

Link to comment
Share on other sites

12 hours ago, blue max said:

Appreciate the answer Flyride. Can you point me to where I would find the info within Synology please? Or is it not when running baremetal?

 

 

You have to connect via putty to your nas (prior you have to activate ssh in "Terminal & SMNP"). When you are in terminal screen, after logon just enter "lspci" and a list of pci deviced is shown. Intel has the manufacutrer code 8086, so you can identify an Intel NIC. 

lspci.PNG

  • Thanks 1
Link to comment
Share on other sites

Interesting.  DS3617 has had historical problems on DSM 6.1.x (for example, ESXi and 6.1.7 don't work on DS3617 but fine on DS3615).

I've read that DS3617 support was not intended but the loader worked, so it was released as a combo.

 

I'll have to load up a test DS3617 install and see what driver version it has.

 

Link to comment
Share on other sites

1 minute ago, flyride said:

6.2.1 DS3615 (loader 1.03b) does not work with vmxnet3, only Intel e1000e virtual

6.2.1 DS918 (loader 1.04b) does work with vmxnet3, but you will need a Haswell+ processor

 

I realize it's a lot to keep track of, but the information is out there:

https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/

 

Thanks for your feedback!!!

 

Now i really understand. I have the 6.2.1 ds3615 right now.

 

I see i cannot use 1.04 because i iave g1060t. What cpu do you have in your microserver gen8?

 

Again thank you.

Link to comment
Share on other sites

I don't have a microserver, you may not be viewing signatures or you would see this:

 

VM: ESXi 6.5 Jun 1.02b DS3615xs / DSM 6.1.7-15284U3 / Supermicro X11SSH-F / E3-1230v6 / 64GB / Mellanox ConnectX-3 dual 10GbE passthrough

Intel P3500 NVMe RAID 1 (physical RDM) / WD Red RAID 10 (chipset SATA controller passthrough) / Samsung PM961 NVMe (ESXi datastore)

Baremetal: Jun 1.04b DS918/ DSM 6.2.1-23824U4 / ASRock J4105-ITX / 4GB

  • Thanks 1
Link to comment
Share on other sites

I had to use the command lspci -tv to see. I have a 105E, which is not on the list for the 918+, but I'm not using that.

This is an HP NC360T card.

 

I've had no luck installing DS3615XS. It shows as migrate, but gives a 169 IP address and won't have anything to do with it.

 

I've rather given up for now. Cost me at least a day's work too.

Link to comment
Share on other sites

8086.105E is the Intel PRO/1000 PT card, which is supported by the "e1000" driver set.  This is different than the "e1000e" which is the only one that appears to work on 1.03b/DS3615/6.2.1

 

EDIT: The above seems incorrect, and I can't replicate my research that led me to state the above.  8086.105E is supported on e1000e.  This doesn't explain why it isn't working for @bluemax.

 

I think the problem is that there are many posts to "buy [any] Intel NIC" not considering the above.

 

Acquire and use an e1000e card (i.e. 82574L-based card) and you should be good.  If you look at the Update Reporting threads you will see many have done this ahead of you.

Edited by flyride
Link to comment
Share on other sites

7 minutes ago, flyride said:

8086.105E is the Intel PRO/1000 PT card, which is supported by the "e1000" driver set.  This is different than the "e1000e" which is the only one that appears to work on 1.03b/DS3615/6.2.1

 

I think the problem is that there are many posts to "buy [any] Intel NIC" not considering the above.

 

Acquire and use an e1000e card (i.e. 82574L-based card) and you should be good.  If you look at the Update Reporting threads you will see many have done this ahead of you.

 

Thank you once again. I have only really been looking at the Microserver updates, but maybe I should broaden my reading to include any. Is there a resource that shows what cards are based on 82574L? 

Link to comment
Share on other sites

6 minutes ago, codedmind said:

@flyride, your baremetal machine... that board have some kind of future prof? Any recent model from synology is based in that cpu and network?

Thanks

 

I don't think anyone can guarantee future proof on any platform, except perhaps ESXi.  I'll respond to your hardware query on PM.

Link to comment
Share on other sites

On 1/10/2019 at 10:08 PM, flyride said:

8086.105E is the Intel PRO/1000 PT card, which is supported by the "e1000" driver set.  This is different than the "e1000e" which is the only one that appears to work on 1.03b/DS3615/6.2.1

 

I think the problem is that there are many posts to "buy [any] Intel NIC" not considering the above.

 

Acquire and use an e1000e card (i.e. 82574L-based card) and you should be good.  If you look at the Update Reporting threads you will see many have done this ahead of you.

 

I actually did buy the HP NC360T nic on the strength of this post...

 

(his signature shows...) Config 1 BAREMETAL: HP G7 N54L Amd Turion Néo II + 4 Go + 1x HD 1,8To (OS + packages) + 3x HD 2,7 To (DATA) + HP NC360T PCI Express Dual Port Gigabit Server Adapter - Internal NIC disabled - xpenology 1.03b DS 3615 XS DSM 6.2.1-23824 Update 4 - EATON USB 650 with server NUT on Raspberry 3 (stretch)

 

On 1/3/2019 at 4:28 PM, zoulou13 said:

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: DSM 6.2.1-23824 update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: BAREMETAL -  HP G7 N54L  

- Additional comments: restart + shutdown + WOL OK

 

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: DSM 6.2.1-23824 update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: VM -  ESXI 6.5 

- Additional comments: restart and shutdown don't work (same problem with DSM 6.2.1-23824 update 1 and update 2)

Edited by blue max
Link to comment
Share on other sites

I understand, our information is collected by the community and is not perfect.  Some of the collective information posted has errors but it cannot be easily corrected once posted. And nobody has all the possible hardware or time with which to test.

 

EDIT: I seem to be contributing to the imperfect knowledge, see update of previous post.

 

My own test VM on 1.03b running DS3615 6.2.1 consistently fails on e1000 emulation but not e1000e.  I did look through the same thread you cited to see if there were other patterns emerging but the majority of the successful reports are using e1000e cards. If you can confirm that certain e1000 cards are working, that will add to the community knowledge.

 

Hopefully we will have a extra.lzma solution again if/when Syno releases the 6.2.1 kernel source, and this discussion will be obsolete.

Edited by flyride
Link to comment
Share on other sites

Indeed. But it was a minimal investment and was worth the attempt. I am running the DS3617XS, so that might make a difference, but was unable to switch for some reason. Maybe I should have removed the card and activated the onboard nic, but it's all further work for little real gain.

 

I suppose the next big push with be for DSM 7, so will be resigned to sticking to 6.2. If it goes beyond, it will be a bonus anyway.

Link to comment
Share on other sites

On 1/10/2019 at 11:08 PM, flyride said:

8086.105E is the Intel PRO/1000 PT card

 

I'm having a; 8086:105e (rev 06) that is branded HP NC360T, based on the 82571GBusing the e1000e driver. (notice the revision level)

Currently this N54L is running as DS3615xs, with DSM 6.2-23739 Update 2, but I have tested the same card with 6.2.1, and it was all good.

Unfortunately, I did not check the driver it used in 6.2.1, might do that if/when I have the time.

 

@hoidoi was having a problem getting a  Intel 1000 CT, id: 10D3 working with 6.2.1, until he tested it with the DS3615xs so it seems to be a "safer" base than the 3617

Link to comment
Share on other sites

 

15 minutes ago, bearcat said:

 

I'm having a; 8086:105e (rev 06) that is branded HP NC360T, based on the 82571GBusing the e1000e driver. (notice the revision level)

 

@Bearcat you are correct and e1000e is the driver for 8086:105E for all the drivers I have records for.  Not sure why I came to that answer but I apologize for the inaccuracy.  The other comments about e1000 card lack of function  on DS3615 6.2.1 remain accurate.

 

33 minutes ago, blue max said:

I am running the DS3617XS

I suppose the next big push with be for DSM 7

 

@bluemax, I do suggest you try DS3615 instead of DS3617.

Link to comment
Share on other sites

17 minutes ago, cpuks said:

Ok as a summary - buying HP NC360T for my gen8 should work properly on 1.03b + 6.2u2 and should allow me to upgrade to 6.2.1?

Wysłane z mojego ONEPLUS A6003 przy użyciu Tapatalka
 

 

Well, that was on a gen7, but I can't see why it wouldn't work on a gen8. I can only say it worked on mine. I was able to update to the latest DSM. 

I'd suggest making another usb stick and removing your hard drives (and marking to keep the order). Then add a spare one and test the hardware first. 

Edited by blue max
  • Like 1
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...