Diverge

How do you get password for alpha 10? I don't understand what the following means on the notes for alpha 10: I've posted comments on your blog, and active in your thread.. but dunno how a password will magically get to me

I think you have a couple issues. 1) your virtual disks need to be 8GB each, minimum (for DSM array). 2) you should use alpha7.img if you're using zImages after alpha6, as gnoboot changed how things work in the grub menus, and packed everything into the zImages.

I was using windows programs to do it, but they are PIA to get working correctly, so I figured out how to do it in linux. fdisk -l image.img. you'll see it has a partition that starts at sector 63. And that each sector is 512 bytes. so then setup a loop device of the image file starting at that offset (so you can access the partition). Then mount it. delete the old zImage, copy over new one. Sync (not sure if needed - can't hurt?). unmount it. delete the loop device. you now have updated image file I created a little script that does it for me and shows the stats of the old zImage and new one so I know it updated. BTW, you can do this with both a image file, or esxi vdmk. losetup /dev/loop0 gnoboot-flat.vmdk -o $((63*512)) mount /dev/loop0 /mnt stat /mnt/zImage rm /mnt/zImage cp zImage /mnt chmod 644 /mnt/zImage stat /mnt/zImage sync umount /dev/loop0 losetup -d /dev/loop0 when using my script, i have both the image file and new zImage in the same path as the script.

What file are you working with? Alpha 9 isn't a disk image, it's a kernel zImage. Some of the prior release were actual disk images that have grub, and a zImage on them. you need to swap out the zImage from one of the older release that was a disk image.

it might be related to these: http://forum.synology.com/enu/viewtopic ... 32&t=81398 http://forum.synology.com/enu/viewtopic ... 32&t=80742 In the first one is a link to a new pat that patches login. Not sure what it does, or if it's for your specific login issue. If you're brave, test it out

it's a common issue it seems. read the official synology forums for dsm 5 beta http://forum.synology.com/enu/viewforum.php?f=232

I'm only getting ~50MB/s too, with paravirtual. Used to get 100MB/s with paravirtual on releases prior to using gnoboot. Then again, that was on DMS 4.2, and esxi 5.1. switched to esxi 5.5, gnoboot , and dsm 5 beta at the same time, so not sure which is the culprit.

Is alpha 9 released? I don't understand why make us jump through hoops for downloads. I can't tell if these survey things lead to download links or are just place holders of some kind, because I've never gotten a link from one. edit: i just noticed this on the blog for alpha 9 I guess that means they are place holders? Why put them in the first place? I see comments from people thanking for new release, that it fixed stuff..

Ignore my previous posts about LSI controller. Since i'm not passing it through via VTd and using RDM, it's using VMware PVSCSI Host Adapter But I plan to move my LSI controller to my machine that has VTd, so hopefully it's fixed

I use iSCSI w/ gnoboot alpha 5 (DSM 5). It works okay here, at least in that version.. I think he may have broken it in some versions. I have mine setup and used in a Windows 8.1 esxi VM, and WMC uses it for it's record drive. both DSM 5 and WMC are VMs, in the same esxi server.

with alpha 8 you have to use dsm 4.3 for new installs, it won't let you use dsm 5 beta - bugs. if you want to use dsm 5 you need to use a prior version of gnoboot for install, then change to alpha 8 if you want. did you try with maybe 1-2 test disks first, rather than 24?

I have a LSI 9201-8i, flashed with latest LSI 9211-8i IT firmware and bios and it works fine with gnoboot alpha 8 here. I didn't have to do anything. Running in an esxi 5.5 VM. Disks setup as RDM is esxi. @ EmmTeh How is your system setup? esxi, baremetal, VTd, RDM?

They are physical RDM. No go for DSM. But other OS can read temp; example open media vault can. Just seems synodisk doesn't like RDM.

How are you presenting your disk drives? I've passed through my sata controller to xpenology and it reads the temps just fine. Well I have 2 systems right now; a test system on a DH61AG w/ i3 2120T, and my main is a DQ77KB w/ i7 3770T. My main system is setup with esxi 5.5, and configured for RDM with onboard intel controller. My test system is setup with esxi 5.5, and RDM with LSI 9201-8i controller. I haven't tried passing through my LSI controller yet, since my test system doesn't support VTd. I plan to eventually move the LSI to my main system as I'm building a new custom enclosure for everything, and will probably test out passing through the LSI controller then. In any event, smartctl built into DSM can read the temps on the RDM'd drives, also other OS's can read temps fine. It's just synodisk that doesn't like RDM I guess.

Any chance of getting synodisk to report hard drive temps correctly in VM? I know this plagues all the XPenology releases, so I don't really expect much. Just not sure why it doesn't work since smartctl can read temps just fine, but synodisk returns -1 (it actually returns -1 for any /dev/sdX you use, even drives that don't exist).

I just bought an LSI 9201-8i (oem only) from ebay for $75. It's basically a 9211-8i w/o raid (just IT mode), and can use 9211-8i bios/firmware. I'm kinda noob when it comes to raid/hba controllers. But if you intend to use it for synology, then you probably want DSM to be handling the raid, so you wouldn't really want to use a controller in raid mode. IR = raid mode, IT = non raid. Here's a quick thread I just found about IT mode http://forums.servethehome.com/raid-con ... -mode.html I have mine working good in my test system under esxi 5.5 and using gnoboot w/ DSM 5. I don't think I installed any drivers for esxi, unless they were included in other driver packs I installed prior. And I didn't have to do anything special with gnoboot.

How do you deal with the fact that Windows wants to format the newly mounted virtual disk because it does not recognize the format? ImDisk is supposed to read ext2/3 partitions, so it should read the disks in windows if its working correctly.

How do you deal with the fact that Windows wants to format the newly mounted virtual disk because it does not recognize the format? ImDisk is supposed to read ext2/3 partitions, so it should read the disks in windows if its working correctly.

I kinda find it a PITA too, but I usually get all his releases working. I mounted a previous version image. deleted it's zImage and rd, and removed all the grub menu stuff, then copied over the newer stuff. Then converted the image to vdmk with StarWind V2V Image Converter. Then upload it to my esxi datastore to be used in my VM. my only issue is rmmod seems to not be working anymore. So I can't prevent kernel mods from loading. edit: I'm now playing with LSI 9201-8i controller on my test system (~$75 on ebay, can be flashed with 9211-8i IT firmware/bios). Seems to work fine so far. But I need more disks to test with. I had to do the same with alpha8. Anybody still having issues, should install ImDisk Virtual Disk. It can mount .img files as a r\w volume within windows. Copy the new files over and unmount which saves all the changes you made ImDisk also lets you create a new .img file by right clicking on the mounted volume. I use the same program. I installed so many windows ext2/3 mounting programs to try to find one that works. ImDisk was the only one that worked reliably. I didn't know about the save as new image function, thanks!

I kinda find it a PITA too, but I usually get all his releases working. I mounted a previous version image. deleted it's zImage and rd, and removed all the grub menu stuff, then copied over the newer stuff. Then converted the image to vdmk with StarWind V2V Image Converter. Then upload it to my esxi datastore to be used in my VM. my only issue is rmmod seems to not be working anymore. So I can't prevent kernel mods from loading. edit: I'm now playing with LSI 9201-8i controller on my test system (~$75 on ebay, can be flashed with 9211-8i IT firmware/bios). Seems to work fine so far. But I need more disks to test with. I had to do the same with alpha8. Anybody still having issues, should install ImDisk Virtual Disk. It can mount .img files as a r\w volume within windows. Copy the new files over and unmount which saves all the changes you made ImDisk also lets you create a new .img file by right clicking on the mounted volume. I use the same program. I installed so many windows ext2/3 mounting programs to try to find one that works. ImDisk was the only one that worked reliably. I didn't know about the save as new image function, thanks!

Thank you Diverge for your answer. I don't have Esxi, but i can try to use your method on my physical hardware. Thanks again. Make sure you don't delete whole grub folder in previous image file, you need certain files not contained in new release. Just stick to deleting the menu stuff.

Thank you Diverge for your answer. I don't have Esxi, but i can try to use your method on my physical hardware. Thanks again. Make sure you don't delete whole grub folder in previous image file, you need certain files not contained in new release. Just stick to deleting the menu stuff.

I kinda find it a PITA too, but I usually get all his releases working. I mounted a previous version image. deleted it's zImage and rd, and removed all the grub menu stuff, then copied over the newer stuff. Then converted the image to vdmk with StarWind V2V Image Converter. Then upload it to my esxi datastore to be used in my VM. my only issue is rmmod seems to not be working anymore. So I can't prevent kernel mods from loading. edit: I'm now playing with LSI 9201-8i controller on my test system (~$75 on ebay, can be flashed with 9211-8i IT firmware/bios). Seems to work fine so far. But I need more disks to test with.

I kinda find it a PITA too, but I usually get all his releases working. I mounted a previous version image. deleted it's zImage and rd, and removed all the grub menu stuff, then copied over the newer stuff. Then converted the image to vdmk with StarWind V2V Image Converter. Then upload it to my esxi datastore to be used in my VM. my only issue is rmmod seems to not be working anymore. So I can't prevent kernel mods from loading. edit: I'm now playing with LSI 9201-8i controller on my test system (~$75 on ebay, can be flashed with 9211-8i IT firmware/bios). Seems to work fine so far. But I need more disks to test with.

how do I remove kernel mods in alpha 8? I edited menu_alpha.lst to: kernel /zImage sn=B3JN00310 rmmod=ata_piix but ata_piix is still loading, and my drives start off at slot 3 instead of 1.