Search results

When I enter a receiver e-mail address and I use a capital at the start (eg. Kim@example.com) proxmox adds the entry as a separate receiver address. So I got 1 entry with Kim@example.com which includes an address I want to block (eg *@chambers.com) and there is another entry kim@example.com...

try the solution in this thread https://forum.proxmox.com/threads/upgrading-to-6-8-kernel-makes-my-raid-disks-dissapear.148027/#post-669565 works for me

Hoi Leesteken, it seems to be working thanks. I am curious how Proxmox is going to be offering this as a fix.

I get this message in journalctl May 29 04:56:41 pxve01 kernel: megaraid_sas 0000:01:00.0: Init cmd return status FAILED for SCSI host 0 May 29 04:56:41 pxve01 kernel: megaraid_sas 0000:01:00.0: Failed from megasas_init_fw 6539

thanks for the heads-up. let's hope for a fast resolve

After upgrading to 6.8 my system no longer has any disks on the raid controller visible in Proxmox. When booting 6.5 again the disks are back. Controller is Megaraid 9341-4i with latest firmware

can this be related? https://forum.proxmox.com/threads/lsi-megaraid-9341-4i-controller-supported-in-proxmox-ve-8.138728/#post-661190 since I am also using the MR9341-4i in the servers with the slow performance

The storage is a HUS726T4TALE6L4 WD Ultrastar DC connected as JBOD on a LSI MR9341-4i I have tried several sources; 1. RAID1 with the same disks as the one above 2. Samsung MZ7L3240HCHQ-00A07 There is no speed difference between the sources. And only the write to the JBOD is slow. Writes to...

I have the card running in 8.2.2 but I do have performance issues on JBOD since 8

Some other test: copied a 2.2 GB file of random data to that single disk and that only took a couple of seconds. I don't believe this is a hardware issue with all the tests done. This is some Proxmox bug

Am I really the only person here with this issue? I cannot believe this. I have this issue on 4 different systems (2 asus and 2 supermicro). The only thing they have in common is the same harddisk type and RAID controller type.

This happened in some version of Proxmox because I used to have normal transfer speeds in Proxmox 7.x or 6.x (it's been a while since I used the extra disk)

The question: why does proxmox almost grind to a halt after copying 2.0 GB of data ?

just 0.2 GB extra took 75 seconds more this is the move of a 2.2 GB disk in 1m37s create full clone of drive scsi1 (local-lvm:vm-100-disk-1) Logical volume "vm-100-disk-0" created. transferred 0.0 B of 2.2 GiB (0.00%) transferred 23.9 MiB of 2.2 GiB (1.06%) transferred 48.1 MiB of 2.2 GiB...

Moves up to 2GB of data are fast, this one took 22s create full clone of drive scsi1 (local-lvm:vm-100-disk-1) Logical volume "vm-100-disk-0" created. transferred 0.0 B of 2.0 GiB (0.00%) transferred 21.9 MiB of 2.0 GiB (1.07%) transferred 44.0 MiB of 2.0 GiB (2.15%) transferred 65.9 MiB of...

Still hoping to start a dialogue here ;) Doing a dd I get a value of 241 MB/s for 32 GB root@pve2:~# dd if=/dev/zero of=/dev/sda bs=1536M count=20 20+0 records in 20+0 records out 32212254720 bytes (32 GB, 30 GiB) copied, 133.783 s, 241 MB/s So why am I getting these terrible values in...

my best guess would be that the proxmox server is not on the same physical network as your other computer or you have some faulty network equipment

you should be able to ping, ssh and reach the web interface. can you ping your computer 192.168.1.133 from the proxmox server 192.168.1.5 ?

what ip address are you pinging from?

have you tried https://192.168.1.5:8006 ? and also a ping to 192.168.1.5 ?