Search results

After upgrade to latest BIOS Micro-Star International Co., Ltd. MS-7D91/MAG Z790 TOMAHAWK WIFI (MS-7D91), BIOS H.H0 08/07/2025 the network interface numbers are changed -> you need to change /etc/network/interfaces . Check ip -a and adjust the file accordingly. I see also ic2 errors -> don't no...

Thanks for the response. Sorry for the late reply. Booting into latest kernel was related to BIOS. After upgrade to latest BIOS Micro-Star International Co., Ltd. MS-7D91/MAG Z790 TOMAHAWK WIFI (MS-7D91), BIOS H.H0 08/07/2025 I was able to boot into kernel 6.17.4-2-pve #1 SMP PREEMPT_DYNAMIC PMX...

Also after bios upgrade and boot into pinned kernel 6.17.2-1 the folowing error appears: Seems to be an i2c bus thing. dmesg | grep i2c i2c_i801 36864 0 i2c_mux 12288 1 i2c_i801 i2c_algo_bit 16384 3 igb,xe,i915 i2c_smbus 20480 1 i2c_i801...

After upgrade to latest BIOS Micro-Star International Co., Ltd. MS-7D91/MAG Z790 TOMAHAWK WIFI (MS-7D91), BIOS H.H0 08/07/2025 the network interface numbers are changed -> you need to change /etc/network/interfaces . Check ip -a and adjust the file accordingly.

I remember indeed IO errors for my disks. Seems to be a know issue with the kernel I pinned the kernel to 6.17.2-1 and will upgrade to latest BIOS

Hi All, I remember indeed IO errors for my disks. I boot from two Samsung 870 EVO SSD as ZFS-R1 for boot and I have wd-black-m2 PCIe This is the hardware of my system: Hardware MAG Z790 TOMAHAWK WIFI The seven SATA 6 Gb/s ports are controlled by the Intel Z790 PCH SATA controller. M.2 / NVMe...

Hardware Micro-Star International MSI MS-7D91/MAG Z Tomahawk 92 GB Memory My boot devices are two SATA SSD's and the data is on 2 * 1 TB PCIe x5 M.2 SSD's I have a working ProxMox server for many years. Working configuration: package versions ProxMox booting into kernel 6.17.2-2.pve...

Lesson learned the hard way :cool:

Solution: see https://www.msi.com/Motherboard/MAG-Z790-TOMAHAWK-WIFI/support#hdd On QVL PCI4 3D TLC Seagate FireCuda 530R-ZP4000GM3A063 Random read/Write (4KB) 1300000 IOPS (MTBF) 1.800.000 = 75.000 days = 204 year! Read 7400 MB/s Write 6800 MB/s

VNAND SSD 990 PRO PCIE NVMe M2 SSD www.delaihe.com/ssd I think I found the reason: https://www.reddit.com/r/hardware/comments/178efvy/fake_39_samsung_990_pro_4tb_ssd_looks_almost_real/ It wasn't even $39 ...

Hi all, Proxmox 8.2.4 up and running incl. all updates. Qnap Nas as source PCIe M2 4TB SSD as destination. IO delay ~ 0,1 to 0,2 0% Shutdown VM Move harddisk from QNAP NAS to PCIe M2 4TB SSD. FileSize = 64 GB copy started ~ 1GB / sec IO delay up to ~ 10% Now stil not ready after 1 HOUR ...

I did not succeed in restoring grub but succeeded in moving the data from non bootable HDD to NAS . DIscussed in Copy lvm disks from HDD-1 to HDD-2

I found the solution from my old Unix Guru If you have a non bootable Proxmox HDD you boot a Ubuntu live CD, Mount your Proxmox HDD .. Mount /mnt/nas towards a NAS. lsblk -> you see the name of the disks and /dev/dm-<number> then dd if=/dev/dm1 of=/dev/nas bs=1024 -> this will dump the lvm...

I checked this threat -> result ... GRUB .. reboot and select proper boot device. Partition not bootable ?? -> boot from EaseUS Partition Master -> looks good to me ... What is the next action?

I booted ProxMox in debug mode. Type command like documentation # proxmox-boot-tool status reply /bin/sh: proxmox-boot-tool: not found. 90% of all command I want to use are not found. What is the purpose of debug mode?

Hi All, I have a non working Proxmox 7.1 installation after the latest upgrade to pve-manager/7.1-10/ Non production repo. The disk is one SDD. I spend 2 days debugging grub errors / boot errors .. I stop now fixing the original disk. I ONLY need the vmdisks located in the lvm volumes. Under...

Hi All, Proxmox 7.1 system is up and running. Last night run upgrade to latest update available ( non production updates) After reboot the error message Grub loading .. error: disk 'lvmid/<number> not found and my system boots into grub rescue. ls hd(0) -> I can see partitions Question: How to...