Jump to content
XPEnology Community

coint_cho

Member
  • Posts

    49
  • Joined

  • Last visited

Recent Profile Visitors

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

coint_cho's Achievements

Junior Member

Junior Member (2/7)

3

Reputation

  1. I don't have two as far as I'm aware, but I do have this manual args command args: -device 'nec-usb-xhci,id=usb-bus0,multifunction=on' -drive 'file=/var/lib/vz/template/iso/tinycore-redpill.v0.9.5.0.m-shell.img,media=disk,format=raw,if=none,id=drive-disk-bootloader' -device 'usb-storage,bus=usb-bus0.0,port=1,drive=drive-disk-bootloader,id=usb-disk-bootloader,bootindex=999,removable=on'
  2. Tried to remake a completely new VM in Proxmox for Xpenology. Current face with these two issues. The built is done and I can see the boot entries on Grub But booting into it gives me Tried to rebuilt on DS920 and other models as well to no avail, any advices on this?
  3. I think it's because I interrupted the process because it took too long, so I probably need to reinstall and redo everything sadly
  4. Just upgraded from 7.1.1-42962 to 7.2.1-69057 DS920+ on my Proxmox box. Currently for some reason there are lots of apps that's broken in package manager, and I can't fix or repair any of it without an error message popping up. My file manager is also not working, and the whole UI is just very sluggish in general. Any ways that I can rebuild the whole Redpill image without losing any data? I tried booting into Tinycore to rebuild it again but for some reason none of the 4 terminals comes up and trying to launch it manually doesn't bring up anything
  5. For anyone with the issue of machine shutting down after accessing setup pages http://[local IP]:5000 after finish installing pat and reboot, 1st check whether you have added the redpill.misc extension, if you have it added and it's still not working, it might be an issue with your CPU just plain not supported. I had the same problem in proxmox with a kvm64 CPU flag pass through to the VM. I passed through my host CPU E5-1275 v6 to it and it booted up straight without any issues. However I can't confirm nor deny completely that this is the issue but that's the only way I've circumvented the error. If I had to guess why, it might be something to do with the flags of your CPU. E5-1276 v6 Host Passthrough KVM64 Passthrough As you can see KVM64 has a lot of flags that host has but it just doesn't, which might be essential for DS3622xs+ to function properly since the original DS3622xs+ is based on Xeon D-1531. And older CPUs or some specific qemu CPU flags just doesn't have the proper CPU features flags passthrough to the VM. There's more sample sizes that'll be needed to make sure if this is the correct theory, as so far I've only done testing on one machine. Baremetal + VMs results input would be appreciated. https://pve-devel.pve.proxmox.narkive.com/d1wiRhm0/kvm64-or-qemu64 Here are some of the flags of each CPU, there are for sure more google to be done on this matter.
  6. Either it'll have to be rtl8139 or e1000
  7. The issue with vmxnet3, is that it doesn't really work for some reason. I was testing it before with my 42621 installation, and for some reason it's reporting back in Xpenology as a gigabit link, but it's only a 100mb link, and even with an assigned IP, I can't reach the box as well.
  8. Oh, I just tested a switching from qemu64 CPU to host in Proxmox and I'm instantly dropped into the web UI and currently it's done being setup... Well that was a stupid fix, if I had to guess it's probably something to do with DS3622xs requiring a specific CPU function flag and qemu64 just doesn't have that? As qemu64 is designed to have bare minimal CPU flags afaik. My host cpu is E3-1275 v6 for reference.
  9. No idea, still waiting on a potential fix from pocopico probably, if I had to guess it's just an issue with the VM? No idea
  10. Here’s the output to that.
  11. Ok, looks like my NIC is the issue here.. And looks like there’s some other issues as well, is there any solutions to any of these? If these are Ethernet based errors, maybe switching to vmxnet3 would help? Or virtio?
  12. /usr/lib/modules-load.d/70-cpufreq-kernel.conf had the original acpi-cpufreq commented out with #. Tried with both pocopico redpill.misc and jumkey redpill.misc, able to install pat on Proxmox VM, after restarting, still not able to access the setup page in any form or way. At a loss here, and if there's no solution, might just downgrade back to 7.0.1-42218 and stay there https://streamable.com/1i0xsl Demo of the current issue I'm facing after installation of PAT.
  13. Correction, I was using ssd emulation to make SHR. SSD Cache wasn't made.
  14. Already have added that during compilation phase. Still the same issue.
×
×
  • Create New...