666 Posted June 5, 2014 Share #26 Posted June 5, 2014 I've created new boot images in different formats for DSM 5.0-4493: .iso .img .vmdk Go to http://www.xpenology.nl/boot-images. Tried 3 times to install with .img using clean installation. All stopped at 40%. But if I use 4482 pat, installation works. Quote Link to comment Share on other sites More sharing options...
wasilek Posted June 5, 2014 Share #27 Posted June 5, 2014 Hi there. How to change the serial number? How do I edit a file I receive information that the disk is full. Previously edited the cfg file and everything worked (version 4482) Sorry for my english. Quote Link to comment Share on other sites More sharing options...
Poechi Posted June 5, 2014 Share #28 Posted June 5, 2014 (edited) - Edited July 10, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
Guest Posted June 5, 2014 Share #29 Posted June 5, 2014 It seems like there is no problem to update from 4458 update 2 to 4493 without problem, am i right? I have an N54L. Thanks in advance Quote Link to comment Share on other sites More sharing options...
Poechi Posted June 5, 2014 Share #30 Posted June 5, 2014 (edited) - Edited July 10, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
Raver Posted June 5, 2014 Share #31 Posted June 5, 2014 after installing the modified USB nanoboot, the synology assistent identify my hardware (n54l) as RS3411RPxs on installation... Quote Link to comment Share on other sites More sharing options...
XPEH Posted June 5, 2014 Share #32 Posted June 5, 2014 Looks like you've successfully guessed serial number from existing RS3411RPxs. Quote Link to comment Share on other sites More sharing options...
Raver Posted June 5, 2014 Share #33 Posted June 5, 2014 I don't changed anything. Maybe Poechi? Quote Link to comment Share on other sites More sharing options...
k3nnis Posted June 5, 2014 Share #34 Posted June 5, 2014 Thanks for the update. Does iSCSI work 100% with this release? i.e. I have a windows media center software on a HTPC Windows 8.1 and I want to record my tv shows on the NAS via iSCSI as WMC won't allow to put it a on network. Thanks, Kenn. Quote Link to comment Share on other sites More sharing options...
Poechi Posted June 6, 2014 Share #35 Posted June 6, 2014 (edited) - Edited July 10, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
Poechi Posted June 6, 2014 Share #36 Posted June 6, 2014 (edited) - Edited July 10, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
Falipene Posted June 6, 2014 Share #37 Posted June 6, 2014 I've successfully upgraded my N54L from trantor 4.3 to Nanoboot 5.0.24 with pat 4493. However booting is not so fast, takes a while. I have my N54L with bios mod, intenal SATA to 5.25" rack, for hot-swap backup, hot plug a drive with a volume worked, but says "Not Initialized", rebooting fixes that. It is possible to really hot-swap drives on Synology for backup puproses? I backed up my HFS drives mounting it manually over SSH (like any linux distro). But I need a safe way to unplug volumes created by Synology. Quote Link to comment Share on other sites More sharing options...
ema Posted June 6, 2014 Share #38 Posted June 6, 2014 Thanks for the update. Does iSCSI work 100% with this release? i.e. I have a windows media center software on a HTPC Windows 8.1 and I want to record my tv shows on the NAS via iSCSI as WMC won't allow to put it a on network. Thanks, Kenn. iSCSI works. Only file level or also block level? Thanks! ema Quote Link to comment Share on other sites More sharing options...
Poechi Posted June 6, 2014 Share #39 Posted June 6, 2014 (edited) - Edited July 10, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
elfeneco Posted June 6, 2014 Share #40 Posted June 6, 2014 Hi, I'm sorry if it's already explained somewhere but I can't find explanations. I have 2 questions : 1) I'am actually on 5.0-4458 update 2 (gnoboot). What is the method to upgrade to 5.0-4493 ? 2) Is there any risk / problem as with 5.0-4482 update for data integrity ? Thx to all. Quote Link to comment Share on other sites More sharing options...
Poechi Posted June 6, 2014 Share #41 Posted June 6, 2014 (edited) - Edited July 10, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
Raver Posted June 6, 2014 Share #42 Posted June 6, 2014 I don't changed anything. Maybe Poechi? I've checked the menu files: kernel /zImage ihd_num=0 netif_num=4 syno_hw_version=DS3612xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 upgrade=5.0-4493 Seems correct. Download a new version of Assistant. With the newest version the same. For now I don't have VGA and can't check what going on. I will wait till my ordered VGA cable is here. Quote Link to comment Share on other sites More sharing options...
ema Posted June 6, 2014 Share #43 Posted June 6, 2014 Well I can create blocklevel but connection is not working through iSCSI initiator Windows. Maybe I'm doing something wrong. No, it's not your fault, simply block level it's not working like in previous version (gnoboot, nanoboot)... they switched from IET to LIO... From http://xpenology.com/forum/viewtopic.php?f=2&t=2152 >> Fixed - Broken block-level iSCSI (LIO), workaround enable IET in synoinfo.conf Thanks! ema Quote Link to comment Share on other sites More sharing options...
yabba235 Posted June 6, 2014 Share #44 Posted June 6, 2014 Now nanoboot is work on my ReadyNas Pro2, but not work power button hack ( acpi ), seems kernel has no acpi option on building ( no button module ). I little unhappy, can only power off nas over gui, not from front button ISCSI target work finally, good job !! Quote Link to comment Share on other sites More sharing options...
Trexx Posted June 6, 2014 Share #45 Posted June 6, 2014 Do not update with the DSM gui. You can use Nanoboot 5.0.2.2 but you have to alter the upgrade option in grub menu to 4493. You can also use new boot image. There appears to be an issue with the x64 4493 image file. I tried multiple ways of restoring it to a boot usb, but I kept getting non-bootable disk error. I ended up using the vfat image for 4482 and modified it for 4493. Quote Link to comment Share on other sites More sharing options...
elfeneco Posted June 6, 2014 Share #46 Posted June 6, 2014 Hi,I'm sorry if it's already explained somewhere but I can't find explanations. I have 2 questions : 1) I'am actually on 5.0-4458 update 2 (gnoboot). What is the method to upgrade to 5.0-4493 ? 2) Is there any risk / problem as with 5.0-4482 update for data integrity ? Thx to all. Wrong topic to ask this above ? Quote Link to comment Share on other sites More sharing options...
wasilek Posted June 6, 2014 Share #47 Posted June 6, 2014 Hi. How to change the serial number? How do I edit a file I receive information that the disk is full. Previously edited the cfg file and everything worked (version 4482) Sorry for my english. Quote Link to comment Share on other sites More sharing options...
Poechi Posted June 6, 2014 Share #48 Posted June 6, 2014 (edited) - Edited July 10, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
Poechi Posted June 6, 2014 Share #49 Posted June 6, 2014 (edited) - Edited July 10, 2015 by Guest Quote Link to comment Share on other sites More sharing options...
Freezer Posted June 7, 2014 Share #50 Posted June 7, 2014 Dear all, im was running DSM 5.0-4482 with nanoboot on my ESXI. I have three Disks: 1. IDE with VMDK Nanoboot 2. 16GB for System 3. 2TB RAW Device Map But i decided to Upgrade to 4493. So this were the steps: I uploaded the new Boot VMDK, deleted the old one, attached the new one as IDE. During boot i choose "Install/Upgrade". I followed the instructions on the Web Gui and uploaded the 4493 PAT File (original from Synology) to "migrate". During the Upload my Computer(Laptop) is getting a "Bluescreen" so I think the Upload was not complete. Very strange my Thinkpad T530 is never getting a Bluescreen before So I restarted the VM, and started the Upload a second time. At 55% it stucks with "unknown ecception". Than i tested to use my old existing 4482 VMDK to boot (to look if it works) --> It works Than i attached again the 4493 VMDK and booted it normaly. --> It also works. Also my GUI says that i am on Version 4493, but i'm not shure if this is true. Any way to check the "true" version that is currently running? Any advises what I should do now? Other Question: Is it possible to reinstall the whole System without deleating mit 2TB drive? Very happy if i can get Help 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.