Jump to content
XPEnology Community

Jun's Alpha Loader for DSM 6.1


CrazyCreator

Recommended Posts

Hey,

Has anyone managed to install DS916 +?

Can check if it has a file:/dev/dri/card0

Execute the command: lsmod

 

I installed it on esxi 6.5 just for testing... here there's not /dev/dri/card0

 

Ciao

ema

Execute the command: lsmod

 

ash-4.3# lsmod | grep card
ash-4.3# 

 

ash-4.3# lsmod
Module                  Size  Used by
cifs                  246536  2 
udf                    81376  0 
isofs                  32127  0 
loop                   17423  0 
iscsi_target_mod      220762  1 
target_core_ep         48756  2 
target_core_file       29955  1 
target_core_iblock     14240  1 
target_core_mod       366535  13 target_core_iblock,iscsi_target_mod,target_core_ep,target_core_file
syno_extent_pool     1290661  0 
rodsp_ep               75623  2 syno_extent_pool,target_core_file
hid_generic             1113  0 
usbhid                 25479  0 
hid                    82660  2 hid_generic,usbhid
usblp                  10474  0 
uhci_hcd               22739  0 
ehci_pci                3560  0 
ehci_hcd               40220  1 ehci_pci
braswell_synobios      46518  0 
ax88179_178a           12076  0 
usbnet                 17845  1 ax88179_178a
ixgbe                 152067  0 
vmxnet3                38149  0 
e1000                 100595  0 
sfc                   156347  0 
jme                    34553  0 
ipg                    15901  0 
libphy                 18253  0 
mii                     3763  4 ipg,jme,usbnet,ax88179_178a
btrfs                 869897  1 
i915                  896981  0 
drm_kms_helper         77262  1 i915
cfbfillrect             3738  1 i915
cfbcopyarea             3246  1 i915
cfbimgblt               2159  1 i915
output                  1612  0 
drm                   245894  2 i915,drm_kms_helper
fb                     32636  3 drm,i915,drm_kms_helper
fbdev                    758  1 fb
intel_agp              10704  1 
intel_gtt              12088  2 i915,intel_agp
agpgart                26307  3 drm,intel_agp,intel_gtt
video                  10824  1 i915
backlight               3888  2 i915,video
button                  4440  1 i915
synoacl_vfs            17118  1 
zlib_deflate           20828  1 btrfs
hfsplus                93058  0 
md4                     4129  0 
hmac                    2689  2 
libcrc32c                898  0 
mdio                    3229  2 sfc,ixgbe
compat                  4521  0 
igb                   177156  0 
i2c_algo_bit            5120  2 sfc,i915
e1000e                170873  0 
fuse                   76906  0 
vfat                   10335  0 
fat                    50639  1 vfat
crc32c_intel           13793  2 
aesni_intel            43613  0 
glue_helper             4057  1 aesni_intel
lrw                     3269  1 aesni_intel
gf128mul                5466  1 lrw
ablk_helper             1676  1 aesni_intel
arc4                    1832  0 
cryptd                  6956  2 aesni_intel,ablk_helper
ecryptfs               79238  1 btrfs
sha512_generic          5064  0 
sha256_generic         10452  1 
sha1_generic            2390  0 
ecb                     1841  0 
aes_x86_64              7295  1 aesni_intel
authenc                 6236  0 
des_generic            16483  0 
ansi_cprng              3732  0 
cts                     3992  0 
md5                     2689  2 
cbc                     2504  0 
cpufreq_powersave        918  0 
cpufreq_performance      922  0 
mperf                   1067  0 
processor              26076  0 
thermal_sys            17969  2 video,processor
cpufreq_stats           2849  0 
freq_table              2372  1 cpufreq_stats
dm_snapshot            26122  0 
crc_itu_t               1259  1 udf
crc_ccitt               1259  0 
quota_v2                3711  0 
quota_tree              7770  1 quota_v2
psnap                   1709  0 
p8022                    971  0 
llc                     3489  2 p8022,psnap
sit                    14674  0 
tunnel4                 2053  1 sit
ip_tunnel              11448  1 sit
ipv6                  304625  58 sit,rodsp_ep
zram                    8073  2 
sg                     25201  0 
megaraid_sas           75118  0 
megaraid               40306  0 
megaraid_mbox          29219  0 
megaraid_mm             7808  1 megaraid_mbox
vmw_pvscsi             15623  0 
BusLogic               21633  0 
usb_storage            47901  0 
etxhci_hcd             85866  0 
xhci_hcd               85788  0 
ohci_hcd               21192  0 
usbcore               176526  13 etxhci_hcd,usblp,uhci_hcd,usb_storage,ohci_hcd,ehci_hcd,ehci_pci,usbhid,usbnet,ax88179_178a,xhci_hcd
usb_common              1544  1 usbcore
el000                  17168  0 

 

Ciao

ema

Link to comment
Share on other sites

Hello

After the update DSM 6.1-15047 Update 2, DS3617xs crashed.

So not yet quite ready this versions.

 

Every person that has updated to u2 has had no problem as far as I know.

Agreed.

Question. When do we have an official 6.1 loader? I think, after a month, it's a right time to launch it.

Link to comment
Share on other sites

DS3617xs on DSM 6.1u2 using Jun's loader v1.02a2 - My system has now been running continuously for 2 days, 21 hours+ under this config.

 

We have noticed that within SynoCommunity, many of the standard packages are not available for the DS3617xs.

SABNZB, NZBDrone, and Python packages, have been modified by my son to run on a DS3617xs, and are all operational and actively managing downloads of TV shows etc.

System appears stable since the migration from v1.02a to v1.02a2 (under v1.02a we had the 12 hour the Time Bomb issue).

We intend running under this config for another 3 days to check reliability/consistency, before going permanent with this config.

Specially built packages for DS3617xs are attached.

Note: the attached SPK files still require their dependencies to function (e.g. Sonarr requires Mono - this can be downloaded from the SynoCommunity; SABNZBD requires Python 2.7 (this is included in the download).

The link to the download is here: https://ufile.io/vsh34

 

1. DS3617xs (based on Supermicro mbrd X10SL7-F, Xeon E3-1241v3 cpu @ 3.5GHz, 4 x 8TB WD-Reds, 16GB ECC.

2. DS1513+ Synology with 5 x 8TB (WD-Reds)

I'm intending to migrate the drives from the DS1513+ into the first (primary) unit and using 5 x 4TB WD-Reds in DS1513+ as a backup NAS once we go operational with the DS3617xs based unit.

Link to comment
Share on other sites

Hello

After the update DSM 6.1-15047 Update 2, DS3617xs crashed.

So not yet quite ready this versions.

 

Every person that has updated to u2 has had no problem as far as I know.

Agreed.

Question. When do we have an official 6.1 loader? I think, after a month, it's a right time to launch it.

 

When Jun decides so. Our opinion is irrelevant on that matter.

Link to comment
Share on other sites

DS3617xs on DSM 6.1u2 using Jun's loader v1.02a2 - My system has now been running continuously for 2 days, 21 hours+ under this config.

 

We have noticed that within SynoCommunity, many of the standard packages are not available for the DS3617xs.

SABNZB, NZBDrone, and Python packages, have been modified by my son to run on a DS3617xs, and are all operational and actively managing downloads of TV shows etc.

System appears stable since the migration from v1.02a to v1.02a2 (under v1.02a we had the 12 hour the Time Bomb issue).

We intend running under this config for another 3 days to check reliability/consistency, before going permanent with this config.

Specially built packages for DS3617xs are attached.

Note: the attached SPK files still require their dependencies to function (e.g. Sonarr requires Mono - this can be downloaded from the SynoCommunity; SABNZBD requires Python 2.7 (this is included in the download).

The link to the download is here: https://ufile.io/vsh34

 

1. DS3617xs (based on Supermicro mbrd X10SL7-F, Xeon E3-1241v3 cpu @ 3.5GHz, 4 x 8TB WD-Reds, 16GB ECC.

2. DS1513+ Synology with 5 x 8TB (WD-Reds)

I'm intending to migrate the drives from the DS1513+ into the first (primary) unit and using 5 x 4TB WD-Reds in DS1513+ as a backup NAS once we go operational with the DS3617xs based unit.

 

Good to know it all working fine for you. One question though, why don't use DS3615XS? You wouldn't need to modify the packages.

Also, I do not recommend you use the curent loader v1.02a2 for production yet. There still are some issues reported here and there. I recommend you stay with v1.01 if possible.

Link to comment
Share on other sites

Thanks for your comments Polanskiman. Will bear them in mind.

I felt preferable to use DS3617xs rather than DS3615xs because the DS3617xs (with Xeon D1527 cpu) is somewhat closer to my config (Xeon E3-1241v3) than the DS3615xs which has an i3 processor.

Admittedly, my system was running stable and reliably as DS3615xs under 5.2-5644 & 5.2-5967 for over 12 months. As my system is currently configured to emulate DS3617xs, I'll just leave it as is and see how it continues for the time being. I'll hang off the switch over until a full (non alpha/beta) DS3617xs DSM 6.1 release is available. If other issues arise, then maybe I'll be forced to revert to DS3615xs v1.01 config.

Link to comment
Share on other sites

Thanks for your comments Polanskiman. Will bear them in mind.

I felt preferable to use DS3617xs rather than DS3615xs because the DS3617xs (with Xeon D1527 cpu) is somewhat closer to my config (Xeon E3-1241v3) than the DS3615xs which has an i3 processor.

Admittedly, my system was running stable and reliably as DS3615xs under 5.2-5644 & 5.2-5967 for over 12 months. As my system is currently configured to emulate DS3617xs, I'll just leave it as is and see how it continues for the time being. I'll hang off the switch over until a full (non alpha/beta) DS3617xs DSM 6.1 release is available. If other issues arise, then maybe I'll be forced to revert to DS3615xs v1.01 config.

 

That makes sense. Just don't put anything too valuable or without a backup with the current v1.02a2. That's all.

Link to comment
Share on other sites

Hi,

 

EDIT: Synonet is working again. The latest Win 10 creators upgrade broke WoL on my PC's by changing either the "fast start" or Power management for PCIe under advanced power settings (maybe both). If you are having trouble with WoL confirm that it works at all before thinking it's a DSM issue

 

I have the latest DSM using the alpha 1.02a2 Loader and it seems fine.

 

I am using this format in SSH successfully:

 

synonet –-wake XX:XX:XX:XX:XX:XX eth0;  

 

I'll try it in task manager. other suggestion is to have it as:

 

/usr/syno/sbin/synonet –-wake XX:XX:XX:XX:XX:XX eth0;

 

So... one less thing to clear up that I needed :smile:. SHame about the time I wasted playing with scripts because of MS :/

Link to comment
Share on other sites

don't try to install 6.1.1 if the updater suggests it, 6.1.1 uses a new kernel 15101 instead of 15047 from 6.1 so jun 1.0.2a/a2 will not work

 

edit: looks like the problem was in the test vm as other people dont have problems with it

so it should have been more a warning that it did not work for me

Edited by Guest
Link to comment
Share on other sites

don't try to install 6.1.1 if the updater suggests it, 6.1.1 uses a new kernel 15101 instead of 15047 from 6.1 so jun 1.0.2a/a2 will not work

 

Not sure to what kernel you are referring to but:

Linux kernel in 6.0.2 is 3.10.77

Linux kernel in 6.1 is 3.10.102

Linux kernel in 6.1.1 is still 3.10.102

 

I was able to install 6.1.1 with v1.02a2 on VBOX. This was a fresh install with 6.1.1.

Nc15ktN.jpg

I also tried doing an upgrade to 6.1.1 from 6.0.2 but that didn't seem to work. I tried several times. I wasn't able to access the GUI and there was no network activity. I did notice some unusual logs though. Those Hunk # signify that the patch needs to be updated for 6.1.1:

patching file etc/rc
Hunk #1 succeeded at 169 (offset 6 lines).
patching file etc/synoinfo.conf
Hunk #1 succeeded at 280 (offset 4 lines).
patching file linuxrc.syno
Hunk #1 succeeded at 38 (offset 1 line).
Hunk #2 succeeded at 117 with fuzz 2 (offset 1 line).
Hunk #3 succeeded at 397 (offset 13 lines).

or

[  151.364970] md1: Failed to send sync event: (sync type: resync, finish: 0, interrupt: 0)

A hard reset did not solve the issue obviously.

 

The advice to everyone is to NOT update to 6.1.1. Even doing a fresh install with 6.1.1 is not advisable. This needs to be addressed by Jun first.

Link to comment
Share on other sites

Update to 6.1.1 from 6.1 u2 worked fine.

 

My real Synology 216J = OK (as you'd expect)

Test server with loader 1.0.2 ds3615 = OK

 

I'll update my Main NAS (loader 1.0.2 ds3615) in a day or two, assuming no issues with the two above..

 

No, I won't be 'upgrading' to the DS3617 version as my DS3615 installs are working fine - and I value my data, thanks! :grin:

Plus, for me, there is absolutely no benefit in doing so.. :wink:

Link to comment
Share on other sites

Update to 6.1.1 from 6.1 u2 worked fine.

 

My real Synology 216J = OK (as you'd expect)

Test server with loader 1.0.2 ds3615 = OK

 

I'll update my Main NAS (loader 1.0.2 ds3615) in a day or two, assuming no issues with the two above..

 

No, I won't be 'upgrading' to the DS3617 version as my DS3615 installs are working fine - and I value my data, thanks! :grin:

Plus, for me, there is absolutely no benefit in doing so.. :wink:

 

No need to upgrade to 3617xs.

 

The test I carried above I also did with 3615xs and with the same result. It would fully upgrade to 6.1.1 from 6.1 with v1.02a2 but then DSM would not be reachable. A clean install did however work like it did with 3617xs.

Link to comment
Share on other sites

Update to 6.1.1 from 6.1 u2 worked fine.

 

My real Synology 216J = OK (as you'd expect)

Test server with loader 1.0.2 ds3615 = OK

 

I'll update my Main NAS (loader 1.0.2 ds3615) in a day or two, assuming no issues with the two above..

 

No, I won't be 'upgrading' to the DS3617 version as my DS3615 installs are working fine - and I value my data, thanks! :grin:

Plus, for me, there is absolutely no benefit in doing so.. :wink:

 

No need to upgrade to 3617xs.

 

The test I carried above I also did with 3615xs and with the same result. It would fully upgraded to 6.1.1 from 6.1 with v1.02a2 but then DSM would not be reachable. A clean install did however work like it did with 3617xs.

 

Dear Polanskiman,

 

I used v1.02a(lpha) and performed a 6.1.1 upgrade, then, as you mentioned, it's not reachable :oops: no surprises.... I really hate myself now :cry:

 

I am about to:

- unplug my current hard drives and perform a clean installation with another flash drive and a spare hard disk;

- shutdown;

- unplug hard disk and replug in my hard disks with same order as before and perform a migration;

 

Will this make things right?

 

Thanks a lot!

And sorry for the bothering.

BR//Wey

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...