Jump to content
XPEnology Community

filippo333

Member
  • Posts

    156
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by filippo333

  1. Make sure you backup your data before you migrate. You should be able to backup your XPE config and import that (but it may be hardware dependent, and if you choose 'migrate keep my settings' or 'clean install'. Also, update the DS1515 to the same base version of DSM as you have on XPE, just to avoid too may variables. 


    So it worked, I migrated the data not the settings just to be safe. Bad news is I think I'm going to have to return it as CPU performance is not as advertised :sad:

    I guess if you really want decent Plex transcoding then stick to a PC.

    Sent from my SM-G935F using Tapatalk

  2. I did the same recently, I put a disk from Xpenology to ds214 and upon its boot up it said something like "I need to reinstall", I agreed, and the reinstall succeeded. I restored the settings, however not everything came back to the original state, e.g. shares ACL. However all shares were present on DSM and data were untouched.
     


    Yeah I saw your post, my thinking was by exporting the data the chances of it being accepted by a new system should be a lot higher.

    Sent from my SM-G935F using Tapatalk

  3. Hello all,

    I finally decided to bite the bullet and ordered a Synology DS1515+ which should be here on Monday :grin:

     

    I'm pretty sure I should be able to import my Hyperbackup to a Synology box, I've tested this works inside a VM though obviously still using Xpenology/Jun's loader. Does anyone see any issues with importing data exported from an Xpenology system?

     

    Thanks.

  4. 51 minutes ago, Elpee said:

    It means those who are using bare metal are screwed in this case.

     

    Yep most modern consumer hardware does not have a serial port whatsoever. Unless someone's tested whether serial works via a PCIe add-in card?

  5. that is because it's missing the lan driver, you should be able to fix it instead of remark as do_no_update.

    as the op said, login in via console (serial, virtual, local, whatever) and copy the modules in the right folder, tha reboot.. it's a very simple fix that require less than a minute, it's not an update problem but a loader bug.

     

    And just how are you supposed to do that without a serial or network connection?

     

     

    Sent from my iPad using Tapatalk

  6. Yeah DO NOT update to 6.1.2 on Jun's 1.0.2a2 loader, my VMware instance no longer gets an IP address after installing the update. It's never a good idea to update to 6.1.x releases.

  7. In terms of memory BTRFS does not require ECC. If you're trying to build a system on the cheap my recommendation would be go for a good known brand such as Crucial or Kingston. Also don't buy memory marketed towards gamers as they tend to be of lower quality and optimised for low latency which you don't need.

     

    Another thing I would suggest is to run memtest for at least 4/5 passes whenever dedicating a machine for mass storage just to double check there aren't any inherent issues with integrity.

     

     

    Sent from my iPad using Tapatalk

  8. Designed to run on bare metal? As was unix, linux, freebsd, openbsd, solaris, whatever. However, they all work fine in VMs as well. Did you know a LOT of embedded systems are running inside of a VM of sorts? There is no magic about a VM that will make the linux the NAS is built on run like s**t. However, unsupported bare metal hardware will. There is that. If everyone relied solely on what software was "designed" to run on, we would all be limited to the very expensive hardware created by a certain three-letter named company and been happy with whatever they decided we needed. We would not have been okay to buy our own, different hardware, to run the software on because it wasn't designed to run on non-whatever company hardware.

     

    You're talking about virtualising an operating system designed to manage low level RAID. I personally would much prefer to run that on bare metal hardware.

     

     

    Sent from my iPad using Tapatalk

  9. During loader startup did you switch to ESXI option? Its the last one in grub menu. Also you can try to build new VM from scratch, just use hard drive from OVF template.

     

    From my experience testing, selecting the ESXI/VMware option causes the VM to not see any of the disks. Leaving it on the default works fine in VMware.

    • Like 1
  10. Back from the dead with some good news...

     

    I can confirm with high confidence that upgrading directly from 5.2 or 6.0.2 to 6.1.1 is completely successful.

     

    To aid future upgrades as the bootloader matures, I am coming up with a nice backup package to backup of the system 2.4gb partition. I recommend for everyone to do this before they do any upgrade/update. Then the risk is really low to upgrade to any version even when untested. If an upgrade fails it is easy to restore back to previous version you were running if you fail. More on that soon.

     

    Great idea, should cure people's anxiety when updating!

  11. I generated an easy to install package to activate a mainboard connected power button for clean shutting down (instead login in web page).

     

    Install package for DSM 5.2, DSM 6.0 and DSM 6.1(.1):

    powerbutton_6.1-0004.spk

     

    I have tested DSM 5.2 and DSM 6.1 for the DS3617 versions only in VM. Please report if there are any problems.

     

    [spoiler=Changelog]Version 6.1-004

    Minor change for recognizing DSM 6.1.1

     

    Version 6.1-003

    Adding support for DSM 5.2

     

    Version 6.1-0002

    Combining DSM 6.0 and DSM 6.1 in one package

     

    Version 6.0/6.1-0001

    Versions for DSM 6.0 and DSM 6.1

     

    Thanks again for your work wer; works like a charm even inside of VirtualBox :smile:

  12.  

    You cant switch from ds3615xs to ds3617xs without fresh install. Those hardware are not compatible, different architecture.

     

    Hello,

     

    Thanks for respond. I have backup all files. How to do clean install? When I start install have a 2 choice "move or new". I installed as a new. But I got always "error 13".

     

    Sincerely,

     

    Hello again,

     

    I am using baremetal and HP microserver gen8

    I deleted all partitions with partition magic. It' s coming with new disks first attemp on "find.synology.com". But I am always getting "error 13".

    I tried "DS3617xs 6.1 Jun's Mod V1.02-alpha" with "DSM_DS3617xs_15047.pat" or "v1.02a2" with "DSM_DS3617xs_15101.pat". Does not matter. Always same error.

     

    Any idea?

     

    Sincerely,

     

    Did you put the correct PID and VID in the grub.cfg file? It will never work without doing that first.

     

     

    Sent from my iPad using Tapatalk

  13. Hi all

     

    I have now upgraded my main Server with Jun 1.02 and DSM 6.1 and all is working fine.

    Virtual DSM Manager is also working but there is only 1027x768 screen resolution no drivers for Sound and Graphic Adapter :sad: (and virtual box is much better :smile:)

     

    My Question is will upgrade my Gen8 also with the newest DSM 6.1 and JUN Loader 1.02 but this is my Backup Server with 30 TB in and when is going wrong im in trouble and i have read that some people have trouble with the GEN 8 DSM 6.1 and Jun Loader 1.02 Could you confirm ? or is it working when i do a fresh install on the Gen8 ?

    I have read the forum but i cant find a defenitly answer for the GEN 8 and DSM 6.1 and Jun Loader 1.02

     

     

    thank you very much for your feedback

     

    You can always just disconnect your existing disks, remove your current USB stick and create a DSM 6.1 USB stick using Jun's loader to do testing. It should work as I've seen others on this forum running on Gen 8.

     

    I'm technically using Skylake (an unsupported architecture by DSM) and don't have any major issues. Everything works out of the box.

×
×
  • Create New...