![]() If a problem occurs in even just one module or addon during this process, the processing process is stopped and an error code is returned. In the case of TCRP, the steps of loading the device module *.ko file related to the device and loading other addons are processed at once. It would be easier to explain if there was a sample of the /var/log/ log file from Junior mode (DSM Pat file installation stage), which had this problem in the past. I'm curious - I wonder if the fellow I wrote to above this comment who has "No disks FOund" has the same problem I did where the incorrect ixgbe module was preventing the mpt3 module loading properly. Peter my Supermicro board uses the x540-T2 and I have no problems with your loader. The CPU is around 55-60☌ and 20-40% load because of Frigate in Home assistant, I also use Coral AI TPU in my NVME slot. The VM does not freeze but the DSM inside shuts down. Read this topic that someone had similar problem with Intel N5005 but that was for Proxmox 7 (kernel 5.x) but Proxmox 8 has kernel 6.2 already, so I can't really update it. Reinstalled Proxmox completely and tried to leave everything on default and even tried other Synology loaders and switched from 923+ to 920+ with the same error.ĭSM shows nothing useful in error logs and same goes for Proxmox. Randomly I get this error message: Synology was shut down improperly and softreboot itself, Proxmox shows no errors. I have 16gb ram, 8gb for Synology and 4gb for Home Assistant without ballooning, 4gb for proxmox. I have 2 VMs Synology and Home Assistant, both got 4 cores to maximise performance (4 core total). I bought an Intel N6005 board from TopTon on aliexpress, and installed Proxmox 8.0.3.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |