| Summary: | upgrading an encrypted system destroys home partition | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Need Real Name <lsof> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | anaconda-maint-list, _deepfire, jonathan, lsof, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-19 22:44:57 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Need Real Name
2011-12-19 21:16:44 UTC
Anaconda does not format any filesystems when performing an upgrade. Please attach the following log files, individually, as text/plain: /tmp/anaconda.log /tmp/storage.log /tmp/program.log /tmp/syslog They are accessible from the shell on tty2, which you can reach by pressing <ctrl>+<alt>+<f2>. Thanks. I thought anaconda formatted at least the system partition. Does it even not format filesystems that are encrypted? I don't have those files any more - sorry. I've done a fresh reinstall. (In reply to comment #2) > I thought anaconda formatted at least the system partition. > > Does it even not format filesystems that are encrypted? It absolutely does not format any filesystems during an upgrade. During a fresh install it does at least reformat the root filesystem. > > I don't have those files any more - sorry. I've done a fresh reinstall. Okay. I'm going to have to close this due to a lack of information, then. I've been basically run into the almost same scenario as the original bug reporter, by the install process. Similarities to his situation: 1. Upgrading using the install process. 2. Encrypted /home partition (LUKS). 3. Not being careful enough during install. Was upgrading from F15. I have been quickly clicking through the anaconda's dialogs, expecting that I'd be offered to upgrade at some point. This never happened, as, apparently, anaconda has failed to detect the existing F15 install. Still, at the point of partitioning/formatting I was operating under assumption that it did operate in "upgrade" mode, and happily agreed to lose all my precious data. I was very sad. BTW, I suggest that no detected[1] /home is ever reformatted, and is instead taken over, with content moved to a per-user subdirectory, say ~/old-home. -- 1. ..hopefully, such detection can be made more reliable than detection of existing Fedora installs.. I suggest the existing encryption key be reused and my /home partition not formatted. |