Search results for query: n5105

  1. E

    Very poor storage performance

    ...it was just installed I had a fixed 3% I/O delay, but the performance was acceptable, now as soon as you do something it literally "sits down" Advice? Where can I start to understand what happened? My conf : N5105 16 GB NVME Patriot P300 512 GB (also tried another model with comparable result)
  2. P

    Proxmox as a router?

    I have a N5105 motherboard with 4x2,5GbE. Now, I do have a PVE setup on a Xeon machine. I want to configure this as a mini/backup NAS with the router capability. So, the question is how do I use the additional ports on this motherboard for accessing the network? I don't want a very complex...
  3. D

    VM freezes irregularly

    ...as of today. All of these have had VMs go into the frozen state talked about in this thread. So, this does not appear to be specific to the N5105 CPU class. Side note, I have another cluster of Protectli systems running Intel Core i7-10810U CPUs, with the same versions of Proxmox and Ubuntu...
  4. leesteken

    Proxmox/OMV/HD Passthrough

    Proxmox has had a lot of problems on N5105, as a search of the forum will show. But this feel less and less as a Proxmox issue. Maybe your network cable is causing silent corruptions or maybe the source (on the NAS) is already corrupted. Or maybe there is some ransomware running and encrypting...
  5. R

    Proxmox/OMV/HD Passthrough

    ...to the use of ZFS? Both OMV and Unraid ran ZFS file systems. 3) Use of non-ECC memory at destination computer. OMV/Unraid run on a cheap N5105 board that does not support ECC memory. II think I'm going to nuke this Unraid install and try Unraid with BTRFS and see if anything changes. If...
  6. R

    kernel BUG at lib/dynamic_queue_limits.c:27!

    I can confirm this also. Running four I225-V rev03 in a N5105 box. It starting acting up all of a sudden, been running rock solid for several months since the PVE8 upgrade. Been running 6.2.16-15-pve and also tried 6.1.10-1-pve but they are all acting up. Funny thing is that one of the 2.5GB...
  7. leesteken

    Issues to start after reboot or shutdown

    ...BIOS is broken (or only works on Windows). Try a BIOS update and/or contact the motherboard vendor support (which will probably tell you they don't support Linux). There have been lots of problems with Proxmox/Linux on N5105. Please have a look at one of the mega threads about it for...
  8. M

    Issues to start after reboot or shutdown

    ...Arguments are initialized for method [_PLD] However, I'm not sure if these is related or not... My hardware is a minipc with an Intel Celeron N5105 with 16GB RAM, and two ssd disks 500GB, I have installed Proxmox VE 8, it's up to date. I also attach the log from the reboot until the web ui...
  9. S

    [TUTORIAL] Plex + hw transcoding, LXC and Jasper Lake iGPU passthru

    ...enable_guc=2” >> /etc/modprobe.d/i915.conf echo 'options i915 enable_guc=3' >> /etc/modprobe.d/i915.conf echo 'options i915 enable_fbc=1' >> /etc/modprobe.d/i915.conf GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on" still necessary or is tteck plex script enough? I have a n5105 and want to run plex.
  10. T

    Just starting out ...

    Can you indicate if your VM storage is ZFS or Ciph? is there any particular tutorials you used ofr OMV and rclone that I can refer to?
  11. D

    [TUTORIAL] Plex + hw transcoding, LXC and Jasper Lake iGPU passthru

    Thanks. Likewise, I couldn't get the OP tutorial to work after a solid couple of hours of farting about, but the tteck scripted container worked immediately out of the box. Would love to know what, exactly, it does differently, but I can't be bothered as it's now working fine :) In short...
  12. K

    Just starting out ...

    Thanks Louie ... I did look at using a secondhand xeon based system, but as I'm intending to leave this powered on 24/7 I also wanted to not over do it and was hoping for something more power efficient (this uses about 25w at idle with just proxmox installed and disks powered up). Not sure if I...
  13. L

    Just starting out ...

    ...went with a refurbished HP Z640 machine instead as I got a nice bargain on it (Xeon 2690V3, 64GB of ECC ram for ~$300) I have a worry that the N5105 is not enough horsepower, but I have no empirical evidence to back that up. You will get conflicting answers on this as to whether these are...
  14. M

    Upgrade Proxmox install nvme + make redundant

    ...sit on another server that i could switch off when not used. I installed Proxmox (for testing) on a very low power mini pc with an Intel N5105, i slapped in a single small nvme ssd and started using it. Since im liking it so much i want to replace the 256gb ssd for a 1tb ssd and also slap in...
  15. K

    Just starting out ...

    ...is such a thing) of Windows ... just because :rolleyes: The hardware I collated for this experiment is as follows Motherboard - Topton Celeron N5105 CPU/ 2x M.2, 6x SATA and 4x 2.5Gb intel NICS - feels like a great little flexible system 2x 8Gb DDR4 RAM 2x M.2 500Gb NVME drives - currently...
  16. R

    Failure to recognize a drive (all cables, SATA ports work)

    ...to get Proxmox to see this so that I can use it? I can't even tell if this is related to Advanced Format or not to be honest. This is all running on a Topton N5105 board from Ali Express. BIOS only sees one drive with reduced capacity, but Proxmox is correctly seeing all three operational...
  17. G

    [TUTORIAL] Plex + hw transcoding, LXC and Jasper Lake iGPU passthru

    Great tutorial. Unfortunately, my Plex still says "transcoding" and not "hw-transcode." The only difference I have with you is my CPU is i9-11900k, but still should be the same process.
  18. B

    Intel N95 problems with Ethernet and GPU driver

    Hi, I have a similary problem with the r8169 and Intel N5105 with the 6.2.x Kernel. I lose network after a moment and need reboot to work again. Network work fine with kernel 6.1.15. I don't dare to update again my proxmox 8.x; i afraid to break again my network. Perhaps working again with the...
  19. W

    Proxmox VE 8.0+ cpu microcode

    For Debin 12/Bookworm+ they moved firmware blobs to: non-free-firmware If you don't need any software from non-free just change that to non-free-firmware If you do just add it to the end of each of the 3 lines.
  20. K

    VM freezes irregularly

    So you're on 8? How do you update to that microcode exactly for Bookworm? Is this the right way?: By adding this: deb http://ftp.us.debian.org/debian sid main non-free-firmware ...in /etc/apt/sources.list?