synoxpe
-
Posts
105 -
Joined
-
Last visited
Everything posted by synoxpe
-
Thanks much for sharing the screenshot @Orphée. I’ve never been able to see these logs yet. I always look at the Console tab appearing just above the Hardware menu item on the left menu bar, which is the novnc console. The Console button on the right as you pointed out on the screenshot seems to be the serial port output then?
-
@Orphée I’ve set up the serial socket but the console only shows till “Booting into Linux” and nothing further when the DSM VM boots. Are you referring to something else or this vnc console?
-
@Orphée keen to hear if you’ve any tips?
-
Awesome man. Will give it a try when I’m back into the arena!
-
UEFI boot worked perfectly with v0.4.5 image on my Intel NUC, I had to turn off secure boot though.
-
DSM is starting fine but crashes spontaneously after running for some time, which ranges from 4 mins to 9 hours. Sometimes I see the confounded e1000e hardware hang messages on proxmox syslog, sometimes not. But the DSM crash happens inevitably and all I get is an email from DSM (which I’ve configured) warning about an “improper shutdown”. The crash is so frequent sometimes that DSM automatically goes to data scrubbing mode to check data integrity, and the crash happens yet again after sometime. As of now I’ve shut everything down to prevent potential data loss. Any pointers are wholeheartedly welcome!!
-
I’m using proxmox 7, DSM 7 using the pocopico tinycore loader 0.4.4. Is the link that you pointed still applicable?
-
What would be a good starting point to troubleshoot an improper shutdown of an instance [ds918+ running on proxmox]? If I ssh in to DSM, I only can see dmesg messages from when the boot up started and not earlier, so it’s not possible to see a possible root cause. @IG-88 @Orphée
-
Thanks for responding @haydibe. I’m running into the Intel Nuc e1000e hardware hang issue which has started to affect the stability of the whole PVE environment all of a sudden. I was using kernel 5.13.9-4. Rolled back to 5.13.9-3 and -2 as well without respite. Seems like I need to reinstall proxmox 7 from the downloaded iso if the this helps. Else I need to turn off the checksum offloading as explained in some workarounds.
-
@IG-88 what happens if the motherboard has more resources than supported by ds918+? Should be a common scenario for bare metal installations.
-
@Peter Suh You need to delete the previously stored key from your authorized_hosts file in the $HOME/.sshd dir. This generally appears as a line starting with the IP address of the node your trying to ssh to. Deleting this line should fix your problem as this will be updated the next time you login successfully with the new key. Having said that, the tinycore boot process regenerates the PKI key pair every time it boots which I think shouldn’t be the case. Perhaps @pocopico has other reasons of making it this way?
-
Yeah VMware is an option indeed but then have to figure out a lot of things like pci passthrough etc. Also the free version has limitations
-
@haydibe you had inspired me to take the proxmox path 😀 and after a short lived bliss the environment has unfortunately become unusable. Curious about your proxmox environment. Which version are you using? Can you please share the details? Also do you know how much hardware the ds918+ can cope up with? I plan to throw Intel i7 12 cores and 32 GB RAM at it if I’m forced to take the bare metal route.
-
What’s the max RAM that ds918+ can work with? After crashing 12 times in as many hours I’ve given up on Proxmox and want to go bare metal on my Intel Nuc 10, which has 32GB RAM.
-
Thanks much for responding @Peter Suh I’ve passed the entire HBA PCI controller to the VM which has been working perfectly so far. Regarding the upgrade to 0.4.5.1, I need to download the new image right? Or the existing 0.4.4 image can be upgraded using rploader update (after clean)?
-
After running the ds918+ off the 0.4.4 image on Proxmox 7 for flawlessly for about a month now, the DSM VM spontaneously started to crash numerous times, over the last 12 hours. I see improper shutdown messages on the DSM log. On the host nothing unusual on the syslog or dmesg. I can’t remember to have done anything to the environment and am absolutely clueless about where to start troubleshooting. Please help 🙏
-
??? I've OOTB support with APC BackUPS No issues here with APC UPS: DSM 7/ds918+
-
Ack!
-
The formatting indeed seems to be the case: root@ds918p:~# iperf3 -c 192.168.1.158 Connecting to host 192.168.1.158, port 5201 [ 5] local 192.168.1.246 port 35082 connected to 192.168.1.158 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 6.31 GBytes 54.2 Gbits/sec 0 3.02 MBytes [ 5] 1.00-2.00 sec 6.34 GBytes 54.5 Gbits/sec 0 3.02 MBytes [ 5] 2.00-3.00 sec 6.19 GBytes 53.1 Gbits/sec 0 3.02 MBytes [ 5] 3.00-4.00 sec 6.31 GBytes 54.2 Gbits/sec 0 3.02 MBytes [ 5] 4.00-5.00 sec 6.29 GBytes 54.0 Gbits/sec 0 3.02 MBytes [ 5] 5.00-6.00 sec 6.30 GBytes 54.1 Gbits/sec 0 3.02 MBytes [ 5] 6.00-7.00 sec 6.25 GBytes 53.7 Gbits/sec 0 3.02 MBytes [ 5] 7.00-8.00 sec 6.24 GBytes 53.6 Gbits/sec 0 3.02 MBytes [ 5] 8.00-9.00 sec 6.32 GBytes 54.3 Gbits/sec 0 3.02 MBytes [ 5] 9.00-10.00 sec 6.22 GBytes 53.5 Gbits/sec 0 3.02 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 62.8 GBytes 53.9 Gbits/sec 0 sender [ 5] 0.00-10.04 sec 62.8 GBytes 53.7 Gbits/sec receiver iperf Done. root@ds918p:~# iperf3 -c 192.168.1.158 -R Connecting to host 192.168.1.158, port 5201 Reverse mode, remote host 192.168.1.158 is sending [ 5] local 192.168.1.246 port 35094 connected to 192.168.1.158 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 5.27 GBytes 45.3 Gbits/sec [ 5] 1.00-2.00 sec 5.47 GBytes 47.0 Gbits/sec [ 5] 2.00-3.00 sec 5.47 GBytes 47.0 Gbits/sec [ 5] 3.00-4.00 sec 5.47 GBytes 47.0 Gbits/sec [ 5] 4.00-5.00 sec 5.42 GBytes 46.6 Gbits/sec [ 5] 5.00-6.00 sec 5.46 GBytes 46.9 Gbits/sec [ 5] 6.00-7.00 sec 5.46 GBytes 46.9 Gbits/sec [ 5] 7.00-8.00 sec 5.45 GBytes 46.8 Gbits/sec [ 5] 8.00-9.00 sec 5.41 GBytes 46.5 Gbits/sec [ 5] 9.00-10.00 sec 5.50 GBytes 47.3 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.04 sec 54.4 GBytes 46.5 Gbits/sec 784 sender [ 5] 0.00-10.00 sec 54.4 GBytes 46.7 Gbits/sec receiver iperf Done. But lower bandwidth from PVE -> DSM and retries seems to be consistent with your findings. @haydibeDo you get the link speed displayed on DSM?
-
Thanks for checking @dodo-dk Perhaps we're using different parameters as in my case transfer is more and bitrate is less: I used on DSM: iperf3 -s -f G onn PVE host: iperf3 -c 192.168.1.xxx -f G Mine is different and also getting lot or retries; [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 54.3 GBytes 5.43 GBytes/sec 1477 sender [ 5] 0.00-10.00 sec 54.3 GBytes 5.43 GBytes/sec receiver both for PVE Host <-> DSM7 VM and inter VM (Ubuntu VM <-> DSM) Thoughts? Maybe master @haydibe has an idea? On the cosmetic side, link speed isn't showing up anymore in Control Panel -> Network -> Network Interface (used to show 100Mbps here when I was using RTL8139)
-
Nice one! thanks. Please share your findings
-
Folks using virtio networking on Proxmox, what link speed are you getting? Network is working but link speed is not showing. Previously it was showing as 100Mbps when I was using the RTL card (which is why I changed to virtio)
-
Anyone got Notifications to work? When I go to Notifications > Push Service, I always get the error message below, although DSFinder is working great on iOS otherwise.
-
Use virtio on Proxmox. Can't get any better.
-
Yes! That did it!! Sometimes you miss the obvious So now this is starting to look like the real deal!
