| Summary: | impossible to format an nvme partition in Ext4 at install | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jean-François Bachelet <jfbachelet> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | jfbachelet |
| Version: | 8 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Jean-François Bachelet
2022-12-04 12:29:53 CET
Jean-François Bachelet
2022-12-04 12:30:06 CET
CC:
(none) =>
jfbachelet an additional note about another finding in line with this one : I've tried this : putting all / /home and /usr/local on a real harddisk and only use the nvme ssd as SWAP. with the speeeeed that pci4 nvme is capable in both read and write, paging to the swap would be lightning fast compared to swapping on an sata3 harddisk... that was what I thinked. wrong :( I get this message at boot when using such a configuration : 'unable to use the /swap on nvme disk'... not working so :( at install I've seen the nvme /swap being formated by drakdisk so that should be working... so, again, what can go wrong there ? (In reply to Jean-François Bachelet from comment #0) > 3. get the bug :) Your description is missing any useful content or the error message itself so that anybody is able to reproduce. Never had any problem to format a NVME with custom Mageia (8) partitioner. I always do custom partitioning as i want to define the size of the partitions myself and add additional data drives. BTW by using the search function your old bug is easily to find: https://bugs.mageia.org/show_bug.cgi?id=27364 (In reply to Jean-François Bachelet from comment #0) > Note : I've seen something very interesting about this bug, if you let the > auto-partition stuff do its job without modifying any of the created > partitions on the nvme, this time ext4 partitions are formated succesfully ! > and install can continue till end... > > so what happens when I need to custom partition the nvme disk to suit my > needs that make the formating of ext4 parts (and some of other filesystems > tried) failing ??? > I'm a little puzzled there, that bug is nonsense for me, auto-partition it > works, custom-partition it fail... So the bug itself seems incalid as you say yourself, that autopartition works well. Given that Mageia 8 is now 1 and a half year old and nobody else complained about this, it seems that your "procedure" for custom partitioning is fundamental wrong. You could start by describing the complete steps i-n d-e-t-a-i-l which you are doing, so that maybe somebody is able to reproduce what you are doing. I'm not ok with that assumption. why invalid if it is reproduceable each time I try ? why my partitionning scheme would be wrong ? I just create partitions the size I need plus one or two in sus of the usual /, /usr/local, /home and /swap, usualy a /vms for all the virtual machines I create and a /save for stocking some stuff. all of these partitions are purelly normal ones and EXT4. and fail to format on M2 nvme in that case. What I do is only use the tools you distribute to do so and their options. That should not trigger a bug that make formating fail. I've never encountered that bug when working with harddisks, so my surprise when it shows with M2 nvmes. you can try this too : let drakdisk auto partition, then just resize the /home part and click on next, it ask which partition should be formated, tick all of it and see, format of EXT4 parts will fail on an m2 nvme. I already given all explications and bug reports on there : https://bugs.mageia.org/show_bug.cgi?id=27364, I can do more if needed. and just for completeness, some answers in there acknowled the presence of a bug when reading the logs.... That kind of machine is tad expensive, so the time It took to me to have one that I can keep to help chasing the cause of this. (and I needed it to work too ;)) what I see is that that bug is still there in fall 2022 despite I've reported it in fall 2020 and all the updates installed since. don't be so fast to put that under the carpet for whatever reasons. please. at least that's what your reaction to my bz make me think. I'm going to try that with mageia 9 cauldron to see if that's fail with it too ^^) Not reproducible due to lack of informations: - is this disk preformatted with some partitions or is it a really empty disk? - which steps do you chose (as already asked and not answered): https://doc.mageia.org/installer/8/en/content/diskPartitioning.html -> Custom Disk Partitioning ->Auto Allocate->fiddling with size afterwards? -> Use existing partitions ->fiddling with size afterwards? -> Custom Disk Partitioning -> real custom partitioning? -> Use Free Space on a Windows Partition->fiddling with size afterwards? -> ??? In bug 27364 you mention that you have Windows on the same disk. Did you shut down Windows properly and made sure that your disk state is consistent and clean? Which iso do you use? Netinstall or which other ISO? Is your BIOS still heavily outdated as in bug 27364? .... Ever confirmed:
1 =>
0 (In reply to Jean-François Bachelet from comment #5) I just create partitions the > size I need plus one or two in sus of the usual /, /usr/local, /home and > /swap, usualy a /vms for all the virtual machines I create and a /save for > stocking some stuff. > .... > you can try this too : let drakdisk auto partition, then just resize the > /home part and click on next, it ask which partition should be formated, Some important information is missing here. The partition scheme you describe in the first sentence is no "usual" scheme. This not possible to be created by any "autopartition". And please clarify what you are doing as asked in my last comment as there is no "auto partition" mode (at least not called this way in drakdisk) https://doc.mageia.org/installer/8/en/content/diskPartitioning.html - Use Existing Partitions - Use Free Space - Use Free Space on a Windows Partition - Custom Disk Partitioning -> Auto allocate |