GatekeeperZA

No WOL doe not work with nanoboot or gnoboot but maybe im doing something wrong have checked setting, mac addressed all seem correct. if anyone has some info please shout.

request DVB-T @ GnoBoot so he can add it to the next release..

if it doesnt list update 2 you can manual the update and ssh just dont click the reboot.

HP N54L I don't get these issues when using GnoBoot.

Im also running this on my test N40L., Just confirmed. swapped back my Gnoboot key and all is great again. also from 10.5 - 5.0.2.2 am testing now to see what could have happened

A few things I noticed since changing from GnoBoot to NanoBoot. If anyone has some fixes I am willing to test. 1. Synology Assistant - Reporting : Status as not configured. <--- anyone know how to fix this its annoying the system is working 100% except that message 2. System will not reboot. 3. Home/s folder is inaccessible since migration. 4. System performance seems a bit on the slow side, but maybe its just me. NOTE: startup is fast the webui is slow. 5. On NanoBoot startup there is a message : not a synology partition or something like that will confirm. 6. System Randomly Crashes / Becomes inaccessible. Forced reboot required. 7. Startup Note : Partition Layout is not DiskStation style .

rofl, i see what u did there

Yes

anyone have the issue of not having their home directory inaccessible. and how do i fix.. ?

+1

Are there any performance improvements with using the x64 nanoboot or not really is it more hardware compatibility..?

Ill stick to GnoBoot I feel safe with what he is putting out.

Agreed

apologies. this is my N54L test box.

Just to clarify can you please post the exact steps to upgrade from DSM 5.0-4458 Update 2 to to DSM 5.0-4482 please. also what must we update on GnoBoot. or is it the same usual method after editing grub..? Thanks For The Great Work Guys..

Maybe a bit off topic. is it possible to use an external hard drive as a hot spare. not esata..?

Hello All. Has anyone successfully tried a 6 Drive install on the N54L. Please post comments.

no no im all happy with the n54l thanks for the info all working good now.

Thanks. thats great wasnt using the power feature anyways only the smart. but its good to know. thanks for the info guys... in other words DON'T use the power features... although im still curious why it modifies the settings in the bios which don't use power settings .. or does it just corrupt ur bios then replace a original copy .. ?

Really sorry about that. but thanks alot the other posts werent clear. when you say NOT any schedule. is that like anything or only power. would like to have smart running. but really appreciate the feedback, Sorry please excuse my ignorance just want to make 100% sure the settings should stick after disabling schedules.. ?

does the following also apply to the n40l .. ? then how are the guys running 5 / 6 drives with this issue... ?

Hello guys, my bios on my N54l keeps loosing its settings when i restart xpenology. i dont know if this has been posted before. i appologise if its a duplicate. how do i write protect the bios or is there altenate bios to use. Please help.

how did you guys solve this on the n54l have the same bios reset crap.

Hey guys how did you ovecome the bios resetting crap please help.

I had some issues getting ipkg installed on dsm 5.0 these are the steps I took.. : http://ipkg.nslu2-linux.org/feeds/optwa ... /unstable/ If you get the following while trying to get ipkg installed : Backup your configuration settings, then type: rm -rf /volume1/@optware rm -rf /usr/lib/ipkg This will remove all existing optware packages. This only appears when you have already got existing @optware and ipkg folders. It means you are trying to install the script over existing folders and it won't do it. Issue the following commands in this order: Type: mount If you see: /volume1/@optware on /opt type bind (bind) as the last line Type : umount /opt Then type the following: Type : rm -rf /volume1/@optware rm -rf /usr/lib/ipkg now reboot the Diskstation. Now start at the beginning of the instructions - as if you'd never typed a command to install ipkg). 1. Reboot your NAS. 2. Enable and then Login to the Command Line Interface as user "root", password is the same as for admin. (My note: You MUST be root and it is best you login over SSH - but telnet will work too) 3. Change to a directory such as "/volume1/@tmp", i.e. enter the command "cd /volume1/@tmp" 4. Get the NAS to download the bootstrap, e.g. if you have an mv6281 ARM model enter the command "wget http://ipkg.nslu2-linux.org/feeds/optwa ... -7_arm.xsh", (Depending on your build) 5. Now run the .xsh script, (My change for DS110j >>>>>) e.g. enter the command "sh syno-mvkw-bootstrap_1.2-7_arm.xsh" (It's best you are IN the same directory as the file...) 6. After the script has finished you can delete the script file, e.g. "rm syno-mvkw-bootstrap_1.2-7_arm.xsh" (<<<<<<< DS110j instruction. No other "rm" commands) 7. Reboot the NAS and login again to the Command Line Interface as user "root" (<<<<< Note to REBOOT FIRST and login again - only then will @optware be linked). 8. Update the ipkg list of available packages using the command "ipkg update" 9. Upgrade any ipkg installed packages to the latest versions using the command "ipkg upgrade" 10. Finished, you can now install ipkg packages using the command "ipkg install xxxx" where xxxx is the name of the package. You can list all the available packages using the command "ipkg list". As this is a long list you can filter it using the command "ipkg list | grep xxxx" where xxxx is the text you want to search for. Alternatively, you view one page at a time using the "more" pipe, e.g. "ipkg list | more"