toobueller

Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

0 Neutral

About toobueller

  • Rank
    Junior Member
  1. toobueller

    Thank You

    I have to chime in on this one as well. Since using Xpenology at home, I have purchased 1 high end and 2 mid grade Synology devices at work. Were it not for Xpenology, I would not have considered anything other than something like FreeNas, which really would not have met my needs the way Synology does. Were the hardware not so expensive, I would replace my xpenology box with a Synology one.
  2. If I understand correctly, there used to be a complete distro called "Xpenology," but for whatever reason, it is no longer released as such. Now we have Xpenoboot which allows us to boot the actual Synology distribution, thus negating the need for "xpenology" as a distro and relegating it to a definition of "A state of running Synology on 3rd party hardware with the assistance of a boot loader" Thus, asking for the latest version of xpenology is basically asking what's the latest Synology vesrsion supported by the latest bootloader? Semantics aside, I would like to see an up to date f
  3. Getting onto the second USB stick might be a problem if the installer doesn't see it as a usable destination. Having said that, if you have an old hard small hard drive (40GB-120GB) that you can install it to, you may be able to use dd to copy it to a USB drive, but you will likely have to edit which drives are marked as 'internal' and 'external' by DSM. Search for topics on hiding the USB drive from DSM or changing ESATA from being seen as external, and that will get you in the ballpark for what you need to do. Best case, you may not need to do any of that. It will have to be a separat
  4. I have had issues with booting after attempting to write the image with dd. This should work, so I must have done something wrong. I haven't found a definite answer on exactly what to write to... dd if=xpenology-latest.img of=/dev/sdg or dd if=xpenology-latest.img of=/dev/sdg1 using the comand: fdisk -l and searching for FAT16 I think would work for determining the boot partition of the USB stick Searching the lines above it for "MB" would qualify as a secondary confirmation that this is a small partition. if the 8011 size is a constant, you could throw that in to the sea
  5. does wget http://YourIpaddress:5000 return anything (From the xpen command line) or http://127.0.0.1:5000 Not sure on the exact command to get it to use port 5000, and no access to test it at the moment, but the idea is to see if maybe it's some kind of new firewall or security setting.
  6. Many have upgraded and are running again. Your best bet is to read the threads and determine what's best for you. Without exact information on your setup you can't reliably expect a definite yes or no that will apply to you. Is yours bare metal or a VM? what hardware are you using? You said yours stops working, but didn't specify what that means? does it hard lock? Is it just the network connection that seems to stop working?
  7. Are you asking if it is possible to boot ubuntu and chroot DSM? (I was wondering this myself, a few days ago.) If not, I think you need to clarify. the debian chroot package looks like what you might want, based on your description.
  8. Try repeating again, after a reboot. examine the contents of /var/log/messages for clues. I think there is another log file that may have some more messages, but I don't remember where it is and don't have access at to find it the moment. I hope this isn't a bug in the patch.
  9. I had a similar problem with 5.0 and resorted to writing a script that was chronned to run every 5 minutes. If interested, I'll post it later. as root... ifconfig eth0 down ifconfig eth1 down ifconfig eth0 up ifconfig eth1 up Mine was dropping IPv4, but IPv6 was still up, which didn't help me trying to connect to it via an ipv4 address. I only needed the eth0 up/down commands for my single interface. Not sure how this will work on the bonded interface, but it's worth a shot. use ifconfig and see what kind of errors you get. That will help in determining what is going o
  10. I have not had that problem. See my previous post. One or more of your feeds are bad and that is what is causing the hang. Either replace your feeds with the contents I posted above, or you could manually go through your list to check which ones are bad. My list is fairly complete and I've removed bad repos. Mine loads in seconds and that's on a slow day. If you want to do it yourself and you're confident your list is complete, manually go through your list, edit each one and change the name/description slightly (No need to change the url portion). When you save it your box
  11. I've Trimmed down feeds file for package sources. If I received errors from a site or could not add a site manually, it was removed from my list. This list loads much faster than before, with bad and unresponsive repos removed. Some of these may require you to set "Any publisher" under Settings ... General in the package center backup your feeds file /usr/syno/etc/packages/feeds and replace the contents with the below. [{"feed":"http://cbo.netau.net/synopackages/","name":"cbo.netau.net"},{"feed":"http://cytec.us/spk/","name":"cytec.us"},{"feed":"http://e-remonty.info/spkrepo/packa
  12. For those editing the host file(see below) to get volumes to work, echo 127.0.0.1 payment.synology.com >> /etc/hosts a possible temporary solution for updating packages is: mv /etc/hosts /etc/nohosts perform your package installs or updates and then mv /etc/nohosts /etc/hosts afterward. This is untested, but based on some feedback I'm seeing, it looks like it would work on a temporary basis. Also, Completely disable any automatic update checking in the control panel, just in case, and also adjust the settings in package manager to allow packages other than the
  13. Just curious what's different in this version, if it is legitimate. I'm going to guess that it fixes some bugs for booting into DSM 5.0, but doesn't yet boot 5.1. http://nanoboot.eu.org (click the download link at the top of the page) I don't trust the colafile download page. Malwarebytes blocks several things on that page and blocks my download. The Dropbox file names indicate version 5.04.1, but the main page (updated January 6th) doesn't mention this version as of today (January 8th). The site nanoboot.tk appears to have expired or been replaced by one of those generic link p
  14. I'm posting this here for my own future reference, and to help anyone that needs a fast and reliable method of getting the list of feeds added to their "Package Center". Basically adding a feed list of the spk repositories all in one file that can be quickly uploaded. docmoe's site is helpful to determine if the site is reachable, but doesn't help to determine if it is still a working SPK repo, so I added that list to my own and filtered out all the sites that I had trouble connecting to, and resulted in a feeds file that can easily be added to any syno box, quickly and painlessly. t