jun

DSM 6.2 Loader

Recommended Posts

19 минут назад, ikkeenjij36 сказал:

Ok no prob for me atm...but now problem is it says its on 6.0.2 but is only repairble..when is start the process it loads dsm for 1% and reboots and says its not connecteble?
On juns loader 1.02b

Read this.

Share this post


Link to post
Share on other sites
2 минуты назад, ikkeenjij36 сказал:

Ok thnx...wich loader should i use?
The 1.02b?

Use the one you hw were working on.

Share this post


Link to post
Share on other sites
Posted (edited)
23 hours ago, Olegin said:

I have no problems with shutdown and reboot with e3 1285L v3 and j4105 too. Here is modified extra.lzma and manual how to change it on the working system, may be it'll help for you.

P.S. One mistake in the manual 😂

I try it again step by step, still no lucky. maybe something wrong.

the 915 driver always get kernel panic:

[   14.899201]  [<ffffffffa05beccf>] i915_driver_load+0xa0f/0xe00 [i915]
[   14.899222]  [<ffffffff813842d1>] driver_probe_device+0x1f1/0x310
[   14.899223]  [<ffffffff81384472>] __driver_attach+0x82/0x90
[   14.899224]  [<ffffffff813843f0>] ? driver_probe_device+0x310/0x310
[   14.899227]  [<ffffffff81383d69>] driver_attach+0x19/0x20
[   14.899228]  [<ffffffff81383993>] bus_add_driver+0x1b3/0x230
[   14.899230]  [<ffffffff81384c7b>] driver_register+0x5b/0xe0
[   14.899231]  [<ffffffff812fb337>] __pci_register_driver+0x47/0x50

and /dev/dri not exists.

 

Edited by Polanskiman
Added code tag

Share this post


Link to post
Share on other sites
6 минут назад, hawie сказал:

and /dev/dri not exists.

What hw config do you use?

Share this post


Link to post
Share on other sites
14 минуты назад, hawie сказал:

ASUS Q87T, https://www.asus.com/us/Motherboards/Q87TCSM/overview/

with XEON E3 1275v3 CPU,  DDR3L 4GB * 2

Try to disable C states in BIOS (or C1 state only). If it'll not help try to update BIOS to the latest version. In my xpen forder /dev/dri appeared after the BIOS version had updated.

Share this post


Link to post
Share on other sites
52 minutes ago, Olegin said:

Try to disable C states in BIOS (or C1 state only). If it'll not help try to update BIOS to the latest version. In my xpen forder /dev/dri appeared after the BIOS version had updated.

C states disabled in BIOS. it's the latest version.

just changed to 6.1.7 ds3617xs, shutdown and reboot works fine.

but 1.04b 918+, no /dev/dri devices, can not shutdown/reboot, HW accelerations shows enabled but not function.

Share this post


Link to post
Share on other sites
2 hours ago, Olegin said:

Try to disable C states in BIOS (or C1 state only). If it'll not help try to update BIOS to the latest version. In my xpen forder /dev/dri appeared after the BIOS version had updated.

https://mega.nz/#F!mRMVXKqS!AzAH57-3YIierx7O8C8FMA

uploaded one more file,  4K HEVC 10bit clip.  

please test it with HW acceleration, 1285L v3. 

Share this post


Link to post
Share on other sites
Posted (edited)
2 часа назад, hawie сказал:

please test it with HW acceleration, 1285L v3. 

Скрытый текст

1796510360_.thumb.png.a8fb8dde322548058b7da439e02d2085.png

Скрытый текст

1391263780_.thumb.png.aa7e501e860be274d82ffe58652f9aed.png

 

Edited by Olegin

Share this post


Link to post
Share on other sites

Trying out the loader 1.04b 918+. How do I get the serial? The serial generator has option for 916+ not 918+. 

Share this post


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

Trying out the loader 1.04b 918+. How do I get the serial? The serial generator has option for 916+ not 918+. 

You don't. Use the serial provided in the loader.

Share this post


Link to post
Share on other sites
16 hours ago, hawie said:

C states disabled in BIOS. it's the latest version.

just changed to 6.1.7 ds3617xs, shutdown and reboot works fine.

but 1.04b 918+, no /dev/dri devices, can not shutdown/reboot, HW accelerations shows enabled but not function.

I have the same problem with motherboard ASRock J3455-ITX (i915 causes kernel panic and no /dev/dri exists).

I think it is the same root cause, but currently no fix available.

 

see more logs in dmesg ->

https://xpenology.com/forum/topic/12332-j3455-hardware-acceleration-for-h265/?do=findComment&comment=107863

Share this post


Link to post
Share on other sites

Hi all,

i'll like to update my microsorver gen8 GT1610 to dsm 6.2.1, can i do this directly, or must i change CPU (and wich cpu) or network card (also, which card?)

 

Regards.

Share this post


Link to post
Share on other sites
Posted (edited)

Hi @le.pipo007
You will have to add an Intel chipset NIC and disable the default one/s.
I used CT EXPI9301CTBLK(Intel 82574L chipset) for two HP Gen8's and the update went flawless.

Edited by sadycus

Share this post


Link to post
Share on other sites
В 20.03.2019 в 10:52, kevingu сказал:

have the same problem with motherboard ASRock J3455-ITX 

With ASRock J4205-itx too, but ASRockJ4105/5005-itx working fine.

  • Like 1

Share this post


Link to post
Share on other sites
On 3/20/2019 at 2:21 AM, Olegin said:
  On my very old notebook by wifi... (Reveal hidden contents)

1796510360_.thumb.png.a8fb8dde322548058b7da439e02d2085.png

  P.S. (Reveal hidden contents)

1391263780_.thumb.png.aa7e501e860be274d82ffe58652f9aed.png

 

it's great, thanks! Haswell is good enough for HEVC transcoding, the wikipedia is not as trustworthy as your actual test. (^_^)

the problem for me, is how to let it works with my mainboard and E3 1275 v3 CPU, which always kernel panic till now.

any other changes with your loader? if yes, please share me.

Share this post


Link to post
Share on other sites
Posted (edited)

Dear

On 3/19/2019 at 9:26 AM, Olegin said:

Read this.

Dear @Olegin followed the tu used a spare and installed 6.1.7 on it after that it finds the nas with only the spare attachted to the mb and it still says it's on 6.0.2.8451 and it's recoverble?

what is going wrong or did i brick it completely now?

Using juns 1.02 loader

Edited by ikkeenjij36

Share this post


Link to post
Share on other sites

Anyone here uses the 1.04b loader on VMWARE, or Proxmox, and able to upgrade to the latest  6.2.1 Update 6?    My Proxmox setup failed to update with these logs:

any idea why? 

2019-03-25T11:34:13-05:00 DSServer updater: updater.c:6006 Start of the updater...
2019-03-25T11:34:13-05:00 DSServer updater: updater.c:6272 ==== Start flash update ====
2019-03-25T11:34:13-05:00 DSServer updater: updater.c:6276 This is X86 platform
2019-03-25T11:34:13-05:00 DSServer updater: updater.c:6293 The SynoBoot partitions exist.
2019-03-25T11:34:13-05:00 DSServer updater: updater.c:3680 SYNORedBootUpdCheckAndApply(3680): Skip bootloader update, no uboot_do_upd.sh exists
2019-03-25T11:34:13-05:00 DSServer updater: updater.c:589 file [zImage] is being copied to [/tmp/bootmnt]
2019-03-25T11:34:13-05:00 DSServer updater: updater.c:597 file [/tmp/bootmnt/zImage] process done.
2019-03-25T11:34:13-05:00 DSServer updater: updater.c:589 file [rd.gz] is being copied to [/tmp/bootmnt]
2019-03-25T11:34:13-05:00 DSServer updater: updater.c:597 file [/tmp/bootmnt/rd.gz] process done.
2019-03-25T11:34:13-05:00 DSServer updater: updater.c:589 file [grub_cksum.syno] is being copied to [/tmp/bootmnt]
2019-03-25T11:34:13-05:00 DSServer updater: updater.c:597 file [/tmp/bootmnt/grub_cksum.syno] process done.
2019-03-25T11:34:13-05:00 DSServer updater: updater.c:580 file [/tmp/bootmnt/updater] is being removed
2019-03-25T11:34:13-05:00 DSServer updater: updater.c:597 file [/tmp/bootmnt/updater] process done.
2019-03-25T11:34:13-05:00 DSServer updater: updater.c:580 file [/tmp/bootmnt/VERSION] is being removed
2019-03-25T11:34:13-05:00 DSServer updater: updater.c:597 file [/tmp/bootmnt/VERSION] process done.
2019-03-25T11:34:14-05:00 DSServer updater: updater.c:1036 This model DS918+
 needs no factory upgrade
 2019-03-25T11:34:14-05:00 DSServer updater: updater.c:6649 ==== Finish flash update ====
 2019-03-25T11:34:14-05:00 DSServer updater: updater.c:4929 successfully backup image for System Migration in path (/tmpRoot/.syno/patch).
 2019-03-25T11:34:14-05:00 DSServer updater: updater.c:6673 ==== Finish updater post-action ====
 2019-03-25T11:34:14-05:00 DSServer updater: updater.c:6727 Congratulations!! The update has been completed!! Do configupdate when next bootup.
 2019-03-25T11:34:14-05:00 DSServer smallupd@ter: smallupdate.cpp:1052 Failed to install /volume1//@smallupd@te_deb/libsynostorage-apollolake-bin_6.2-23824-s6_all.deb
 2019-03-25T11:34:14-05:00 DSServer smallupd@ter: smallupdate.cpp:1052 Failed to install /volume1//@smallupd@te_deb/libsynostoragecore-apollolake-bin_6.2-23824-s6_all.deb
 2019-03-25T11:34:15-05:00 DSServer smallupd@ter: smallupdate.cpp:1052 Failed to install /volume1//@smallupd@te_deb/linux-4.4.x-apollolake-bin_4.4.15-23824-s6_all.deb
 2019-03-25T11:34:15-05:00 DSServer smallupd@ter: smallupdate.cpp:1052 Failed to install /volume1//@smallupd@te_deb/mdadm-apollolake-bin_6.2-23824-s6_all.deb
 2019-03-25T11:34:15-05:00 DSServer smallupd@ter: smallupdate.cpp:1052 Failed to install /volume1//@smallupd@te_deb/netatalk-3.x-apollolake-bin_3.1.1-23824-s6_all.deb
 2019-03-25T11:34:15-05:00 DSServer smallupd@ter: smallupdate.cpp:1052 Failed to install /volume1//@smallupd@te_deb/selfcheck-cu06_6.2-23824-s6_all.deb
 2019-03-25T11:34:15-05:00 DSServer smallupd@ter: smallupdate.cpp:1395 failed to do install debain action
 2019-03-25T11:34:15-05:00 DSServer smallupd@ter: small_update.cpp:20 Failed to apply smallupdate.
 2019-03-25T11:34:15-05:00 DSServer synoscgi_SYNO.Core.Upgrade_1_start[7396]: Upgrade.cpp:236 Fail to exec smallupdater
 2019-03-25T11:34:15-05:00 DSServer synoscgi_SYNO.Core.Upgrade_1_start[7563]: update_cpputil.cpp:705 synoservice: start all packages ...
 2019-03-25T11:34:20-05:00 DSServer synoscgi_SYNO.Core.Upgrade_1_start[7563]: update_cpputil.cpp:755 synoservice: finish started all packages
 2019-03-25T11:34:20-05:00 DSServer synoscgi_SYNO.Core.Upgrade_1_start[7396]: Upgrade.cpp:708 Failed to apply smallupdate

 

Share this post


Link to post
Share on other sites

Hello! I have problems with bringing xpenology up after reboot or shutdown have been issued. The system works fine. Its when I have the system start up again that it is not able to be found on the network. I have to reinstall and then everything is back to normal. I have seen someone else ask the question but havent seen an answer as to why that would happen.

 

ASUS B250-HDV motherboard

i5 processor

Barebones install

4x6TB drives

Intel Pro Dual gigabit network card

DSM 6.2.1 Update 1

Bootloader 1.03b no custom files

Share this post


Link to post
Share on other sites

So, I ******* up again.

 

I've happily used 6.1.7 for several months now, but today I thought i'd be nice to give my Gen8 some love. I wrote Jun's 1.0.3b bootloader for  DS3615xs on a new USB drive and attempted an update. I think I selected the "Install latest version" option during the migration and I'm now stuck. I later on saw the warning on the forum that upgrading is not recommended. 

 

After writing the USB bootloader again, the NAS became discoverable again via the assistant and web app and listed as a DS3615xs running 6.2-23739.

 

I'm presented with the migration path but no avail - I get the "Failed to install the file. The file is probably corrupt (13)" error message. Tried upgrading, downgrading, whatever, to no avail.

 

Based on previous blunders, I know that I should be deleting the system partition so the NAS would let me downgrade.

 

Thing is that I have two 4TB drives in one volume that shows as ZFS in gparted. It has sda1, sda2, sda3 and sdb1, sdb2, sdb3, but not EXT4 as they used to be - they are now listed as LINUX RAID.

 

How do I proceed further to revert the damage? I have backup copies of essential stuff, but the loss of data would still hurt. Any advice is more than welcome.

Share this post


Link to post
Share on other sites

how to make only show 4 drivers on ds918+

Outcome of the update: SUCCESSFUL

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

- Loader version and model: JUN'S LOADER v1.04b - DS918+

- Installation type: esxi 6.7

uefi

vxm3

sata 0.0   boot loader 50 MB

sata 0.1   120 GB  2041377923_Capture11.thumb.PNG.78e9350049d25851d24d73198c8322ef.PNG

 

showing 14 disks

 

would like only show 4 disks

 

 

Share this post


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.