billat29
-
Posts
351 -
Joined
-
Last visited
-
Days Won
10
Posts posted by billat29
-
-
Somewhere between the version you have and the current version, the devs changed the synology model for a more up to date one - DS3615xs. So the ones you are looking at are fine. When you upgrade, DSM thinks that you have taken the disks out of a DS3612xs and put them into the later unit and goes ahead with the changes.
I'm sure there is a step by step guide for bare metal somewhere here, but I had a quick look and couldn't find it. javakias' guide will work with some modifications.
"Converting the boot image" becomes : Create a bootable USB stick from the img file using something like win32diskimager.
"Configure your VM" becomes: Attach a screen and keyboard to your box and boot from the new USB stick.
-
Some thoughts:
First of all, if you can recreate the VM in a new datastore with the same RDM mappings it should "just work"
1) RDM is a bit of a red herring here. It just allows you to attach the drive or controller directly to the virtual machine and have the VM control it directly. So, there's nothing special about the format and any method for getting data off a DSM disk - such as mount it in Ubuntu - will work. Doing this as a first step before you try to recreate the VM would be advised.
2) I'm not sure how readable your ESXi drive is. You might be able to open the old datastore from your new installation or you could try VMFS tools to try to copy the directories and files from the old datastore and use them recreate the VMs on a new datastore - http://woshub.com/how-to-access-vmfs-da ... x-windows/
3) I have moved a set of drives from ESXi to bare metal and later (after adding a new drive) back to ESXi with the HDDs mounted via RDM. DSM didn't care.
-
2 gig of HDD is not enough. I just tried it and got the same error.
It worked if I gave it more space.
-
You can create a VMDK on the disk you have added. But for best performance you can pass the drive through via Raw Device Mapping (RDM). Given that you have created it as part of an array, I don't know whether you would now need to pass the whole array through or just the drive. The following guide may help:
-
I can't comment on the installation error but the "Operating System Not Found" is probably because vmware is trying to boot from the DSM drive not the xpenoboot drive.
Quick test is to remove the DSM drive from the VM configuration (you can add it back later) and see whether the vm boots.
If it does, add it back and then edit the .vmx file in the virtual machine folder and add the line
bios.hddOrder = "devicename" where devicename points to the xpenoboot drive and is in the form scsi0:1 or ide1:0 depending where you put the drive in the vm configuration.
-
I did something similar. I had one drive as the ESXi datastore and two drives via RDM. I replaced the ESXi USB key with one containing XPEnoboot, removed the disk with the datastore and ait all just worked. AFAIK the DSM system is copied to each data disk that you start with and to new disks as you add them. This allows DSM to run whenever one (or maybe more) disks are down.
-
.When I try the first one it gives errors on the: "type ifconfig eth0 IPofNAS netmask 255.255.255.0 up -> now you can connect via browser on the given ip"When I do ifconfig there is also a strange ip address in the inet addr. Does it mean it gets a wrong ip address? I made a static ip in the router for my NAS.
Is this where it goes wrong?
I'm really hoping that you typed something like
ifconfig eth0 192.168.1.99 netmask 255.255.255.0 up
What error message did you get?
and, yes you ought to be able to connect using the "strange" address that eth0 has - as long is in the same subnet as your PC.
-
Two things to try:
restart the network interface
viewtopic.php?f=2&t=6247&hilit=ifconfig&start=20
and
follow the instructions on the following page to do a clean install
-
Yes.
Have a look here for tutorials: xpenology.nl
-
I think you'll find that on xpenology.nl too.
-
I also had a problem where images wouldn't download properly. Under VMWare in my case. There is a thread on the Synology forum about the problem.
I updated to 5565.1 and then 5565.2 and on one of those steps the problem went away.
-
I am sure that the general advice is to backup data and also settings (from the DSM control panel) before you start. That won't, unfortunately, backup all the settings you might need.
I would continue with RDM.
I suspect most people have done 5.0 -> 5.1 -> 5.2 and that seems to have worked - with some issues for some configurations. I would have a read through the various 5.2 threads before I start.
There is a tutorial for 5.2 install here: http://www.xpenology.nl/how-to-install-dsm-5-2/ There are other useful tutorials on that site.
Finally as you are under ESXi, there's always the possibility to create a test system and try the upgrade on a VM before you start on the real thing.
-
I think you just need to create a virtual disk with the same copy of the image and then define your disks as RDM.
I did it the other way - started under ESXi and then went to bare metal by building the same version of bootloader on USB. DSM didn't notice.
-
Yes, once you have successfully installed DSM, you don't need the monitor and keyboard attached to the machine. Let it run.
Once that is done, we are in Synology land. DSM is designed to hide all the Linux complexity from the user and to provide various applications and servces. Their web site has all the information needed to set up DSM and its applications - which gets me back to my point about what you are trying to do. The user home service is a standard DSM function that will automatically set up a "home" directory for all the users you create. Rather than me giving a step by step, it would be better for you to head over there where you will find all the information about what you can do with DSM. Oh, and while you are over there, don't say you are using Xpenology to host DSM, they will just send you away.
Over here is where you will find information about what hardware works - with which versions of DSM, how to make it work and issues people are finding with specific versions and hardware.
-
I'm not sure what you are trying to achieve. I am assuming that you have followed one of the tutorials to install the system.
It looks like you are at the system console of the machine on which you have installed DSM. Normally you wouldn't use it after the installation but instead go to the web console at ipofyournas:5000.
Your first error message is there because you have not set up the user home service in the DSM control panel.
-
I'm running under Win7. If I go into manage>virtual machine settings then double click the adapter and uncheck "connect at power on", I get your problem. When I check the box and restart the machine, it all works.
So, assuming that you have that option checked normally, my guess is that it is something to do with the binding of the virtual machine network adapter with your real one which would make it a VMware problem.
The other thing I just decided that I don't know, is how VMware handles the network adapter. It might be that your real machine has to have an adapter that xpenoboot supports.
-
First of all, I am running my test system under player, so it does work.
How have you configured your virtual machine's network adapter? Have you changed it from the default of NAT to Bridged?
-
Most of the users in the moderator list don't visit very often. Maybe we need one or two extras who come here regularly and can delete these posts
-
Bryan,
have you discussed this with your IT guys? From what I understand you have said, you are putting your box on both their network and also to another one with ports forwarded.
This could be a security risk for their network.
Bill
-
That's right. Original configuration was:
Key with ESXi 5.5
250Gb disk containing the ESX datastore with the nanoboot disk image
2x4TB disks as RDM,
Replaced the key with ESXi on it with one containing the same version of nanoboot.
Removed the 250GB disk.
Booted from the new key.
Carried on as a normal
-
I did this on n54l. I did have the disks as RDM. I just created a nanoboot USB stick and booted from that instead.
DSM was unaware of the change.
-
Thank you billat29.
How is your method different from say...creating a esxi server from scratch ,and then putting the win 7 VM and the DSM VM in? ..or installing virtual box in my current bare metal DSM, and putting in a win 7 VM?
Which has better performance overall, and easier to maintain and backup?
much thanks...still learning so much from everyone!
Using VMware player is very similar to using ESXi. The major difference here is that you can continue with the Win7 machine as is, add player as Windows application and run DSM under that. There is less risk involved as you will not be changing the WIndows 7 setup.
Player is a little easier to setup and use, but is less flexible than ESXi. Obviously you will be dependent on the Windows host running.
If, at a later stage, you wish to virtualise the Win7 machine, then it is straightforward to move the DSM machine from running under player to running under ESXi.
Performance will depend on the hardware you are running on. There is an overhead to virtualisation and I think I have seen some people say that the DSM file transfer speed is a bit lower under ESXi but not that much. The big difference for me is that under ESXi, DSM doesn't have access to the SMART data from the disks. ESXi also doesn't allow DSM to spin the disks down when idle. I know that you have a 24/7 requirement and that there are different opinions on whether unloading the disks is desirable or not.
If starting from scratch, I would be tempted to install DSM on bare metal, migrate the database to DSM if at all possible and create a Win7 VM under virtualbox. (note, I have tried virtualbox under DSM, itself in a VM, but haven't done that much with it myself).
Backup? Unless anyone has better thoughts, I think that as you will be attaching real disks to the VM, then there isn't that much difference in your backup strategy but I'm willing to be corrected.
-
I suggest you download vmware player (as it's free) and install it under Win7.
You can then create a virtual machine to run DSM in.
You can create disks for your VM in two ways:
1) By allowing player to create a file in the Windows file system which it will use to simulate a real disk. (this is what you do for the nanoboot drive).
2) You can attach a real, physical disk directly to the VM bypassing Windows. This is what all the RDM stuff is about and how you handle the DSM volumes.
The second option is going to be faster for the VM and in vmware player is a simple menu option in the edit machine menus.
You can then keep your Win 7 installation as is and just concentrate on one new thing.
-
Yes,
Just follow the ESXi instructions.
If you are creating virtual disks for storage, then you need to partition them before running the install
Update DSM running on ESXi
in Archives
Posted
In principle but this one is a bit more comprehensive:
http://idmedia.no/projects/xpenology/in ... -or-later/