https://bugzilla.suse.com/show_bug.cgi?id=1190939
https://bugzilla.suse.com/show_bug.cgi?id=1190939#c5
Stefan Hundhammer changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(steven.quinata@su
| |se.com)
--- Comment #5 from Stefan Hundhammer ---
Steven, do you remember what was on that SSD previously?
Did you have a filesystem directly on the disk and no partition table? To me it
looks very much like that.
Creating a partition table with a tool like fdisk or parted will overwrite only
the first few blocks, and thorough tools like that parted call may still detect
a signature of a filesystem. That kind of warning may alert you that you may be
in the process of doing something very destructive; you may change your mind
and try to use (external) tools to try to restore something half-wrecked.
Some of the tools that we use from YaST via libstorage-ng perform such checks;
that's why we usually use tools like wipefs to zero existing signatures of
filesystems, LVMs, MD-RAIDs etc.; if you removed a preexisting filesystem
manually with parted or fdisk, that won't happen, and such warnings may appear.
Is this a plausible scenario in your case?
If yes, this was a legitimate warning, and you did the right thing by simply
confirming it; as you wrote, the installation went without problems otherwise.
--
You are receiving this mail because:
You are on the CC list for the bug.