Jump to content
XPEnology Community

timonych

Member
  • Posts

    41
  • Joined

  • Last visited

Posts posted by timonych

  1. В 09.10.2020 в 18:39, tronba сказал:

    The which i have downloaded extracted was ending .vma. What i did change was vma.lzo

     

    Is that also correct?

     

    If You have download *.lzo - You don't need to extract it. It native format of Proxmox Backup's. 

     

    Just Go to WEB UI to Backup Storage, choose the backup and just click on Restore

     

    image.thumb.png.440095451871f3356ffc16ecf319ce66.png

  2. 20 часов назад, arkilee сказал:

    I created a proxmox backup template for ds3615xs with virtio drivers added and based on timonych's one.

    It can be downloaded here:
    https://mega.nz/file/XZwAwYAC#3kIcZ8C3heA9UBTAUKdora74I7qes6kUVTrXkla3e9w

     

    Virtio_net network seems to work fine and it can reach 13Gbits/s on my host rig.
    Virtio_blk seems to work as well, but disk are not recognised by dsm ... and it doesn't really matter because up to some test( on ssd drive) sata disk are as fast as virtio disk.

    I haven't tried pci/disk passtrough, but it should work with "q35" conf.
    Well let me know if this has issue.

    @timonych Please feel free to add this backup to your mega repository.

     

     

    @arkilee

     

    Great Work! Bit Thanks for dump. 

     

    I have added to https://mega.nz/fm/h7pwlSaS (in subdirectory).

     

    Can You make for ds918 and ds3617 too, please?

  3. NEWS!

    I have made clean version of ds3617xs, dx3615xs, ds918+ and have uploaded to mega.co.nz. 

     

    Download Link:

    Dowload link can be found in 1 Post.

    Also this -> MEGA.CO.NZ

    Works without modifying boot Image or custom QEMU configuration (not need e1000e in vmid.conf)

     

    Works with old CPU (Tested on CPU(s) 8 x Intel(R) Xeon(R) CPU E3-1245 V2 and FCLGA1155, so I think it will work on old platforms)

     

    HOW TO install from Backup:

    Video by Geeked on Youtube

     

    Do not try to Update 2 as described in this post  (it fails and maybe break your system) -> 

     

    Configuration default as image.

    image.thumb.png.aaedf29ebc7825d6a50c6e1a3514d2ff.png

  4. В 18.09.2020 в 12:26, maxime сказал:


    In which folder did you upload the file .lzo?

     

    You should upload it to folder with backup.

     

    By default, Proxmox creates "local" Storage which is located in /var/lib/vz.

     

    By the way, For information for All

    I have successfully update XPenology to DSM 6.2.3-25426 without modifying anything. Just Press button in WEB Interface to Download new version and after it to Update. After reboot by XPenology was available by internet.

    You can try to restore Clean XPenology from my backup and try it by yourself to experiment.

     

    Hardware: AMD Ryzen 7 2700 / Asrock B450M Pro 4 and Proxmox 6.2.1 (proxmox-ve: 6.2-1 (running kernel: 5.4.60-1-pve))

     

    P.S. but no success with Update 2 at this point.

    image.thumb.png.cf6a65ffb3a5b7cf0456c1388beaee15.png

    • Like 1
  5. В 01.02.2020 в 21:13, rostigue сказал:

    Please, I installed the vzdump. How do I change the serial number ??? Thank you

    Hello,

    You can do it as standard manual 

     

     

    Boot image is 60 MB image. But for what do you need change serial number?

     

    В 19.05.2020 в 12:47, Takolag сказал:

    Thanks a lot, it's very good.

     

    Be carreful with Promox 6.2.4, you must rename backup template filename's with this format "vzdump-qemu-xxx-yyyy_mm_dd-hh_mi_ss.vma.lzo" !

    Else you will an error "TASK ERROR: ERROR: couldn't determine archive info from '/var/lib/vz/dump/vzdump-qemu-xpnology-ds918-62.clean.vma.lzo'.

     

    I think it can help you

     

     

     

    Will write this information on Proxmox forum. 

     

    I think it's a bug because before there was no such error. I have some backups with such naming (it more usefull for clean backup)

  6. 8 часов назад, david008 сказал:

    thanks a lot for backup templates.

     

    Is possible ds video transcoding with this backup templates ???

    Is necessary change serial number/mac ??

     

    thanks again

     

    Hi!

     

    1. I don't tested it. But as I know transcode if fully worked in DS918.

    But I have install Plex into Linux Container CentOS 7. So, video transocoding for me is redundant.

     

    2. In bootloader is not necessary to change Serial/MAC.

     

    But You should change MAC Address  in Proxmox GUI for Second NIC. First NIC has a MAC 00:00:00 - it is dummy interface which is disabled by Proxmox GUI.

    I have found this more easily configures that changing in Bootloader this settings.

     

    First NIC interface takes MAC address from Bootloader. That's why this NIC is Disabled. But the Second NIC takes MAC from Proxmox GUI. That's why it's enabled and be reconfigured more easily.

     

    image.thumb.png.ea09b6a526bdbc072a43abfa02073ea3.png

     

    image.thumb.png.bb307c5134e43acdfdac3d037961a2f2.png

  7. 17 часов назад, bluepr0 сказал:

    Just a quick question from a noob trying to learn Proxmox to virtualize DSM there (currently on bare-metal). I would like to passthrough all my disks so I can restore all my data and configuration... would this be possible by adding the physical disks to the VM? I'm currently on 6.1.7 with 3617xs on bare-metal as I said

     

    Yes, you can.

     

    Just use this command in console:

    qm set <vmid> -sata<id> /dev/<device>

    and your disk will used by QM. 

     

    <vmid> = ID of Your VM

    <id> = Free Sata index

    <device> = Your Disk

     

    But this is QEMU / Proxmox question. not Xpenology.

     

    32 минуты назад, bluepr0 сказал:

    Nevermind, I took a look at some articles and it seems you need to use the --storage option

     

    Of course. You need use --storage . I have made backup and restore via Web Interface.

  8. 1 час назад, codedmind сказал:

    Anyone already tried to run esxi inside proxmox and then run xpenology ?

     

    In theory there no any barrier, but You should use nesting virtualization in Proxmox under ESXi.

     

    But for me it is strange to use Virtualization inside Virtualization to use XPenology. 

  9. В 08.02.2019 в 16:51, vanaema78 сказал:

    So if I understand correctly, there is no way of updating the 3615xs DSM 6.2-23739 Update 2 to DSM 6.2.1?

    Yes,

     

    It depends on bootloader by Yun. If he can made a new bootloader with E1000 driver than I can upgrade and publish new backup.

  10. В 10.01.2019 в 19:03, codedmind сказал:

    and even that cannot have the 2384?

    No, it cannot be upgraded to 23824.

     

    4 часа назад, Nevexo123 сказал:

    Hey, I tried using your ds918 images on my PVE 5.3.5, there's nothing on serial (COM 0) 

    No, e1000e is not necessary. I have a success with ds918 and e1000 on Xeon Silver. 

     

    The main requirement is CPU Haswell or newer.

    • Thanks 1
  11. There is information in Warning post that upgrading to 23824 with kernels 1.03b or below - no any custom network interfaces would be worked. 

    Or just change to e1000e maybe usefull - there are feedbacks in 6.2x kernel thread. I have no success with that because I didn't find how emulate e1000e instead of e1000 in proxmox.

  12. Hi Everyone!

     

    I'm sorry for creating this thread but after reading some topics I've found that somebody has any troubles with installing XPenology on Proxmox.

    This also concerns me - I have a trouble with 6.2 on my Microserver Gen 8 with Proxmox on it - no network devices.

     

    So, after some attempts I have a success with 6.2 DSM with 3615xs and 3617xs only with 6.2_23739 with manual Installation.

    After fresh install I make a full backup, so this can be used as template. 

    image.png.c58d08aaa1de3c73f3726c887928b43e.png


    There are 6.1 and 6.2 of DSM version. 

     

    So, You just need to copy this backup to Your Backup Directory in Proxmox and Restore it.

    3615xs and 3617xs has successfully tested on HP MicroServer Gen 8 / Proxmox 5.3.5 | 5.3.6!

    DS918 was successfully installed on SuperMicro SYS-1029P-WT with Intel Xeon Silver 4110. I've decided to publish it to for everybody too.

     

    Download Link --------------->>>>>  MEGA.CO.NZ

     

    There are some several important points:

    1. TWO Network Interfaces. First NIC is disabled. It has been done because for DSM first device must be with suitable MAC which is fixed in Grub. If You need multiple instance of DSM (as me) - it's costly to mofidy everytime Grub. So Second NIC uses any MAC address from Proxmox.
    2. TWO Disk Drives. Firsk disk - is bootable disk made by Jun! Don't try to use is as Storage. (maybe it's painfully, I haven't checked). Second Drive - it's a System Drive where was DSM has already installed. 
      1. Second drive capacity - 6 GB! For me it's suitable - I use free capacity 1.3 GB only for Software and another drive for everything. If You need more for System Drive - Just Resize Disk before first start/initialization. I have tested that there is no errors after resizing before first initialization.
    3. Boot Drive - Sata0. 

    image.thumb.png.2df1299ad0d2bb0a321313bea54abae6.png 

    • Like 4
    • Thanks 2
×
×
  • Create New...