Announcement

Collapse
No announcement yet.

Partition Manager crashing? unknown file system type "dos"

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Partition Manager crashing? unknown file system type "dos"

    Yesterday I noticed KDE Partition Manager crashes at every attempt to launch. I launched it from konsole and see this:
    Code:
    "Device found: AGAMMIXS70B-1T-CS"
    smartctl initialization failed for "/dev/nvme3n1" : No such file or directory
    error during smart output parsing for "/dev/nvme3n1" : No such file or directory
    unknown file system type "dos" on "/dev/nvme3n1"
    KCrash: Application 'partitionmanager' crashing... crashRecursionCounter = 2
    Segmentation fault (core dumped)
    ​Ok weird. "nvme smart-log" shows no errors or issues. At first I suspected this might be meaningful:

    unknown file system type "dos" on "/dev/nvme3n1"

    Here is the whole konsole output:
    Code:
    stuart@office:~$ partitionmanager
    Loaded backend plugin: "pmsfdiskbackendplugin"
    "Using backend plugin: pmsfdiskbackendplugin (1)"
    "Scanning devices..."
    "Device found: AGAMMIXS70B-1T-CS"
    smartctl initialization failed for "/dev/nvme0n1" : No such file or directory
    error during smart output parsing for "/dev/nvme0n1" : No such file or directory
    unknown file system type "" on "/dev/nvme0n1p1"
    "Partition ‘/dev/nvme0n1p1’ is not properly aligned (first sector: 34, modulo: 34)."
    "Partition ‘/dev/nvme0n1p4’ is not properly aligned (last sector: 2,000,409,230, modulo: 655)."
    "Device found: Samsung SSD 990 PRO 1TB"
    getting temp failed for "/dev/nvme1n1" : No such file or directory
    getting powered on time failed for "/dev/nvme1n1" : No such file or directory
    getting power cycles failed for "/dev/nvme1n1" : No such file or directory
    unknown file system type "" on "/dev/nvme1n1p1"
    "Partition ‘/dev/nvme1n1p1’ is not properly aligned (first sector: 34, modulo: 34)."
    "Partition ‘/dev/nvme1n1p2’ is not properly aligned (last sector: 1,953,525,134, modulo: 1,423)."
    "Device found: Samsung SSD 990 PRO 1TB"
    getting temp failed for "/dev/nvme2n1" : No such file or directory
    getting powered on time failed for "/dev/nvme2n1" : No such file or directory
    getting power cycles failed for "/dev/nvme2n1" : No such file or directory
    unknown file system type "" on "/dev/nvme2n1p1"
    "Partition ‘/dev/nvme2n1p1’ is not properly aligned (first sector: 34, modulo: 34)."
    "Device found: AGAMMIXS70B-1T-CS"
    smartctl initialization failed for "/dev/nvme3n1" : No such file or directory
    error during smart output parsing for "/dev/nvme3n1" : No such file or directory
    unknown file system type "dos" on "/dev/nvme3n1"
    KCrash: Application 'partitionmanager' crashing... crashRecursionCounter = 2
    Segmentation fault (core dumped)​
    3 other nvme drives have the same error but "" instead of "dos". This is probable because this drive is MBR and the other are all GPT. Most of that output shows KDE Partition Manager is attempting to read the smart output for nvme drives, which aren't really smart enabled. There's a different utility called "nvme" that does that sort of thing.

    Opening the suspect drive with gdisk gets me this message:
    Code:
    Partition table scan:
    MBR: MBR only
    BSD: not present
    APM: not present
    GPT: not present​
    
    ************************************************** *************
    Found invalid GPT and valid MBR; converting MBR to GPT format
    in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by
    typing 'q' if you don't want to convert your MBR partitions
    to GPT format!
    ************************************************** *************
    but no errors if I open it with fdisk so this all seems normal.​ I guess I'm going to try and convert it to GPT but Steam is on it so I probably need to backup first. The other stuff in the disk is Win11 and UEFI for it, but I haven't booted it in over a year.
    It definitely is crashing when trying to access nvme3n1 because I see the GUI pause when trying to scan the drive just before crashing. I haven't made any significant changes to this drive or is partitions other than removing a adding a test partition.

    Please Read Me

    #2
    Apparently not just me: https://bugs.kde.org/show_bug.cgi?id=503148

    Please Read Me

    Comment


      #3
      https://bugs.kde.org/show_bug.cgi?id=502141 maybe?

      Are any of the partitions/drives un-formatted? I can get it to crash after zapping the gpt on a flash drive

      Comment


        #4
        Yes, but If you read the bug report it's crashing if ANY VFAT partitions exist on the scanned devices using MBR partitioning and I can verify that.

        Here, I had installed Win11 on the 4th nvme drive and for whatever reason, the Windows installer used MBR. I could see KDEPartMan crash when it scanned the 4 nvme drive.

        I then converted it to GPT and KDEPartMan then crashed when it scanned a USB drive I had plugged in. I then pulled all the USB drives out and KDEPartMan launched successfully.

        Regardless, they've already published a patch so I assume we'll get the fix pretty soon.

        Please Read Me

        Comment


          #5
          It goes weirder.
          The past few KDE neon image builds, calamares crashes when opened for some people. For me it only does so if I have any drive connected with unpartitioned space. Such as when setting up a virtual machine. Or a new bare or wiped drive.

          Kpmcore causes it. This is the same bit that Partition Manager uses under the GUI.

          On top of my first link:
          https://invent.kde.org/system/kpmcore/-/issues/23
          https://bugs.kde.org/show_bug.cgi?id=502141

          Chatting with a dev, I gave that info, and hopefully the libkpmcore fix gets into the next ISO build, which also means (I assume) that Partition Manager should be, as well.

          Comment

          Working...
          X