Jump to content
XPEnology Community

Schmill

Member
  • Posts

    148
  • Joined

  • Last visited

Everything posted by Schmill

  1. It seems my VM's were being created in the wrong location... It seems that the installation defaults to creating the VM's in the /root directory, NOT on a created volume. This seems to have filled my "/dev/md0" which then not only stopped the VM from being able to operate, but also stopped me from being able to log into DSM (see viewtopic.php?f=2&t=4596 ). Performing a "mv /root/VirtualBox\ VMs/ /volume2/" now seems to have solved all my problems
  2. Seems I may have solved it So I mounted /dev/md0 as /tmp/work/ and ran "du -hs *" to find the largest directory... So then drilling into the 'root' subdirectory: So it seems as if by default the VirtualBox install (viewtopic.php?f=15&t=3497) locates the VM's directly on this /dev/md0, rather than on one of the volumes. By doing a "mv VirtualBox\ VMs/ /volume2/" I have now freed space on the /dev/md0 and can log back into the web gui
  3. What is /dev/md0 ? If I try to login via the DSM web interface I get the message; However, there is no way that my disks should be full, and if I log in via SSH and run a 'df' I get this: df -h Filesystem Size Used Available Use% Mounted on /dev/md0 2.3G 2.3G 0 100% / /tmp 940.2M 800.0K 939.4M 0% /tmp /dev/vg1000/lv 224.8G 1.0G 223.7G 0% /volume1 /dev/vg1001/lv 1.8T 672.2G 1.1T 37% /volume2 /dev/sdu1 30.8M 12.5M 18.4M 40% /volumeUSB1/usbshare /dev/sdv1 1.8T 1.3T 495.2G 73% /volumeUSB2/usbshare The only thing that is 100% used is /dev/md0, but I don't know what this is.... Any ideas? Thanks
  4. This worked really nicely for me until I rebooted the server, now I get the phpVirtualBox login screen, and can log in with admin/admin, but after that get an error: Exception Object ( [message:protected] => Could not connect to host (http://127.0.0.1:18083) [string:Exception:private] => [code:protected] => 64 [file:protected] => /volume1/web/phpvirtualbox/lib/ajax.php [line:protected] => 128 [trace:Exception:private] => Array ( ) [previous:Exception:private] => ) As per a few post up from here I checked for /opt/VirtualBox, and it existed, but for good measure I deleted it, then recreated as per the instructions above. Now when I try to start the package I get the following errors on the terminal: /opt # cp -pR /var/packages/virtualbox/target/opt/VirtualBox /opt/VirtualBox /opt # /var/packages/virtualbox/scripts/start-stop-status start Starting VirtualBox kernel modules ...done. Starting VirtualBox web serviceVBoxManage: error: Failed to create the VirtualBox object! VBoxManage: error: Start tag expected, '<' not found. VBoxManage: error: Location: '/root/.config/VirtualBox/VirtualBox.xml', line 1 (0), column 1. VBoxManage: error: /home/vbox/tinderbox/4.3-lnx64-rel/src/VBox/Main/src-server/VirtualBoxImpl.cpp[531] (nsresult VirtualBox::init()) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component VirtualBox, interface IVirtualBox ...fail! ...fail! VBoxManage: error: Failed to create the VirtualBox object! VBoxManage: error: Start tag expected, '<' not found. VBoxManage: error: Location: '/root/.config/VirtualBox/VirtualBox.xml', line 1 (0), column 1. VBoxManage: error: /home/vbox/tinderbox/4.3-lnx64-rel/src/VBox/Main/src-server/VirtualBoxImpl.cpp[531] (nsresult VirtualBox::init()) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component VirtualBox, interface IVirtualBox Doing a "cat /root/.config/VirtualBox/VirtualBox.xml" reveals an empty file... Any ideas what is going on?
  5. ...or at least it was whilst it worked. One reboot of the host later and now I can login to the phpVirtualbox screen with admin/admin, but after that I get an error explained as: Exception Object ( [message:protected] => Could not connect to host (http://127.0.0.1:18083) [string:Exception:private] => [code:protected] => 64 [file:protected] => /volume1/web/phpvirtualbox/lib/ajax.php [line:protected] => 128 [trace:Exception:private] => Array ( ) [previous:Exception:private] => )
  6. Nice solution - thanks (but as an aside, how DO you install a 32bit version?)
  7. Because the server is already in use EDIT Oh I see, actually WITHIN Xpenology... sorry - I'll take a look
  8. Hi, I am trying to solve some issues I am having with Plex on my xpenology install. This is tiresome as once it is 'broken' it stays broken... Ideally what I want to do is setup a VM on my laptop and install xpenology and plex onto that to do some investigating. The snag is that my laptop is only a 32bit machine, so can only run a 32bit VM, whereas what I normally run on my N54L is 64bit... Can anyone give me any pointers as to how / what to install in order to run a 32bit VM based version of xpenology and nanoboot? Thanks
  9. That I couldn't tell you as I don't particularly stress my system, and so the temperature seems to stay fairly stable. Drive2 temperature has today has changed from 33 to 34, so to be honest as most of the heat seems to be coming from the drives, a system temperature of around 34 seems reasonable too.
  10. I don't think there is any harm in you updating to 5.0 4528 update 1 (or 2 as of today), but don't quote me on that - just don't go to 5.1 yet.
  11. Sooo.... a couple of questions. I currently have a 250GB drive and a 2TB drive. Now the calculator on Synology doesn't go down as far as a 250GB drive, and I think it also indicates what happens when you install the drives, NOT if you change them. So if I setup volume1 as SHR with 250GB and 2TB drive now, will I then later be able to remove the 250GB drive, and replace with a 3TB drive, let it repair / rebuild/ whatever, and then add another 3TB? Lastly, before I go ahead and flatten my server in order to change the drive setup... is there anyway to move packages installed on /volume1 to /volume2, or am I better off just starting again? Thanks
  12. I'm running bare metal, but on an N54L, which is a fairly common platform so may benefit from more support? Anyway, my temps are reported as per below; Thermal Status green 'blob' tooltip: 34c /93f Thermal Status orange 'blob' tooltip: 34c / 93f Storage Tab: Disk1: 34c / 93f Disk2: 33c / 91f I can't do the "cat /sys/bus/platform/devices/coretemp.0/temp1_input" command as I don't have a "coretemp.0" under devices!
  13. 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
  14. Thanks fjf - I'm relatively happy with how the drives combine under the SHR system, this was more a question add to how people arrange it LOGICALLY. At the moment (in hindsight) I don't really see why you would run more than one volume...
  15. I understand this is probably down to personal preference, but I was interested to know other peoples arrangements, thoughts, and reasons... So I purchased the N54L when it came in the 2GB memory / 250GB HDD configuration. So firstly I installed DSM on the 250GB drive, as /volume1 SHR and 'played' with it. After this I decided to strip one of my external USB2 WD drives, and took the 2TB WD Green and installed that in the server. I now have it configured as: /volume1 'n54L' 250GB /volume2 WD 2TB Generally I install packages to /volume1, and have my home folders, media etc all created on /volume2, but generally this is because I am thinking of disks = volumes, which I know isn't the case I'm now in the situation where I am going to re-configure the server, and install 2 drives (2TB or 3TB) as a single SHR volume to provide redundancy - of course I still have the 250GB drive, and the 2TB drive... So what is the best configuration? Is it a good idea to keep the 'installed packages' and the 'data' on separate volumes, (perhaps packages on /volume1 (250GB), and data on /volume2 (2/3TB SHR with redundancy)), or am I better just 'lumping' everything together as one volume? Thanks for any thoughts / replies - I'm interested to see what comes from this Thanks!
  16. que? (Even google won't translate it for me - sorry! )
  17. Is there anyway that I can set something so that my USB drives will mount at the same mount point all the time? At the moment the first one connected is /volumeUSB1, the second is /volumeUSB2, etc, but what I am alooking for is something that would (perhaps) take into account the serial number of the USB drive, so that anytime THAT drive was connected it would be mounted to /mnt/MyMediaDrive (for example), whereas another drive would always mount to /mnt/MyBackupDrive Is there anyway to do this? Thanks
  18. Thanks Dfds - hopefully that means that it is a good idea, as this is what I did this evening (before checking for posts on here - lol): External view: 20141104_233210.jpg[/attachment] Will see how it goes!
  19. Thanks - the file is there on my system, I've even now tried adjusting the permissions and everything. Spent too long on it now, doing a fresh install and will copy the data back from backup and see if it works then!
  20. Thanks for your reply spiderben - I'll give that card a go Incidentally - have you found anyway to stop the N54L filling with dust? I wouldn't say my house is THAT dusty but the N54L seems to be a great little vacuum cleaner and my drives and 'insides' are covered in fine dust, especially around the door area
  21. Hi I checked the permissions and nothing appeared amiss - I even changed some as per a post I found, but it made no difference so I changed it back. Thing is I don't know how old some of the information on the net is and if I just fiddle I might break it further - lol Yes - I tried the pack from synology package manager, then uninstalled that and tried the latest Intel / Synology pack from the Plex site and neither worked correctly.
  22. Not really a solution to getting Plex working I think, but thanks for pointing out an alternative none the less...
  23. Its part of the Synology restriction - why do you want to?
  24. I don't seem to be able to get plex to start on my box at the moment, (the package shows as started, but it is not running correctly, there is no web interface etc). If I SSH in and cd to "/var/packages/Plex Media Server/scripts" ...... I have stopped the service in package manager, and the start_stop_status script confirms this: /var/packages/Plex Media Server/scripts # ./start-stop-status status Plex is not running However when I try to start plex I get a LOT of errors: /var/packages/Plex Media Server/scripts # ./start-stop-status start Starting Plex ... /volume1/@appstore/Plex Media Server/Resources/rsync: error while loading shared libraries: libiconv.so.2: cannot open shared object file: No such file or directory /volume1/@appstore/Plex Media Server/Resources/rsync: error while loading shared libraries: libiconv.so.2: cannot open shared object file: No such file or directory /volume1/@appstore/Plex Media Server/Resources/rsync: error while loading shared libraries: libiconv.so.2: cannot open shared object file: No such file or directory /volume1/@appstore/Plex Media Server/Resources/rsync: error while loading shared libraries: libiconv.so.2: cannot open shared object file: No such file or directory /volume1/@appstore/Plex Media Server/Resources/rsync: error while loading shared libraries: libiconv.so.2: cannot open shared object file: No such file or directory I have truncated this for readability as there are a fair few of these messages! A status check will then show plex as running, but needless to say it does not 'appear' to be running (no web interface etc). /var/packages/Plex Media Server/scripts # ./start-stop-status status Plex is running Any ideas as to what is happening here? Thanks EDIT Also looking in the plex log, (via package manager), it shows a long list of trying to install plug-ins, and errors in the form of: error - system returned error, errno=10
  25. Not sure it helps now but... Did you select the correct menu options during your initial 'boot' from the new USB stick? You have to manually select the 'upgrade' option on one of the boot menus the first time. Thereafter accepting the default (letting it timeout) is fine...
×
×
  • Create New...