Jump to content
XPEnology Community

coint_cho

Member
 View Profile  See their activity

  • Posts

    49

  • Joined

  • Last visited

 Content Type 

Everything posted by coint_cho

  1. coint_cho
    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. coint_cho
    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. coint_cho
    Anyone? 😕
  4. coint_cho
    I think it's because I interrupted the process because it took too long, so I probably need to reinstall and redo everything sadly
  5. coint_cho
    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
  6. coint_cho
    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.
  7. coint_cho
    Either it'll have to be rtl8139 or e1000
  8. coint_cho
    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.
  9. coint_cho
    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.
  10. coint_cho
    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
  11. coint_cho
    Here’s the output to that.
  12. coint_cho
    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?
  13. coint_cho
    /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.
  14. coint_cho
    Correction, I was using ssd emulation to make SHR. SSD Cache wasn't made.
  15. coint_cho
    Already have added that during compilation phase. Still the same issue.
  16. coint_cho
    There's no apparent error messages, it just straight crashes when I access the web interface with the assigned IP to install the pat file. And the site returns with "Sorry, the page you are looking for is not found."
  17. coint_cho
    I was using SSD emulation in proxmox. Now even with it ticked off, I can set the custom static IP, and ifconfig down and up after. And it still automatically shut down for some reason. Kinda at a loss now.
  18. coint_cho
    And it looks like I’m consistently dropping connection to my NIC despite having the setup for static IP done. I have to do ifconfig eth0 down and ifconfig eth0 up to manually restart the link. My Ethernet is e1000 in proxmox, since virtio didn’t work for me, and I’m skipping vmxnet3 since it’s only limited to 100m base-t
  19. coint_cho
    Did some more testing and currently I’m in 7.0.1-42218, did the same thing as what I did for 7.1.0-42621, so not sure what the issue is… I’ll gladly help with more tests on 7.1.0 if needed since this is just a test VM for Xpenology. No crashes no nothing, installed the PAT and I’m dropped straight into synology setup for 7.0.1.
  20. coint_cho
    Hi, ive checked the afformentioned file and the line is commented out with #. And after a while I noticed that the system crashes whenever I access the IP I assigned to it (10.10.10.10) and just shuts off. Not sure what the issue is.. my CPU is set to kvm64 tho, will that cause any issue?
  21. coint_cho
    So I've successfully made the image for broadwellnk-7.1.0-42621 and have installed the pat, but currently for some reason when I tried to root to change the ifconfig for eth0 as I'm running in proxmox, the machine automatically power off right after and I have to reinstall, as starting it up again it would just power off again. Any ideas what's happening? Note: I do not have DHCP on my proxmox machine and every IP is manually specified via static IP.
  22. coint_cho
  23. coint_cho
    And I'm pretty sure all my files is still there..
  24. coint_cho
    Updated rploader to the latest version and cleaned everything before building again and currently stuck at this phase. Enviroment proxmox, stuck at here twice after updating from a fresh image of tc.
  25. coint_cho
    For mine, even in lspci I only have one controller, and before this my other motherboard has only 4 ports, which by this logic I assume that 3/4 was muxed hence why it wasn't showing up in RedPill, and it shows 1,2,5.6, 5.6 I assume being a virtual port that RedPill created to fit into the signal without messing with mux data. (I also had hotplug enabled for it but never suceeded in installing DSM7 on the old motherboard.) So definitely an interesting write up..
×
×
  • Create New...