laris

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About laris

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. As a good NAS product, there are some essential key points like: 1, data integrity, make sure data safe 2, data service and management, make sure client can access and data are easy to mange 3, flexibility, like all platform clients, easy to integrated with external service, 3rd-party application 4, maintenance availability (upgrade) and rescue plan, etc. Back to the DSM and item by item, 1, DSM is not a full strong data integrity but very strong for rootfs (md0/RAID1) with multi disks if no additional HW RAID 2, DSM integrate with very good data servi
  2. I solved. adjust the kernel module load sequence like here: EXTRA_MODULES="mii mdio libphy atl1 atl1e atl1c alx uio ipg jme skge sky2 ptp_pch pch_gbe qla3xxx qlcnic qlge netxen_nic sfc e1000 pcnet32 vmxnet3 bnx2 libcrc32c bnx2x cnic e1000e igb ixgbe r8101 r8168 r8169 tg3 usbnet ax88179_178a button evdev ohci-hcd virtio virtio_ring virtio_pci virtio_mmio virtio_balloon virtio_net virtio_blk virtio_scsi virtio_console 9pnet 9pnet_virtio fscache 9p aufs" but still have some issue with other modules root@DSMPVE:~# dmesg|grep virtio [ 14.131531] virtio-pci 00
  3. Hi @segator Did you test the latest junboot 103b for DSM 62? I complied the 9p kernel module but failed to mount host shared dir in proxmox. And also some virtio Unknown symbol dmesg error root@DSMPVE:/sys/class# dmesg|grep virtio [ 11.462819] virtio_pci: Unknown symbol vring_transport_features (err 0) [ 11.462831] virtio_pci: Unknown symbol vring_interrupt (err 0) [ 11.462837] virtio_pci: Unknown symbol vring_new_virtqueue (err 0) [ 11.462848] virtio_pci: Unknown symbol vring_del_virtqueue (err 0) [ 11.464985] virtio_mmio: Unknown symbol vring_transp
  4. You can use qm terminal 100 to monitor the DSM VM serial port to debug any failure. I also got a "mount failed" as others on Proxmox, but it was successful when using a sata image disk I guess maybe there are some error in the bootloader for 6.2 (junboot 103b)
  5. Hi @segator Do you solve the problem and find the root cause?
  6. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 - Loader version and model: Jun's Loader v1.02b - DS3615XS - Using custom extra.lzma: NO - Installation type: VM - Proxmox - Additional comments: DSM 6.1.5-15254 update to 6.1.6-15266 auto reboot // 6.1.6-15266 update to 6.1.6-15266 Update 1 no reboot
  7. Thank you! I will try it. But maybe VM will better maybe. I will try to compare.
  8. I checked your github and understand the docker VM. Proxmox also can run docker and I will try your disclose code. Is this https://github.com/segator/xpenology-docker what your mentioned? or any update one?
  9. Hi Segator, I search in github, and I guess this should what you mentioned? https://github.com/segator/xpenology-docker
  10. That sound excellent. I'm running Proxmox on Gen8 and create zfs as data pool, if xpenology can run in LXC container, that will good to avoid create VM. Could you to share your code in github?