Jump to content
XPEnology Community

DSM 6.1.x Loader


jun

Recommended Posts

for me installation is failing still on bare metal hardware.

Used the loader V1.01 and changed the pid/vid in grub.cfg according to instruction

 

Systems boots and i can enter the webinterface, running the installattion fails with error 13 invalid or incorrupt pat file.

Tried synology_bromolow_3615xs.pat & DSM_DS3615xs_8451.pat (from synology site) without luck.

 

Any additional suggestions ?

 

A) Tried 3 different USB sticks

B) Tried to change pid/vid in console (hit c and enter values

C) Tried same but then directly on USB stick by editing grub.cfg

 

Until now it keeps failing and i am unable to install DSM on my bare metal machine

Link to comment
Share on other sites

Does the onboard NIC also work or did you add a NIC?

I used the onboard NIC.

 

But: I have not yet tried to proceed with the actual installation of DSM, mainly because I first had to take care of my SAS/SATA controller (cross flashing M1015 to 9211-8i). So I don't know yet whether the installation will actually succeed or not. So far I just saw that the system obtained an IP address from my DHCP server and showed up in the Synology Assistant.

Link to comment
Share on other sites

I used the onboard NIC.

 

But: I have not yet tried to proceed with the actual installation of DSM, mainly because I first had to take care of my SAS/SATA controller (cross flashing M1015 to 9211-8i). So I don't know yet whether the installation will actually succeed or not. So far I just saw that the system obtained an IP address from my DHCP server and showed up in the Synology Assistant.

 

 

If you got an IP it works, thanks for your message!

Link to comment
Share on other sites

It is running perfectly on my system standalone.

 

Upgrade from 5 to the latest version on 6 all want okay.

Unfortunately I lose one drive, my mistake because I used diskpart -clean command and that make my EX4 empty :oops:

I did that because on the first part on that disk was my boot diks :wink: but I could not changed the PID / VID on that one so I was hoping it cleans only the first part, but is was all :roll:

Link to comment
Share on other sites

If you got an IP it works, thanks for your message!

I have now successfully installed DSM 6.0.2 Update 6 on my System (ASRock J3455M "Apollo Lake" Mainboard, LSI 9211-8i SAS/SATA HBA, bare metal).

 

I had changed VID/PID, MAC and SN in my grub.cfg as described and then installed DSM to two 80GB disks attached to the LSI.

When creating a RAID1 volume I got an error, but i'd rather blame that on the 12 y/o drives I had kicking around my junk drawer for years than on DSM :wink:

Everything else went smoothly and looks very promising so far.

Link to comment
Share on other sites

[spoiler=Version: 6.0.2-8451.7 (2016/12/22)]Important Note

1. The update is expected to be available for all regions within the next few days, although the time of release in each region may vary slightly.

2. This update will restart your Synology NAS.

 

Fixed Issues

1. Enhanced the stability of RAID 5.

http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-7/

 

Regards.-

Link to comment
Share on other sites

Hello there,

 

first of all thanks devs for the great work..!!

 

I have an HP N54L with 4x4TB WD Reds for some time in DSM 6, one of them had bad sectors and i got a replace with a new one (!) 5TB WD Red.

 

Xpenology reads the new drive correctly but doesn't allow me to perform Secure Erase (It says my drive doesn't support it). Is it a because of hardware limitation or software related?

 

Thanks in advance!!

 

Screen%20Shot%202016-12-24%20at%2010.36.52_zpssfcoxdgb.png

Link to comment
Share on other sites

[spoiler=Version: 6.0.2-8451.7 (2016/12/22)]Important Note

1. The update is expected to be available for all regions within the next few days, although the time of release in each region may vary slightly.

2. This update will restart your Synology NAS.

 

Fixed Issues

1. Enhanced the stability of RAID 5.

http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-7/

 

Regards.-

 

did you manage to install the update?

Link to comment
Share on other sites

[spoiler=Version: 6.0.2-8451.7 (2016/12/22)]Important Note

1. The update is expected to be available for all regions within the next few days, although the time of release in each region may vary slightly.

2. This update will restart your Synology NAS.

 

Fixed Issues

1. Enhanced the stability of RAID 5.

http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-7/

 

Regards.-

 

did you manage to install the update?

 

I did yesterday on my test instance of DSM6. Update was applied without a problem. Survived the reboot.. So it seems fine for now.

Will wait a couple of more days before I apply it to my two "productive" boxes as well.

Link to comment
Share on other sites

update to 7 fails too.

also tried update 6 first, exactly the same results.

 

so, remains update 5 version. waiting for new progress...

 

BTW: AMD cpu, N54L, ...

 

Have you tried the upgrade fromthe control panel on the disk station ? Just did the 7'th update and everything went fine and straight forward...

Link to comment
Share on other sites

It is running perfectly on my system standalone.

 

Upgrade from 5 to the latest version on 6 all want okay.

Unfortunately I lose one drive, my mistake because I used diskpart -clean command and that make my EX4 empty :oops:

I did that because on the first part on that disk was my boot diks :wink: but I could not changed the PID / VID on that one so I was hoping it cleans only the first part, but is was all :roll:

 

Hi,

 

all esx drives are partitionned the same, so, it should be possible to recover the detroyed partition table.

the question is, is it a dos pt ou a gpt ?

if dos pt, a simple dd from 1 drive to the other should suffice :

dd if=/dev/sdX of=/dev/sdY bs=512 count=1

sdX is the source disk et sdY the target disk.

for gpt, it's possible with a recent fdisk :

fdisk --version => fdisk from util-linux 2.26.2

sfdisk -d /dev/sdX | sfdisk /dev/sdY

well, this solution should work for dos pt too...

 

Regards

Link to comment
Share on other sites

update to 7 fails too.

also tried update 6 first, exactly the same results.

 

so, remains update 5 version. waiting for new progress...

 

BTW: AMD cpu, N54L, ...

 

 

Did you upgraded from DSM 5->DSM6? Or Clean installed DSM 6?

 

I'm asking because i also have an HP N54L and successfully installed Update 7 with no problem at all.

Link to comment
Share on other sites

I am confused. Do you mean that we still need to use a physical USB to boot from a VM environment to get rid of the 50MB hdd? In 5.2 age, I remembered I don't see this boot drive under DSM, yet I was booting from the vmdk directly.

Could it be the rmmod / mod_del doesn't work in this loader?

 

I am okay to leave this hdd in the system but it is annoying that it generate smart error once every few seconds.

 

You don't need to use USB drive for bootloading into xpenology under esxi. That is just the way I wanted it to work, so to a) save space on my SSD even though it is only few hundred MBs, b) making use of the already there internal usb port, in fact I even use the MircoSD slot for running esxi, c) in relation to previous point, booting from USB drive means I could easily backup and replace bootloader in case anything went wrong.

 

The entire concept of my setup is to isolate Xpenology as much as possible from the other VMs on the same Gen8 physical machine, so to up the reliability and increase revival chance. To do so I also passthrough the entire B120i (ran in AHCI mode) for Xpenology use only; that way the drives connected to B120i works just as a proper Synology drive without the layer of vmdk or use of RDM. Touch wood, if my Gen8 decide to not work, I can still unplug my drives and use Linux to read all data directly. This is abit off topic but I hope you get the idea.

 

Now I know there are ways to overcome the 50MB issue, especially when bootloader running from vmdk on SSD and such. Mine is just a way that I worked out and find suitable for my requirement. I think there are still things that I could fine tune, but my xpenology is running smooth and stable that I would rather stick with it for now. A side note that I happened to try upgrading my esxi 6 to 6.5 yesterday and for some reason it didn't work out well. I could not downgrade from 6.5 to 6 either, so I did a reinstallation of esxi 6. From this exercise, I have been able to add my xpenology back to esxi easily and everything runs as if I never upgraded; that proofs the reliability that I am after.

 

about how to upgrade from ESXi 6.0 to 6.5...

 

1st solution

 

try the HPE Custom Image for VMware ESXi 6.5 Install CD or the HPE Custom Image for VMware ESXi 6.5 Offline Bundle

https://my.vmware.com/fr/group/vmware/d ... ductId=614

for historical reason, I use the solution below since I begin with this.

well, in the begining the of year, there was no up to date HPE images, so, I prefer to build an up to date image instead of using a one year old image...

 

2nd solution

 

build yourself an up to date image

powercli

https://my.vmware.com/group/vmware/deta ... ductId=614

vmware tools

https://my.vmware.com/fr/group/vmware/d ... ductId=615

esxui (html5) & vmware remove console (vmrc) vibs

https://labs.vmware.com/flings/esxi-emb ... ost-client

esxi customizer

https://www.v-front.de/p/esxi-customizer-ps.html

HPE drivers

http://vibsdepot.hpe.com/hpe/nov2016/

http://vibsdepot.hpe.com/hpe/oct2016/

well, for faster download, I get the offline bundles, then extract the vibs from them

http://vibsdepot.hpe.com/hpe/nov2016/esxi-650-bundles/

http://vibsdepot.hpe.com/hpe/nov2016/es ... cedrivers/ (hpdsa, hpvsa & nhpsa)

http://vibsdepot.hpe.com/hpe/oct2016/es ... cedrivers/ (hpsa & nx1_tg3)

 

not used, for reference only...

additionnal drivers

https://vibsdepot.v-front.de/wiki/index ... i_packages

patches (none for 6.5 yet)

https://my.vmware.com/group/vmware/patc ... 241#search

 

built images, upload not yet terminated, 2-3 hours yet...

for offline upgrade

http://cyrillelefevre.free.fr/vmware/ES ... omized.iso

for online upgrade

http://cyrillelefevre.free.fr/vmware/ES ... omized.zip

 

for online installation, go in maintance mode, then :

well, don't remember if I do install or update... I suppose install :???:

esxcli software profile install -d $PWD/ESXi-6.5.0-4564106-standard-customized.zip -p ESXi-6.5.0-4564106-standard-customized

also, while the vmware tools are in the image, they don't get installed ! so, I installed them manually :

esxcli software vib install -v file://$PWD/VMware_locker_tools-light_6.5.0-0.0.4564106.vib

don't remember if -n tools-light is needed or not ?

 

to build the images yourself

 

contents of vibs subdirectory

 

amshelper-650.10.6.0-24.4240417.vib

conrep-6.0.0.01-02.00.1.2494585.vib

esxui-signed-4762574.vib

hpbootcfg-6.0.0.02-02.00.6.2494585.vib

hpe-cru_650.6.5.8.24-1.4240417.vib

hpe-esxi-fc-enablement-650.2.6.10-4240417.vib

hpe-ilo_650.10.0.1-24.4240417.vib

hpe-nmi-600.2.4.16-2494575.vib

hpe-smx-limited-650.03.11.00.13-4240417.vib

hpe-smx-provider-650.03.11.00.17-4240417.vib

hponcfg-6.0.0.4.4-2.4.2494585.vib

hptestevent-6.0.0.01-01.00.5.2494585.vib

net-tg3_3.137l.v60.1-1OEM.600.0.0.2494585.vib

nhpsa-2.0.10-1OEM.650.0.0.4240417.x86_64.vib

scsi-hpdsa-5.5.0.54-1OEM.550.0.0.1331820.vib

scsi-hpsa_6.0.0.120-1OEM.600.0.0.2494585.vib

scsi-hpvsa-5.5.0.102-1OEM.550.0.0.1331820.x86_64.vib

ssacli-2.60.18.0-6.0.0.vib

VMware_locker_tools-light_6.5.0-0.0.4564106.vib

VMware-Remote-Console-9.0.0-Linux.vib

VMware-Remote-Console-9.0.0-Windows.vib

 

under powercli

 

PS D:\vmw> .\ESXi-Customizer-PS-v2.5.ps1 -v65 -pkgDir vibs

This is ESXi-Customizer-PS Version 2.5.0 (visit https://ESXi-Customizer-PS.v-front.de for more information!)
(Call with -help for instructions)

Logging to D:\Users\xxx\AppData\Local\Temp\ESXi-Customizer-PS-8096.log ...

Running with PowerShell version 3.0 and VMware PowerCLI 6.5 Release 1 build 4624819

Connecting the VMware ESXi Online depot ... [OK]

Getting Imageprofiles, please wait ... [OK]

Using Imageprofile ESXi-6.5.0-4564106-standard ...
(dated 10/27/2016 05:43:44, AcceptanceLevel: PartnerSupported,
The general availability release of VMware ESXi Server 6.5.0 brings whole new levels of virtualization performance to da
tacenters and enterprises.)

Loading Offline bundles and VIB files from vibs ...
  Loading D:\vmw\vibs\amshelper-650.10.6.0-24.4240417.vib ... [OK]
     Add VIB amshelper 650.10.6.0-24.4240417 [OK, added]
  Loading D:\vmw\vibs\conrep-6.0.0.01-02.00.1.2494585.vib ... [OK]
     Add VIB conrep 6.0.0.01-02.00.1.2494585 [OK, added]
  Loading D:\vmw\vibs\esxui-signed-4762574.vib ... [OK]
     Add VIB esx-ui 1.13.0-4762574 [OK, replaced 1.8.0-4516221]
  Loading D:\vmw\vibs\hpbootcfg-6.0.0.02-02.00.6.2494585.vib ... [OK]
     Add VIB hpbootcfg 6.0.0.02-02.00.6.2494585 [OK, added]
  Loading D:\vmw\vibs\hpe-cru_650.6.5.8.24-1.4240417.vib ... [OK]
     Add VIB hpe-cru 650.6.5.8.24-1.4240417 [OK, added]
  Loading D:\vmw\vibs\hpe-esxi-fc-enablement-650.2.6.10-4240417.vib ... [OK]
     Add VIB hpe-esxi-fc-enablement 650.2.6.10-4240417 [OK, added]
  Loading D:\vmw\vibs\hpe-ilo_650.10.0.1-24.4240417.vib ... [OK]
     Add VIB hpe-ilo 650.10.0.1-24.4240417 [OK, added]
  Loading D:\vmw\vibs\hpe-nmi-600.2.4.16-2494575.vib ... [OK]
     Add VIB hpe-nmi 600.2.4.16-2494575 [OK, added]
  Loading D:\vmw\vibs\hpe-smx-limited-650.03.11.00.13-4240417.vib ... [OK]
     Add VIB hpe-smx-limited 650.03.11.00.13-4240417 [OK, added]
  Loading D:\vmw\vibs\hpe-smx-provider-650.03.11.00.17-4240417.vib ... [OK]
     Add VIB hpe-smx-provider 650.03.11.00.17-4240417 [OK, added]
  Loading D:\vmw\vibs\hponcfg-6.0.0.4.4-2.4.2494585.vib ... [OK]
     Add VIB hponcfg 6.0.0.4.4-2.4.2494585 [OK, added]
  Loading D:\vmw\vibs\hptestevent-6.0.0.01-01.00.5.2494585.vib ... [OK]
     Add VIB hptestevent 6.0.0.01-01.00.5.2494585 [OK, added]
  Loading D:\vmw\vibs\net-tg3_3.137l.v60.1-1OEM.600.0.0.2494585.vib ... [OK]
     Add VIB net-tg3 3.137l.v60.1-1OEM.600.0.0.2494585 [OK, replaced 3.131d.v60.4-2vmw.650.0.0.4564106]
  Loading D:\vmw\vibs\nhpsa-2.0.10-1OEM.650.0.0.4240417.x86_64.vib ... [OK]
     Add VIB nhpsa 2.0.10-1OEM.650.0.0.4240417 [OK, replaced 2.0.6-3vmw.650.0.0.4564106]
  Loading D:\vmw\vibs\scsi-hpdsa-5.5.0.54-1OEM.550.0.0.1331820.vib ... [OK]
     Add VIB scsi-hpdsa 5.5.0.54-1OEM.550.0.0.1331820 [OK, added]
  Loading D:\vmw\vibs\scsi-hpsa_6.0.0.120-1OEM.600.0.0.2494585.vib ... [OK]
     Add VIB scsi-hpsa 6.0.0.120-1OEM.600.0.0.2494585 [OK, replaced 6.0.0.84-1vmw.650.0.0.4564106]
  Loading D:\vmw\vibs\scsi-hpvsa-5.5.0.102-1OEM.550.0.0.1331820.x86_64.vib ... [OK]
     Add VIB scsi-hpvsa 5.5.0.102-1OEM.550.0.0.1331820 [OK, added]
  Loading D:\vmw\vibs\ssacli-2.60.18.0-6.0.0.vib ... [OK]
     Add VIB ssacli 2.60.18.0-6.0.0.2494585 [OK, added]
  Loading D:\vmw\vibs\VMware-Remote-Console-9.0.0-Linux.vib ... [OK]
     Add VIB vmrc-linux 9.0.0-0.2 [OK, added]
  Loading D:\vmw\vibs\VMware-Remote-Console-9.0.0-Windows.vib ... [OK]
     Add VIB vmrc-win 9.0.0-0.2 [OK, added]
  Loading D:\vmw\vibs\VMware_locker_tools-light_6.5.0-0.0.4564106.vib ... [OK]
     Add VIB tools-light 6.5.0-0.0.4564106 [iGNORED, already added]

Exporting the Imageprofile to 'D:\vmw\ESXi-6.5.0-4564106-standard-customized.iso'. Please be patient ...

All done.

D:\vmw> .\ESXi-Customizer-PS-v2.5.ps1 -v65 -pkgDir vibs -ozip

This is ESXi-Customizer-PS Version 2.5.0 (visit https://ESXi-Customizer-PS.v-front.de for more information!)
(Call with -help for instructions)

Logging to D:\Users\xxx\AppData\Local\Temp\ESXi-Customizer-PS-8096.log ...

Running with PowerShell version 3.0 and VMware PowerCLI 6.5 Release 1 build 4624819

Connecting the VMware ESXi Online depot ... [OK]

Getting Imageprofiles, please wait ... [OK]

Using Imageprofile ESXi-6.5.0-4564106-standard ...
(dated 10/27/2016 05:43:44, AcceptanceLevel: PartnerSupported,
The general availability release of VMware ESXi Server 6.5.0 brings whole new levels of virtualization performance to da
tacenters and enterprises.)

Loading Offline bundles and VIB files from vibs ...
  Loading D:\vmw\vibs\amshelper-650.10.6.0-24.4240417.vib ... [OK]
     Add VIB amshelper 650.10.6.0-24.4240417 [OK, added]
  Loading D:\vmw\vibs\conrep-6.0.0.01-02.00.1.2494585.vib ... [OK]
     Add VIB conrep 6.0.0.01-02.00.1.2494585 [OK, added]
  Loading D:\vmw\vibs\esxui-signed-4762574.vib ... [OK]
     Add VIB esx-ui 1.13.0-4762574 [OK, replaced 1.8.0-4516221]
  Loading D:\vmw\vibs\hpbootcfg-6.0.0.02-02.00.6.2494585.vib ... [OK]
     Add VIB hpbootcfg 6.0.0.02-02.00.6.2494585 [OK, added]
  Loading D:\vmw\vibs\hpe-cru_650.6.5.8.24-1.4240417.vib ... [OK]
     Add VIB hpe-cru 650.6.5.8.24-1.4240417 [OK, added]
  Loading D:\vmw\vibs\hpe-esxi-fc-enablement-650.2.6.10-4240417.vib ... [OK]
     Add VIB hpe-esxi-fc-enablement 650.2.6.10-4240417 [OK, added]
  Loading D:\vmw\vibs\hpe-ilo_650.10.0.1-24.4240417.vib ... [OK]
     Add VIB hpe-ilo 650.10.0.1-24.4240417 [OK, added]
  Loading D:\vmw\vibs\hpe-nmi-600.2.4.16-2494575.vib ... [OK]
     Add VIB hpe-nmi 600.2.4.16-2494575 [OK, added]
  Loading D:\vmw\vibs\hpe-smx-limited-650.03.11.00.13-4240417.vib ... [OK]
     Add VIB hpe-smx-limited 650.03.11.00.13-4240417 [OK, added]
  Loading D:\vmw\vibs\hpe-smx-provider-650.03.11.00.17-4240417.vib ... [OK]
     Add VIB hpe-smx-provider 650.03.11.00.17-4240417 [OK, added]
  Loading D:\vmw\vibs\hponcfg-6.0.0.4.4-2.4.2494585.vib ... [OK]
     Add VIB hponcfg 6.0.0.4.4-2.4.2494585 [OK, added]
  Loading D:\vmw\vibs\hptestevent-6.0.0.01-01.00.5.2494585.vib ... [OK]
     Add VIB hptestevent 6.0.0.01-01.00.5.2494585 [OK, added]
  Loading D:\vmw\vibs\net-tg3_3.137l.v60.1-1OEM.600.0.0.2494585.vib ... [OK]
     Add VIB net-tg3 3.137l.v60.1-1OEM.600.0.0.2494585 [OK, replaced 3.131d.v60.4-2vmw.650.0.0.4564106]
  Loading D:\vmw\vibs\nhpsa-2.0.10-1OEM.650.0.0.4240417.x86_64.vib ... [OK]
     Add VIB nhpsa 2.0.10-1OEM.650.0.0.4240417 [OK, replaced 2.0.6-3vmw.650.0.0.4564106]
  Loading D:\vmw\vibs\scsi-hpdsa-5.5.0.54-1OEM.550.0.0.1331820.vib ... [OK]
     Add VIB scsi-hpdsa 5.5.0.54-1OEM.550.0.0.1331820 [OK, added]
  Loading D:\vmw\vibs\scsi-hpsa_6.0.0.120-1OEM.600.0.0.2494585.vib ... [OK]
     Add VIB scsi-hpsa 6.0.0.120-1OEM.600.0.0.2494585 [OK, replaced 6.0.0.84-1vmw.650.0.0.4564106]
  Loading D:\vmw\vibs\scsi-hpvsa-5.5.0.102-1OEM.550.0.0.1331820.x86_64.vib ... [OK]
     Add VIB scsi-hpvsa 5.5.0.102-1OEM.550.0.0.1331820 [OK, added]
  Loading D:\vmw\vibs\ssacli-2.60.18.0-6.0.0.vib ... [OK]
     Add VIB ssacli 2.60.18.0-6.0.0.2494585 [OK, added]
  Loading D:\vmw\vibs\VMware-Remote-Console-9.0.0-Linux.vib ... [OK]
     Add VIB vmrc-linux 9.0.0-0.2 [OK, added]
  Loading D:\vmw\vibs\VMware-Remote-Console-9.0.0-Windows.vib ... [OK]
     Add VIB vmrc-win 9.0.0-0.2 [OK, added]
  Loading D:\vmw\vibs\VMware_locker_tools-light_6.5.0-0.0.4564106.vib ... [OK]
     Add VIB tools-light 6.5.0-0.0.4564106 [iGNORED, already added]

Exporting the Imageprofile to 'D:\vmw\ESXi-6.5.0-4564106-standard-customized.zip'. Please be patient ...

All done.

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