Diverge

If you have an array linux is not automatically going to see your data, you'd need to manually assemble the array. It makes it even harder if your partition info got destroyed. Here's my adventures in recovering a lost array due to wiped partition info: http://forum.cgsecurity.org/phpBB3/foun ... t2600.html If your partition info is intact, it should be a lot easier than what I went through. Good luck!

Thanks for the update. I personally like using the stock synology PATS, and would rather not rely on modified pats. I was hoping there would be some way to prevent the updates from messing with the boot image. Editing the updater script between download and pressing update works, and that just seems to prevent a portion of the updater script from writing to boot. Can the boot image be set to read only, or does info get written to it under normal use? And if I seem to not know what I am talking about, can you explain how different parts of synology DSM work (boot, updates, ect)?

I dunno what to tell you. I had similar issue a long time ago when I setup DSM 4.2 in ESXI using the idots guide, but eventually got it to work somehow. I haven't messed with new installs until recently w/ gnoboot (which supposedly has fixes to prevent the issues you're having). Try a different boot img, or gnoboot, or maybe someone else has advice for you. edit: to sum up the problem, it's nothing you're doing wrong. An untouched PAT image writes to the boot drive. From what I understand there's two ways around this; either you have patched PAT files, or boot images that prevent it (and also let you use stock PATs right from synology).

At what point are you getting the error? the first boot, or after trying to install a PAT file? If it's the later, then it's because the install process of the PAT is writing over parts of you boot drive and messing it up. Some people get around this by making a copy of the boot drive before you try to install a PAT, then replace the messed up one by the PAT install with the unbroken copy you made. If it's the initial boot I dunno what to say. I been playing with gnoboot's boot images and they work pretty nice, at least for testing purposes. I haven't testing any of the other boot images on here, but his doesn't get grub errors after installing.

weird, i never had any problems using plex PMS on beta 5. I forget if I manually installed initially, but that's how I always update to the latest PMS (downloading spk and manual install).

The idiots guide in this thread works fine, I've followed it for my first esxi VM's. The easiest to way to convert images is to use StarWind Software V2V Image Converter. It's free, you can find mirrors from download sites so you don't have to register at starwind to get it. The alternative to that is using a live linux cd in a VM, with a virtual IDE HD attached to it. Transfer the IMG to the running linux VM and then dd if=name_of_image.img of=/dev/sda (or whatever drive letter the virtual IDE gets assigned. power down linux and move the virtual IDE drive to your synology VM to boot off of.

First I'd like to thank you for all your work But I have one question. Does dis mean, if using XPEnology gnoBoot it is possible to simply use a orginal pat file from the Synology website? And if I did understand it correctly also online updates will be working without modification? Thanks for clarification. Regards Vlaves You can use original pats, I have every time I played with a new install. I'm not 100% sure about the updates, since I followed a guide here that changes the updater script just before you apply the updates so it doesn't try to reflash over the boot flash (i'm not sure if there is any built in protection in gnoboot to prevent that - would be cool if there was ).

I recently moved my ESXI install and datastore over to a PCIe mSATA card, and my test build is running good so far. Later I'll move that card to a system that can passthrough hardware and try to pass through the onboard SATA controller of my motherboard (DQ77KB). In case anyone is looking for a good card that has drivers available for ESXI, here's the one I picked up for ~$25 on ebay. http://www.ebay.com/itm/mSATA-SATA-3-HD ... 1067002021 It uses the ASM 1061 chipset, and the drivers can be found here http://vibsdepot.v-front.de/wiki/index.php/Sata-xahci If all goes well with passing through the onboard SATA controller, I also picked up one of these to turn my onboard mSATA slot into a sata port so I can add a 5th disk to my array http://www.ebay.com/itm/290955489021?ss ... 1439.l2649

Kinda crazy that somehow people are hacking miners into other peoples NASes. I personally don't leave any ports open on my LAN but SSH on a non standard port, and tunnel anything I need to do through SSH. The times when I did have FTP open on my NAS, the logs were pretty crazy with the amount of bots trying to bruteforce in.

Good to know, I was thinking maybe it was something I was doing wrong when going from .IMG's to virtual disks, or adding/removed stuff from the images (zImage, rd, kernel mods, ect).

cool, I'll give it a test whats with the download changes? that jdownloader tool wants to install browser tool bars (no thanks)... edit: found an online site that decrypts the DLC file. edit2: did a little testing, seems to work good. haven't attached my array yet. will try that tomorrow.

Just in case anyone who's playing with DSM 5 didn't know, update 1 has been released. I successfully updated via the method posted here viewtopic.php?f=2&t=2049.

Okay, thanks. I wasn't sure I did it correctly the first time when I renamed the file. I guess that's what works for now. edit: just posting back that I was able to get all 12 disks working in the same VM I made earlier that was ignoring slots 1 and 2. I had to remove ata_piix.ko from the ramdisk, and the next boot DSM said it reassmbled my array and needed to do a scandisk and reboot. Rebooted and all was good I been having fun trying to break my gnoboot/Xpenology VM. So far I haven't lost any of my test data moving my array around to all different VM's, rebuilding arrays, expanding, ect

Thanks. Maybe I should have done that prior to adding my array, because the change has no effect on how the disks fill the slots now. I double checked lsmod | grep ata_piix after rebooting, and it's not loaded. edit: I just removed array from VM and rebooted so synoboot disk was only one present. ata_piix is loaded. so I did it again while setup like this (no array), rebooted, and it's back again. any ideas?

gnoboot, nope, i never changed that in grub. I'm playing with fresh VM, newly assembled gnoboot (rd, zImage), with the same array. whats the correct way to keep ata_piix from loading? Last time I mounted rd and just renamed it... not sure if that is the correct way to do it.

edit: Something is weird with my VM, it keeps powering off. I might just delete it all and start fresh. But I have a log for you if you're curious with what might be going on. edit2: gnoboot, I PMd you the link to logs. They were too big to send in a message.

gnoboot, i'll try what you said and see if I can get the logs to you. I also just saw that a decent amount of people are losing their partitions when updating from dsm 4.x to 5, and it's supposedly a bug that synology will fix http://forum.synology.com/enu/viewtopic ... 32&t=79886 . Just a heads up for people paying around with drives with unbacked up data

My post also might be helpful in getting back your missing data : http://forum.cgsecurity.org/phpBB3/foun ... t2600.html . I got a bunch of help from Remy, and was able to figure out some stuff on my own when his suggestions didn't work as expected. So I figured I'd post my step by step experience in case it's helpful to anyone I never was able to repair my partition tables so DSM worked correctly. But I was able to manually reassemble my array, then get all my data off my drives and build a new virtual DSM system.

All my playing has been with DSM 5 w/ gnoboot. Here's a summary of steps I took: 1) VM #1, with 10 disk array using gnoboot alpha 0 for DSM 5 working okay (just couldn't use slots 1 and 2 - they were reserved for IDE controller) 2) created new VM #2 w/ gnoboot alpha 1 for DSM 5 w/ single disk. 3) powered down VM #2, removed single disk. Added 10 disk array from VM #1. 4) booted up VM #2, saw weird stuff shown in my screen caps from previous post. gnoboot turns itself off. 5) booted up VM #2, it boots fine. I verify my test data is still there. It was. 6) shut down VM #2, added 2 more disks. One blank, the other from my initial test of VM #2. 7) booted VM #2, saw wierd stuff again. gnoboot turns itself off. 8) booted VM #2 again, all good. Booted into DSM, all 12 disk shown in the 12 slots. Now have volume 2 from since one of the drives had data from initial tests of VM #2. 9) deleted volume 2 with DSM disk managment. Expanded volume 1 from 10 disk array to 12 disk array. All good, data still there. 10) shut down VM #2 . Create 13 disk for testing the weird shutdown at boot. 11) booted VM #2, saw same stuff I been seeing. gnoboot turns itself off. I removed disk 13 from array. 12) repeat steps 10-13 to see weird stuffs. None of my testing consisted of removing a drive already in the array. Just added new drives (additional) to VM and rebooting. All disks added were when power was off (VM off). All my disks are virtual disk just for testing.

Here's the best I can do, since it floods the screen with stuff. When it detects a disk change (add/remove), synocfgen fails. On normal boot, synocfgen follows after last module load, and is close to one of the last things displayed before login prompt. When it detects a disk change, there's a bunch of stuff between last module load, and the synocfgen check, then a bunch of stuff after it, it unmounts all the drives and powers off. You can reproduce it easily by just adding and removing same disk over and over (i created a tiny disk for testing). edit: it took me a bunch of reboots to get it to boot normally again. Here's what it looks like at first normal boot after going through all that stuff:

I just successfully migrated 10 disks from an earlier version of gnoboot to the latest for dsm 5 (alpha1). Then 2 more disks, one blank, and one used as a single disk dsm install. It successfully migrated both my 10 disk array, and had an additional volume from the 1 disk dsm install, as well as the one blank disk. I was able to remove volume 2, and add the other 2 disks to my array for a total of 12. It retained all my data too something I noticed, is when gnoboot/dsm detects disk changes on boot it will do some stuff then shutdown. you have to manually restart it, then all is good.

I'm not sure if I removed ata_piix.ko correctly so my VM of DSM doesn't see ata controllers, and start the raid array at slot 3, but I got it to work I guess. I booted into gnoboot (after putting in new zImage and rd) and logged into root and renamed ata_piix.ko to ata_piix.ko.old at /lib/modules/ then reboot and proceeded to install. With no other VM drives (but gnoboot), the installer still says it sees one disk. At console, cat /proc/partitions returns /dev/sda (which I guess is gnoboot still, and why the installer sees 1 disk). But it can't install to it, which is good - gets an error. With an additional disk the installer says it sees 2 disks, but proceeds to install to just the one, and it installed to slot 1

You know there is an easier way.... Just use starwind v2v converter. It will convert the .IMG to .vmdk which with is working fine for me on DSM 5 Thanks for heads up. Much easier than booting up DSL live CD in a VM.

Thanks for this info. From it I created a formula in a google drive spreadsheet. Just paste the following into a cell and it will calculate the password, and always update for current date. =CONCATENATE(DEC2HEX(MONTH(NOW())), TEXT(MONTH(NOW()) ; "*0#0") , "-", DEC2HEX(DAY(NOW())), TEXT((GCD(DAY(NOW()),MONTH(NOW()))) ; "*0#0"))

How would modules work? Would you then need to add/remove a particular module for lets say in my case IDE, at initial boot, prior to installing? http://en.wikipedia.org/wiki/Loadable_kernel_module For virtual machines, gnoboot image will not add any ATA drivers but you can still have an option to load it after installation. But this would bring problems to baremetal users during installation if drivers are not available. EDIT: modular ATA drivers working - http://xpenology.com/forum/viewtopic.php?f=2&t=2152&p=11010#p11010 Thanks. I'm learning about all this stuff as I play around with your gnoBoot I hope i'm not filling your thread with noob stuff hehe