supernoman
-
Posts
12 -
Joined
-
Last visited
Posts posted by supernoman
-
-
I got 918+ loaded on ESXi 6.7 but only 5 of 7 drives from HBA showing up on 1.04b loader on DSM 6.2.1-23824 Update 6. DSM shows 14 slots available.
I have another VM running 1.03b and 3615sx and the same HBA will show all 7 drives in DSM 6.1.7-15284 Update 3.
Any help on getting all 7 showing up on 918+?
-
BTW, I have that CPU in my old NAS. It's great for NAS but would probably be pretty bad/slow as an ESXi CPU running multiple VMs.
-
FYI - I tested VMDirectPath as follows...
1. Did a bare metal install on a spare PC with a couple of 1TB drives. Copied some test data to volume1
2. Moved 1TB drives to the T20 and connected them to the Marvell SATA controller.
3. Configured PCI-e Pass-through in the vSphere Native Client - connected the Marvell card directly to my test DSM VM.
4. Confirmed that the drives and volume1 was accessible in the test DSM VM - tested both reading and writing to volume1.
I haven't moved my 'production' drives to the T20 yet as I need to sort out the config of all my apps first (SABNZBD+, Plex, SickRage, etc.) - the apps will reside on separate DSM VMs in the new setup (I want to separate file serving, downloading and media streaming functions).
So, for this setup, if you don't mind me asking: When you set up ESXi what did you do for a primary data store? I've got ESXi 6 installed on a USB flash drive currently and I don't see how you can proceed with configuring a VM for XPEnology without a data store. I'm probably overlooking something simple, but ideally, I'd like ESXi to use the XPEnology volume for VM storage if possible. Is that even possible?
I'm running esxi 6 with direct IO as well. I'm booting off thumb drive for esxi. It doesn't natively support onboard sata controllers but I installed a user mod to enable it. I have an SSD off the motherboard sata controller as datastore1. xpenology runs off the SSD configured with small boot vm disk and secondary 32gb vm disk that shows up as volume1 to be the default share for syno apps. I followed the esxi tuturial on here. I have 2 dell 310 8 port cards flashed to IT mode that I passthrough to xpenology. I had to go the sata ssd route since I couldn't use the raid cards as a datastore and as a passthrough device.
-
In ESXi actual setup, bootloader file XPEnoboot_DS3615xs_5.2-5644.4.vmdk is used as boot disk. (probably with value Virtual Device Node - IDE (0:0)).
The goal is replace this disk with new boot loader XPEnoboot_DS3615xs_5.2-5644.5.vmdk.
That is the goal. Should I just power down the VM and copy XPEnoboot_DS3615xs_5.2-5644.5.vmdk over to XPEnoboot_DS3615xs_5.2-5644.4.vmdk and power on or is there a way to replace the boot disk without creating a new VM.
-
In ESXi actual setup, bootloader file XPEnoboot_DS3615xs_5.2-5644.4.vmdk is used as boot disk. (probably with value Virtual Device Node - IDE (0:0)).
The goal is replace this disk with new boot loader XPEnoboot_DS3615xs_5.2-5644.5.vmdk.
That is the goal. Should I just power down the VM and copy XPEnoboot_DS3615xs_5.2-5644.5.vmdk over to XPEnoboot_DS3615xs_5.2-5644.4.vmdk and power on or is there a way to replace the boot disk without creating a new VM.
-
So I had created a xpenoboot folder and added the .4 vmdk. I just uploaded .5 vmdk to same folder.
-rw-r----- 1 root root 17891328 Feb 15 16:38 XPEnoboot_DS3615xs_5.2-5644.4.vmdk
-rw-r--r-- 1 root root 18153472 Feb 20 15:18 XPEnoboot_DS3615xs_5.2-5644.5.vmdk
When I created the VM, I named it xpenology and pointed it to existing vmdk as instructed by tutorial. Here are the contents of the xpenology VM folder.
-rw------- 1 root root 65536 Feb 17 18:11 XPEnoboot_DS3615xs_5.2-5644.4.vmdk-s001.REDO_qKbRMv
-rw------- 1 root root 379 Feb 17 18:11 XPEnoboot_DS3615xs_5.2-5644.4.vmdk.REDO_qKbRMv
-rw-r--r-- 1 root root 174680 Feb 15 18:12 vmware-3.log
-rw-r--r-- 1 root root 666749 Feb 15 22:26 vmware-4.log
-rw-r--r-- 1 root root 158776 Feb 15 23:08 vmware-5.log
-rw-r--r-- 1 root root 42453 Feb 17 18:08 vmware-6.log
-rw-r--r-- 1 root root 42453 Feb 17 18:09 vmware-7.log
-rw-r--r-- 1 root root 42453 Feb 17 18:09 vmware-8.log
-rw-r--r-- 1 root root 2079417 Feb 21 21:14 vmware.log
-rw------- 1 root root 171966464 Feb 17 18:11 vmx-xpenology-4250321199-1.vswp
-rw------- 1 root root 0 Feb 15 22:26 xpenology-fd56c12f.vswp
-rw------- 1 root root 34359738368 Feb 21 21:14 xpenology-flat.vmdk
-rw------- 1 root root 8684 Feb 21 21:04 xpenology.nvram
-rw------- 1 root root 471 Feb 17 18:11 xpenology.vmdk
-rw-r--r-- 1 root root 0 Feb 15 17:05 xpenology.vmsd
-rwxr-xr-x 1 root root 3067 Feb 17 18:11 xpenology.vmx
-rw------- 1 root root 0 Feb 17 18:11 xpenology.vmx.lck
-rwxr-xr-x 1 root root 3067 Feb 17 18:11 xpenology.vmx~
The xpenology-flat.vmdk is the additional drive I created to be for synology to create apps on. Which boot disk am I supposed to replace?
-
5.2-5644 Update 3. I got the notice of the update 5 available in DSM so I jumped on here to see if it would be safe to install. Then I see new xpenoboot and thus my post.
Current installed xpenoboot is 5.2-5644.4.
-
I just recently installed on ESXi 6 using a guide on here. Can anyone link me to instructions on how to update the XPenoboot to recently release XPEnoboot 5.2-5644.5?
I am currently migrating my data over to it and don't want to break it.
Thanks!
-
i install the latest update and now i can't do anything with my nas
Read this very thread you posted in. It would have told you 5.2 breaks stuff. I will also has information on how to downgrade.
-
Problem right now is I don't have all the drives in. I guess I'll just proceed and trouble shoot when I get more drives in. The internalportcfg calculation I understand but I'm not sure about the usbportcfg offset.
-
I'm searching to see if there is any way to support more than 12 drives? I have 2 m1015 IT cards and a 16 drive server. I found a thread with modified 4.3 install but nothing mentioned 5.1.
Thanks!
Missing disks on 1.04b 918+ esxi6.7
in DSM 6.x
Posted
Solved my issue by playing with sata_args. Mapped my HBA to 1-8 and synoboot on 9/10.