Oh, sorry, maybe I miss explain or mistake when write... On the same disk of the Proxmox OS I store CTs and VMs... in the other disks I store non important CTs and VMs... Then, I´m right?
But, as I understand, mSATA is a miniSATA... performance is equal than a SATA but in small form factor... if negotiate at SATAII the performance are slow than a SDD negotiated at SATAIII speeds.... Am I right?
mmm, I not make any speed test... I suppose with hdparm to read and dd to write tests.... For my use, my servers goes well but it´s sad that mSATA port not work at 6Gb/s.... but mSATA is a mini SATA... I suppose that the speed of a mSATA and a SATA SSD at 6Gb/s are the same... Tomorrow I´ll move...
I think so... thanks to you that guide me to the solution....
Check my post about the chipset... Means that when have two SATA or mSATA used, the third (and the others) works at SATAII
Oh... tomorrow move the SSDs... leave the mSATA for backups :D
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e02] (rev 04)
Subsystem: Hewlett-Packard Company 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] [103c:3398]
Kernel driver in...
I have one drive (mSATA)to Proxmox Operating System and CTs and VMs... other SSD for CTs and VMs and a last SSD for daily backups...
Maybe to "solve" my issue I´ll use mSATA port to backups and the other ports (working at 6Gb/s) to Proxmox Operating System and for other SSD to store CTs and...
If I search for C210 chipset I found this:
https://ark.intel.com/content/www/us/en/ark/products/66416/intel-c216-chipset.html
And in the middle of the page say:
Total # of SATA Ports 6
Max # of SATA 6.0 Gb/s...
I will put outputs of one server only (to have a short reply :p), because two server all the same, the issue is only on the mSATA. About the cable, it´s an mSATA, no wires, it´s connected direct to the mSATA socket (both servers).
This is the output of the "journalctl -b | grep SATA":
May 23...
Hi, I have some machines with Proxmox installed. The machines are HP8300 USDT. They have an mSATA port and two SATA ports.
The question is... in the two machines the mSATA ports only negotiate at 3Gbps, the mSATA disks are 6Gbps but only run at 3Gbps. I know mSATA ports works at 6Gbps, right...
Yeah, some days working with the new SSD for VMs and CTs and other HDD for backups and no more delays and no more machines stuck...
The issue, a new SSD
Regards!!
Hi, I swapped a SDD with an LVM volume and I´m trying to delete and use with FAT32 format but it´s impossible.... I have the SDD with an sata adapter connected in a computer with Debian 11
lvdisplay and I get the VG Name...
then
lvremove proxvg (the name) then ask for remove 22 dependent...
Finally , I think found the issue... saturday I change the "backup" hard disk... the hdd that spin on and off lot of times... and the next day I got issue that one proxthin sdd was fail (in the proxmox I have the system in a msata unit and a SDD with the VMs and CTs) and the HDD for backups...
Yes, I know, the hard disk is at minimum power saving... maybe the hard disk could be failing? could be a good idea to change the hard disk for another one?
Yes, maybe this disk was from a laptop disk... I use only for store backups, templates and isos... then you saw changing APM to 192 could solve this issue... I´ll change it...
I have other proxmox server with same configuration and same disk drive and has double hours and half headparkings...
Hi, thanks for your prompt reply, I´ve fixed the thread and added "CODE" tags... no, the CPU is not slow... this issue start 10th Feb of this year... machine working two years ago without troubles... then the CPU could not be the trouble... and the same backup configuration....
Regards!!
Hi, issue again... it´s not a Windows 10 machine issue... again it´s with high delay and and un-finished backup task... anyone can help me with this issue?
Hi, finally solved, finally I go shut down VM to VM and a Windows 10 machine was doing the issues with the backups and causing the IO delay... deleted Windows 10 machine and installed in their place a Linux Mint machine.... issue solved!!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.