Ton_O

Thanks again mate! I was preparing for the process of copying the vfat-img to the internal flash-memory which, imho (but I'd like to see myself as a n00b), will render the Readynas into a nice brick, hence the hesitation. Meanwhile, I've indeed copied the *vfat.img to internal flash memory, just tried the bootstrap-script for Atom D410, rebooted and got myself the ipkg-command:-) Did a "ipkg update" and "ipkg upgrade", then installed the packages mentioned to silence the fans. In that process, added bash-shell through "ipkg install bash" to follow the original posters solution as much as possible and rebooted the Readynas. Unfortunately, fan still running at full speed, but checking the start from the fan control daemon, must be something wrong with it. Thank you very much for your contribution. P.s. I'm told that the lcd CAN be put to work. I picked up the following init-script from nexentastor.org: $ cat /etc/init.d/lcd #!/bin/bash echo "E" > /dev/term/b sleep 0.5 echo "L NexentaStor" > /dev/term/b

Thanks for your response! I expected one of the zip-parts had to be the right one, but the size of the backup I created (the dd-statement) created a dump of 128MB (the size of the filesystem), so I was reluctant to just "try a file" with the risk of bricking the readynas. Any idea on "How to bootstrap this device once gnoboot is running on it? "Is that a process regardless of whether the Readynas is using Radiator or Gnoboot? Ton.

Hi, maybe a simple question, but where did you get/can I get the current bootcode? (synoboot-5-beta.img). I've got my Readynas already booting from USBStick and saved the old bootcode, but where can I find the right version now? Maybe a second question once I've got this finished, bootstrapping the Readynas with DSM, is it just a matter of finding the right bootstrap-code for this processor-type? I've got an Atom A410. Thanks for sharing and hope I'll get a response from you guys! Reagrds, Ton.

No need to apologize. XPEH already gave more information on the allocation of the OS over all drives, so I hope that's clear now; it's just a matter of keeping the NAS's availability as high as possible. You mentioned you've got two harddrives and planning on buying a third one. What you could do is create a disk group for your data on the 3.5 inch sata-drive for now and expand it with the new 3.5 data once that's there: that will increase the protection of your data, but will not increase the amount of available storage. Perhaps you already have looked at the Raid-calculator on the Synology website (http://www.synology.com/en-global/suppo ... calculator) that shows you exactly what you can achieve when combining harddisks. Good Luck! P.s. My N54L needs a BIOS-hack to achieve high performance on the 6th bay, I assume the N40 needs the same.

Well, I don't think that the post right above yours is trying to be funny when stating that the OS is written on ALL discs. Your question about data protection is confusing: do you have one disk or two in the system? Two partitions on the same harddiscs is NOT considered data protection: a crash of that drive will affect al your data. If you have two drives, things are different.

Make sure that you use the correct port number. I noticed that the package itself users port 5000 (when clicking on Transmission in the browser) to go to Transmission; yet Transmssion users 9091 for it's web interface. So if you change the 5000 in the URL that times out, into 9091, you would end up with results. I would suggest using the Transmission Remote Gui, that's a much better interface than the default one.