fma965 Posted May 13, 2014 Share #176 Posted May 13, 2014 Nanoboot worked fine on my VirtualBox test instances Used VBoxManage to create .vdi from .img VBoxManage convertfromraw -format VDI NanoBoot-5.0.2.1-fat.img NanoBoot-5.0.2.1-fat.vdi or just use the provided vmdk file? or doesn't vmdk work on virtualbox? Quote Link to comment Share on other sites More sharing options...
phoenix73 Posted May 13, 2014 Share #177 Posted May 13, 2014 I built vdi from img since VirtualBox is a kind of test instance before going live to N54L Quote Link to comment Share on other sites More sharing options...
hieloiceberg Posted May 15, 2014 Share #178 Posted May 15, 2014 First of all want to thank everyone for this awesome project! I do not use any virtual machine so all I did was on my homemade nas My setup: Disk 1 (very small in size) I keep the main DiskStation software and also it becomes volume 1 for my apps in use Any other Disks will become Volume 2 for data …anyways frustrated because the 4482 update. This is what I did: Made me a gnoboot-alpha10.5 boot drive and install DSM_DS211_4458 once finish I turn it off and replaced the usb boot drive with the NanoBoot-5.0.2.2-fat usb drive and installed the famous DSM_DS3612xs_4482 as explained by fma965. Everything working great so far and I even switch usb boot drives and works great with either one! Thank you so much guys. Quote Link to comment Share on other sites More sharing options...
fma965 Posted May 15, 2014 Share #179 Posted May 15, 2014 First of all want to thank everyone for this awesome project!I do not use any virtual machine so all I did was on my homemade nas My setup: Disk 1 (very small in size) I keep the main DiskStation software and also it becomes volume 1 for my apps in use Any other Disks will become Volume 2 for data …anyways frustrated because the 4482 update. This is what I did: Made me a gnoboot-alpha10.5 boot drive and install DSM_DS211_4458 once finish I turn it off and replaced the usb boot drive with the NanoBoot-5.0.2.2-fat usb drive and installed the famous DSM_DS3612xs_4482 as explained by fma965. Everything working great so far and I even switch usb boot drives and works great with either one! Thank you so much guys. Thanks, Glad it helped Quote Link to comment Share on other sites More sharing options...
mtheo Posted May 15, 2014 Share #180 Posted May 15, 2014 My setup: Disk 1 (very small in size) I keep the main DiskStation software and also it becomes volume 1 for my apps in use Any other Disks will become Volume 2 for data …anyways frustrated because the 4482 update. Hi hieloiceberg, thank you for your description. On short question, can I do this also whit vm on esxi. I mean to use on smal vmdk (HD1) for the os and a 2end (HD2) only fort the data. So I can place the HD1.vmdk on my ssd datastore where only the vm placed and HD2.vmdk datastore only for datas The other thing is, I have a real synology DS713+ can I use also this image to setup a virtual synology DS on the esxi server. Think the 3612xs which most of the useres using hast to much funtion we never use whit this vm. All thest mtheo Quote Link to comment Share on other sites More sharing options...
GatekeeperZA Posted May 15, 2014 Share #181 Posted May 15, 2014 anyone have the issue of not having their home directory inaccessible. and how do i fix.. ? Quote Link to comment Share on other sites More sharing options...
phoenix73 Posted May 15, 2014 Share #182 Posted May 15, 2014 Did you get your home inaccessible after update to 4482 ? 4482 with Nanoboot ? Quote Link to comment Share on other sites More sharing options...
GatekeeperZA Posted May 15, 2014 Share #183 Posted May 15, 2014 Did you get your home inaccessible after update to 4482 ?4482 with Nanoboot ? Yes Quote Link to comment Share on other sites More sharing options...
martimic Posted May 16, 2014 Share #184 Posted May 16, 2014 Thanks for you help. A clean installation of DSM 5.0-4482 works with NanoBoot-5.0.2.1-fat.img, DSM_DS3612xs_4482.pat and HP Proliant G7 N54L. The migration probably works but due a human mistake, I lost all configuration of DSM but no data. Bye, Martial Quote Link to comment Share on other sites More sharing options...
xerafoo Posted May 24, 2014 Share #185 Posted May 24, 2014 I was able to install the stock 5.0 DSM-4482.pat (downloaded from Synology) as follows: gnoboot > fresh install stock 4458 > reboot > boot using nanoboot 5.0.2.2-fat (sees the box as a 3612xs, 5.0.2.4 thinks its a 214play) > nano boot option >upgrade -DSM 4482< > install stock 4482 from synology. My system is a homebuilt NAS box with an intel chip asus mobo.... FYI - I already had the original 5.0 Beta from Trantor installed with a 5 disk (3TB each) SHR volume and a bunch of apps installed so I wanted to test it before I ran it on my existing build. I removed all the drives and tested it all from a scratch install with a usb thumb drive and a single 320GB HDD. After verifying that it worked, i put all my drives back in and booted my existing install (DSM 5 beta) with gnoboot. I installed 4458 (selecting the 'migrate" option to keep all my data) i then rebooted and installed the 4482 stock update. My apps, 11.0 TB SHR and all settings were persistent (with the exception of my static IP)! YMMV... Cheers! Quote Link to comment Share on other sites More sharing options...
djelusion Posted May 26, 2014 Share #186 Posted May 26, 2014 so there is hope in upgrading , i still need to make my special cable in order to see anything that happens on the screen, Im running a headless setup and cannot see any syntax. Quote Link to comment Share on other sites More sharing options...
chanquete69 Posted May 26, 2014 Share #187 Posted May 26, 2014 I was able to install the stock 5.0 DSM-4482.pat (downloaded from Synology) as follows: gnoboot > fresh install stock 4458 > reboot > boot using nanoboot 5.0.2.2-fat (sees the box as a 3612xs, 5.0.2.4 thinks its a 214play) > nano boot option >upgrade -DSM 4482< > install stock 4482 from synology. My system is a homebuilt NAS box with an intel chip asus mobo.... FYI - I already had the original 5.0 Beta from Trantor installed with a 5 disk (3TB each) SHR volume and a bunch of apps installed so I wanted to test it before I ran it on my existing build. I removed all the drives and tested it all from a scratch install with a usb thumb drive and a single 320GB HDD. After verifying that it worked, i put all my drives back in and booted my existing install (DSM 5 beta) with gnoboot. I installed 4458 (selecting the 'migrate" option to keep all my data) i then rebooted and installed the 4482 stock update. My apps, 11.0 TB SHR and all settings were persistent (with the exception of my static IP)! YMMV... Cheers! Which Apps did you have installed?? I thought that we must reinstall extra packages like "Plex Media Server", "Audio Station", etc. If they persist after migration I will do it! Quote Link to comment Share on other sites More sharing options...
freddan83 Posted May 26, 2014 Share #188 Posted May 26, 2014 they persist Quote Link to comment Share on other sites More sharing options...
chanquete69 Posted May 27, 2014 Share #189 Posted May 27, 2014 Thank you for your answer! So let's do it! Quote Link to comment Share on other sites More sharing options...
chanquete69 Posted June 1, 2014 Share #190 Posted June 1, 2014 The migration went flawlessly! No data nor configuration lost. Thank you very much for your advice! Quote Link to comment Share on other sites More sharing options...
FranzK Posted June 1, 2014 Share #191 Posted June 1, 2014 Nanoboot & gnuboot both execution errror, but nanoboot don't have my network driver, so i have to use gnuboot. Started the Install Mode with 4482 can someone help? Quote Link to comment Share on other sites More sharing options...
GatekeeperZA Posted June 4, 2014 Share #192 Posted June 4, 2014 did u select gnoboot.me when doing the install. Please post exact steps and versions.. Quote Link to comment Share on other sites More sharing options...
FranzK Posted June 4, 2014 Share #193 Posted June 4, 2014 did u select gnoboot.me when doing the install.Please post exact steps and versions.. - Start gnoboot.me - with e edit the Line to 4482 - start install/upgrade 4482 - upload the .pat (donwloaded servial times) - error Quote Link to comment Share on other sites More sharing options...
Vortex Posted June 5, 2014 Share #194 Posted June 5, 2014 Paranoia increasing! Instead of lame [X+2] stirng "coding", Syno implements RSA encryption with AES256 PEM cert hiding for essential stings in 5.0-4493. I know that Sinology reading this topic. Nice try, Syno, nice try... Here is lastest devices and file protection lists from scemd 5.0-4493: [spoiler=devlist] synology_bromolow_3611xs 0200 111d806e pcieport 0310 111d806e pcieport 0318 111d806e pcieport 0320 111d806e pcieport 0328 111d806e pcieport 0400 11ab7042 sata_mv 0500 11ab7042 sata_mv 0600 11ab7042 sata_mv 0700 11ab7042 sata_mv 0800 11ab7042 sata_mv 0a00 808610d3 e1000e 0b00 808610d3 e1000e 0c00 808610d3 e1000e 0d00 808610d3 e1000e synology_bromolow_3612xs 0200 111d806e pcieport 0310 111d806e pcieport 0318 111d806e pcieport 0320 111d806e pcieport 0328 111d806e pcieport 0400 11ab7042 sata_mv 0500 11ab7042 sata_mv 0600 11ab7042 sata_mv 0700 11ab7042 sata_mv 0800 11ab7042 sata_mv 0a00 808610d3 e1000e 0b00 808610d3 e1000e 0c00 808610d3 e1000e 0d00 808610d3 e1000e synology_bromolow_rs3411rpxs 0200 111d806e pcieport 0310 111d806e pcieport 0318 111d806e pcieport 0320 111d806e pcieport 0328 111d806e pcieport 0400 11ab7042 sata_mv 0500 11ab7042 sata_mv 0600 11ab7042 sata_mv 0700 11ab7042 sata_mv 0800 11ab7042 sata_mv 0a00 808610d3 e1000e 0b00 808610d3 e1000e 0c00 808610d3 e1000e 0d00 808610d3 e1000e synology_bromolow_rs3411xs 0200 111d806e pcieport 0310 111d806e pcieport 0318 111d806e pcieport 0320 111d806e pcieport 0328 111d806e pcieport 0400 11ab7042 sata_mv 0500 11ab7042 sata_mv 0600 11ab7042 sata_mv 0700 11ab7042 sata_mv 0800 11ab7042 sata_mv 0a00 808610d3 e1000e 0b00 808610d3 e1000e 0c00 808610d3 e1000e 0d00 808610d3 e1000e synology_bromolow_rs3412rpxs 0200 111d806e pcieport 0310 111d806e pcieport 0318 111d806e pcieport 0320 111d806e pcieport 0328 111d806e pcieport 0400 11ab7042 sata_mv 0500 11ab7042 sata_mv 0600 11ab7042 sata_mv 0700 11ab7042 sata_mv 0800 11ab7042 sata_mv 0a00 808610d3 e1000e 0b00 808610d3 e1000e 0c00 808610d3 e1000e 0d00 808610d3 e1000e synology_bromolow_rs3412xs 0200 111d806e pcieport 0310 111d806e pcieport 0318 111d806e pcieport 0320 111d806e pcieport 0328 111d806e pcieport 0400 11ab7042 sata_mv 0500 11ab7042 sata_mv 0600 11ab7042 sata_mv 0700 11ab7042 sata_mv 0800 11ab7042 sata_mv 0a00 808610d3 e1000e 0b00 808610d3 e1000e 0c00 808610d3 e1000e 0d00 808610d3 e1000e synology_bromolow_rs3413xs+ 0200 111d806e pcieport 0310 111d806e pcieport 0318 111d806e pcieport 0320 111d806e pcieport 0328 111d806e pcieport 0400 11ab7042 sata_mv 0500 11ab7042 sata_mv 0600 11ab7042 sata_mv 0700 11ab7042 sata_mv 0800 11ab7042 sata_mv 0a00 808610d3 e1000e 0b00 808610d3 e1000e 0c00 808610d3 e1000e 0d00 808610d3 e1000e synology_bromolow_rs10613xs+ 0100 10000072 mpt2sas 0300 808610d3 e1000e 0400 808610d3 e1000e 0500 808610d3 e1000e 0600 808610d3 e1000e synology_cedarview_412+ 0100 808610d3 e1000e 0200 808610d3 e1000e 0300 10953531 sata_sil24 synology_cedarview_713+ 0100 808610d3 e1000e 0200 808610d3 e1000e 0300 10953531 sata_sil24 synology_cedarview_1512+ 0100 808610d3 e1000e 0200 808610d3 e1000e 0300 10953132 sata_sil24 synology_cedarview_1513+ 0100 80861533 igb 0200 80861533 igb 0300 10953132 sata_sil24 0400 1b6f7023 etxhci_hcd 0500 80861533 igb 0600 80861533 igb synology_cedarview_1812+ 0100 808610d3 e1000e 0200 808610d3 e1000e 0300 10953132 sata_sil24 0400 10953132 sata_sil24 synology_cedarview_1813+ 0200 80861533 igb 0300 10953132 sata_sil24 0400 10953132 sata_sil24 0500 1b6f7023 etxhci_hcd 0800 80861533 igb 0900 80861533 igb synology_cedarview_2413+ 0100 808610d3 e1000e 0200 808610d3 e1000e 0300 11ab7042 sata_mv 0400 10953132 sata_sil24 0500 11ab7042 sata_mv 0600 1b6f7023 etxhci_hcd synology_cedarview_rs812+ 0100 808610d3 e1000e 0200 808610d3 e1000e 0300 10953531 sata_sil24 synology_cedarview_rs812rp+ 0100 808610d3 e1000e 0200 808610d3 e1000e 0300 10953531 sata_sil24 synology_cedarview_rs2212+ 0100 808610d3 e1000e 0200 808610d3 e1000e 0300 11ab7042 sata_mv 0500 11ab7042 sata_mv synology_cedarview_rs2212rp+ 0100 808610d3 e1000e 0200 808610d3 e1000e 0300 11ab7042 sata_mv 0500 11ab7042 sata_mv synology_cedarview_rs2414+ 0100 80861533 igb 0400 1b6f7023 etxhci_hcd 0500 80861533 igb 0600 10953132 sata_sil24 0700 11ab7042 sata_mv 0800 1b4b9235 ahci 0b00 80861533 igb 0c00 80861533 igb synology_cedarview_rs2414rp+ 0100 80861533 igb 0400 1b6f7023 etxhci_hcd 0500 80861533 igb 0600 10953132 sata_sil24 0700 11ab7042 sata_mv 0800 1b4b9235 ahci 0b00 80861533 igb 0c00 80861533 igb synology_x86_411+ 00d0 80862937 uhci_hcd 00d1 80862938 uhci_hcd 00d2 80862939 uhci_hcd 00d7 8086293c ehci_hcd 00e8 80862934 uhci_hcd 00e9 80862935 uhci_hcd 00ea 80862936 uhci_hcd 00ef 8086293a ehci_hcd 00fa 80862922 ahci 0200 10953531 sata_sil24 synology_x86_411+II 00d0 80862937 uhci_hcd 00d1 80862938 uhci_hcd 00d2 80862939 uhci_hcd 00d7 8086293c ehci_hcd 00e8 80862934 uhci_hcd 00e9 80862935 uhci_hcd 00ea 80862936 uhci_hcd 00ef 8086293a ehci_hcd 00fa 80862922 ahci 0200 10953531 sata_sil24 synology_x86_710+ 00c8 808610e5 e1000e 00d0 80862937 uhci_hcd 00d1 80862938 uhci_hcd 00d2 80862939 uhci_hcd 00d7 8086293c ehci_hcd 00e8 80862934 uhci_hcd 00e9 80862935 uhci_hcd 00ea 80862936 uhci_hcd 00ef 8086293a ehci_hcd 00fa 80862922 ahci 0100 10953132 sata_sil24 synology_x86_712+ 0100 10953531 sata_sil24 0200 808610d3 e1000e 0300 808610d3 e1000e synology_x86_1010+ 0100 10953132 sata_sil24 0200 808610d3 e1000e 0300 808610d3 e1000e synology_x86_1511+ 0100 10953132 sata_sil24 0200 808610d3 e1000e 0300 808610d3 e1000e synology_x86_2411+ 0100 11ab7042 sata_mv 0200 11ab7042 sata_mv 0300 11ab7042 sata_mv 0400 11ab7042 sata_mv 0500 808610d3 e1000e 0600 808610d3 e1000e synology_x86_rs810+ 0100 10953531 sata_sil24 0200 808610d3 e1000e 0300 808610d3 e1000e synology_x86_rs810rp+ 0100 10953531 sata_sil24 0200 808610d3 e1000e 0300 808610d3 e1000e synology_x86_rs2211+ 0100 11ab7042 sata_mv 0200 11ab7042 sata_mv 0300 11ab7042 sata_mv 0400 11ab7042 sata_mv 0500 808610d3 e1000e 0600 808610d3 e1000e synology_x86_rs2211rp+ 0100 11ab7042 sata_mv 0200 11ab7042 sata_mv 0300 11ab7042 sata_mv 0400 11ab7042 sata_mv 0500 808610d3 e1000e 0600 808610d3 e1000e synology_evansport_214play 0160 80862e6e e1000 0200 1b6f7023 etxhci_hcd 0300 10953531 sata_sil24 synology_evansport_114+ 0160 80862e6e e1000 0200 1b6f7023 etxhci_hcd 0300 10953531 sata_sil24 synology_bromolow_rs3614xs 0a00 1b4b9235 ahci 0b00 1b4b9235 ahci 0c00 1b4b9235 ahci 0e00 1b4b9235 ahci 0f00 1b4b9235 ahci 1100 80861539 igb 1200 80861539 igb 1300 80861539 igb 1400 80861539 igb synology_bromolow_rs3614rpxs 0a00 1b4b9235 ahci 0b00 1b4b9235 ahci 0c00 1b4b9235 ahci 0e00 1b4b9235 ahci 0f00 1b4b9235 ahci 1100 80861539 igb 1200 80861539 igb 1300 80861539 igb 1400 80861539 igb synology_bromolow_rs3614xs+ 0400 1b4b9235 ahci 0500 1b4b9235 ahci 0600 1b4b9235 ahci 0800 1b4b9235 ahci 0900 1b4b9235 ahci 0a00 1b4b9235 ahci 0b00 1b6f7023 etxhci_hcd 0c00 80861539 igb 0d00 80861539 igb 0e00 80861539 igb 0f00 80861539 igb synology_cedarview_rs814+ 0100 80861539 igb 0200 80861539 igb 0300 10953531 sata_sil24 0400 1b6f7023 etxhci_hcd 0500 80861539 igb 0600 80861539 igb synology_cedarview_rs814rp+ 0100 80861539 igb 0200 80861539 igb 0300 10953531 sata_sil24 0400 1b6f7023 etxhci_hcd 0500 80861539 igb 0600 80861539 igb synology_bromolow_2414xs 0700 11ab7042 sata_mv 0800 11ab7042 sata_mv 0b00 11ab7042 sata_mv 0c00 80861539 igb 0d00 80861539 igb 0e00 80861539 igb 0f00 80861539 igb synology_evansport_415play 0160 80862e6e e1000 0200 11ab7042 sata_mv 0300 1b6f7023 etxhci_hcd synology_bromolow_rs3415xs+ 0200 1b4b9235 ahci 0300 1b4b9235 ahci 0400 1b4b9235 ahci 0500 1b4b9235 ahci 0600 1b6f7023 etxhci_hcd 0700 80861539 igb 0800 80861539 igb 0900 80861539 igb 0a00 80861539 igb synology_avoton_415+ 00a0 80861f41 igb 00a1 80861f41 igb 00b0 80861f2c ehci_hcd 00b8 80861f22 ahci 00c0 80861f32 ahci 00f8 80861f38 lpc_ich 00fb 80861f3c i801_smbus 0100 10953132 sata_sil24 0200 1b6f7023 etxhci_hcd synology_bromolow_3615xs 0700 1b4b9235 ahci 0800 1b4b9235 ahci 0900 1b4b9235 ahci 0a00 1b4b9235 ahci [spoiler=filelist] /usr/syno/bin/findhostd /usr/syno/bin/scemd /usr/syno/bin/lspci /usr/syno/synoman/webman/modules/StorageManager/storagehandler.cgi /usr/syno/synoman/webman/modules/StorageManager/volumehandler.cgi /usr/syno/synoman/webman/modules/PkgManApp/PkgMan.cgi /usr/syno/synoman/webman/modules/PkgManApp/PkgSynoMan.cgi /usr/syno/synoman/webman/modules/DSMNotify/dsmnotify.cgi /usr/syno/synoman/webman/modules/PollingTask/polling.cgi /usr/syno/synoman/webman/modules/SystemInfoApp/LogViewer.cgi /usr/syno/synoman/webman/initdata.cgi /usr/syno/synoman/webman/usersettings.cgi /usr/syno/synoman/webman/uistrings.cgi /lib/libdsm.so /lib/libsynocgi.so Enjoy. Quote Link to comment Share on other sites More sharing options...
yabba235 Posted June 5, 2014 Share #195 Posted June 5, 2014 Good job, Vortex !! So only need to simply replace these files to be able to do the update 4493 ? I still use gnoboot 10.5 to boot because nanoboot dont't work on redaynas pro 2 Quote Link to comment Share on other sites More sharing options...
demon_sl Posted June 5, 2014 Share #196 Posted June 5, 2014 it's a great job !!! Vortex !!! +1 thank you Quote Link to comment Share on other sites More sharing options...
mcdull Posted June 6, 2014 Share #197 Posted June 6, 2014 Paranoia increasing!Instead of lame [X+2] stirng "coding", Syno implements RSA encryption with AES256 PEM cert hiding for essential stings in 5.0-4493. I know that Sinology reading this topic. Nice try, Syno, nice try... In that case, can we declare xpenology project close? Quote Link to comment Share on other sites More sharing options...
newbi Posted June 6, 2014 Share #198 Posted June 6, 2014 More decrypted strings from scemd:[spoiler=text]/var/log/pmesg /usr/syno/bin/lspci | grep /usr/bin/logger -p err -t dnsdsm "Check failed. %s" /usr/bin/logger -p err -t dnsdsm "Check failed. %s";/usr/syno/bin/synonotify DsmProtectionCheckFailed /dev/sd* /dev/sas* LD_PRELOAD /proc/self/comm /sys/bus/pci/devices/*/uevent /proc/sys/kernel/syno_deno_of_spinup_time /sys/bus/pci/devices/0000:%s:%s.0/uevent /proc/bus/pci/devices all "hidden log" entries now encoded with public key, so we need a private key to decode it! /dev/sd* and /dev/sas* is a mask for drives unmounting in case of protection check fails Great work dude. Do you think it can be done? Quote Link to comment Share on other sites More sharing options...
Vortex Posted June 6, 2014 Share #199 Posted June 6, 2014 We do not need to decrypt the "hidden log". I post the info to the community so that the community can know more about protection and override it in GPL part of firmware (kernel, drivers etc). We need to avoid to "hack" a non-GPL, proprietary Synology code in XPEnology. Quote Link to comment Share on other sites More sharing options...
newbi Posted June 6, 2014 Share #200 Posted June 6, 2014 We do not need to decrypt the "hidden log".I post the info to the community so that the community can know more about protection and override it in GPL part of firmware (kernel, drivers etc). We need to avoid to "hack" a non-GPL, proprietary Synology code in XPEnology. Synology will hire you soon I hope a new gnoBoot version comes out very soon. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.