svens Posted June 18, 2017 Share #3126 Posted June 18, 2017 Hi all, What's happened to the boot log? It used to be working on older versions of the loader. Can it be brought back? Thanks. Quote Link to comment Share on other sites More sharing options...
sze Posted June 18, 2017 Share #3127 Posted June 18, 2017 Is there a way to migrate a original DS1815 ( DSM 6.1-15047 Update 2 ) to Xpenology? To make sure I don't lost any data I have a backup. But a restore of 20TB needs a lot of time. So a migration without losing data is a good option. But I don't know the best way. Quote Link to comment Share on other sites More sharing options...
zhenfu Posted June 18, 2017 Share #3128 Posted June 18, 2017 Will the new version support hyper-v? Quote Link to comment Share on other sites More sharing options...
zhenfu Posted June 18, 2017 Share #3129 Posted June 18, 2017 Posting requests to join hyper-v support, or can not be achieved? Quote Link to comment Share on other sites More sharing options...
mXfored Posted June 18, 2017 Share #3130 Posted June 18, 2017 (edited) A little update on my side, updated from 1.0.1jun+6.0.2update9 straight to 1.02b+6.1.2latest - went very smooth. Updates has been done on a HP Microserver Gen8 (Xeon), the installation is based on Proxmox4.x latest with drives passthrough. Hint: - after the first reboot, the VMware/ESXI grub entry is booted, be sure to reboot and select the first one - otherwise your drives wont be detected - virtio NIC / virtio drives still do not work Edited June 18, 2017 by mXfored Quote Link to comment Share on other sites More sharing options...
Qwertyz Posted June 18, 2017 Share #3131 Posted June 18, 2017 I tried 1.02b with my N36L (HP G7) baremetal but I cannot see it in the Synology Assistance. The only loader which worked for N36L baremetal was the 1.01. Did anybody managed to make the 1.02b working with N36L baremetal? Quote Link to comment Share on other sites More sharing options...
nevusZ Posted June 18, 2017 Share #3132 Posted June 18, 2017 just wanted to inform everybody that my update to 1.02b + dsm 6.1.2 15132 worked. I came from version 5.2 5466 xpenoboot. I had no problems with update file and did not need to have serial access baremetal qnap ts459 - intel atom d510 altough this is my first post here, I am working with xpenology since years. thanks everybody for great work here! Quote Link to comment Share on other sites More sharing options...
Ysyn Posted June 18, 2017 Share #3133 Posted June 18, 2017 Can I just install the new loader without it effecting my install on my running system? Quote Link to comment Share on other sites More sharing options...
IceBoosteR Posted June 18, 2017 Share #3134 Posted June 18, 2017 (edited) Hi, just a simple question from my side: Is is possible to access disks via fibre channel? Got the Qlogic QLE2462 and a disk shelf, it would be awesome if there is support on the kernel for the same. If is is not, where can I request the support? Edited June 18, 2017 by IceBoosteR typo Quote Link to comment Share on other sites More sharing options...
jitesh_88 Posted June 19, 2017 Share #3135 Posted June 19, 2017 Hi Guys, just wondering how do i create an SHR with 6.1.2 i backed up my data and deleted my volumes and raid group to migrate to btrfs but i dont see an option to be able to create SHR. i have different size drives 1TB,2TB,4TB any advice? Quote Link to comment Share on other sites More sharing options...
jitesh_88 Posted June 19, 2017 Share #3136 Posted June 19, 2017 47 minutes ago, jitesh_88 said: Hi Guys, just wondering how do i create an SHR with 6.1.2 i backed up my data and deleted my volumes and raid group to migrate to btrfs but i dont see an option to be able to create SHR. i have different size drives 1TB,2TB,4TB any advice? i guess i answered my own question. so 3615xs does not support Disk Group. i tried porting to DS916+ since this is like a new install for me however i cant find my NAS in synology assistant. is it possible my NIC drivers are present in the image for DS3615xs and not in DS916+ ? Quote Link to comment Share on other sites More sharing options...
jitesh_88 Posted June 19, 2017 Share #3137 Posted June 19, 2017 Thanks to @koroziv there is a post how to fix this issue: SHR on dsm6: edit synoinfo.conf located in /etc.defaults/synoinfo. conf comment out / delete supportraidgroup="yes" then add support_syno_hybrid_raid ="yes" Quote Link to comment Share on other sites More sharing options...
mariad Posted June 19, 2017 Share #3138 Posted June 19, 2017 Got the update done without issues. 1 Quote Link to comment Share on other sites More sharing options...
SwDude Posted June 19, 2017 Share #3139 Posted June 19, 2017 On 6/16/2017 at 11:04 AM, SwDude said: Hey guys, After reading all these pages, I'm still a little confused about whether or not I should update. Configuration- Loader v1.02a, baremetal, Btrfs volume on 6.1-15047 Update 2. Can I safely update to 6.1.2-15132? Thanks! Updated over the weekend, worked without any issues! Quote Link to comment Share on other sites More sharing options...
Benoire Posted June 20, 2017 Share #3140 Posted June 20, 2017 On 2017-6-18 at 9:30 AM, Benoire said: I'm running DSM 6.1-15047 Update 2 on a ESXi 6.5 install. Am I able to simply install the new version b loader over my old boot image and then let DSM reboot and then allow it to update to the latest version without a clean install? I've got a large amount of data that I would rather not have to re-download using Hyperbackup... Is someone able to answer this directly? Can I use the latest loader from Jun, and then simply update to the latest version of DSM or does it require a completely clean install? If it requires a clean install, can O snapshot the VM, add a new virtual HDD and let the OS be mirrored, and then remove the proper drives, update boot loader and then boot from the virtual drive on the new version and then add the existing drives and repair the DSM partition for it all to work? Quote Link to comment Share on other sites More sharing options...
Haris2887 Posted June 20, 2017 Share #3141 Posted June 20, 2017 Hello All. I am having trouble ISCSI drives being recognised in ESXi 6.x. I am trying to do RMD mapping for 3 x 2TB Disks that I have as local Disks on an ESXI host . (I don't have a raid card so no pass-through vt-d option) Creating an RDM Mapping for Local Disk vmkfstools -r /vmfs/devices/disks/vml.0100000000202020202057442d574d43333030343931373636574443205744 /vmfs/volumes/datastore1/RDMRed3.vmdk Then to see what the created Vmdk looks like Nest I just add the VMDk to the esxi VM power On the Vm , all Good But disks do not show in DSM. long story short, I am not sure what else to do , this is a fresh clean install of the latest DMS using the latest loader. I suspect that SCSI disk are not supported and I must use SATA, can anyone confirm this form me please . Quote Link to comment Share on other sites More sharing options...
jjaing Posted June 20, 2017 Share #3142 Posted June 20, 2017 Anyone tried this latest v1.02b on hyper-v, I still can't find it in the Synology Assistance Quote Link to comment Share on other sites More sharing options...
carlchan Posted June 20, 2017 Share #3143 Posted June 20, 2017 Dear I am using v1.02b 3615xs, in esxi 5.5, I already amend the sn and mac, Before, it would not show the following error, and all video could view in ds video and ds photo. " System failed to convert video [/volume1/photo/.../2016-12-24 chung wedding/20161224 (9).MTS] to mpeg4 " " System failed to convert video [/volume1/photo/.../2016-12-24 chung wedding/20161224 (9).MTS] to mpeg4 " ... etc., After upgrade to 6.x.x, all video could not be covert, Is it due to sn/mac address problem? Thanks! : > Quote Link to comment Share on other sites More sharing options...
epicurean Posted June 20, 2017 Share #3144 Posted June 20, 2017 I did a fresh install on Esxi 6 with the 1.02a 3615 loader. All ok so far How do I update my loader to the newer 1.02b, in anticipation for the next update from Synology? Quote Link to comment Share on other sites More sharing options...
john_matrix Posted June 20, 2017 Share #3145 Posted June 20, 2017 You can flash your USB key to 1.02b the same way you had done with 1.02a Don't forget to change your serial and mac address in the grub.conf Quote Link to comment Share on other sites More sharing options...
hpk Posted June 20, 2017 Share #3146 Posted June 20, 2017 (edited) Thanks for the new 1.02b bootloader. Now, DS3617xs with DSM 6.1.2-15132 runs well on ESXi 6.0. Did not have any issues so far. However, I use it only as Backup and Streaming Server. Installed and used Packages: Hyper Backup Hyper Backup Vault Cloud Station ShareSync Logitech Media Server On the latency of the 5TB Harddisk I have some room of improvement, but I had bad latency with 1.02a and DS3615xs as well ... As there are several Windows and Unix VMs running on this ESXi, I can't use Pass-Thru mode for the Synology VM Edited June 20, 2017 by hpk Quote Link to comment Share on other sites More sharing options...
abced Posted June 20, 2017 Share #3147 Posted June 20, 2017 Anybody successfully running the DS916 loader? I only see people pisting about DS3615 and DS3617. Quote Link to comment Share on other sites More sharing options...
Haris2887 Posted June 20, 2017 Share #3148 Posted June 20, 2017 3 hours ago, john_matrix said: You can flash your USB key to 1.02b the same way you had done with 1.02a Don't forget to change your serial and mac address in the grub.conf Do I need to change the Serial number on my fresh install on ESXi ? Quote Link to comment Share on other sites More sharing options...
pigr8 Posted June 20, 2017 Share #3149 Posted June 20, 2017 i wanted to try 1.02b on my baremetal (hp gen8 with i3 3220t cpu), 3615xs loader tested and working, 3617xs loader tested and working, 916+ loader not working, hangs on boot: [ 0.192870] invalid opcode: 0000 [#1] SMP [ 0.194242] Modules linked in: [ 0.195217] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.10.102 #15047 [ 0.197217] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 07/16/2015 [ 0.199283] task: ffff880200d23510 ti: ffff880200d24000 task.ti: ffff880200d24000 [ 0.201473] RIP: 0010:[<ffffffff8148f33e>] [<ffffffff8148f33e>] sha_transform+0x2e/0x12e0 [ 0.203924] RSP: 0000:ffff880200d27d60 EFLAGS: 00010092 [ 0.205485] RAX: ffffffff819c2a80 RBX: 0000000010325476 RCX: 00000000e8a4602c [ 0.207646] RDX: ffff880200d27db0 RSI: ffffffff819c2a80 RDI: ffff880200d27d98 [ 0.209730] RBP: 00000000c3d2e1f0 R08: 00000000efcdab89 R09: 0000000010325476 [ 0.211814] R10: 0000000067452301 R11: 0000000098badcfe R12: 00000000f33d5697 [ 0.213886] R13: ffff880200d27e66 R14: 0000000000000286 R15: 0000000000000004 [ 0.215986] FS: 0000000000000000(0000) GS:ffff88020ba40000(0000) knlGS:0000000000000000 [ 0.218407] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 0.220116] CR2: 0000000000000000 CR3: 000000000180d000 CR4: 00000000001407e0 [ 0.222202] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 0.224281] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 0.226362] Stack: [ 0.227048] 0000000000000010 ffffffff81842cc0 ffffffff81842ce4 ffff880200d27e66 [ 0.229395] 0000000000000286 0000000000000004 ffffffff812fa652 efcdab8967452301 [ 0.231747] 1032547698badcfe 00000000c3d2e1f0 ffffffff81842e10 0000000000000246 [ 0.234128] Call Trace: [ 0.234853] [<ffffffff812fa652>] ? extract_buf+0x62/0x140 [ 0.236492] [<ffffffff810579a5>] ? __wake_up+0x35/0x50 [ 0.238091] [<ffffffff812fa464>] ? account+0x104/0x290 [ 0.239617] [<ffffffff812fab9c>] ? extract_entropy+0x5c/0x170 [ 0.241334] [<ffffffff8115f047>] ? proc_register+0x67/0x140 [ 0.242982] [<ffffffff813e89fb>] ? neigh_hash_alloc+0x7b/0xb0 [ 0.244657] [<ffffffff813e8ab6>] ? neigh_table_init+0x86/0x2b [ 0.325107] [<ffffffff818a13af>] ? arp_init+0xc/0x47 [ 0.348100] [<ffffffff818a16c0>] ? inet_init+0x18e/0x27a [ 0.349743] [<ffffffff818a1532>] ? ipv4_offload_init+0x63/0x63 [ 0.351496] [<ffffffff810003aa>] ? do_one_initcall+0xea/0x140 [ 0.353222] [<ffffffff81876dc8>] ? kernel_init_freeable+0x13a/0x1bb [ 0.355053] [<ffffffff814909f0>] ? rest_init+0x70/0x70 [ 0.356589] [<ffffffff814909f5>] ? kernel_init+0x5/0x180 [ 0.358232] [<ffffffff814a2548>] ? ret_from_fork+0x58/0x90 [ 0.359868] [<ffffffff814909f0>] ? rest_init+0x70/0x70 [ 0.361422] Code: 8b 5f 08 44 8b 17 41 56 44 8b 47 04 44 89 d1 41 55 c1 c1 05 41 54 45 8d 23 55 8b 6f 10 41 81 c4 99 79 82 5a 53 8b 5f 0c 41 89 d9 <0f> 38 f0 06 45 31 d9 89 02 45 21 c1 41 c1 c8 02 41 31 d9 41 01 [ 0.369569] RIP [<ffffffff8148f33e>] sha_transform+0x2e/0x12e0 [ 0.371349] RSP <ffff880200d27d60> [ 20.207634] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu1 Quote Link to comment Share on other sites More sharing options...
pigr8 Posted June 20, 2017 Share #3150 Posted June 20, 2017 17 minutes ago, abced said: Anybody successfully running the DS916 loader? I only see people pisting about DS3615 and DS3617. i tried, i was interessed to 916 too but doesnt work for me Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.