Jump to content
XPEnology Community

Jun's Alpha Loader for DSM 6.1


CrazyCreator

Recommended Posts

I have tried with several USB sticks but the same thing happens. The way that I change SN and MAC is that I just change those values in grub.cfg each time I have this issue.

 

Do you have any suggestions??

 

Are you simply editing the grub file on your USB or are you editing the image file then re-writing it to the USB stick?

 

I had some issues making direct edits to the grub file. It may be changing it in a manner that alters the file with characters or formatting you cannot see.

 

 

My advice:

1. Redo the USB from scratch with a fresh image mounted using OSFMount and then edited using Notepad ++ as advised in the tutorial.

2. Download the spreadsheet (excel) for serial and MAC and create them (if you download it and make it editable it will redo the serial each time for you).

3. If you do not need "Quick Connect" just use your actual NIC MAC rather than the one from the spreadsheet.

4. Burn the image to the USB with Win32Diskimager or similar.

 

Also, have you changed any bios settings? Mine was being troublesome until I set it to EFI and cleaned up some of the options. I'm using a Supermicro server board though so my issues may not reflect yours.

 

If you are having issues I advise go back to basics and ensure you are not overlooking any simple aspects.

Link to comment
Share on other sites

I have this installed and am still testing aspects of the packages and general functions.

 

So far the DSM seems operable. Disks are discovered and Volume functions etc are all ok. Network and account behaviour seems normal.

 

I am running bare metal on a Xeon-D platform using the DS3617xs installer. No apparent issues with the time stamp so Jun has got it right with the MCU emulation I believe.

 

As a quick test I am getting 550MB/s down from a 4 Disk RAID 5 Array (5400RPM drives) to an nVM.e drive using SMB3 over 10GBase-T (SAMBA share -> windows 10 folder) just copying using windows.

Link to comment
Share on other sites

How does the time bomb issue show up? Last night I was getting "Sorry, the page you are looking for is not found."

 

I thought this was from a power button script I had installed but perhaps it is the time bomb? basically I could not log into DSM or access shares in windows (only via mapped drives).

Link to comment
Share on other sites

How does the time bomb issue show up? Last night I was getting "Sorry, the page you are looking for is not found."

 

I thought this was from a power button script I had installed but perhaps it is the time bomb? basically I could not log into DSM or access shares in windows (only via mapped drives).

Write the version of the bootloader (1.02a or 1.02a2?) and operating time.

Link to comment
Share on other sites

I had installed it with 1.02a2 and DS3617 on ESXi 6.5 and it works fine. It runs longer than 48h without any issue. Right know I switch it of because it was only a test.

I use the pure syno img without any changes of serial or MAC.

Link to comment
Share on other sites

hi,

 

just to give some feedback

got baremetal install working on Asrock C2550D4I (all 12 SATA ports working, just short testing) with jun 1.02a and 3615, the 3617 was not installing at all (found with syno assistant but failed while uploading the image - missing network support in 3617 for the intel onboard nic? atm no clue whats going on when uploading a pat image when booting from usb, did the vid/pid and mac thing right for shure)

plan to migrate to 6.1 later after complete backup, raid array is ext4 and i want it to be btrfs so i will have to make a clean new install with all disks empty and restore files after install

Edited by Guest
Link to comment
Share on other sites

I had installed it with 1.02a2 and DS3617 on ESXi 6.5 and it works fine. It runs longer than 48h without any issue. Right know I switch it of because it was only a test.

I use the pure syno img without any changes of serial or MAC.

Hi since you have the same environment setup like me (esxi 6.5) and tried with the latest loader too.

May I ask you if you are able to migrate from 6.0.2 to 6.1?

I tried with all 1.02 loaders now and after migration the VM is not visible anymore on the network.

What I did is the following:

- Installed xpenology 6.0.2 fresh on test environment, gave it the synoboot.img by adding the vmdk drive (which essentially is a link to the image file) and one additional drive all on scsi

- edit grub file in image to have the mac1 address correct, nothing else

Then I shut the vm down. Replaced the vmdk and image file with 6.1 loader 1.02a2. Edited grub file to match same mac1.

Turned the VM back on. Got to the migration screen.

Did migrate from ds3615 to ds3617 with keeping the data option.

All went through without error.

Then the assistant reboots and no xpenology anymore on the network.

Synology assistant tool also does not find it anymore.

 

I wonder if anybody made a successful migration on esxi, yet...

 

Gesendet von meinem ONE A2003 mit Tapatalk

Link to comment
Share on other sites

I had installed it with 1.02a2 and DS3617 on ESXi 6.5 and it works fine. It runs longer than 48h without any issue. Right know I switch it of because it was only a test.

I use the pure syno img without any changes of serial or MAC.

Hi since you have the same environment setup like me (esxi 6.5) and tried with the latest loader too.

May I ask you if you are able to migrate from 6.0.2 to 6.1?

I tried with all 1.02 loaders now and after migration the VM is not visible anymore on the network.

What I did is the following:

- Installed xpenology 6.0.2 fresh on test environment, gave it the synoboot.img by adding the vmdk drive (which essentially is a link to the image file) and one additional drive all on scsi

- edit grub file in image to have the mac1 address correct, nothing else

Then I shut the vm down. Replaced the vmdk and image file with 6.1 loader 1.02a2. Edited grub file to match same mac1.

Turned the VM back on. Got to the migration screen.

Did migrate from ds3615 to ds3617 with keeping the data option.

All went through without error.

Then the assistant reboots and no xpenology anymore on the network.

Synology assistant tool also does not find it anymore.

 

I wonder if anybody made a successful migration on esxi, yet...

 

Gesendet von meinem ONE A2003 mit Tapatalk

Link to comment
Share on other sites

I had installed it with 1.02a2 and DS3617 on ESXi 6.5 and it works fine. It runs longer than 48h without any issue. Right know I switch it of because it was only a test.

I use the pure syno img without any changes of serial or MAC.

 

 

How did you install 1.02a2 DS3617 in ESXi? Did you write the image to an USB drive, and then boot your VM from the USB? or did you add the img as a disk in the VM? I had trouble getting it to install on my ESXi 6.5. It kept getting the File Corrupt (13) error during installation.

Link to comment
Share on other sites

I had installed it with 1.02a2 and DS3617 on ESXi 6.5 and it works fine. It runs longer than 48h without any issue. Right know I switch it of because it was only a test.

I use the pure syno img without any changes of serial or MAC.

 

 

How did you install 1.02a2 DS3617 in ESXi? Did you write the image to an USB drive, and then boot your VM from the USB? or did you add the img as a disk in the VM? I had trouble getting it to install on my ESXi 6.5. It kept getting the File Corrupt (13) error during installation.

Do you mean a real usb drive? That is not easily (and consistently) done in esxi. You would have to pass through the usb device to the vm to always have the same device present. Using the virtual USB device in esxi is not permanent. You would have to map the device to the vm on every boot manually.

I personally don't do the bare metal way on esxi.

Adding the drive is easier - or you could add a 5 bug pci usb controller card and pass it through to the vm.

 

Gesendet von meinem ONE A2003 mit Tapatalk

Link to comment
Share on other sites

Hi,

 

I am after someone to test/verify the operation of "Synonet" under the latest DSM version - specifically the Wake on Lan function.

 

I am on bare metal (DS3617xs) and attempting to use Synonet to wake a PC.

 

I have tried it through task manager and via SSH directly (with root privilege) and neither work. I can bring up the synonet command info/help

 

I am using this format:

 

/usr/syno/sbin/synonet –wake XX:XX:XX:XX:XX:XX eth0

 

Under task manage the log states no activity when I manually run the task.

 

I found some extra info here suggesting Synology managed to break Synonet in the later updates to v6.0:

https://forum.synology.com/enu/viewtopic.php?f=90&t=116493&sid=3e22f42a963198ae3eff778d4850bc55&start=15

 

 

My production Synology unit (a DS1813+) running a WoL package wakes the PC so I know the PC end is working. I use ether-wake -i eth0 XX:XX:XX:XX:XX:XX to get that working.

Notably, I had to install a package for that to function (I'm on 5.2 for that unit I believe) and have not touched it or upgraded DSM since it's running stable

Link to comment
Share on other sites

Hi there

 

I also tried to upgrade 6.0.2 to 6.1 on ESXi without sucess.

 

As far as I know, it is impossible right now.

 

-brauner

 

I had installed it with 1.02a2 and DS3617 on ESXi 6.5 and it works fine. It runs longer than 48h without any issue. Right know I switch it of because it was only a test.

I use the pure syno img without any changes of serial or MAC.

Hi since you have the same environment setup like me (esxi 6.5) and tried with the latest loader too.

May I ask you if you are able to migrate from 6.0.2 to 6.1?

I tried with all 1.02 loaders now and after migration the VM is not visible anymore on the network.

What I did is the following:

- Installed xpenology 6.0.2 fresh on test environment, gave it the synoboot.img by adding the vmdk drive (which essentially is a link to the image file) and one additional drive all on scsi

- edit grub file in image to have the mac1 address correct, nothing else

Then I shut the vm down. Replaced the vmdk and image file with 6.1 loader 1.02a2. Edited grub file to match same mac1.

Turned the VM back on. Got to the migration screen.

Did migrate from ds3615 to ds3617 with keeping the data option.

All went through without error.

Then the assistant reboots and no xpenology anymore on the network.

Synology assistant tool also does not find it anymore.

 

I wonder if anybody made a successful migration on esxi, yet...

 

Gesendet von meinem ONE A2003 mit Tapatalk

Link to comment
Share on other sites

I have tried with several USB sticks but the same thing happens. The way that I change SN and MAC is that I just change those values in grub.cfg each time I have this issue.

 

Do you have any suggestions??

 

Are you simply editing the grub file on your USB or are you editing the image file then re-writing it to the USB stick?

 

I had some issues making direct edits to the grub file. It may be changing it in a manner that alters the file with characters or formatting you cannot see.

 

 

My advice:

1. Redo the USB from scratch with a fresh image mounted using OSFMount and then edited using Notepad ++ as advised in the tutorial.

2. Download the spreadsheet (excel) for serial and MAC and create them (if you download it and make it editable it will redo the serial each time for you).

3. If you do not need "Quick Connect" just use your actual NIC MAC rather than the one from the spreadsheet.

4. Burn the image to the USB with Win32Diskimager or similar.

 

Also, have you changed any bios settings? Mine was being troublesome until I set it to EFI and cleaned up some of the options. I'm using a Supermicro server board though so my issues may not reflect yours.

 

If you are having issues I advise go back to basics and ensure you are not overlooking any simple aspects.

 

I am just simply editing grub file with notepad++ and save it on USB. I think that i have fix the problem by adding IP adress to fixed IP on my router so now my server is upp and runing for about 4 days. Please can you share link to spreadsheet (excel) for serial and MAC.

 

Regards

Igor

Link to comment
Share on other sites

On GA-N3150N-D3V v1.02a2 3617. ds916p wanted, but in network it wasn't found.

Time bomb hasn't worked. Though earlier twice on 1.02a worked approximately after work of 12 hours.

2563978

It not about us:

Tick-Tick-Boom-Time-Bomb.gif

 

 

Hello,

You can check if you have a file: /dev/dri/card0

Execute the command: lsmod

Link to comment
Share on other sites

Hello,

You can check if you have a file: /dev/dri/card0

Execute the command: lsmod

I welcome!

In the dev folder there is no dri folder therefore there is no card0 file.

lsmod:

Module                  Size  Used by
bridge                 53853  0
stp                     1549  1 bridge
aufs                  178577  0
macvlan                 8638  0
veth                    4263  0
xt_conntrack            3129  1
xt_addrtype             2621  1
nf_conntrack_ipv6       6163  0
nf_defrag_ipv6         22249  1 nf_conntrack_ipv6
ip6table_filter         1324  0
ip6_tables             15488  1 ip6table_filter
ipt_MASQUERADE          1634  1
xt_REDIRECT             1534  0
xt_nat                  1769  0
iptable_nat             2582  1
nf_nat_ipv4             3240  1 iptable_nat
nf_nat                 11557  5 ipt_MASQUERADE,nf_nat_ipv4,xt_nat,xt_REDIRECT,iptable_nat
xt_recent               8336  0
xt_iprange              1504  0
xt_limit                1777  0
xt_state                1095  0
xt_tcpudp               2271  0
xt_multiport            1622  0
xt_LOG                 12036  0
nf_conntrack_ipv4      11196  2
nf_defrag_ipv4          1203  1 nf_conntrack_ipv4
nf_conntrack           52176  8 ipt_MASQUERADE,nf_nat,xt_state,nf_nat_ipv4,xt_conntrack,iptable_nat,nf_conntrack_ipv4,nf_conntrack_ipv6
iptable_filter          1320  1
ip_tables              14851  2 iptable_filter,iptable_nat
x_tables               15256  16 ip6table_filter,xt_iprange,xt_recent,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_limit,xt_state,xt_conntrack,xt_LOG,xt_nat,xt_multiport,iptable_filter,xt_REDIRECT,ip6_tables,xt_addrtype
cifs                  244488  0
udf                    79072  0
isofs                  32063  0
iscsi_target_mod      218458  1
target_core_ep         48500  2
target_core_file       29699  1
loop                   16591  0
target_core_iblock     14176  1
target_core_mod       360519  13 target_core_iblock,iscsi_target_mod,target_core_ep,target_core_file
syno_extent_pool     1287269  0
rodsp_ep               73959  2 syno_extent_pool,target_core_file
hid_generic             1113  0
usbhid                 25223  0
hid                    82276  2 hid_generic,usbhid
usblp                  10474  0
bonding                90885  0
broadwell_synobios     44394  0
button                  4440  0
ax88179_178a           12012  0
usbnet                 17781  1 ax88179_178a
tg3                   149376  0
r8169                  54371  0
cnic                   52799  0
bnx2                   73633  0
vmxnet3                36741  0
pcnet32                30594  0
e1000                  99699  0
sfc                   154427  0
netxen_nic             96660  0
qlge                   77290  0
qlcnic                227416  0
qla3xxx                36545  0
pch_gbe                33267  0
ptp_pch                 5646  1 pch_gbe
sky2                   46798  0
skge                   29459  0
jme                    34105  0
ipg                    15837  0
uio                     7600  1 cnic
alx                    25873  0
atl1c                  34188  0
atl1e                  27956  0
atl1                   30566  0
libphy                 18061  1 tg3
mii                     3763  8 ipg,jme,atl1,r8169,usbnet,pch_gbe,pcnet32,ax88179_178a
btrfs                 856265  1
synoacl_vfs            17182  1
zlib_deflate           20444  1 btrfs
hfsplus                91202  0
md4                     3553  0
hmac                    2689  0
bnx2x                1417616  0
libcrc32c                898  1 bnx2x
mdio                    3293  3 alx,sfc,bnx2x
mlx5_core             285427  0
mlx4_en               102617  0
mlx4_core             284602  1 mlx4_en
mlx_compat              5930  3 mlx4_en,mlx4_core,mlx5_core
compat                  4329  4 mlx_compat,mlx4_en,mlx4_core,mlx5_core
tn40xx                 28149  0
i40e                  271500  0
ixgbe                 250024  0
be2net                116509  0
igb                   175037  0
i2c_algo_bit            5120  1 sfc
e1000e                169017  0
dca                     4512  2 igb,ixgbe
fuse                   75882  0
vfat                   10143  0
fat                    50319  1 vfat
crc32c_intel           13793  2
aesni_intel            43485  0
glue_helper             3993  1 aesni_intel
lrw                     3269  1 aesni_intel
gf128mul                5338  1 lrw
ablk_helper             1676  1 aesni_intel
arc4                    1832  0
cryptd                  6956  2 aesni_intel,ablk_helper
ecryptfs               77510  1 btrfs
sha512_generic          4936  0
sha256_generic          9620  0
sha1_generic            2198  0
ecb                     1841  0
aes_x86_64              7295  1 aesni_intel
authenc                 6172  0
des_generic            15843  0
ansi_cprng              3732  0
cts                     3928  0
md5                     2241  0
cbc                     2504  0
cpufreq_conservative     6232  0
cpufreq_powersave        918  0
cpufreq_performance      922  4
cpufreq_ondemand        8013  0
acpi_cpufreq            6614  1
mperf                   1067  1 acpi_cpufreq
processor              26076  1 acpi_cpufreq
thermal_sys            17649  1 processor
cpufreq_stats           2849  0
freq_table              2372  3 cpufreq_stats,cpufreq_ondemand,acpi_cpufreq
dm_snapshot            26058  0
crc_itu_t               1259  1 udf
crc_ccitt               1259  0
quota_v2                3711  0
quota_tree              7450  1 quota_v2
psnap                   1645  0
p8022                    971  0
llc                     3489  4 stp,p8022,psnap,bridge
sit                    14418  0
tunnel4                 2053  1 sit
ip_tunnel              11448  1 sit
ipv6                  300785  57 sit,cnic,rodsp_ep,nf_defrag_ipv6,nf_conntrack_ipv6
zram                    7881  4
sg                     24881  0
mpt3sas               281913  0
mpt2sas               238978  0
megaraid_sas           72622  0
ata_piix               23344  0
mptctl                 26101  0
mptsas                 38463  0
mptspi                 12916  0
mptscsih               18705  2 mptsas,mptspi
mptbase                61898  4 mptctl,mptsas,mptspi,mptscsih
scsi_transport_spi     19098  1 mptspi
megaraid               37746  0
megaraid_mbox          27683  0
megaraid_mm             7552  1 megaraid_mbox
vmw_pvscsi             15239  0
BusLogic               21185  0
usb_storage            47709  0
etxhci_hcd             84394  0
xhci_hcd               84124  0
uhci_hcd               22419  0
ohci_hcd               20680  0
usbcore               174990  11 etxhci_hcd,usblp,uhci_hcd,usb_storage,ohci_hcd,usbhid,usbnet,ax88179_178a,xhci_hcd
usb_common              1544  1 usbcore
mv14xx                533289  0
el000                  14864  0

Still in 3617 in a source of http://packages.synocommunity.com packages there is no midnight commander package.

Also, I have noticed that in 6.1 that on 3615 that on 3617 it seems there is a hardware decoding of video for which all wait from the 916th assembly. I seldom watch therefore I not strongly paid attention. Earlier I noticed that my processors were strongly loaded on both systems at start of movies. Now there is for 4-5% a loading - it is when viewing through VideoStation. Though here PLEX loads system. Maybe I am mistaken.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...