[Einbindung extra Treiber Pack]

Ich beantworte meine Frage mal selber

ich habe den Stick mit dem Bootloader in meinen Windows Rechner gesteckt, dort die extra.lzma gesichert und die neue drauf geschoben - erkennung der netzwerkkarte hat wunderbar funktionier

[Einbindung extra Treiber Pack]

Moin,

wo finde ich denn "die Anleitung" :)?

 

Ich habe aktuell DS3617xs mit 6.2.2 laufen - auch ich würde gerne die onboard NIC zum arbeiten bewegen.

Folgendes zip habei ch heruntergeladen: extra3617_v0.5_test (ist doch aktuell - oder?)

 

wo müsste ich nun die extra.lzma einbinden?

[Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+]

4 hours ago, Polanskiman said:

1.03b was already there  😉

 

I still have to rub my sleepy eyes ^^ - where can I find the download link?

[DSM 6.2 Loader]

6 minutes ago, flyride said:

The only way you will be able to run 6.2.1 then will be to run DS918 and compiled drivers to support your cards (which may not exist at this point).

 

What's wrong with the security fixes in 6.1.7 U3?

Because, as I wrote above, I am on version 6.2 (23739).

[DSM 6.2 Loader]

4 minutes ago, flyride said:

 

DS918 probably will not properly support your add-in cards.

 

You should also be able to use 1.03b and DS3615xs

You must also use the Intel NIC for it to boot.  But ask yourself why you want to upgrade, and if you still must, test compatibility thoroughly before you commit your data.

 

Unfortunately my motherboard has only one Realtek network card, which doesn't work anymore since the upgrade from 6.1 to 6.2 - but for me it's not a pain, because I use the 10Gbit network card anyway.

 

I want to update because I am afraid that my NAS can be attacked from the outside by the open security holes in 6.2.
And I just don't like completely encrypted data or the like

[DSM 6.2 Loader]

30 minutes ago, Olegin said:

Better safe than sorry. If you did not add any drives in extra.lzma by yourself or not use modified by IG-88 1.04 will work.

mmmh,

i think i'll disconnect the HDD for my updated installation, and reinstall it with the Loader 1.04 - then i'll check with a dummy HDD if everything works - if so, i'll try to downgrade from 3617xs to 918+ somehow

[DSM 6.2 Loader]

23 minutes ago, Olegin said:

Ups... stop!

It seems that this hw will not work on 1.04.

 

  List of bild in drivers on 1.04 (Hide contents)

alx.ko
atl1.ko
atl1c.ko
atl1e.ko
ax88179_178a.ko
bnx2.ko
BusLogic.ko
button.ko
cnic.ko
e1000.ko
ixgbe.ko
jme.ko
libphy.ko
mdio.ko
megaraid.ko
megaraid_mbox.ko
megaraid_mm.ko
megaraid_sas.ko
mii.ko
mptbase.ko
mptctl.ko
mptsas.ko
mptscsih.ko
mptspi.ko
netxen_nic.ko
ohci-hcd.ko
pcnet32.ko
qla3xxx.ko
qlcnic.ko
qlge.ko
r8168.ko
r8169.ko
scsi_transport_spi.ko
sfc.ko
skge.ko
sky2.ko

tg3.ko
uio.ko
usbnet.ko
vmw_pvscsi.ko
vmxnet3.ko

 

 

Dude, you're about to mess with my head.

 

So the LSI controller is currently working.
And the Mellanxo NIC is in Synology's supported hardware list.

Currently I'm running Loader 1.03 and DSM 6.2.

 

But it is possible that the hardware would not work anymore?

 

edit...

Wait a minute ..

in your list ist megaraid - and "Megaraid" in a productname for the LSI raidcontroller

[DSM 6.2 Loader]

3 hours ago, Olegin said:

Yes.

 

All right - is there a guide that you can recommend that I use for the change?

[DSM 6.2 Loader]

51 minutes ago, Olegin said:

On 1.04 you must install 918 DSM only! Read this.

So I have to change from 3617xs to 918+ to upgrade to version 6.2.1?

[DSM 6.2 Loader]

6 hours ago, chipped said:

 

If you have 4th Gen CPU or newer then you can upgrade using 1.04 loader.

 

The loader is customised to set 16 drives visible on the system on every boot. So it’s all good if you have up to 16 drives. 

 

See compatible hardware here

 

 

Good morning,
thank you for your answer.

 

So I installed a 3617xs.
There is no 1.04 loader for that - or do I see it wrong?

I have a Skylake CPU (5th generation?)

A LSI RAID controller in IT mode.
and a Mellanox Connect-X 3 10Gbit NIC.

I only use the onboard SATA controller for the SSD cache.

I use 8 HDDs, 2 SSD as cache and one SSD as system drive - no virtualization.

[DSM 6.2 Loader]

Hello, what are the DS3617 users doing about updates?

Should we wait for a new loader until we can update to 6.2.1?

6.2 has very serious security flaws that have led me to deny my NAS access to the Internet.

[DSM 6.2 Loader]

Hello,
for over a year I have been using a baremetal installation with the bootloader of DS3617xs.

Currently I'm using version 1.03b which runs DSM 6.2 - 23739.

 

I was already on version 6.2.1, but after a few days my RAID controller (LSI-9211i [IT Mode - P20 Firmware]) was not recognized anymore.
(Thread to it:

 

Now I am afraid that if I update to the latest version again, my RAID controller will not be recognized anymore.

Synology has released two updates in the past few days that plug serious security holes - I wouldn't want to do without them 😕

 

What are the upgrade options?

If the question has already been answered, I apologize

[RAID controller is no longer found]

No, I haven't tried that so far because the controller worked - is there any guid on how to do that?

[Driver extension jun 1.03a2/DSM6.2.x for DS918+]

On 10/1/2018 at 11:35 PM, IG-88 said:

doing any additional or replacement driver would be pointless as with 6.2.1 only the original synology drivers work, that the reason why the realtek did not work, thats a additonal driver from juns loader

to have a look about the disks you might check /var/log/dmesg, you should see the mpt2sas recognizing the card and after that there should be something about the connected disk

 

 

I opened an extra thread because of my problem.

[RAID controller is no longer found]

Hi,
I have a problem with a RAID controller, which is not recognized anymore since 25.9.2018.

The Raid Controller is a DELL PERC H310, which I reflashed to a LSI-9211i in IT mode. The firmware is the latest with P20.

On that day I noticed that all hard disks connected to the controller were no longer recognized by DSM.
My first conclusion was that the RAID controller was defective - so I ordered a new one and flashed it over as well. To my great astonishment I noticed that this controller didn't show any hard disks either.

So I started Ubuntu 18.04 from a USB stick and here all hard disks were recognized by both the old and the new RAID controller without any problems.

On 11.9.2018 I upgraded from DSM 6.1.x to 6.2.1 (jun 1.03 3617), where everything worked fine. After that, Synology didn't release any updates, so I didn't do any more updates after that.

It should be noted that when I turn on the computer, all hard disks perform the self check, but when loading DSM there is no further check, which would have to be done if the driver was loaded.

When booting from Ubuntu, the second check is performed.

 

I am at the end with my Latin - In the appendix I uploaded a dmesg, and here I don't find any entries concerning the RAID controller.

 

I hope someone can join me in searching for clues 😕

 

Thanks

dmesg

[Driver extension jun 1.03a2/DSM6.2.x for DS918+]

Thanks for the answer.
I used your packages at 6.1.x and upgraded directly to 6.2.1 in early September.
Except for the Realtek network card, everything, obvious, worked flawlessly.

 

On Tuesday, the volume became unavailable to me.
Not a single one of the eight hard drives was displayed.
Since no hard disk was started either, and the longer shutdown did not help, I thought the RAID controller was defective.

 

I ordered the same one again and flashed the firmware - meanwhile also the IT mode.

 

But in DSM no drive is shown.
lspci shows me the vid and pid of the RAID controller, but my knowledge is too superficial for me to continue debugging.

 

As I said, both controllers display all hard disks under Ubuntu without any problems.

 

I'll do an extra thread on it tomorrow ...

[Driver extension jun 1.03a2/DSM6.2.x for DS918+]

Is it possible to compile this package for 3817 as well?

Or can I include them directly?

 

I have an LSI 9211-8i (IR) which is not recognized from one day to the next.
With Ubuntu all hard disks are recognized perfectly.

Even a replacement controller recognizes all hard disks under Ubuntu but not under DSM 😕

[Port Mapping nach Wechsel ESXi -> Bare Metal]

Hallo,

ich werde keinen neuen Thread aufmachen.

Mein Problem konnte ich lösen - vielleicht kannst du damit auch deines Lösen.

 

Ich habe durch googlen eine asiatische Seite gefunden - http://zective.com/code/xpenology/

Welche du, wenn du sie z.b. in Chrome öffnest, automatisch übersetzten lassen kannst.

 

Dort trägst du die Standardwerte der synoconf.cfg ein:

usb 300000

esata ff000

internal fff

 

und bestätigst mit dem unten liegenden button.

Du erhälst eine Übersicht der configuration, durch einfaches anklicken der Checkboxen kannst du nun einzelne Ports USB, eSATA oder intern SATA zuweisen. 

Diese werte überträgst du dann in die synoconf.cfg und in die synoinfo ... neustarten und mit etwas daumendrücken hat alles geklappt

[Port Mapping nach Wechsel ESXi -> Bare Metal]

Ich stehe vor einem sehr ähnlichen Problem.

Und frage mal, ob ich mich an diesen Thread hier anghängen darf  ?

 

Ich habe einen DELL PERC i310 (LSI 8 Kanal) und 6 interne SATA Ports.

Angeschlossen, sind drei SSDs (eine 64GB auf der das OS läuft und zwei fürs Caching) die HDDs sollen komplett vom LSI Controller angesteuert werden. Jedoch werden die letzten zwei HDDs als eSATA angezeigt.

Durch google bin ich darauf gestoßen, dass es sich nicht um einen Fehler im Controller oder Treiber handelt, sondern nur um eine Konfiguration.

 

Das ändern/ausprobieren in etc und etc.default hat mich jedoch dazu gebracht, dass das System garnicht mehr gebootet werden kann :/

 

Es hat sich mir also noch nicht erschlossen, WIE ich auf eine korrekte konfig komme (esata habe ich nicht)

 

Danke