Diverge

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?

I haven't tried that, but I don't think it will make a difference. I was playing around in the VM bios, and it has 2 IDE controllers built in (primary and secondary), which would be 0:0,0:1,1:0,1:1, since I see my gnoBoot drive attached to the secondary controller after I moved it to 1:0. I can disable primary IDE in the bios, but settings don't stick even after I hit save. Apparently you can extract ESXI virtual machine bios and edit it http://forums.mydigitallife.info/thread ... ols/page10 . I've edited my physical machine bioes before, but that just seems like too much work for testing purposes

I found an easier way to get rid of gnoBoot mounting itself in DSM. just move it to IDE 1:0 instead of 0:0 right in ESXI - no editing of config files necessary. It's no longer listed in /proc/partitions. Only problem now is disk slots 1 and 2 still aren't usable. my last 2 drives out of 12 are mounted as sdm and sdn. DSM looks for disk 1, 2, 3...12 as sda, sdb, sdc...sdl,everything else is ignored for building volumes. my first data disk is SCSI 0:0 and it gets mounted by gnoboot (dsm) as sdc for some reason. edit: I guess because it sees IDE 0:0 and IDE 0:1 even though there are no drives attached to them, and reserves those for sda and sdb.

No thanks (on USB stick), but there must be better way to do it. I'm not complaining, or trying to create work for you. I figure you made gnoBoot cause you like to create and fix stuff I have another ESXI system. It's my main system and has been running for over 6 months on DSM 4.2. It's not based on trantor's builds, its step by step from the ESXI pdf someone made. Anyway, that VM doesn't mount boot as sda. sda is the first data disk. So there must be a way to do it Below is an ESXI 5.1 system with 4 physical 2TB disks using RDM mapping with DSM 4.2. BusyBox v1.16.1 (2013-03-01 01:11:47 CST) built-in shell (ash) Enter 'help' for a list of built-in commands. DiskStation> cat /proc/partitions major minor #blocks name 8 0 1953514584 sda 8 1 2490240 sda1 8 2 2097152 sda2 8 3 1 sda3 8 5 1948780864 sda5 8 16 1953514584 sdb 8 17 2490240 sdb1 8 18 2097152 sdb2 8 19 1 sdb3 8 21 1948780864 sdb5 8 32 1953514584 sdc 8 33 2490240 sdc1 8 34 2097152 sdc2 8 35 1 sdc3 8 37 1948780864 sdc5 8 48 1953514584 sdd 8 49 2490240 sdd1 8 50 2097152 sdd2 8 51 1 sdd3 8 53 1948780864 sdd5 9 0 2490176 md0 9 1 2097088 md1 9 2 5846338944 md2 253 0 5846335488 dm-0 DiskStation> If you want to fix it, somehow, so synoboot isn't mounted by itself as sda, i'll be glad to keep testing for ya It seems DS3612 DSM only looks at sda-sdl for it's 12 data disks. Is it possible to mount gnoboot to something higher than sdl or not at all like above example? Not that I ever plan to use so many disks.

The kernel was built from scratch with Andy's patches and mine. It's very different from Trantor's boot image and kernel. Yeah, I know. I'm just testing stuff, playing around, and pointing out any problems I see. I'm not complaining. If you want to fix them it's up to you.

Something I just noticed playing around. you can't put disks is slots 1 and 2. The first disk starts off in slot 3. I created 12 x 8GB virtual drives, but can only use 10 of them, as nothing goes into slots 1 and 2. Also, I'm pretty sure this happens for both versions of gnoboot DSM 4.3 and 4.5, at least for me, on my system using ESXI 5.5 and a Intel DH61AG motherboard. edit: DS45> cat /proc/partitions major minor #blocks name 8 0 204800 sda 8 1 16033 sda1 8 32 8388608 sdc 8 33 2490240 sdc1 8 34 2097152 sdc2 8 35 1 sdc3 8 37 3654768 sdc5 8 48 8388608 sdd 8 49 2490240 sdd1 8 50 2097152 sdd2 8 51 1 sdd3 8 53 3654768 sdd5 8 64 8388608 sde 8 65 2490240 sde1 8 66 2097152 sde2 8 67 1 sde3 8 69 3654768 sde5 8 80 8388608 sdf 8 81 2490240 sdf1 8 82 2097152 sdf2 8 83 1 sdf3 8 85 3654768 sdf5 8 96 8388608 sdg 8 97 2490240 sdg1 8 98 2097152 sdg2 8 99 1 sdg3 8 101 3654768 sdg5 8 112 8388608 sdh 8 113 2490240 sdh1 8 114 2097152 sdh2 8 115 1 sdh3 8 117 3654768 sdh5 8 128 8388608 sdi 8 129 2490240 sdi1 8 130 2097152 sdi2 8 131 1 sdi3 8 133 3654768 sdi5 8 144 8388608 sdj 8 145 2490240 sdj1 8 146 2097152 sdj2 8 147 1 sdj3 8 149 3654768 sdj5 8 160 8388608 sdk 8 161 2490240 sdk1 8 162 2097152 sdk2 8 163 1 sdk3 8 165 3654768 sdk5 8 176 8388608 sdl 8 177 2490240 sdl1 8 178 2097152 sdl2 8 179 1 sdl3 8 181 3654768 sdl5 8 192 8388608 sdm 8 208 8388608 sdn 9 0 2490176 md0 9 1 2097088 md1 9 2 32883264 md2 253 0 32882688 dm-0 DS45> DS45> fdisk -l Disk /dev/sdc: 8589 MB, 8589934592 bytes 64 heads, 32 sectors/track, 8192 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Device Boot Start End Blocks Id System /dev/sdc1 1 2432 2490240 fd Linux raid autodetect Partition 1 does not end on cylinder boundary /dev/sdc2 2433 4480 2097152 fd Linux raid autodetect Partition 2 does not end on cylinder boundary /dev/sdc3 4609 8185 3662816 f Win95 Ext'd (LBA) Partition 3 does not end on cylinder boundary /dev/sdc5 4616 8185 3654768 fd Linux raid autodetect Disk /dev/sdd: 8589 MB, 8589934592 bytes 64 heads, 32 sectors/track, 8192 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Device Boot Start End Blocks Id System /dev/sdd1 1 2432 2490240 fd Linux raid autodetect Partition 1 does not end on cylinder boundary /dev/sdd2 2433 4480 2097152 fd Linux raid autodetect Partition 2 does not end on cylinder boundary /dev/sdd3 4609 8185 3662816 f Win95 Ext'd (LBA) Partition 3 does not end on cylinder boundary /dev/sdd5 4616 8185 3654768 fd Linux raid autodetect Disk /dev/sde: 8589 MB, 8589934592 bytes 64 heads, 32 sectors/track, 8192 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Device Boot Start End Blocks Id System /dev/sde1 1 2432 2490240 fd Linux raid autodetect Partition 1 does not end on cylinder boundary /dev/sde2 2433 4480 2097152 fd Linux raid autodetect Partition 2 does not end on cylinder boundary /dev/sde3 4609 8185 3662816 f Win95 Ext'd (LBA) Partition 3 does not end on cylinder boundary /dev/sde5 4616 8185 3654768 fd Linux raid autodetect Disk /dev/sdf: 8589 MB, 8589934592 bytes 64 heads, 32 sectors/track, 8192 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Device Boot Start End Blocks Id System /dev/sdf1 1 2432 2490240 fd Linux raid autodetect Partition 1 does not end on cylinder boundary /dev/sdf2 2433 4480 2097152 fd Linux raid autodetect Partition 2 does not end on cylinder boundary /dev/sdf3 4609 8185 3662816 f Win95 Ext'd (LBA) Partition 3 does not end on cylinder boundary /dev/sdf5 4616 8185 3654768 fd Linux raid autodetect Disk /dev/sdg: 8589 MB, 8589934592 bytes 64 heads, 32 sectors/track, 8192 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Device Boot Start End Blocks Id System /dev/sdg1 1 2432 2490240 fd Linux raid autodetect Partition 1 does not end on cylinder boundary /dev/sdg2 2433 4480 2097152 fd Linux raid autodetect Partition 2 does not end on cylinder boundary /dev/sdg3 4609 8185 3662816 f Win95 Ext'd (LBA) Partition 3 does not end on cylinder boundary /dev/sdg5 4616 8185 3654768 fd Linux raid autodetect Disk /dev/sdh: 8589 MB, 8589934592 bytes 64 heads, 32 sectors/track, 8192 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Device Boot Start End Blocks Id System /dev/sdh1 1 2432 2490240 fd Linux raid autodetect Partition 1 does not end on cylinder boundary /dev/sdh2 2433 4480 2097152 fd Linux raid autodetect Partition 2 does not end on cylinder boundary /dev/sdh3 4609 8185 3662816 f Win95 Ext'd (LBA) Partition 3 does not end on cylinder boundary /dev/sdh5 4616 8185 3654768 fd Linux raid autodetect Disk /dev/sdi: 8589 MB, 8589934592 bytes 64 heads, 32 sectors/track, 8192 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Device Boot Start End Blocks Id System /dev/sdi1 1 2432 2490240 fd Linux raid autodetect Partition 1 does not end on cylinder boundary /dev/sdi2 2433 4480 2097152 fd Linux raid autodetect Partition 2 does not end on cylinder boundary /dev/sdi3 4609 8185 3662816 f Win95 Ext'd (LBA) Partition 3 does not end on cylinder boundary /dev/sdi5 4616 8185 3654768 fd Linux raid autodetect Disk /dev/sdj: 8589 MB, 8589934592 bytes 64 heads, 32 sectors/track, 8192 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Device Boot Start End Blocks Id System /dev/sdj1 1 2432 2490240 fd Linux raid autodetect Partition 1 does not end on cylinder boundary /dev/sdj2 2433 4480 2097152 fd Linux raid autodetect Partition 2 does not end on cylinder boundary /dev/sdj3 4609 8185 3662816 f Win95 Ext'd (LBA) Partition 3 does not end on cylinder boundary /dev/sdj5 4616 8185 3654768 fd Linux raid autodetect Disk /dev/sdk: 8589 MB, 8589934592 bytes 64 heads, 32 sectors/track, 8192 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Device Boot Start End Blocks Id System /dev/sdk1 1 2432 2490240 fd Linux raid autodetect Partition 1 does not end on cylinder boundary /dev/sdk2 2433 4480 2097152 fd Linux raid autodetect Partition 2 does not end on cylinder boundary /dev/sdk3 4609 8185 3662816 f Win95 Ext'd (LBA) Partition 3 does not end on cylinder boundary /dev/sdk5 4616 8185 3654768 fd Linux raid autodetect Disk /dev/sdl: 8589 MB, 8589934592 bytes 64 heads, 32 sectors/track, 8192 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Device Boot Start End Blocks Id System /dev/sdl1 1 2432 2490240 fd Linux raid autodetect Partition 1 does not end on cylinder boundary /dev/sdl2 2433 4480 2097152 fd Linux raid autodetect Partition 2 does not end on cylinder boundary /dev/sdl3 4609 8185 3662816 f Win95 Ext'd (LBA) Partition 3 does not end on cylinder boundary /dev/sdl5 4616 8185 3654768 fd Linux raid autodetect Disk /dev/sdm: 8589 MB, 8589934592 bytes 64 heads, 32 sectors/track, 8192 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Disk /dev/sdm doesn't contain a valid partition table Disk /dev/sdn: 8589 MB, 8589934592 bytes 64 heads, 32 sectors/track, 8192 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Disk /dev/sdn doesn't contain a valid partition table DS45> first data drive always starts at sdc for me. The 11 and 12 disks get ingnored since DSM isn't looking at anything past sdl, since it's not using sda and sdb for data drives for some reason. sda is gnoBoot I guess.

It seems to install fine for me (besides it saying it's installing to 2 disks), then stalls here on boot: edit: it seems to have installed, it was at a new IP. The console is buggy though... it's like lagged. can't see what you type until you hit enter. edit2: after a reboot of first boot, no more console lag, also didn't see that message again.

My image in my previous post was from before trying to install. I tried with an 8GB drive like you said, and it still said it was installing to two disks, but the install worked perfectly. But like I said, trantor's boot image just says it sees one disk, so I guess it's just a cosmetic bug during install process. Thanks for making this, it's pretty cool! And thanks for pointing out my disk size issue for testing, it got me past my other install issue

Just tried new one, same problem here. I tried what you said, but there is no awk. So here's the best I can do for info about partitions: btw, i tied both DMS 4.3 and 4.5 gnoBoot's.

Fixed - download alpha2 and dd it again, no need to reinstall. Just tested it, still the same. I have gnoBoot IDE, and one SCSI to test install, and it wants to write to 2 disks. When I try the same with trantor's boot image it works correctly and doesn't try to install to the boot drive.

I just set up another ESXI system to play around with. I followed all the instructions, and able to boot gnoBoot. But when I got to the webpage to start that install process it's including the boot drive (one with gnoBoot on it) as part of the disks it is going to wipe and install on. Am I missing a step so that gnoBoot doesn't see it's own drive during the install?

ESXI build pretty please! Will even send a donation via paypal if you can make one

sounds like a port forwarding issue. do you have whatever ports it needs forwarded?

recheck your settings against the doc. Specifically the IDE/SATA types used. They change on their own when adding stuff to the VM.

Well ESXi is it's own host OS. The others you need to run on top of another OS. That's one difference.

I'm interested. I wish someone make a guide on whats needed to either compile or modify the official .pats, specifically for ESXi. XVortex already released some modified pats for Qynology http://forum.qnap.com/viewtopic.php?f=9 ... &start=510 But that for running on actual hardware, and not in a VM. I used his files long ago, before XPnology.

Double check your settings against the idiots guide. Make sure your drives are using the correct mode (paravirtual, or whatever the guide said - i forget), as that setting will keep reverting back to something else each time a drive is added to the VM (or something like that.. I forget what makes it change). I used the exact same guide, once I made sure none of the settings changed on me everything worked great, and still does

Hey Diverge i'm also running a dq77kb. The dq77kb is perfect for esxi, i'm running it with a x4 HBA card and 2 additional GigE NIC's on the full/half height mini-pcie slots. Are you using Vga passthrough for your HTPC? Nope, I haven't passed anything through. For the HTPC part, my Windows 8 VM isn't even activated. The activation nagging is no bother, since it's not even used locally. It only serves as my WMC host. I use an Xbox 360 in WMC extender mode (that remotely uses the WMC on the win 8 VM), that's connected to my TV.

Nice, I have a Lian-LI PC-V354 collecting dust. Been thinking maybe I should build my EXSI into it, and ditch the smaller Lian LI Q16 (since I don't really need it at my TV for WMC anymore, using virtualized windows and a Xbox 360 for WMC extender).

I'm using RDM. I could use VT-d though, as I just got a PCIe card that can mount my mSATA (for ESXI and datastore), then pass through the onboard sata controller (at least I think I can, i'm new to this stuff).

interested, Your system looks pretty unique. What does it consist of? EXSI? Raw Device Mappping for harddrives, Direct I/O passthrough?

I was using iscsi on my xpenology esxi box before I broke my data volume partitions. It worked fine for me, although I had never used iscsi before, so I had to do some reading to figure it out. My ESXi consists of 2 VM's: Synology NAS Windows 8 w/ Windows Media Center (my HTPC). I created an iscsi on the NAS so I can set it as my record drive for TV in the WMC VM. It worked well except for the part I had to manually connect the iSCSI on windows after each reboot (must be a bug, or I don't know what I am doing ). Here's my custom Lian Li Q16 which is now my ESXI box. https://picasaweb.google.com/1049792069 ... ianLiPCQ16 except the box consists of the following now: Intel DQ77KB Intel i7 3770T 45W CPU Crucial 2 x 8GB SODIMM DDR3 MyDigitalSSD 64GB Smart Series SATA III (6G) SandForce mSATA SSD - ESXI Install and Datastore Samsung F4 HD204UI 2TB x 4 - Synology SHR Array SilconDust HD Prime Network Cablecard Tuner Xbox 360 WMC extender to watch TV

I have 1 data volume partition. I'm not sure about md2 or md3 but I can do some investigation when I get home tonight. Thanks for the reply. Things just got even weirder, but I'm still curious on how this all works. Eventually if I can't figure it out or corrupt the drive contents I'm gonna start over fresh (since I have all the data off it now), so I'll see how my partition layout is supposed to be and how it differs from everyone who posts here.

Can you guys that posted your info also do a: fdisk -l so I can see partition types Maybe I created my #5 partition with the wrong type.

Thanks 'interested'! This throws me in a loop and confuses me. Your array doesn't have an sdx3 partition. Basically I'm trying to piece back together my array, without knowing all the partitions that existed. My array in it's broken state consisted of the following: DiskStation> sfdisk -l /dev/sda1 256 4980735 4980480 fd /dev/sda2 4980736 9175039 4194304 fd /dev/sda3 9437184 3907015007 3897577824 f /dev/sdb1 256 4980735 4980480 fd /dev/sdb2 4980736 9175039 4194304 fd /dev/sdc1 256 4980735 4980480 fd /dev/sdc2 4980736 9175039 4194304 fd /dev/md01 0 4980351 4980352 0 /dev/md11 0 4194175 4194176 0 With testdisk I found my data partition. I confirmed that I did find my data partition, by manually putting it together using losetup. Got all my data off it, and now trying to fix it to learn how. I outlined what I did here if anyone is interested: http://forum.synology.com/enu/viewtopic ... 15&t=71546 Based on graymouser's info I wrote a new partition table to all my drives. I assume my array consisted of the DSM partition sd[abc]1, the swap sd[abc]2, then an extended partion sd[adb]3. then logical partition sd[abc]5. Everything I had correlated to graymousers array setup, but he had different sized drives, so his end point for his data partition is different. But I don't know why I can't build the array manually with the new sd[abc]5 partitions vs creating loop devices w/ losetup. I can still see my data if I create loop devices again and assemble the array with them rather then the partitions. Here's my current setup w/ my recently rewritten partition tables: DiskStation> sfdisk -l /dev/sda1 256 4980735 4980480 fd /dev/sda2 4980736 9175039 4194304 fd /dev/sda3 9437184 3907015007 3897577824 f /dev/sda5 9453280 3907012583 3897559304 fd /dev/sdb1 256 4980735 4980480 fd /dev/sdb2 4980736 9175039 4194304 fd /dev/sdb3 9437184 3907015007 3897577824 f /dev/sdb5 9453280 3907012583 3897559304 fd /dev/sdc1 256 4980735 4980480 fd /dev/sdc2 4980736 9175039 4194304 fd /dev/sdc3 9437184 3907015007 3897577824 f /dev/sdc5 9453280 3907012583 3897559304 fd /dev/md01 0 4980351 4980352 0 /dev/md11 0 4194175 4194176 0 The only thing I can think of is somehow I have the wrong end point for partition 5. Any expert advice is welcome, and more sfdisk -l info from other peoples systems will be helpful