Running 6.2.3 on ESXi? Synoboot is BROKEN, fix available


Recommended Posts

But my mainboard is special,so the 2nd and 3rd SATA controller has only 4ports and 3ports(the 4th was bad) to DSM DISK 1-7.And the loader SSD is the minisata on mainboard at (0:1).

I have 8 disks NAS,so I have to use the (0:0) SATA port to DSM DISK 8.

 

I have did this:

 

Keep my loader disk to position 0:1(it's the miniSATA port on my mainboard,so I can't move it.)

SataPortMap=243

DiskIdxMap=070003(I'm using DS3617xs)

now,the script is useful.and the loader is on DISK 9.

 

In this situation,can I suppress the loader SSD?

Or I have to use U-disk to make a loader?

 

 

 

Edited by JoyLife
Link to post
Share on other sites

If you insist on the boot disk being #2 port on a controller with other drives, I do not see a solution to the problem.  Best practice dictates that the boot loader has its own dedicated controller (which is what all the tutorials indicate), and is why you have your issue.

 

I'm still not clear on exactly why you are using the boot configuration that you are.

 

Are you running virtualized?  If so, just add a virtual SATA controller and shift the other three controllers over one slot.

If you are running baremetal, what is stopping you from just using a USB flash drive as recommended?  That would solve your problem.

Link to post
Share on other sites
  • 3 weeks later...

Hi guys. I have successfully achieved the update on a test server but I always fail in the second one I have. I'm puzzled at this point as why it happens.

Where could I get a log with more details? its a 3615xs on esxi 6.7u3.

Thanks in advance.

Screen Shot 2021-01-17 at 14.26.36.png

Jan-17-2021 14-27-57.gif

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

$ ls /dev/synoboot*

$ cat /usr/local/etc/rc.d/FixSynoboot.sh

Thanks for your reply Flyride. 

ls shows there are no folders and the cat shows the file just fine.

(Just in case, yes I rebooted (within the DSM and but doing a shutdown and hitting play in the esxi itself).

Screen Shot 2021-01-17 at 17.21.59.png

Screen Shot 2021-01-17 at 17.22.19.png

Link to post
Share on other sites

Since your disks do not start with sda, and you have no isolated disk device, I believe you have modified DiskIdxMap and inadvertently made the loader device inaccessible to DSM, so therefore it cannot remap/create synoboot.  Post the relevant lines from grub.cfg for more advice.

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

Since your disks do not start with sda, and you have no isolated disk device, I believe you have modified DiskIdxMap and inadvertently made the loader device inaccessible to DSM, so therefore it cannot remap/create synoboot.  Post the relevant lines from grub.cfg for more advice.

 

set extra_initrd="extra.lzma"
set info="info.txt"

set vid=0x058f
set pid=0x6387
set sn=_________
set mac1=001B2177AE6D
set rootdev=/dev/md0
set netif_num=1
set extra_args_3615=''
#set extra_args_3615='earlycon=uart8250,io,0x3f8,115200n8 earlyprintk loglevel=15'

set common_args_3615='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_port_thaw=1'

set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0'

set default='0'
set timeout='1'
set fallback='1'

 

Screen Shot 2021-01-18 at 07.12.14.png

Edited by anibalin
Link to post
Share on other sites
1 hour ago, anibalin said:

Screen Shot 2021-01-18 at 14.41.34.png

 

Here is your issue.  You have your boot loader set to slot 2 when the tutorials indicate that it must be SATA (0:0).  Because your SataPortMap=1 that means the first controller (SATA 0) is only mapped for one drive, so this device is not assigned a /dev/sd slot.  Therefore, the loader and script cannot find the device to remap for the synoboot devices.  Change this to SATA (0:0) and you should find your upgrade works properly.

  • Like 1
Link to post
Share on other sites
On 1/18/2021 at 4:32 PM, flyride said:

 

Here is your issue.  You have your boot loader set to slot 2 when the tutorials indicate that it must be SATA (0:0).  Because your SataPortMap=1 that means the first controller (SATA 0) is only mapped for one drive, so this device is not assigned a /dev/sd slot.  Therefore, the loader and script cannot find the device to remap for the synoboot devices.  Change this to SATA (0:0) and you should find your upgrade works properly.

Worked like a charm. Thanks for your patience and kindness mate.

  • Like 1
Link to post
Share on other sites

my grub.cfg looks like this but i keep getting corrupted file when trying to update or reinstall. any help will be appreciated. 

#set extra_args_3617='earlycon=uart8250,io,0x3f8,115200n8 earlyprintk loglevel=15'
set extra_args_3617=''

set common_args_3617='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3617xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_port_thaw=1'

set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0'

 

Link to post
Share on other sites

I was a dummy and managed to kill my XPE install on ESXi with 6.2.3 Update 3.  Could anyone educate me how to roll it back or update bootloader image to bring the machine back? Serial log below:

 

Quote

Hunk #1 succeeded at 184 (offset 13 lines).

patching file etc/synoinfo.conf

Hunk #1 FAILED at 261.

1 out of 1 hunk FAILED -- saving rejects to file etc/synoinfo.conf.rej

patching file linuxrc.syno

Hunk #1 FAILED at 39.

Hunk #2 succeeded at 131 (offset 32 lines).

Hunk #3 succeeded at 694 (offset 179 lines).

1 out of 3 hunks FAILED -- saving rejects to file linuxrc.syno.rej

patching file usr/sbin/init.post

cat: can't open '/etc/synoinfo_override.conf': No such file or directory

START /linuxrc.syno

Insert Marvell 1475 SATA controller driver

Insert basic USB modules...

:: Loading module usb-common ... [  OK  ]

:: Loading module usbcore ... [  OK  ]

:: Loading module ehci-hcd ... [  OK  ]

:: Loading module ehci-pci ... [  OK  ]

:: Loading module ohci-hcd ... [  OK  ]

:: Loading module uhci-hcd ... [  OK  ]

:: Loading module xhci-hcd ... [  OK  ]

:: Loading module usb-storage ... [  OK  ]

:: Loading module BusLogic ... [  OK  ]

:: Loading module vmw_pvscsi ... [  OK  ]

:: Loading module megaraid_mm ... [  OK  ]

:: Loading module megaraid_mbox ... [  OK  ]

:: Loading module megaraid ... [  OK  ]

:: Loading module scsi_transport_spi ... [  OK  ]

:: Loading module mptbase ... [  OK  ]

:: Loading module mptscsih ... [  OK  ]

:: Loading module mptspi ... [  OK  ]

:: Loading module mptsas ... [  OK  ]

:: Loading module mptctl ... [  OK  ]

:: Loading module megaraid_sas ... [  OK  ]

:: Loading module mpt2sas[    2.113257] BUG: unable to handle kernel paging request at ffffffffa020764c

[    2.114024] IP: [<ffffffff81341123>] sd_probe+0x303/0xab0

[    2.114347] PGD 1810067 PUD 1811063 PMD 231251067 PTE 0

[    2.114442] Oops: 0002 [#1] SMP

[    2.114455] Modules linked in: mpt2sas(O+) megaraid_sas(F) mptctl(F) mptsas(F) mptspi(F) mptscsih(F) mptbase(F) scsi_transport_spi(F) megaraid(F) megaraid_mbox(F) megaraid_mm(F) vmw_pvscsi(F) BusLogic(F) usb_storage xhci_hcd uhci_hcd ohci_hcd(F) ehci_pci(F) ehci_hcd(F) usbcore usb_common mv14xx(O) cepsw(OF)

[    2.114467] CPU: 0 PID: 4009 Comm: insmod Tainted: GF          O 3.10.105 #25426

[    2.114480] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018

[    2.114493] task: ffff880234c8c800 ti: ffff880231054000 task.ti: ffff880231054000

[    2.114506] RIP: 0010:[<ffffffff81341123>]  [<ffffffff81341123>] sd_probe+0x303/0xab0

[    2.114518] RSP: 0018:ffff8802310577e0  EFLAGS: 00010202

[    2.114531] RAX: ffffffffa0202600 RBX: ffff8802311b1970 RCX: 0000000000000001

[    2.114544] RDX: ffffffff8132eca0 RSI: ffffffff8177d13b RDI: ffff880232f56000

[    2.114557] RBP: ffff8802312f2800 R08: ffffffff810889e0 R09: 0000000000000000

[    2.114569] R10: ffff880232d38ac0 R11: 0000000045fa1bf3 R12: 00000000fffffff4

[    2.114582] R13: 0000000000000007 R14: 0000000000000000 R15: 0000000000000007

[    2.114595] FS:  00007fcea045f700(0000) GS:ffff88023fc00000(0000) knlGS:0000000000000000

[    2.114608] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033

[    2.114620] CR2: ffffffffa020764c CR3: 000000023103c000 CR4: 00000000001607f0

[    2.114633] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000

[    2.114646] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400

[    2.114659] Stack:

[    2.114671]  ffff880232db4000 ffff8802312f9898 0000000000000000 ffff880200000000

[    2.114684]  ffff8802311b1970 ffff8802311b1970 ffffffff8184bdc8 0000000000000006

[    2.114697]  ffff880230bfdc28 ffff8802310579f8 ffffffffa0000e97 ffff8802311b1970

[    2.114710] Call Trace:

[    2.114728]  [<ffffffffa0000e97>] ? SYNOSATADiskLedCtrl+0xd87/0x1cd5 [cepsw]

[    2.114746]  [<ffffffff81307e8a>] ? really_probe+0x5a/0x220

[    2.114764]  [<ffffffff81308050>] ? really_probe+0x220/0x220

[    2.114781]  [<ffffffff81306223>] ? bus_for_each_drv+0x53/0x90

[    2.114799]  [<ffffffff81307e18>] ? device_attach+0x88/0xa0

[    2.114816]  [<ffffffff81307388>] ? bus_probe_device+0x88/0xb0

[    2.114835]  [<ffffffff8130578f>] ? device_add+0x5cf/0x6a0

[    2.114853]  [<ffffffff813267ca>] ? scsi_sysfs_add_sdev+0x6a/0x2c0

[    2.114872]  [<ffffffff81324323>] ? scsi_probe_and_add_lun+0xee3/0xf70

[    2.114890]  [<ffffffff813230b6>] ? scsi_alloc_target+0x276/0x310

[    2.114909]  [<ffffffff813246dd>] ? __scsi_scan_target+0x8d/0x5d0

[    2.114927]  [<ffffffff81305a8f>] ? device_create+0x2f/0x40

[    2.114944]  [<ffffffff81324cf3>] ? scsi_scan_target+0xd3/0xe0

[    2.114960]  [<ffffffff8133113f>] ? sas_rphy_add+0x10f/0x170

[    2.114984]  [<ffffffffa01e80e1>] ? mpt2sas_transport_port_add+0x321/0xc40 [mpt2sas]

[    2.115005]  [<ffffffffa01d9d15>] ? _scsih_scan_finished+0x1f5/0x2b0 [mpt2sas]

[    2.115022]  [<ffffffff81324fc7>] ? do_scsi_scan_host+0x67/0x80

[    2.115042]  [<ffffffffa01d8d87>] ? _scsih_probe+0x4b7/0x8c0 [mpt2sas]

[    2.115060]  [<ffffffff8129d250>] ? pci_device_probe+0x60/0xa0

[    2.115076]  [<ffffffff81307e8a>] ? really_probe+0x5a/0x220

[    2.115093]  [<ffffffff81308111>] ? __driver_attach+0x81/0x90

[    2.115111]  [<ffffffff81308090>] ? __device_attach+0x40/0x40

[    2.115127]  [<ffffffff81306183>] ? bus_for_each_dev+0x53/0x90

[    2.115144]  [<ffffffff81307628>] ? bus_add_driver+0x158/0x250

[    2.115161]  [<ffffffffa0208000>] ? 0xffffffffa0207fff

[    2.115178]  [<ffffffff81308718>] ? driver_register+0x68/0x150

[    2.115195]  [<ffffffffa0208000>] ? 0xffffffffa0207fff

[    2.115215]  [<ffffffffa02081f0>] ? _scsih_init+0x1f0/0x21c [mpt2sas]

[    2.115233]  [<ffffffff810003aa>] ? do_one_initcall+0xea/0x140

[    2.115250]  [<ffffffff8108be04>] ? load_module+0x1a04/0x2120

[    2.115267]  [<ffffffff81088fc0>] ? store_uevent+0x40/0x40

[    2.115283]  [<ffffffff8108c5b1>] ? SYSC_init_module+0x91/0xc0

[    2.115303]  [<ffffffff814c5dc4>] ? system_call_fastpath+0x22/0x27

[    2.115316] Code: 01 00 00 8b 8b 14 ff ff ff 8b 93 10 ff ff ff 8b b3 18 ff ff ff ff d0 41 89 c5 41 89 c7 48 8b 83 90 fe ff ff 48 8b 80 10 05 00 00 <44> 89 a8 4c 50 00 00 e9 21 fe ff ff 90 83 3d 19 af 62 00 01 41

[    2.115329] RIP  [<ffffffff81341123>] sd_probe+0x303/0xab0

[    2.115342]  RSP <ffff8802310577e0>

[    2.115354] CR2: ffffffffa020764c

[    2.115367] ---[ end trace 6badd467ebda8a0a ]---

... [FAILED]

:: Loading module mpt3sas[    2.119980] mpt3sas version 22.00.02.00 loaded

[    3.106657] usb 1-1: new full-speed USB device number 2 using xhci_hcd

[    3.118890] Got empty serial number. Generate serial number from product.

 

Edited by bateau
Link to post
Share on other sites
  • 2 weeks later...
  • 1 month later...

I am running 6.7.0 Update 3 (Build 15820472)

 

I have downloaded this version: https://mega.nz/file/adVDmaLS#2SN_FA-kkOb_yP0lfQJ84DFywMBW15I3Wk3i3ZTfEew  

 

and I still can't get it to show up in http://find.synology.com/#

I even changed the MAC ID:

1. turn off the vm from the web based Esxi interface. 
2.  Edit the settings of the vm and go to network adapters. 
3. Change the adapter type to E1000e, and set the mac address to manual, and change it to 00:11:32:2C:A7:85
4. Boot up the Vm guest and go to find.synology.com

 

What am I doing wrong?

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.