Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1639021
Summary: | Can't restore partition with KDE Partition Manager | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ivan Romanov <drizt72> | ||||||||||
Component: | kde-partitionmanager | Assignee: | Mattia Verga <mattia.verga> | ||||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 30 | CC: | mattia.verga, thomasj | ||||||||||
Target Milestone: | --- | Keywords: | Reopened | ||||||||||
Target Release: | --- | ||||||||||||
Hardware: | Unspecified | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | kde-partitionmanager-4.0.0-1.fc30 | Doc Type: | If docs needed, set a value | ||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2019-05-22 15:59:03 UTC | Type: | Bug | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Attachments: |
|
Created attachment 1493689 [details]
Screenshot
I think the problem is that in the end it tries to check the whole disk instead of the partition. It only fails the check, not the restore, so it should be safe. I'll report this upstream. https://bugs.kde.org/show_bug.cgi?id=399791 This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This will soon be fixed by the upcoming kde-partitionmanager 4.0.0. Moving to F30 for the moment. kde-partitionmanager-4.0.0-1.fc30 kpmcore-4.0.0-1.fc30 calamares-3.2.7-3.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea83c1a9f9 calamares-3.2.7-4.fc30, kde-partitionmanager-4.0.0-1.fc30, kpmcore-4.0.0-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea83c1a9f9 calamares-3.2.7-6.fc30 kde-partitionmanager-4.0.0-1.fc30 kpmcore-4.0.0-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea83c1a9f9 calamares-3.2.7-7.fc30, kde-partitionmanager-4.0.0-1.fc30, kpmcore-4.0.0-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea83c1a9f9 calamares-3.2.7-10.fc30 kde-partitionmanager-4.0.0-1.fc30 kpmcore-4.0.0-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea83c1a9f9 calamares-3.2.7-10.fc30, kde-partitionmanager-4.0.0-1.fc30, kpmcore-4.0.0-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea83c1a9f9 Doesn't fixed in kde-partitionmanager-4.0.0-1.fc30.x86_64. The same problem Created attachment 1565953 [details]
Restoring error in 4.0.0 version
calamares-3.2.7-10.fc30 kde-partitionmanager-4.0.0-1.fc30 kpmcore-4.0.0-2.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea83c1a9f9 calamares-3.2.7-10.fc30 kde-partitionmanager-4.0.0-1.fc30 kpmcore-4.0.0-2.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea83c1a9f9 calamares-3.2.7-10.fc30, kde-partitionmanager-4.0.0-1.fc30, kpmcore-4.0.0-2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea83c1a9f9 calamares-3.2.8-3.fc30 kde-partitionmanager-4.0.0-1.fc30 kpmcore-4.0.0-2.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea83c1a9f9 calamares-3.2.8-3.fc30, kde-partitionmanager-4.0.0-1.fc30, kpmcore-4.0.0-2.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-ea83c1a9f9 calamares-3.2.8-3.fc30, kde-partitionmanager-4.0.0-1.fc30, kpmcore-4.0.0-2.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. Problem is not solved. (In reply to Ivan Romanov from comment #19) > Problem is not solved. Please tell us more and post the full log. What kind of filesystem is in the backup file? Are you restoring to an already existent partition, or to free space (and let partitionmanager create the partition)? I cannot reproduce the problem anymore with kde-partitionmanager-4.0.0-1.fc30 / kpmcore-4.0.0-2.fc30 KDE Partition Manager: SMART Status Report Date: 5/21/19 8:50 PM Program version: 4.0.0 Backend: pmsfdiskbackendplugin (1) KDE Frameworks version: 5.57.0 Machine: Linux lix 5.0.16-300.fc30.x86_64 #1 SMP Tue May 14 19:33:09 UTC 2019 x86_64 Restore partition from ‘/home/taurus/develop/efi.backup’ to ‘/dev/sda2’ Job: Restore the file system from file ‘/home/taurus/develop/efi.backup’ to partition ‘/dev/sda’ Copying 10 blocks (104857600 bytes) from 94371840 to 73495740416, direction: right. Closing device. This may take a few seconds. Restore the file system from file ‘/home/taurus/develop/efi.backup’ to partition ‘/dev/sda’: Success Job: Check file system on partition ‘/dev/sda’ Command: fsck.fat -a -w -v /dev/sda Check file system on partition ‘/dev/sda’: Error Checking target file system on partition ‘/dev/sda’ after the restore failed. Restore partition from ‘/home/taurus/develop/efi.backup’ to ‘/dev/sda2’: Error Created attachment 1571702 [details]
My HDD partitions
I did simple actions. First backup /dev/sda2 to efi.backup file. And then restore efi.backup back to /dev/sda2. Are you sure you have upgraded kpmcore to 4.0.0-2? Can you post the output of "rpm -q kpmcore"? From the line Job: Restore the file system from file ‘/home/taurus/develop/efi.backup’ to partition ‘/dev/sda’ it seems you are still using 4.0.0-1. $ rpm -q kpmcore kpmcore-4.0.0-1.fc30.x86_64 I update kpmcore. Now I have such error: Restore partition from ‘/home/taurus/efi.backup’ to ‘/dev/sda2’ Job: Restore the file system from file ‘/home/taurus/efi.backup’ to partition ‘/dev/sda2’ Copying 10 blocks (104857600 bytes) from 94371840 to 73495740416, direction: right. Copying 10 blocks (104857600 bytes) finished. Closing device. This may take a few seconds. Restore the file system from file ‘/home/taurus/efi.backup’ to partition ‘/dev/sda2’: Success Job: Check file system on partition ‘/dev/sda2’ Command: fsck.fat -a -w -v /dev/sda2 Check file system on partition ‘/dev/sda2’: Success Job: Maximize file system on ‘/dev/sda2’ to fill the partition Resizing file system from 104857600 to 204800 sectors. Command: fatresize --verbose --size 104857600 /dev/sda2 Maximize file system on ‘/dev/sda2’ to fill the partition: Error WARNING: Maximizing file system on target partition ‘/dev/sda2’ to the size of the partition failed. Restore partition from ‘/home/taurus/efi.backup’ to ‘/dev/sda2’: Warning Yes, this other error is expected, but it doesn't hurt anything (in fact, the job now ends with a warning, not with an error). I'll report this warning to upstream, but I'm going to close this bug since the restore operation itself is now performed without errors. Thanks! |
Created attachment 1493688 [details] Restoring log Description of problem: When partition manager restores a partition it uses incorrect command to resize partition after restoring. Actually it tries to resize whole disk (/dev/sda) instead of targeted partition (/dev/sda1) Version-Release number of selected component (if applicable): kde-partitionmanager-3.3.1-2.fc28.x86_64 How reproducible: always Steps to Reproduce: 1. Try to restore any partition with partitionmanager Actual results: Error when trying to resize partition. Partition seems ok and contains files. Expected results: No any errors.