https://bugs.kde.org/show_bug.cgi?id=373355
--- Comment #2 from dreyerbe...@hotmail.de --- Good afternoon, great thanks Andrius. After I have modified a partition with Gparted, it took a bit longer, before, after recognition of the USB-drive, the volumes of the disk in question disappeared again in the Windows Explorer. So, I could start Testdisk and select the questionable disk in the USB-drive. After scanning, Testdisk found the boot sector of the fist partition being longer than expected. After that, I have written a new boot sector using the Testdisk tools and as a result all disk partitions are fully accessible now. Kindest regards Bernd Dreyer -----Ursprüngliche Nachricht----- Von: Andrius Štikonas [mailto:bugzilla_nore...@kde.org] Gesendet: Dienstag, 6. Dezember 2016 16:22 An: dreyerbe...@hotmail.de Betreff: [partitionmanager] [Bug 373355] Damaged partition table - file system type reported as empty https://bugs.kde.org/show_bug.cgi?id=373355 Andrius Štikonas <andr...@stikonas.eu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Andrius Štikonas <andr...@stikonas.eu> --- 8 MB gaps might be cause by partition alignment but it's nothing too serious. In the worse case you just loose a tiny amount of space an slight reduction in performance. Please be careful before proceeding, I'm not sure what Mini Tool has broken. Make sure you have backup of all your data. Changing fs in partition properties dialog would format that partition from scratch, this is not what you want, don't do it. But I would need more information to be able to help... E.g. what kind of partition table you have, maybe some screenshots what partition manager shows etc... Also if you have not enabled log output in kde partition manager (in view menu) then enable it, it can show useful errors. You can try to inspect what is your state of partition table with some tools, e.g. fdisk. If your hard drive is at /dev/sda, then run sudo fdisk /dev/sda and press p to show state of the hard drive. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
