Jump to content
XPEnology Community

DSM 6.2 Loader


jun

Recommended Posts

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 by Polanskiman
Added code tag
  • Like 2
Link to comment
Share on other sites

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

 

Link to comment
Share on other sites

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 by nvrsk
Link to comment
Share on other sites

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 by typer77
typo
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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).

 

1623625168_ScreenShot2018-08-02at11_37_59AM.png.571d7824cb78291e7c6610c2329c95d7.png

 

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

 

379019840_ScreenShot2018-08-02at2_05_13PM.png.912aacabcb1eeee3d69d89d2c2ed672f.png

 

1468681164_ScreenShot2018-08-02at1_55_49PM.thumb.png.a14adc09e3d1b17139e44511cde12466.png

 

 

 

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.

Link to comment
Share on other sites

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.

 

Link to comment
Share on other sites

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 by wwweagle
Link to comment
Share on other sites

 

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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 🤨

Link to comment
Share on other sites

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

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

×
×
  • Create New...