Search results

I'm trying to track down where things are going wrong. So far I've been experimenting with an Ubuntu guest within Proxmox. But it looks like the problem is coming from below - virtio/qemu or something like that. So I need to debug down into the Proxmox side. I will install a Proxmox in a VM so...

Ah yes, exactly the same usecase as Thomas in comment #9. Given the dates on that bug, I assume it's at the bottom of the priority list though :-(

I'm experimenting with some OS changes that I would like to roll back if things fail. But I have several GB (approaching a TB) of data that I need to test with after the changes are in place. Back in the day on ESXi, I would just mark the "data" drive as "independent", and snapshots would ignore...

Yeah that's basically what's being done in the Bugzilla. But it only changes the physical sector size, so blocks are still reported 512/4096 instead of 4Kn.

I did a bit of testing and updated the Bugzilla. TRIM is definitely throwing errors when the device is set to 4K/4K sectors.

Yeah I will try something to see if it would at least work, and if I get any obvious errors without too much effort. One question: Where do I specify the global options?

Thanks for the related link. I hadn't thought of the bootability issue if I create the drive with 4Kn sectors. But I think I agree with Bug 3200 - shouldn't the drive by default be created with the underlying block size. Then if for some reason (boot would be a good one) 512e is required for...

So in Proxmox itself, /dev/sda reports as 4096/4096. If I create a VM and install Ubuntu in the Thin-LVM storage VM (where the Thin-LVM is on the 4Kn drive), then Ubunty will report 512B sectors. Now from Proxmox again, if I do "fdisk -l /dev/mapper/RAID-vm-blahblah" it shows me nothing since it...

I just set up a new Proxmox 7.0 on a 4Kn native array. Everything is running, and I can create and run VMs fine. But the VM disks I create are treated as 512B drives. This works within the VM - but from the Proxmox host, I can't do any mounting or inspection of the drives since the sector size...

Did anything ever get resolved here? I'm in the same boat (native 4k HDD), but QEMU DISK reports 512B. The VM works, but I *really* prefer to be able to mount the disks from the Promox host too,

Hmm it's definitely something with the RAID array. I could install on a SATA drive plugged into the AHCI interface on the motherboard.

Exactly same problem here. Also an Intel S5520HC motherboard. Drives is a large array on a MegaRAID controller. (6.3 installed fine on the same hardware when that came out) Did you guys get anywhere on tracking the issue down?