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


Recommended Posts

Thanks for the quick answer.

 

I have downloaded this http://www.filedropper.com/extra3617v0112test driver extension. The DSM version on the VM is: 6.2.3-25426 Update 2. I have only replaced the extra.lzma file in my bootloader image.

 

But my NIC is in the thread what you linked, so i think it will work. (I cant test it right now, i get the new ethernet card tomorrow.)

Link to post
Share on other sites
26 minutes ago, havast said:

But my NIC is in the thread what you linked, so i think it will work. (I cant test it right now, i get the new ethernet card tomorrow.)

you don't need a driver pack, the broadcom and vmware vmxnet3 drivers are in the original package of the loader from jun

just add a vmxnet3 nic to your vm and try it, thats the "normal" way of doing it, using vt-d to have pcie nic handled by the vm is unusual, that might be used for storage controllers when you want dsm to have complete access to the disks to have smarts and temp readings (to give the same experience as on a baremetal system)

you loose a lot of comfort and options when ignoring vmware base functionality and handling network on virtual switches with high speeds is just one

Link to post
Share on other sites

First, thank you VERY much for your reply, this thread, the many other threads you maintain, and of course for your contributions in general!

 

On 10/27/2020 at 5:46 PM, IG-88 said:

i only remember one or two comments about the filedropper links and when i checked the link worked

 

In a previous post, I counted up at least 5 which I linked to.  There may have been others.  If it seemed I was implying there were 10s or 100s, I do apologize. 

 

it wasn't very difficult to miss at least 5 users over the span of about 2 months in this thread requesting a re-upload. If I were not one of those users I probably would not have noticed, either.

 

It was a small number, but it was a frustrated few at least.

 

On 10/27/2020 at 5:46 PM, IG-88 said:

anyway one of the problems was to find a new free file hoster where i dont have to register, where files stay up long enough and where you preferably not get scammed to much, i found this pretty frustrating, you get zillions of candidates but you need to invest some time on each only to find out they do not really provide the service i'm looking for - i will try the hosters you used next (i have 6 now, will hopefully enough - and tinyupload.com is back online and it seems they still have the old files)

 

If nothing less, I am very glad to have contributed to your list of viable free file hosting!

 

While it's probably a bit premature for this, you can look into something like  z_o_o_m to make the process easier:

 

http://z-o-o-m.eu/

 

On 10/27/2020 at 5:46 PM, IG-88 said:

i don't mind if you start a new thread to mirror files as long as its clear what version number it is and what they are for (dsm type and version)

now that i have a few hoster a can add a mirror or two

 

I am sending you a PM on this part of your reply.

 

On 10/27/2020 at 5:46 PM, IG-88 said:

from my point of view its pretty normal that there might be 3-4 weeks of complete inactivity, there are things like vacation and i might have a look here in that time but i will not do anything about drivers or files...

 

“Only wimps use tape backup. REAL men just upload their important stuff on ftp and let the rest of the world mirror it.”

Linus Torvalds

 

Agreed on the first part.

 

As to the second part, I wish I was as cavalier as the Big L's sentiment there.  I'm more of a 3-2-1 guy myself.  Although it's probably more accurate to say currently it's 3-2-1 + 1 for me, personally.

 

On 10/27/2020 at 5:46 PM, IG-88 said:

don't worry, thasts normal, people are very different - i'm at least normal enough to have a job i'm getting paid for and i don't need to visit a psychologist - good enough

 

I dunno if this is one step better than Mr. Torvalds, but some Jungian wisdom suggests normality is a fine ideal, for those who have no imagination.

 

That said, I also happily belong to the "at least normal enough" category you mention above, so huzzah for us both!

Link to post
Share on other sites

Generally it is to get the i915 driver from Syno's latest update, which is newer than the one Jun compiled as part of the DS918+ 1.04b loader.

 

The other reason is to revert any mangling done to make 6.2.2 functional, as that solution won't work with 6.2.3 (but getting the files from a clean copy of the loader works as well).

Edited by flyride
Link to post
Share on other sites
20 hours ago, merve04 said:

Whats the purpose of copying zImage and rd.gz from the pat file to the usb key?

 

6.2.2 kernel does not work with drivers from before (like jun's default extra) and drivers made for 6.2.2 do not work with the older pre 6.2.2 kernel

jun's loader contains the kernel of dsm 6.2.0 and extra.lzma with drivers for 6.2.0

2 scenarios

1. juns loader as it comes boots fine (nic driver works), installing dsm 6.2.2 copy's  the new kernel to the usb and an next boot (content of dsm pat file copied to disk) the drivers do not work anymore because now we have kernel 6.2.2 instead of 6.2.0 - lots of people hat this wen updating from a installed dsm 6.2.0 to 6.2.2

most often seen where hp microserver users using the onbaord broadcom driver and after the update the driver did not work anymore but the "native" intel driver that is part of dsm was ok and the "official" additional card from hp was intel based, that why so many people think you need one of these, at the time where no specific drivers for 6.2.2 where available it was the easy way to again get access over network (the downgrade process is not that easy and depending on which you follow you might loose the dsm settings and start over with factory defaults)

 

2. you have additional drivers for 6.2.2 (extra.lzma) and place it on the loader before booting the 1st time (like in the tutorial) now the loader still contains kernel 6.2.0 and your driver are 6.2.2, booting will result in additional drivers not loading because of the mismatch, so when also placing the matching kernel files on the loader it will work and when installing 6.2.2 nothing will change, as 6.2.2 install process places 6.2.2 kerenl files on the loader

 

but thats all not so important anymore because with 6.2.3 synology returned the state of the kernel it had with 6.2.0 so in scenario 1 after install you will of dsm you will have kernel 6.2.3 on usb but the "old" 6.2.0 drivers are still working with 6.2.3 so the system will boot, only flaw is the i915 driver in 918+ loader (see explanation below)

 

when using 6.2.3 extra.lzma its still not wrong to also copy the 6.2.3 kernel to the loader, that way you can't have surprises  like loader works and after installing dsm it does not, there is no guarantee that the old drivers will all work with the newer 6.2.3 kernel, i did not had problems when testing it but i had only a limited selection of hardware to test with, the lowest incompatibility expectation is when using the latest 6.2.3 extra.lzma (made from kernel source on the level of dsm 6.2.2 from 3/2020) with kernel 6.2.3 that way source code used for drivers (6.2.2) and binary kernel of 6.2.3 (we don't have kernel source for this as synology does not publish it) are as close together as possible so it minimizes the possible incompatibility's

it would be best to build drivers from the same source as the binary kernel was build from but as synology is not eager to publish the source (even if GPL should make them publish it) we have to use whats available and hope for the best

in theory they should have published source of 6.2.3 when publishing that version but they did not and seem to be waiting to threads or complaints from outside before doing so, beside new protections with new dsm major versions this is one way to stall unwanted projects like xpenology and beside this they also have no interest that people extend dsm with "uncertified" hardware by building drivers that can be added (to original synology  systems)

(users of original hardware should be able to use our drivers too but 3615/17 are not common for home use and 918+ has not much to extend beside usb 3.0)

 

20 hours ago, flyride said:

Generally it is to get the i915 driver from Syno's latest update, which is newer than the one Jun compiled as part of the DS918+ 1.04b loader.

 

its not really "getting" the drivers, the new i915 drivers are part of dsm 6.2.3 and the now "older" incompatible drivers from jun are in the way because how synology backported is different from the way jun did it and these kernel changes synology made are now incompatible to jun's i915 driver and it does not load anymore

because jun's driver is in the path "update" its preferred to load over the driver in /usr/lib/modules/ from dsm, the 6.2.3 extra does not contains jun's drivers anymore and also deletes the still existing driver in "update" (the process that copy's drivers from the extra to disk does not remove anything from disk so even when removed from the extra on the loader the i915 would still be on disk and loaded when present and to not make it mandatory for the user to manually delete files from disk when updating from 6.2.x to 6.2.3 i modified the patch in the extra to delete the i915 files from /usr/lib/modules/update)

so its more the other way around you dont get anything with the new 6.2.3 extra.lzma, something is removed from the loader and also gets removed from disk to clear the path for dsm's own i915 driver to be loaded

 

side note: in fact the i195 source code jun used was e few month newer but made no difference when in comes to supported devices

Link to post
Share on other sites
1 hour ago, Richard Hopton said:

Has anyone got LSI 9305-16i (MPT SAS3224) working? I've tried updating to newest extra.lzma but doesn't pick the drives up.

 

you did not specify what dsm type and version you tried and if you used a extra.lzma for more/better drivers

for the controller in question i find the following pci id's (vendor/device)

1000 - Broadcom/LSI

00c4 - SAS3224 PCI-Express Fusion-MPT SAS-3

 

that controller should work with dsm 6.2.3 for 3617 (even without my latest extra.lzma)

did you look into dmesg for its pci id and what driver mpt3sas writes to the log when loading?

in general 3617 is the best choice for lsi sas controller as synology supports newer controller by default (3615 does not get newer drivers from synology)

Link to post
Share on other sites

 

Quote

you did not specify what dsm type and version you tried and if you used a extra.lzma for more/better drivers

Apologies - I tried a bunch of things...

1, Existing 3615 running DSM 6.2.3 in a VM (ESXi 6.7) with a couple old LSI cards already passed through; passed the 9305-16i through but no drives recognized.

2, Ran an Ununtu VM and passed thru the 9305; drives showed up just fine.

3, Created new 3617 VM using Jun's 1.03.b synoboot untouched (except for grub.cfg changes for S/N, mac & menu entry); passthu 9305 but no drives recognized

4, Updated synoboot for 3617 with extra.lzma, rd.gz & zimage from the first post on this thread (6.2.2??); no drives recognized

 

 

Quote

did you look into dmesg for its pci id and what driver mpt3sas writes to the log when loading?

I didn't do either of these (not really sure where to look at logs)

 

When setting up the 3617xs VM I added synoboot.vmdk drive as per tutorial, and passthru 9305 with a few drives... do I need to add any extra virtual drives? Should I update the synoboot img with 6.2.3 rd.gz, zimage and some new extra.lzma?

Screen Shot 2020-11-14 at 12.26.03 PM.png

Edited by Richard Hopton
Link to post
Share on other sites
16 hours ago, Richard Hopton said:

I didn't do either of these (not really sure where to look at logs)

/var/log/

dmesg is a file there but is also a command that can be used in a shell

dmesg |more

(in this case return scroll by line, space scrolls a page, strg-c ends it)

 

 

7 hours ago, Richard Hopton said:

Okay - looks like it was showing up but was being recognized as drive 15+ - After some fiddling I got it to show but the drives aren't 1-16 as I'd expect... will have to figure out how to fix that! Thanks for your help.

 

as this is not a driver problem and we are in the wrong thread - this one is about dsm 6.2.2 - please open a new thread in the hardware section

 

a general comment, 3617 has a default of 12 drives and you would need to modify the synoinfo.conf to change this and as this is not a change that is checked and done by the loader it will get lost on bigger updates, might leaving a raid in crashed state after a update  or lost of redundancy (depending on how many drives get lost when being back on 12 drives default)

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

 

Link to post
Share on other sites
  • 4 weeks later...

this is the thread for dsm 6.2.2, the extra you reference is for 6.2.3

mixing is not going to work, 6.2.2 has different kernel settings

in generel rtl5153 (i dont know where you got that "x" from) is supported in the r8152.ko driver

check the dmesg log for messages about "r815"

you can also check the vid/pid and the sub id's with lsusb and write the result here

Link to post
Share on other sites
  • 5 weeks later...
On 6/1/2020 at 6:03 AM, richv31 said:

Interesting, I have a jmb585 5 port card on order. My j4105 MB has only 2 onboard ports and a single pcie 2-lane slot that gives me 7 drives (my u-nas chassis can handle 8). Regarding my current system, on wake-up, the system seems to do a staggered (one drive at a time) wake-up. I looked up the error codes (ASC=0x4 ASCQ=0x2) - "Logical Unit Not Ready, Init. Cmd Required Indicates that the drive is ready to go, but it is not spinning. Generally, the drive needs to be spun up." So it looks like DSM is not waiting for the disks to be spun up before attempting to access them.

 

  HDD wakeup errors (Reveal hidden contents)

[   51.663675] FAT-fs (synoboot2): fat_set_state: set=1 process=synopkicompatsy pid=11143
[   51.679804] FAT-fs (synoboot2): fat_set_state: set=0 process=synopkicompatsy pid=11143
[   53.741388] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[   53.741680] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[   53.741744] ata1.00: configured for UDMA/133
[   53.743542] ata1: EH complete
[   53.743563] ata1.00: Enabling discard_zeroes_data
[   58.460556] iSCSI:target_core_rodsp_server.c:1027:rodsp_server_init RODSP server started, login_key(001132123456).
[   58.492479] iSCSI:extent_pool.c:766:ep_init syno_extent_pool successfully initialized
[   58.517653] iSCSI:target_core_device.c:617:se_dev_align_max_sectors Rounding down aligned max_sectors from 4294967295 to 4294967288
[   58.517780] iSCSI:target_core_lunbackup.c:361:init_io_buffer_head 512 buffers allocated, total 2097152 bytes successfully
[   58.593806] iSCSI:target_core_file.c:146:fd_attach_hba RODSP plugin for fileio is enabled.
[   58.593813] iSCSI:target_core_file.c:153:fd_attach_hba ODX Token Manager is enabled.
[   58.593827] iSCSI:target_core_multi_file.c:91:fd_attach_hba RODSP plugin for multifile is enabled.
[   58.593839] iSCSI:target_core_ep.c:786:ep_attach_hba RODSP plugin for epio is enabled.
[   58.593840] iSCSI:target_core_ep.c:793:ep_attach_hba ODX Token Manager is enabled.
[   58.687936] capability: warning: `nginx' uses 32-bit capabilities (legacy support in use)
[   59.079129] loop: module loaded
[ 4851.309911] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4851.309926] sd 2:0:0:0: [sdc] tag#0 Sense Key : 0x2 [current]
[ 4851.309934] sd 2:0:0:0: [sdc] tag#0 ASC=0x4 ASCQ=0x2
[ 4851.309942] sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x28 28 00 00 4c 06 80 00 00 08 00
[ 4851.309949] blk_update_request: I/O error, dev sdc, sector in range 4980736 + 0-2(12)
[ 4856.022445] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.022459] sd 2:0:0:0: [sdc] tag#0 Sense Key : 0x2 [current]
[ 4856.022466] sd 2:0:0:0: [sdc] tag#0 ASC=0x4 ASCQ=0x2
[ 4856.022474] sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x28 28 00 00 90 00 08 00 00 08 00
[ 4856.022480] blk_update_request: I/O error, dev sdc, sector in range 9437184 + 0-2(12)
[ 4856.023055] sd 2:0:2:0: [sde] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.023062] sd 2:0:2:0: [sde] tag#1 Sense Key : 0x2 [current]
[ 4856.023069] sd 2:0:2:0: [sde] tag#1 ASC=0x4 ASCQ=0x2
[ 4856.023075] sd 2:0:2:0: [sde] tag#1 CDB: opcode=0x28 28 00 00 4c 06 80 00 00 08 00
[ 4856.023080] blk_update_request: I/O error, dev sde, sector in range 4980736 + 0-2(12)
[ 4856.023624] sd 2:0:2:0: [sde] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.023630] sd 2:0:2:0: [sde] tag#2 Sense Key : 0x2 [current]
[ 4856.023636] sd 2:0:2:0: [sde] tag#2 ASC=0x4 ASCQ=0x2
[ 4856.023642] sd 2:0:2:0: [sde] tag#2 CDB: opcode=0x28 28 00 00 90 00 08 00 00 08 00
[ 4856.023646] blk_update_request: I/O error, dev sde, sector in range 9437184 + 0-2(12)
[ 4856.024265] sd 2:0:3:0: [sdf] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.024272] sd 2:0:3:0: [sdf] tag#3 Sense Key : 0x2 [current]
[ 4856.024281] sd 2:0:3:0: [sdf] tag#3 ASC=0x4 ASCQ=0x2
[ 4856.024291] sd 2:0:3:0: [sdf] tag#3 CDB: opcode=0x28 28 00 00 4c 06 80 00 00 08 00
[ 4856.024296] blk_update_request: I/O error, dev sdf, sector in range 4980736 + 0-2(12)
[ 4856.024849] sd 2:0:3:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.024855] sd 2:0:3:0: [sdf] tag#0 Sense Key : 0x2 [current]
[ 4856.024860] sd 2:0:3:0: [sdf] tag#0 ASC=0x4 ASCQ=0x2
[ 4856.024866] sd 2:0:3:0: [sdf] tag#0 CDB: opcode=0x28 28 00 00 90 00 08 00 00 08 00
[ 4856.024871] blk_update_request: I/O error, dev sdf, sector in range 9437184 + 0-2(12)
[ 4856.025431] sd 2:0:4:0: [sdg] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.025446] sd 2:0:4:0: [sdg] tag#1 Sense Key : 0x2 [current]
[ 4856.025451] sd 2:0:4:0: [sdg] tag#1 ASC=0x4 ASCQ=0x2
[ 4856.025457] sd 2:0:4:0: [sdg] tag#1 CDB: opcode=0x28 28 00 00 4c 06 80 00 00 08 00
[ 4856.025462] blk_update_request: I/O error, dev sdg, sector in range 4980736 + 0-2(12)
[ 4856.026010] sd 2:0:4:0: [sdg] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.026016] sd 2:0:4:0: [sdg] tag#2 Sense Key : 0x2 [current]
[ 4856.026021] sd 2:0:4:0: [sdg] tag#2 ASC=0x4 ASCQ=0x2
[ 4856.026027] sd 2:0:4:0: [sdg] tag#2 CDB: opcode=0x28 28 00 00 90 00 08 00 00 08 00
[ 4856.026032] blk_update_request: I/O error, dev sdg, sector in range 9437184 + 0-2(12)
[ 4856.865160] sd 2:0:2:0: [sde] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.865182] sd 2:0:2:0: [sde] tag#1 Sense Key : 0x2 [current]
[ 4856.865190] sd 2:0:2:0: [sde] tag#1 ASC=0x4 ASCQ=0x2
[ 4856.865200] sd 2:0:2:0: [sde] tag#1 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
[ 4856.865214] blk_update_request: I/O error, dev sde, sector in range 4980736 + 0-2(12)
[ 4856.865746] md: super_written gets error=-5
[ 4856.865758] md_error: sde1 is being to be set faulty
[ 4856.865763] raid1: Disk failure on sde1, disabling device.
                Operation continuing on 4 devices
[ 4856.866456] sd 2:0:3:0: [sdf] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.866465] sd 2:0:3:0: [sdf] tag#2 Sense Key : 0x2 [current]
[ 4856.866472] sd 2:0:3:0: [sdf] tag#2 ASC=0x4 ASCQ=0x2
[ 4856.866480] sd 2:0:3:0: [sdf] tag#2 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
[ 4856.866489] blk_update_request: I/O error, dev sdf, sector 4982400
[ 4856.866918] md: super_written gets error=-5
[ 4856.866938] md_error: sdf1 is being to be set faulty
[ 4856.866952] raid1: Disk failure on sdf1, disabling device.
                Operation continuing on 3 devices
[ 4856.867687] sd 2:0:4:0: [sdg] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4856.867693] sd 2:0:4:0: [sdg] tag#3 Sense Key : 0x2 [current]
[ 4856.867698] sd 2:0:4:0: [sdg] tag#3 ASC=0x4 ASCQ=0x2
[ 4856.867705] sd 2:0:4:0: [sdg] tag#3 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
[ 4856.867711] blk_update_request: I/O error, dev sdg, sector 4982400
[ 4856.868134] md: super_written gets error=-5
[ 4856.868140] md_error: sdg1 is being to be set faulty
[ 4856.868143] raid1: Disk failure on sdg1, disabling device.
                Operation continuing on 2 devices
[ 4867.014224] sd 2:0:0:0: [sdc] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4867.014238] sd 2:0:0:0: [sdc] tag#1 Sense Key : 0x2 [current]
[ 4867.014245] sd 2:0:0:0: [sdc] tag#1 ASC=0x4 ASCQ=0x2
[ 4867.014253] sd 2:0:0:0: [sdc] tag#1 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
[ 4867.014262] blk_update_request: I/O error, dev sdc, sector 4982400
[ 4867.014693] md: super_written gets error=-5
[ 4867.014705] md_error: sdc1 is being to be set faulty
[ 4867.014710] raid1: Disk failure on sdc1, disabling device.
                Operation continuing on 1 devices
[ 4867.035989] RAID1 conf printout:
[ 4867.035997]  --- wd:1 rd:16
[ 4867.036003]  disk 0, wo:1, o:0, dev:sdc1
[ 4867.036008]  disk 1, wo:0, o:1, dev:sdd1
[ 4867.036012]  disk 2, wo:1, o:0, dev:sdg1
[ 4867.036016]  disk 3, wo:1, o:0, dev:sde1
[ 4867.036019]  disk 4, wo:1, o:0, dev:sdf1
[ 4867.040944] RAID1 conf printout:
[ 4867.040952]  --- wd:1 rd:16
[ 4867.040958]  disk 1, wo:0, o:1, dev:sdd1
[ 4867.040962]  disk 2, wo:1, o:0, dev:sdg1
[ 4867.040966]  disk 3, wo:1, o:0, dev:sde1
[ 4867.040970]  disk 4, wo:1, o:0, dev:sdf1
[ 4867.040982] RAID1 conf printout:
[ 4867.040985]  --- wd:1 rd:16
[ 4867.040988]  disk 1, wo:0, o:1, dev:sdd1
[ 4867.040992]  disk 2, wo:1, o:0, dev:sdg1
[ 4867.040995]  disk 3, wo:1, o:0, dev:sde1
[ 4867.040999]  disk 4, wo:1, o:0, dev:sdf1
[ 4867.049937] RAID1 conf printout:
[ 4867.049945]  --- wd:1 rd:16
[ 4867.049951]  disk 1, wo:0, o:1, dev:sdd1
[ 4867.049956]  disk 2, wo:1, o:0, dev:sdg1
[ 4867.049960]  disk 4, wo:1, o:0, dev:sdf1
[ 4867.049968] RAID1 conf printout:
[ 4867.049971]  --- wd:1 rd:16
[ 4867.049975]  disk 1, wo:0, o:1, dev:sdd1
[ 4867.049978]  disk 2, wo:1, o:0, dev:sdg1
[ 4867.049982]  disk 4, wo:1, o:0, dev:sdf1
[ 4867.056935] RAID1 conf printout:
[ 4867.056942]  --- wd:1 rd:16
[ 4867.056948]  disk 1, wo:0, o:1, dev:sdd1
[ 4867.056952]  disk 2, wo:1, o:0, dev:sdg1
[ 4867.056960] RAID1 conf printout:
[ 4867.056963]  --- wd:1 rd:16
[ 4867.056966]  disk 1, wo:0, o:1, dev:sdd1
[ 4867.056970]  disk 2, wo:1, o:0, dev:sdg1
[ 4867.063954] RAID1 conf printout:
[ 4867.063962]  --- wd:1 rd:16
[ 4867.063968]  disk 1, wo:0, o:1, dev:sdd1
 

I understand and I don't need temps or fan speeds. The interesting part is that something changed for ds3615 between 6.2.2 and 6.2.3 with these errors now showing up regularly in scemd.log. Also at the same time HDD hibernation stopped working in 3615/6.2.3 (drives will not hibernate) and I assume this is due to these errors and the log writing. I don't know if this issue is LSI controller specific or it also applies to ahci drives, I will test. Also, these errors are not present in the 918+/6.2.3 logs.

 

This is  how it looks for me in using the lsi 9211-8i controller:

 

Loader OS/ver/driver HDD go into hibernate HDD come out of hibernate
1.03b 3615/6.2.2/mpt2sas OK OK
1.03b 3615/6.2.3/mpt2sas NO n/a
1.04b 918+/6.2.2/mpt3sas OK OK for basic volume, Crash for RAID volumes
1.04b 918+/6.2.3/mpt3sas OK
OK for basic volume, Crash for RAID volumes

 

Hi, may I ask if v1.04b loader for 918+ with mpt2sas under 6.2.3 still haven't issue with HDD Hibernation? Is there any solution to re-gain the HDD hibernation under this combination? Thanks a lot!

Link to post
Share on other sites
13 hours ago, e-ghost said:

Hi, may I ask if v1.04b loader for 918+ with mpt2sas under 6.2.3 still haven't issue with HDD Hibernation? Is there any solution to re-gain the HDD hibernation under this combination?

may be you should read what i wrote in the 6.2.3 post about that matter, it exists since 6.2.0 and happens with jun's original drivers, you can/will have the same problems with 6.2.2

jun did not document how he made the drivers and from what kernel source

it was discovered pretty late and seems not to effect a lot of people or we would have seen complains earlier

its not so difficult now to get around that by using ahci controllers (i do it that way, also the control over the write cache of the disks does not work with lsi sas controlelrs but does with ahci)

 

Link to post
Share on other sites
13 hours ago, IG-88 said:

may be you should read what i wrote in the 6.2.3 post about that matter, it exists since 6.2.0 and happens with jun's original drivers, you can/will have the same problems with 6.2.2

jun did not document how he made the drivers and from what kernel source

it was discovered pretty late and seems not to effect a lot of people or we would have seen complains earlier

its not so difficult now to get around that by using ahci controllers (i do it that way, also the control over the write cache of the disks does not work with lsi sas controlelrs but does with ahci)

 

Hi @IG-88, read what you wrote and understood the situation now. Thanks a lot! 

Link to post
Share on other sites
  • 1 month later...

First of all you're incredible! Thank so much for all!

 

I've this problem:

 

MB Asrock E350M1/USB3

 

Using loader 1.03b DS3615 (6.2) and DSM 6.2.3 surprisingly everything works but..... i've a problem!

 

Network performance are poor (SMB), 11Mb/sec transfer rate on gbit network. I have read several posts and done countless tests and have come to the conclusion that it is a driver problem. I tried using the extra 0.5 package but it doesn't boot anymore.

 

I have seen that there are recent sources of the network driver that this motherboard uses (8.048.03), I was wondering if anyone can help me to have this driver compiled on the extras or something else, especially IG-88 (thanks again for the endless work you do).

 

I don't know if it will fix it but I think it's worth it

Link to post
Share on other sites
21 hours ago, Simonz said:

First of all you're incredible! Thank so much for all!

 

I've this problem:

 

MB Asrock E350M1/USB3

 

Using loader 1.03b DS3615 (6.2) and DSM 6.2.3 surprisingly everything works but..... i've a problem!

 

Network performance are poor (SMB), 11Mb/sec transfer rate on gbit network. I have read several posts and done countless tests and have come to the conclusion that it is a driver problem. I tried using the extra 0.5 package but it doesn't boot anymore.

 

I have seen that there are recent sources of the network driver that this motherboard uses (8.048.03), I was wondering if anyone can help me to have this driver compiled on the extras or something else, especially IG-88 (thanks again for the endless work you do).

 

I don't know if it will fix it but I think it's worth it

UPDATE: installed extra 3615 v0.11, boot well but no change in speed, 11mb/sec transfer rate on smb

Link to post
Share on other sites
30 minutes ago, Simonz said:

UPDATE: installed extra 3615 v0.11, boot well but no change in speed, 11mb/sec transfer rate on smb

can you try a live linux from usb, the speed sounds like you are running the nic with 100MBit, check speed led and settings in dsm, check cable, check switch

Link to post
Share on other sites
19 hours ago, IG-88 said:

can you try a live linux from usb, the speed sounds like you are running the nic with 100MBit, check speed led and settings in dsm, check cable, check switch

 

It's the cable...

 

...but only if you move it or move it to a precise point...incredible hasn't been moved in a long time. Sorry if I wasted your time

Link to post
Share on other sites

it's been a while and I forgot what steps are needed to move over to 6.2.3 on an HP Microserver Gen 8 with jun 1.0.3b. Is the process to upgrade to the latest DSM then copy the needed files to the USB drive, or will the upgrade write the correct files and nothing is required?

Link to post
Share on other sites
20 hours ago, TyShawn said:

it's been a while and I forgot what steps are needed to move over to 6.2.3 on an HP Microserver Gen 8 with jun 1.0.3b.

for that reason i wrote some information about that in the 1st post post of the 6.2.3 driver thread

https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/

 

it got a little untidy over time but beside the red warnings you should find what you need when start reading from this point

"...

i completely removed jun's i915 drivers from the ..."

 

as drivers are different with 6.2.1 and 6.2.2 and you use the 6.2.2 adapted extra.lzma, then for 6.2.3 you will need jun's old extra.lzma (extract with 7zip from original loader) or my new one made for 6.2.3 (if the microserver does not have any "special" added hardware the old extra from jun would be enough)

Edited by IG-88
  • Like 1
Link to post
Share on other sites

Hi ,I am new here

First thanks for the great work

I use G6400 ASUS Prime-H410I-PLUS

I try to install this to that my gpu can work.

Is there any install guide I can check?

I have alreay install https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/

DS918+  DSM 6.2.3-25426 Update 3 

Link to post
Share on other sites
  • 1 month later...

Looking to get this going so I can get my second ethernet port working. If someone wouldn’t mind sanity checking before I dive into this

Hardware:

ASrock Rack C246 WSI - 2 x RJ45 GLAN by Intel® i210+Intel® i219LM
Intel I3-9100
DMS 6.2.2-23739 – jun 1.04b – 918+

Install:

SSH w/ root
rm -rf /usr/lib/modules/update/*
rm -rf /usr/lib/firmware/i915/*

Shut down the system

Chuck the usb into my computer, mount w/ osfmount, replace the original files in the partition with the updated lzma

done?

Link to post
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.