yud
-
Posts
21 -
Joined
-
Last visited
Posts posted by yud
-
-
1 hour ago, flyride said:
Why use XPEnology and DSM then? A regular Linux server with Samba will suffice... in any case the answer to your original question is to just alllocate a virtual disk.
You are right, no reason...
...except that I like DSM...
Been using XPEnology and DSM for quite a few years now. First on my N54L, then on my Gen8, ran DSM 5.x and didn't update much. It was rock solid and I simply like it. I know a plain Linux server will do the job, perhaps even more efficiently.
I run a few services on my XPEnology and I like the ease of installing packages in DSM. Sure, all can run on plain Linux as well.
I really appreciate your help and advice.
-
Managed to resolve the issues. Up and running:
HP Proliant Microserver Gen8
P222 array controller
ESXi 6.5 U2
DSM 6.2.3-25426
DS3615xs 6.0.2 Jun's Mod V1.01
In case it helps anyone else:
I solved it with the following setup:
HDD1 on SATA 0:0 - Juns synoboot.vmdk
HDD2 on SCSI Controller 0:1 - my ~4TB datastore
SCSI Controller 0 - VMware Paravirtual SCSI (was previously set to LSI Logic Parallel)
Then, in the VM BIOS, I changed the boot order to boot from SATA.
All good now.
-
1
-
-
On 10/15/2020 at 2:09 AM, Rihc0 said:
You still get the problem with with the btrfs or the ext4 fs over the btrfs. Trust me, dont use the physical raid controller and use the dsm one. Been there
Thank you.
But I have to use the RAID controller. I have other VM's running on the ESXi host, all use storage attached to the array controller.
-
8 minutes ago, bearcat said:
On your new VM, what sort of vnic are you using? (e1000e should be the "safe" choice).
Did you configure the mac of that vnic, to reflect the mac in grub.cfg?
Did you edit grub.cfg? (make sure the mac is not already used in your environment)
Thanks for your reply.
Yes to all.
I use the 1000e NIC but have tried the others too.
I configured a unique MAC address in the VM and in grub.cfg
I used the SN generator for SN.
-
I had XPEnology running DSM 5.x as an ESXi VM on My Gen 8 for a number of years. For various reasons (irrelevant) I decided to build a new VM with a newer XPEnology and larger storage.
My setup:
HP Proliant Microserver Gen8
16GB RAM
P222 Array Controller
2 x 1TB in RAID1 for ESXi VM datastore (hardware RAID)
2 x 4TB in RAID1 for XPEnology datastore (hardware RAID)
ESXi 6.5 U2 (upgraded recently from 6.0)
I followed the tutorial and configured the VM. Unfortunately I am having great difficulties installing.
If I boot with the synoboot.img from Juns loader for DSM 6.2 (either 3615 or 3617) the VM boots up, I get the message to open find.synology.com but I cannot find the synology on the network. Tried with Synology Assist as well.
If I boot with the synoboot.img which was in the vmdk folder (older, according to the date stamp) I can find the synology, connect, install DSM, but when it reboots after installation it shows as recoverable installation and the whole thing goes in loop.
My aim is to get the latest stable boot image and DSM possible for my setup. Don't mind starting with an older versions and upgrade (if an upgrade is more straight forward than a clean install of the latest).
Will appreciate any help.
-
2 hours ago, Rihc0 said:
You don't want to use the raid controller and the dsm raid
Thanks.
I wasn't going to use the DSM RAID. Only the hardware RAID controller.
-
4 hours ago, flyride said:
Again, you are losing much of the benefit of DSM if you insist on using a physical RAID controller in a hardware RAID mode. Most can be put into AHCI mode or a bunch of RAID 0 disks and then can provide direct access to the drives via RDM or passthrough.
RDM simply translates the native drive instructions into whatever virtual controller dialect you want to use in your VM, otherwise providing direct access to the disk. This has benefits for disk portability to baremetal, etc in addition to giving DSM the direct disk access it needs to do what it does best.
But if you insist on using the hardware RAID, there is no need to RDM. Just create a virtual disk and be done with it.
Thank you!
This is very helpful.
Started going through the process. Created the new VM as per tutorial.
... tried at least...
Created the VM on my VM datastore. Removed the devices as per tutorial.
Attempted to create a drive on my 4TB datastore and no matter what I do it always gets created on the VM datastore. Tried to move it and to no avail.
-
13 minutes ago, flyride said:
Thank you for the link.
Unfortunately I still don't know the difference and therefore cannot decide what's best for me.
Either way, I have a physical RAID array controller, so I'm not letting DSM manage my physical disks. My choice is between a standard VMDK and RDM, I just don't know which...
-
Proliant Microserver Gen8
P222 RAID array controller
ESXi 6.0 (HP image)
2 x 1TB in RAID1 for VM's
2 x 4TB in RAID1 for XPEnology storage (data shared on my network)
Going to do a clean install of XPEnology (DSM 6.2.3)
My question:
Should I configure the 4TB storage for XPEnology as RDM or as standard ESXi VM disk?
What is the advantage of RDM?Also: is the this tutorial still relevant?
Will appreciate any advice.
Thanks.
-
Hi,
Sorry if this has been asked before, I think my situation is a bit different and I need some advice.
Currently running DSM 5.2-5565 Update 2 on ESXi 6 on HP Microserver Gen8.
I think my XPEnoboot version is 5.1-5022, but I'm not sure (is there an easy way to check without a reboot?)
My EPEnology storage is on 2 x 3TB in RAID1 (hardware array controller in the Microserver) and is mapped with RDM.
I'd like to upgrade because I like having the latest and the greatest. (but not at all costs...)
So:
Should I upgraded to the latest 5.2?
or
Should I upgrade to DSM 6?
and:
is the upgrade simple? or do I need to jump through hoops?
do I also need to upgrade XPEnoboot in either case?
should I keep RDM? or just wipe it and go with a standard VM storage?
If the recommendation is to upgrade I will appreciate a link to a simple guide.
Thanks.
Y.
-
I think you'll find that on xpenology.nl too.
Thanks again.
Performed all the upgrades on the weekend, had a hell of a hard time but all is done.
Running DSM 5.1 and will upgrade to 5.2 during the week.
-
Thank you!
So I should upgrade from 5.0 to 5.1 first, is this correct?
Is this a simple process? Isn't it a case of also changing from Nanoboot to XPEnoboot?
Can you recommend a step by step guide for upgrading from 5.0 to 5.1?
-
need some advice please.
Currently running DSM 5.0-4528 on Microserver N54L with ESXi 5.1 U2
The N54L has a P410 array controller (+512M+BBWC), with 2 x RAID1 1 arrays. The XPEnology storage is on one of the RAID1 arrays mapped with RDM. ESXi is booting from a USB flash drive.
Just bought a Microserver Gen8 and am planning a major upgrade. The plan is:
1. Migrate everything "as is" to the Gen8 (i.e. P410 + HDD's + ESXi boot, etc)
once everything is working:
2. Replace the P410 with P222 array controller
once everything is working:
3. Upgrade DSM to 5.2-xxxx
...and once everything is working...
4. (maybe) upgrade ESXi to ver 6.0
If steps 1 and 2 go smoothly, how should I upgrade XPEnology to DSM 5.2-xxxx ?
Should I still use RDM?
Or should I install XPEnology from scratch and restore my data from backup?
If the recommendation is fresh install: is there a way to backup my DSM 5.0 settings, shares, permissions, Plex, etc, and restore into the new 5.2 installation?
(I dread the thought of configuring XPEnology from scratch...)
again, if the recommendation is for a fresh install: is there an updated step by step guide for DSM 5.2?
I used the guide here to do the 5.0 install: http://cyanlabs.net/Thread-Install-ESXi ... gy-on-ESXi
Will appreciate any advise.
THANKS!
Y.
-
I'm running Xpenology in a VM on ESXi on my N54L.
Also running FreePBX, Ubuntu Server 14 and an occasional use of a Win 7 test machine. The Xpenology is running PMS, straeming nicely.
All running happily, no issues.
-
Could you please explain how you installed the HP SIM pack so that you are able to see all those sensors?
I used this guide:
http://www.cosonok.com/2012/02/installi ... mware.html
I think I had to play with it a bit before I managed to get it working (sorry, don't remember...), but now it's working beautifully.
-
Not sure if this helps but I'm running ESXi (HP) on the MicroServer N54L. I installed the HP SIM pack and can see this in the vSphere Client:
-
Hi yud - put simply, no. Don't touch 5.1 yet, there are various issues with it that the great minds here are still figuring out
You can always keep an eye on the status table at the bottom of the page (above the comments) on xpenology.nl to see the overall status of a release:
http://www.xpenology.nl/synology-released-dsm-5-1-5004/
Welcome to xpenology
Thanks!
I will stick to my current version for now...
-
I am totally new to Synology/Xpenology so please be gentle on me...
Currently I'm on 5.0-4493 Update 7
Given all the reported problems from some people here should I upgrade to 5.1?
If so - what is the method of upgrading (given that it's a major version)?
Sorry, I only know how to update a minor version...
A link to a step by step guide will be highly appreciated!
-
An update:
Replaced the Adaptec 2405 with HP P410 (with 512MB+BBWC).
Created RDM using the same command.
No errors, no issues, Xpenology is up and running on my N54L.
So the issue is definetely with the Adaptec card under this setup (MicroServer+Adaptec RAID cards+ESXi)
Hope it helps someone in the future.
-
Hi,
I'm completely new to XPEnology and am asking for some assistance.
Trying to install XPEnology on Proliant MicroServer N54L and following the guids here http://xpenology.com/forum/viewtopic.php?f=2&t=2147 and here http://cyanlabs.net/tutorials/how-to-install-esxi-on-n54l-and-xpenology-on-esxi.
When I try to attach the disks to Synology (step 11 in this guide http://xpenology.com/forum/viewtopic.php?f=2&t=2147) I get the error:
"Failed to create virtual disk: Invalid argument (1441801)"
I searched the error and found it is common with Adaptec RAID cards. Unfortunately all the troubleshooting steps suggested in the posts were way over my head (I'm new to all this...)
My Setup:
* Proliant MicroServer N54L
* 8 GB ECC RAM
* Adaptec 2405 RAID card
* 2 x Seagate 1TB HDD's (ST31000524AS) in RAID1 for VM's
* 2 x Seagate 3TB HDD's (ST3000DM001) in RAID 1 for XPEnology storage
* ESXi 5.5 (1746974-HP-5.72A.3-Jun2014) booting from USB stick
ESXi is configured and working. I have 2 x datastores: 1 for VM's and the other is destined for the XPEnology storage. I have other VM's running with no issues.
The command I issued to add the storage to XPEnology is as follows:
vmkfstools -z /vmfs/devices/disks/mpx.vmhba2:C0:T1:L0 /vmfs/volumes/VM_Datastore/RDM/NAS_Drive1.vmdk
(I copied the path in bold from the vSphere client)
It resulted in the error: "Failed to create virtual disk: Invalid argument (1441801)"
Is there anything I can do to resolve this?
Will appreciate any help but please be gentle on me as I'm new...
Thanks!
Y.
Problems installing on HP Microserver Gen8
in DSM 6.x
Posted
For me the advantage in running ESXi is the ability to run other VM's on the Gen8. My microserver is not dedicated to XPEnology.
I'm running Sophos UTM, FreePBX, APC Virtual Appliance and XPEnology, all running 24x7. I also have a couple of Windows VM's running occasionally (on demand).
Can't speak for others though...