Diverge

My one experience with expanding an array didn't go well either.. but this was way before DSM 5. I'm curious what the success rate if someone did some tests with a few disks and dummy data.

So much for trying to help someone... Good luck understanding how to convert binary to hex and vice versa.. it's that simple

This has been discussed various times on these forums. viewtopic.php?f=2&t=4687&hilit=+esata#p27928 You just need to make sure if you change a drive to external, that you subtract it from the correct internal spot. There's 3 lines that have to do with how the disk slots are defined (noted in the above link). One important detail to doing this is that the drives need to enumerate to the same slots every time, or you could end up with a broken array.

Give details on what you used. What vdmk?

Correct! Along with DSM 5.1 you get a flashy, fancy pants new name too! Since this release is a cross collaboration between a bunch of developers we decided to give the project a new name. There are also some tactical architecture changes which make it drastically different from how previous boot images were built and worked. These changes will hopefully broaden hardware support and lengthen the lifetime of releases (ie. support more versions of DSM & updates). Hope I've wet your anticipation a bit more. Is there any chance you guys separated rd from zImage, like how it used to be early in gnoboot days?

Is there a way of getting USB 3.0 working on with new dsm 5.1 ? Really good news. i'll donate for it. All prior XPNnology builds were based on the DS3612, which only has USB 2.0 ports. The upcoming version is supposedly based on DS3615, which has USB 3.0 ports. So I guess there is a chance 3.0 might work.

Thanks for heads up! I updated to P20 on a new system not too long ago. I haven't done much with it but test stuff... but I just downgraded to P19.

First thing you need to make sure is that it isn't trying to install to you nanoboot drive. I suggest removing all drives but nanoboot, boot the VM, go to the webinstall page, go through the motions and see if it still gives you the option to install... usually it will tell you the number of drives it finds. Take note of this info. power off, attach your array disks, virtual disks, ect, repeat the previous process and make sure it is seeing the additional drives. 2 thinks could be happening; it could be trying to install to your nanoboot drive, or it might not be seeing the drives you want to build the array with. Doing the above should help you narrow down those 2 variables, or eliminate them both. I'd also try vmware/esxi, since it is the most common of all virtual machine software used for xpenology, and proven to work. I'm not too sure about virtual box, but I tried Citrix Zenserver just playing around, and wasn't able to get it to work with my nic cards. I'm pretty sure people have gotten these alternatives to work, but in the end, it's more work adding/removing/building new kernel modules to get stuff supported.

360W is way more than enough for that system. A typical 5900rpm drive uses about 20 watts at initial power up, then only about 4-5 watts for reads and writes. You're cpu is only 35 watts, and that is at full load. My current systems uses 4 x 3TB WD Reds, 1 x 4 seagate, and an i7 3770T (45W)... all on a 120W power brick. The key for my system is staggered powerup of the hard drives.

I have no experience with this, but it might be a better idea to try to build what worked already (before 5.1), so you have a better understanding of what gnoboot/nanoboot did, and also have a good baseline. Once you get that working, then move on to figuring out 5.1. Again, I have no experience with building kernels. Just a suggestion based on troublshooting 101

Sorry, I have no experience with sync. I only use vpn to access my lan.

you can't go by the system information within DSM to see how many cores it uses. That info isn't accurate. I'm not sure if that is what you're using to check core usage or not. I just figured I'd mention that fact. check dmesg or some other linux until that will give you info about hardware from command line.

I know you're using an older version. But I openvpn is working great for me on DSM 5.0. 4493. It was real simple to setup using the exported files from DSM and imported w/ the official openvpn android client on my phone.

On my main system (esxi DSM vm), i have a 4 disk array, and i've changed the 5th disk to show as eSATA within DSM. Then I setup Backup & Replication to do a backup to that eSATA drive every 3 days. The only problem I have is when I power cycle my system I have to pull my eSATA drive before DSM boots up, or the drives might enumerate in a different order and the wrong drive will end up being the 5th (eSATA), and mess up my array. I had some weird issue once with my array, and have since been pulling my eSATA drive before booting up to prevent it from happening... but I haven't tested it thoroughly to see if this is a real issue or not heh. I'm building a new system and will be doing some tests on it, so I guess I'll play around more once it's complete. I've also accidentally forgot to pull it and it booted up fine (maybe I got lucky). If you want to do this you need to edit /etc.defaults/synoinfo.conf stock setttings look like this: DS-Test> cat /etc.defaults/synoinfo.conf |grep portcfg esataportcfg="0xff000" usbportcfg="0xf00000" internalportcfg="0xfff" To change it so the 5th drive becomes eSATA, I do this: cat synoinfo.conf>synoinfo.conf.bak | sed -i -e 's/internalportcfg="0xfff"/internalportcfg="0xfef"/' -e 's/esataportcfg="0xff000"/esataportcfg="0xff010"/' synoinfo.conf To understand the config settings convert the hex to binary. For example. default internal config is FFF, which is 111111111111 (12 drives). So if you wanted to remove the 5th drive from the internal drive pool you'd need 111111101111 (0 at 5th slot), which is FEF. Then to assign the 5th slot as an esata you need to change FF000 to FF010.

It's very similar to a system I'm currently building using an Asrock E3C224D4I-14S. Today my board came, so I borrowed a buddies i3 CPU just so I can test everything. I'm waiting for my new processor to come (XEON E3-1275L V3). The i3 I borrowed doesn't support VT-d, so I can't passthrough the LSI SAS yet. So I just installed esxi and create a VM with nanaboot. But I'm loving these server features, IPMI, iKVM

viewtopic.php?f=2&t=3052&p=20337&hilit=PID#p20337 I'm sure you can find other examples in the nanoboot thread. just search for VID and/or PID in the thread

Nanoboot has a grub option (by VID & PID) to mask out your usb device (DOM) so it won't show as a drive within DSM.

Any LSI card based on the LSI SAS 2008 controller should work. I use one in my current setup, and it works great. I'm going to be building a new system based on the LSI SAS 2308 controller, and I'm hoping that works as well.

I think I do enough for this community running a website (see sig) with tutorials and what not. It's in my own interest that I'd like to continue this. So, if this comment was towards me, I think it's uncalled for. The only thing I like to see is this community a bit more stable. I have said it before and will say it again. In the say what, 6 months, we had 3 people making boot images and none of them are here! Things come to a halt. Which is a shame I think. So I'm glad Vortex is helping out. I've sent Vortex a message if he could help etc. So, just that I make a comment on some donation thing, doesn't mean I disapprove. It was a general comment. So, enough about donations. Let's focus on the thing at hand, making a boot image for 5.1. Vortex, sorry if my comment put you over the edge, that is not my intention. I would like to see your work. My comment wasn't totally directed at you, more so someone who's posts seem to have disappeared. It's good that someone makes easy guides for noobs who don't want to try to learn how to do the easy things themselves (editing grub menus, converting .imgs to ISOs and VDMKs), but without the people who spend tons of time reverse-engineering DSM none of that stuff would be useful. And I don't mean to come off as insulting to what you do. Vortex wanted to get a system that is used very commonly among those in this community, so he had something to work with so he can try to release modded images. He doesn't really work with virtual machines (at least from what I've read following his work all these years). Personally I'm not interested in that HP machine, since I like my virtual machines.... but I don't want people, who want everything handed to them, pissing off the few people that are left who reverse-engineer and/or release boot images, ect. It's bad enough that gnoboot disappeared, we don't need vortex disappearing too - as I'm sure he'd have helped whoever continues gnoboot/nanoboot's work in some way.

Good works guys, chasing away one of the few who has bypassed securities for past versions of DSM. His work predates XPEnology, and is probably one of the reasons this site even exists. I've personally used his Qnology releases on my intel based systems long before XPEnology even existed http://forum.qnap.com/viewtopic.php?f=9 ... it=qnology If you don't want to donate, then just don't and STFU. Don't complain and cry on forum posts, because probably you have nothing to offer the community yourself.

I figured it would be cool to have a thread where we can show off our custom NAS / Servers. My current system consists of: Motherboard: Intel DQ77KB CPU: Intel i7 3770T RAM: 16GB SODIMM HBA: LSI 9201-8i (IT mode) Storage: 60GB mSATA (ESXI Install and Datastore) Storage: 4 x 3GB WD REDS Storage: 1 x 4GB Samsung (set as eSATA for backups) Storage: Supermicro CSE-M35TQB SAS/SATA Mobile Rack - 5 Bay OS: ESXI 5.5 VM1: Ubuntu 64bit VM2: Synology DSM 5.0 I never got around to completing the custom case. Recently I wanted to play around with ESXI 6 (it's in beta), but lacked another system ideal for virtualization. So I started researching new parts for another system. If all goes well I'll make it my new main NAS / Server and test stuff on my old one. Here's what on it's way now: Motherboard: Asrock E3C224D4I-14S http://www.asrockrack.com/general/productdetail.asp?Model=E3C224D4I-14S CPU: Intel Xeon Processor E3-1275L v3 RAM: 16GB Super Talent DDR3-1600 8GB/512Mx8 ECC Micron Chip Very Low Profile Server Memory HBA: onboard LSI 2308 Storage: Intel FUP8X35HSDK Drive Enclosure - 8 X 3.5" Bays OS: ESXI 6.0 I thought about buying one of those U-NAS cases, but figured I'd have more fun building my own. I figured building something around this shouldn't be too hard: I am going to try to turn my Lian Li Q25 case into this, if it fits. The dimensions, based on 6 x 5.25 bays, will just kinda fit within the Q25's dimensions. I won't know for sure until the bay comes:

The sed command is only for small updates, it's not for full updates. This thread should really be closed as it has nothing to do with 5.1.

/md0 is the DSM install partition. md1 is swap file partition, and md2 is your array volume. if you have multiple volumes, you'll have md3,4, ect. edit: my experience with getting data off a broken array: http://forum.cgsecurity.org/phpBB3/foun ... t2600.html try googling "You cannot log into the system because the disk space is full currently. Please restart the system and try again" you'll find lots with similar problems. You probably have a misbehaving app or service filling it with log files, or mem dumps.

Any chance it will support Supermicro A1SRM-LN7F-2758-O ? It's very similar hardware, well at least the CPU is. It has 7 ethernet ports.. can make it into a router Specifications Mfr Part Number: A1SRM-LN7F-2758-O CPU (Included): Intel Atom C2758 Processor; Supports up to 20W TDP (Eight-Core) Chipset: System-on-Chip Memory: 4x 240pin DDR3-1600/ 1333 UDIMM Slots, ECC/Non-ECC, Max Capacity of 64GB Slots: 1x PCI-Express 2.0 x8 Slot (runs at x4) SATA: 2x SATA3 Ports, 4x SATA2 Ports Video: Aspeed AST2400 BMC Graphics LAN: Intel C2000 SoC i354 Quad Gigabit Ethernet Controller & Intel I210-AT Gigabit Ethernet Controller & Intel i350-AM2 Dual Gigabit Ethernet Controller Ports: 7x USB 2.0 Ports (4 rear, 2 via header, 1 Type A), 1x VGA Port, 2x Serial Ports (1 rear, 1 via header), 7x RJ45 LAN Ports Form Factor: MicroATX, 9.6 x 8.0 inch / 24.38 x 20.32 cm edit: On second thought I actually like your system better.. will have to wait and see

Weird, because the sed command prevents flash update; which would be were gnoboot/nanoboot lives. Here's an example of the script the update process normally runs: autoupd@te.info { "blNeedReboot":true, "buildnumber":4418, "debDir":"/volume1//@smallupd@te_deb", "flashupdateDeb":"flashupdate_5.0-4418-s1_all.deb", "installDeb":["apache-2.2.x-bromolow-bin_2.2.25-4418-s1_all.deb", "lnxessential-bromolow-bin_5.0-4418-s1_all.deb", "samba-3.6.x-bromolow-bin_3.6.9-4418-s1_all.deb", "dsm-bromolow-bin_5.0-4418-s1_all.deb", "dsm-AdminCenter-bromolow-bin_5.0-4418-s1_all.deb", "postgresql-9.3.x-bromolow-bin_9.3.1-4418-s1_all.deb"], "newSmallFixNumber":1, "smallupdateDeb":"smallupdate_5.0-4418-s1_all.deb", "updateType":"smallupdate" } And the sed command, which if applied to the above example spoofs the location where flashupdate_5.0-4418-s1_all.deb is applied (to flashupdateDeb1): sed -i 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info I'm curious what is different that it worked for you guys without halting the update, or messing up your nanoboot.