flyride

Running 6.2.3 on ESXi? Synoboot is BROKEN, fix available

Recommended Posts

Posted (edited)

i'm really sorry flyride for my bad english, maybe this is the issue, so let me explain.....

your script works really better, the my ONLY question is:  after each reboot, everytime that i reboot i see this in the log UI:

 

dsm.JPG

 

on the red circle in english say "External sata disk 1 not removed corretly".

and i saw this logs EVERYTIME that i reboot the DSM, but ALL WORKS CORRECTLY, all folders, volumes, etc etc, but only this log is my problem.

it's normal that i see this in the log on web UI?

Edited by reziel84

Share this post


Link to post
Share on other sites
Posted (edited)

The entries in the logfile below are normal with 6.2.3 on ESXi and when FixSynoboot.sh is installed.

 

image.thumb.png.4a1ac91546318460d47bdfced5718996.png

 

Web UI notifications such as the one below are not expected. Code in FixSynoboot.sh is intended to suppress these messages.

 

image.thumb.png.546b176eb2dded334e61e09c074da063.png

 

 

I asked you to run FixSynoboot.sh manually from the command line.  That would have generated log messages. Again, that's normal given the configuration.

DID THE COMMAND LINE RUN CAUSE A WEB UI NOTIFICATION??  YES OR NO?

 

 

Edited by flyride

Share this post


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

The entries in the logfile below are normal with 6.2.3 on ESXi and when FixSynoboot.sh is installed.

 

image.thumb.png.4a1ac91546318460d47bdfced5718996.png

 

Web UI notifications such as the one below are not expected. Code in FixSynoboot.sh is intended to suppress these messages.

 

image.thumb.png.546b176eb2dded334e61e09c074da063.png

 

 

I asked you to run FixSynoboot.sh manually from the command line.  That would have generated log messages. Again, that's normal given the configuration.

DID THE COMMAND LINE RUN CAUSE A WEB UI NOTIFICATION??  YES OR NO?

 

 

 

NO! if i run the script manually in another folder after a reboot no WEB UI notified regarding sata appear.

 

i explain a step by step what i do:

1) change script folder

2) reboot DSM

3) launch script from shell by root user

 

all works correctly and no notification on webui (except for those in the first picture).

now my situation is this:

 

 

dsm.JPG

 

 

 

but at this point if i  move the script under rc.d and restart DSM, the situation is this:

dsm2.thumb.JPG.0f763cbd4a788dc85a75b1774047785d.JPG

 

 

all works correctly, only the mesage in the UI is really strange

Edited by reziel84

Share this post


Link to post
Share on other sites

The issue is a matter of timing in the first place. Something in your system is causing the eSATA initialization to happen later than other systems, or perhaps there needs to be more time between unmounting and device deactivation. The moment where /etc/local/rc.d executes seems to work for most, but on your system it must be too soon.

 

I'd try modifying the script to add pauses in the following locations and see if it helps:

 

Add a line containing sleep 5 immediately before echo "remove" >/sys/class/block/$basename/uevent

 

Add a line containing sleep 15 between start) and FixSynoboot

  • Thanks 1

Share this post


Link to post
Share on other sites
On 6/13/2020 at 4:20 PM, flyride said:

The issue is a matter of timing in the first place. Something in your system is causing the eSATA initialization to happen later than other systems, or perhaps there needs to be more time between unmounting and device deactivation. The moment where /etc/local/rc.d executes seems to work for most, but on your system it must be too soon.

 

I'd try modifying the script to add pauses in the following locations and see if it helps:

 

Add a line containing sleep 5 immediately before echo "remove" >/sys/class/block/$basename/uevent

 

Add a line containing sleep 15 between start) and FixSynobootu

 

unfortunately this 2 changes not solved my problem, log still remain in the webui. thanks a lot for your support flyride and thanks for all time that you spend to help me.

the changes are liste in the picture below:

 

dsm.JPG

Share this post


Link to post
Share on other sites
Posted (edited)

Hi,

 

Currently the fixsynoboot.sh file can't be downloaded. Can you reupload the file please?

 

Edit: I can be downloaded after loggin in

Edited by RobbieT

Share this post


Link to post
Share on other sites

Thanks  flyride for the instructions. I uploaded the file, changed permissions, installed the 6.2.3 update, restarted automatically after the update, everything smooth.

Share this post


Link to post
Share on other sites

Thank you so much for the fix, just installed as instructed, and now I successfully upgrade the software to 6.2.3 25426 update 2, previous, it was always promoting the software was broken.

Share this post


Link to post
Share on other sites
Posted (edited)

Thank you for the script!

I had the issue that my config was changed back to the defaults, which caused a degraded array (8 of 10 disks only visible). However, I have used that script before figuring out that the config was not up to date, and I guess your script did part of the job ;)

Now its working and I can start to repair my array. Thanks for your work!

 

Edited by IceBoosteR

Share this post


Link to post
Share on other sites

Hey Guys,

 

my last XPEnology was with DSM 5.x. Now I made some tests on my ESXi 6.7 and was happy how stable it's working. I uses Juns Loader 1.04b with 918+. I add synobook.vmdk as Sata 0:0 und all other drives as RAW using SCSI Controller.

 

/dev/syno* are all fine. Just one issue: DSM Shows 50 MB disk under Disks. I tried this script, but nothing changed, like expected because it's fresh install. Any idea what I can do, to hide this one drive?

 

Thanks for this great community!

Bildschirmfoto 2020-07-30 um 13.29.12.png

Bildschirmfoto 2020-07-30 um 14.34.33.png

Bildschirmfoto 2020-07-30 um 14.34.16.png

Bildschirmfoto 2020-07-30 um 13.29.29.png

Share this post


Link to post
Share on other sites

Two probable reasons - 1) failed to pick the VMWare option at the grub boot menu, or 2) your grub.cfg needs to include DiskIdxMap=0C00 which should also fix the slot placement of your live hard disks.

Share this post


Link to post
Share on other sites
6 hours ago, flyride said:

Two probable reasons - 1) failed to pick the VMWare option at the grub boot menu, or 2) your grub.cfg needs to include DiskIdxMap=0C00 which should also fix the slot placement of your live hard disks.

@flyride thanks for fast answer. 1) is impossible, uncommented all baremetal options. ;-) 2) I tried and it looks different, but now its 50 MB Drive at the end (please find attached my grub)

 

@StanG I found here in the forum as solution for my mounting problem, it's possible to switch it. But I went back now.

 

 

Bildschirmfoto 2020-07-30 um 23.37.07.png

Bildschirmfoto 2020-07-30 um 23.37.39.png

 

grub.cfg

Edited by etests
Old grup replaced

Share this post


Link to post
Share on other sites

Oh, you are using DS918+ with original MaxDisk=16.  So DiskIdxMap should be 1000, that will make the 50MB disappear. You have SataPortMap=4 which probably should be "1"

Edited by flyride

Share this post


Link to post
Share on other sites

It takes some minutes, ecause it starts now in repair mode. Have to fix or install new. Thanks for your extreme fast answers. :)

 

Edit: @flyride you made my day - DiskIdxMap=1000 solved it. Next fight get Hibernation working. Maybe I have to ask in new thread.

Edited by etests

Share this post


Link to post
Share on other sites

Hello!

 

First, thanks for this fix!

I have a question:

Is it normal that the fix works well when I restart the computer whereas if I only reboot DSM I get the message in notification?

 

Thanks!

Share this post


Link to post
Share on other sites

The UI pop-up message is a cosmetic problem not a functional one.  But the current version of the script is intended to suppress the pop-up error message. Reading back through the thread, there was an individual that for some reason received UI notification, and to my knowledge never resolved it. I was unable to duplicate this reliably in test. 

 

Can you be very specific as to what you are doing when you do and don't receive the message?  Are you using ESXi or baremetal?  Do you mean restarting ESXi?

Share this post


Link to post
Share on other sites

Hello flyride,

 

I'am using ESXI 6.7 in an HP ProLiant MicroServer G8 (customised with a Xeon and 16 go of ram) with a VM with 2 CPU and 4 go of RAM.

So sorry for the explanation let me rephrase:

if I click to "Restart" in the DSM WebUI I get the error message.

If I click to "Shutdown" in the DSM WebUI and then restarting the VM through ESXI I did NOT get the error message.

 

Thanks

Edited by MaTTrs

Share this post


Link to post
Share on other sites

Unfortunately I still can't duplicate this behavior.  The issue is probably a resource timing issue in the first place, so I suspect it's a difference between the boot up time of the systems.

 

Your system is somewhat slower than the system I am using to test.  You might want to try the modifications suggested in this post here.  If you do and it works for you please report back.

https://xpenology.com/forum/topic/28183-running-623-on-esxi-synoboot-is-broken-fix-available/?do=findComment&comment=150336

 

Again, even if you receive the pop-up messages, your synoboot should be working correctly and your system ought to be fully functional.

 

Share this post


Link to post
Share on other sites

So, I change the script and it was worst, error notification at each restart or reboot...

I put back your script, add cpu and RAM to my VM and now it works in any case...

But yeah I know it is only cosmetic :) 

 

Thanks

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.