synofreak Posted August 2, 2018 Share #26 Posted August 2, 2018 Hi @Jun THX for great Update! HP Microserver N40L no Problems at the Moment!!! cu-ya Quote Link to comment Share on other sites More sharing options...
JBark Posted August 2, 2018 Share #27 Posted August 2, 2018 (edited) HP MicroServer Gen8 with E3-1256L V2 boots fine with new loader and upgraded OK from 6.1 to 6.2, but getting some odd behaviour when I log into DSM. If I don't mess with DSM, it runs fine, including the VM I have configured under VMM. The second I log into DSM, it shuts down every service and I lose connection about 30 seconds later. It's not a hard crash, as I can watch the logs and see it's shutting down/pausing every service that's running. Pretty odd, I'm guessing something didn't upgrade nicely from 6.1 -> 6.2, I doubt it's loader related. From /var/log/messages: 2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgtool.cpp:2284 chmod failed for /var/packages (Operation not permitted) 2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgtool.cpp:2293 chmod failed for /usr/local/etc/rc.d (Operation not permitted) 2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-phpMyAdmin (err=-1) [0x0900 servicecfg_root_object_set.c:43] 2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-PHP5.6 (err=-1) [0x0900 servicecfg_root_object_set.c:43] 2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-MariaDB10 (err=-1) [0x0900 servicecfg_root_object_set.c:43] 2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-Apache2.2 (err=-1) [0x0900 servicecfg_root_object_set.c:43] 2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-FileStation (err=-1) [0x0900 servicecfg_root_object_set.c:43] 2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-TextEditor (err=-1) [0x0900 servicecfg_root_object_set.c:43] 2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-tvheadend (err=-1) [0x0900 servicecfg_root_object_set.c:43] 2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-SynoFinder (err=-1) [0x0900 servicecfg_root_object_set.c:43] Tons of entries like that, followed by.... 2018-08-02T12:21:55+08:00 HPGEN8 ore.Desktop.Initdata_1_get: service_pause_all.c:173 Pause service [synosnmpcd] by reason of [unidentified] failed. 2018-08-02T12:21:55+08:00 HPGEN8 ore.Desktop.Initdata_1_get: service_pause_all.c:173 Pause service [synogpoclient] by reason of [unidentified] failed. 2018-08-02T12:21:55+08:00 HPGEN8 ore.Desktop.Initdata_1_get: service_pause_all.c:173 Pause service [crond] by reason of [unidentified] failed. 2018-08-02T12:21:55+08:00 HPGEN8 ore.Desktop.Initdata_1_get: service_pause_all.c:173 Pause service [iscsitrg] by reason of [unidentified] failed. 2018-08-02T12:21:55+08:00 HPGEN8 ore.Desktop.Initdata_1_get: service_pause_all.c:173 Pause service [atalk] by reason of [unidentified] failed. Continues like that until I lose the connection. If I check messages after the next boot, it's shutdown everything like it's planning to reboot or something, but never actually finishes. Edited October 22, 2018 by Polanskiman Added code tag 2 Quote Link to comment Share on other sites More sharing options...
marcos_59143 Posted August 2, 2018 Share #28 Posted August 2, 2018 (edited) test on 3615xs DSM6.2 ASRock T48EM1 it's work update ok legacy bios Edited August 2, 2018 by marcos_59143 Quote Link to comment Share on other sites More sharing options...
Steven3743 Posted August 2, 2018 Share #29 Posted August 2, 2018 Thank you! Works fine by Bare Metal Migration DS3617xs 6.1.7-15284u2 to DS3617xs 6.2-23739u2 CPU: Intel E3-1245v2 MB: Gigabyte GA-B75M-D3H Ethernet: Mellanox MNPA19-XTR (Only works after installation done, have to use the On Board realtek ethernet to upgrade system) legacy bios Quote Link to comment Share on other sites More sharing options...
nvrsk Posted August 2, 2018 Share #30 Posted August 2, 2018 (edited) Gigabyte GA-P43T-ES3G / Pentium Dual-Core CPU E530 @ 2.20GHz tried clean install of 3615xs on wiped empty HDD. first boot goes fine - machine shows up in assistant ready to install. after I passed the PAT file to it, assign a constant IP and name to the server - it starts to install, reboots, and looses the network. the COM-console shows that it continues installation after reboot but with no luck. I suppose there may be smth wrong with "apply network settings" installation step so that the final "writing configuration file" step never finishes. one more thing about it: I give a name to the server, and it changes it's name in assistant for the moment, but if I force the "search" button - it returns without IP address and default "DiskStation" name in the list before reboot. it also displays "DiskStation login" prompt in COM-console instead of "<myservername> login" after reboot. - have just tried clean install of previous version (15284) - assistant and login prompt reacts just the same although system works fine, so it is senseless. the 3617xs version gives just the same result. the captured bootlog is attached. 62-3615-clean.txt Edited August 2, 2018 by nvrsk Quote Link to comment Share on other sites More sharing options...
JiaHsien Posted August 2, 2018 Share #31 Posted August 2, 2018 MB:n70e-dr CPU:1037u It's not working .... Quote Link to comment Share on other sites More sharing options...
Flotho Posted August 2, 2018 Share #32 Posted August 2, 2018 (edited) ESXI, DS3617xs and LSI 9211 IT Mode not working for me! Cant detect any hard drive... Edited August 2, 2018 by Flotho Quote Link to comment Share on other sites More sharing options...
simoareva Posted August 2, 2018 Share #33 Posted August 2, 2018 Ok I managed it. On ESXi 6.7 i setted up legacy BIOS on the VM and it was enough to put the disk on SATA instead that on SCSI (the rest of the disks remained the same). Then I migrated from VM Version 14 from 6.1.2 to 6.2 U2 with no problems. (3615) Quote Link to comment Share on other sites More sharing options...
zhenfu Posted August 2, 2018 Share #34 Posted August 2, 2018 Can this version be used on hyper-v? Quote Link to comment Share on other sites More sharing options...
snakefox666 Posted August 2, 2018 Share #35 Posted August 2, 2018 6 hours ago, synofreak said: Hi @Jun THX for great Update! HP Microserver N40L no Problems at the Moment!!! cu-ya Did you update from previous version or it's a fresh install ? I'm curious because I have an N40L too Thanks mate ! Quote Link to comment Share on other sites More sharing options...
typer77 Posted August 2, 2018 Share #36 Posted August 2, 2018 (edited) I am a bit confused. In this upgrade on ESXi, I am using the ISO file as CDROM loader converted from the img file in the v1.03b folder. How about synoboot.vmdk? Where can I find .vmdk file for this upgrade? Thanks in advance! Edited August 2, 2018 by typer77 typo Quote Link to comment Share on other sites More sharing options...
sliders Posted August 2, 2018 Share #37 Posted August 2, 2018 hello ,Thank you very much jun Jun's Mod 1.03b - DS3617 Installation type: HP Z210 Workstation Intel Xeon E3-1280 we find no networks with SynologyAssistant 😞😟 Quote Link to comment Share on other sites More sharing options...
typer77 Posted August 2, 2018 Share #38 Posted August 2, 2018 HP Proliant ML10V2 Xeon E3-1281 v3 EXSi HPE 5.5. using DS3617XS Loader stopped after showing "Screen will stop updating shortly, please open http://find.synology.com to continue". Synology assistant can't find the new NAS on network. Quote Link to comment Share on other sites More sharing options...
M3kk Posted August 2, 2018 Share #39 Posted August 2, 2018 ML10 v2 E3-1270 v3 + Mellanox ConnectX + LSI 9211-8i IT mode (Perc H200), bare metal.All working fine.Clean install - Ok.Upgrade from 6.1 to 6.2 - Ok.Sent from my ONEPLUS 6 using Tapatalk Quote Link to comment Share on other sites More sharing options...
nvrsk Posted August 2, 2018 Share #40 Posted August 2, 2018 18 minutes ago, typer77 said: Loader stopped after showing "Screen will stop updating shortly ... this is the normal behavior of all loaders' direct output to monitor. more boot-info may be available via connecting another computer to COM-port of the server. after the wiring with a Win-machine (as I do) - Putty can be used, selecting the "serial" connection type, choosing the right COM-port and setting the speed to 115200. Quote Link to comment Share on other sites More sharing options...
flyride Posted August 2, 2018 Share #41 Posted August 2, 2018 3 hours ago, typer77 said: I am a bit confused. In this upgrade on ESXi, I am using the ISO file as CDROM loader converted from the img file in the v1.03b folder. How about synoboot.vmdk? Where can I find .vmdk file for this upgrade? Thanks in advance! Load a vmdk file in a text editor and you will have your answer. Quote Link to comment Share on other sites More sharing options...
autohintbot Posted August 2, 2018 Share #42 Posted August 2, 2018 I did a DSM 6.2 update on one of my real ESXi VM setups today, after testing some VM-only disks overnight. ESXi 6.5.0 Update 2 (Build 8294253) PowerEdge R320 Intel(R) Xeon(R) CPU E5-2450L 0 @ 1.80GHz The VM has a LSI SAS9200-8e passed through, connected to a SA120 enclosure with 10/12 disks populated. It didn't go great. DSM came back up with only 4 disks showing (marked disks 9-12). After trying some things, I was able to get the other disks to appear by increasing the *portcfg settings. Two weird things: - The 50MB SATA boot disk is showing through to DSM, where it didn't before - DSM is holding open disks 1-8, which is why only 4 disks made it through with the 12-disk limit The only difference between this and my DSM 6.1 config is the firmware going from EFI -> BIOS. I guess with a BIOS boot the SATA controller appears, and DSM thinks it has an 8-disk capacity, and with EFI it doesn't? I've had a bad history with any XPEnology setup that require portcfg changes to synoinfo.conf, since inevitably those values reset during an update and your volumes get severed. Although I did notice this over serial in the very early boot stages, so maybe there's a new way to inject values from the bootloader now? Quote patching file linuxrc.syno patching file usr/sbin/init.post cat: can't open '/etc/synoinfo_override.conf': No such file or directory Fortunately, I can repair the volume affected here (and it's not a very important install overall). I'll hold off until EFI is working before I do more updates. Quote Link to comment Share on other sites More sharing options...
6688 Posted August 2, 2018 Share #43 Posted August 2, 2018 (edited) DSM6.2 Baremetal Motherboard: N70E-DR V3 CPU: Intel 1037U Ethernet: 2 Intel 82574L Gigabit Memory: 4 GB Edited August 3, 2018 by Dfds Translated from Chinese English Quote Link to comment Share on other sites More sharing options...
CrazyCreator Posted August 2, 2018 Share #44 Posted August 2, 2018 16 hours ago, hoppler said: HP MicroServer Gen8 with E3 1260L works fine. Did a migration from DSM 6.1 DS3615 to 6.2 DS3617 Is there a specific reason why you switched from DS3615 to 6.2 DS3617? I'm currently on the DS3615 and I'm a bit worried about my data when I switch to the DS3617. Quote Link to comment Share on other sites More sharing options...
wwweagle Posted August 3, 2018 Share #45 Posted August 3, 2018 (edited) hello, test it in my pc, it don't work. U: E3 1220V2 MB:GA-6uasv1 rev2.0 the MB bios setting boot page don't show legacy boot opinion so i boot with UEFI mode. my pc seems to boot ok but Synology assistant can't find the new NAS on network PS. the network chip is Broadcom BCM5718 Edited August 3, 2018 by wwweagle Quote Link to comment Share on other sites More sharing options...
ideasman69 Posted August 3, 2018 Share #46 Posted August 3, 2018 4 hours ago, autohintbot said: After trying some things, I was able to get the other disks to appear by increasing the *portcfg settings. Two weird things: - The 50MB SATA boot disk is showing through to DSM, where it didn't before - DSM is holding open disks 1-8, which is why only 4 disks made it through with the 12-disk limit Now that you're running the new boot loader and BIOS mode - have you made sure to select ESX mode from Juns boot menu? I had the same thing when upgrading my ESX install. The first option was selected by default (bare metal) which left me without seeing all my drives but i could see the 50MB virtual boot device. After making sure ESX was selected the 50MB disappeared and all my drives were detected again. Quote Link to comment Share on other sites More sharing options...
ideasman69 Posted August 3, 2018 Share #47 Posted August 3, 2018 1 hour ago, wwweagle said: hello, test it in my pc, it don't work. U: E3 1220V2 MB:GA-6uasv1 rev2.0 the MB bios setting boot page don't show legacy boot opinion so i boot with UEFI mode. my pc seems to boot ok but Synology assistant can't find the new NAS on network PS. the network chip is Broadcom BCM5718 I think gigabyte call it "CSM" so check your BIOS and enable that - should allow you to boot in BIOS (non-EFI) mode. Quote Link to comment Share on other sites More sharing options...
autohintbot Posted August 3, 2018 Share #48 Posted August 3, 2018 7 minutes ago, ideasman69 said: Now that you're running the new boot loader and BIOS mode - have you made sure to select ESX mode from Juns boot menu? I had the same thing when upgrading my ESX install. The first option was selected by default (bare metal) which left me without seeing all my drives but i could see the 50MB virtual boot device. After making sure ESX was selected the 50MB disappeared and all my drives were detected again. Yeah, this is using the ESXi/VMWare option (I tried the other options out of curiosity but nothing ever came up after initial message on VGA/serial). If I can fix this now that'd be great, but I'm in no huge rush, so hopefully Jun has time to fix the EFI boot. There's note that it's on his radar in the OP. Are you using a passthrough hardware HBA or virtual disks? Quote Link to comment Share on other sites More sharing options...
ideasman69 Posted August 3, 2018 Share #49 Posted August 3, 2018 1 minute ago, autohintbot said: hopefully Jun has time to fix the EFI boot i've never used EFI so didn't know it was a problem nice that Jun knows about it though. Just now, autohintbot said: Are you using a passthrough hardware HBA or virtual disks? i'm passing through a controller. it detected my first disk as disk 31 when the baremetal option was selected. when switching back to ESX mode it showed my first disk as disk 7. so not sure whats happening there 🤨 Quote Link to comment Share on other sites More sharing options...
oxn1k0xo Posted August 3, 2018 Share #50 Posted August 3, 2018 hello, thank you very much Jun for your work. I have updated my asrock 5005 and it turns out that it has no option in bios to boot into legacy. Now it does not work At this point what should I do? Apart from recovering my data (15tb) can the configuration be recovered ?. thank you very much 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.