https://bugs.kde.org/show_bug.cgi?id=453333
--- Comment #9 from daiaji <hentaiwushu...@gmail.com> --- (In reply to Andrius Štikonas from comment #8) > (In reply to daiaji from comment #7) > > (In reply to Andrius Štikonas from comment #6) > > > Might be an issue here: > > > > > > https://invent.kde.org/system/kpmcore/-/blob/master/src/plugins/sfdisk/ > > > sfdiskbackend.cpp#L454 > > > > > > Can you try it with 4096 and 8191? You'll have to rebuild KPMcore. Note > > > that > > > this is just a quick check and will not work with 512 (I guess proper fix > > > would be d.logicalSize() and d.logicalSize() * 2 - 1 > > > > CopySourceDevice source(d, 4096, 1023); > > > > After modifying and compiling the source code here, this fault is > > eliminated. > > Can you please also test with > > qint64 sectorSize = d.logicalSize(); > CopySourceDevice source(d, sectorSize, sectorSize * 2 - 1); https://github.com/daiaji/kpmcore/commit/47e1984febde6ade6740d89457cbf2892ec0d7cd After the source code is modified in this way, it seems that the devices with 4096 byte LBA and 512 byte LBA can normally use kpmcore to create new partitions. But it seems strange that an MBR partition table can be created on an SSD with an LBA of 4096 bytes, even without any modification to the source code, and partitions can also be created on the MBR partition table. Does this check only occur on the GPT partition table? -- You are receiving this mail because: You are watching all bug changes.
