NTFS Festplatte kann nicht gemounted werden

TriumphOfDeath · September 24, 2023, 3:55pm

… hi,
seit gestern kann ich meine NTFS Festplatte in EndeavourOS KDE nicht mehr mounten.

Im Terminal bringt er:

udisksctl mount -b /dev/sdb1
Error mounting /dev/sdb1: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sdb1 at /run/media/terrorizer/TV: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error

sudo fdisk -l
[sudo] Passwort für terrorizer:
Festplatte /dev/sda: 931,51 GiB, 1000204886016 Bytes, 1953525168 Sektoren
Festplattenmodell: ST1000VM002-1ET1
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Größe (minimal/optimal): 4096 Bytes / 4096 Bytes
Festplattenbezeichnungstyp: dos
Festplattenbezeichner: 0x2a36203d
Gerät Boot Anfang Ende Sektoren Größe Kn Typ
/dev/sda1 * 2048 1953520064 1953518017 931,5G 83 Linux

Festplatte /dev/sdb: 465,76 GiB, 500107862016 Bytes, 976773168 Sektoren
Festplattenmodell: 2105
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Größe (minimal/optimal): 4096 Bytes / 4096 Bytes
Festplattenbezeichnungstyp: dos
Festplattenbezeichner: 0xa75b10f4
Gerät Boot Anfang Ende Sektoren Größe Kn Typ
/dev/sdb1 2048 976773119 976771072 465,8G 7 HPFS/NTFS/exFAT

komischerweise funktionieren andere USB-Sticks mit NTFS ganz normal & diese Festplatte läßt sich auf meinem Linux-Laptop ganz normal einbinden ??!!??

joekamprad · September 24, 2023, 6:12pm

Könnte das hier sein:

github.com/storaged-project/udisks

Issue with kde plasma and udisks 2.10

opened 10:16PM - 06 Jul 23 UTC

closed 11:58AM - 04 Sep 23 UTC

alexjp

Nixos distro updated udisks to 2.10 some days ago, and since then, kde plasma st…arting up and at first login freezes for some 5 seconds ( and has other issues, which seems like plasma crashed, although logs don't show any crash ). This only happens at the first login after boot, being the following ones without this issue. Going back to 2.9 fixes this. Also disabling udisks fixes the freezing. I also tested on archlinux, manually updating udisks2 and libblockdev packages and the issue happens also on archlinux. I apologize because I don't have enough tecnical knowledge to give more detailed info, but I have 2 nvme disks and 2 hdd disks. I also see this on the systemd udisksd unit log: ``` udisksd[1486]: udisks daemon version 2.10.0 starting udisksd[1486]: Failed to load config files: Failed to get contents of the config dir (/etc/libblockdev/3/conf.d/)Error opening directory “/etc/libblockdev/3/conf.d/”: No such file or directory. Using the buil t-in config udisksd[1486]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1) udisksd[1486]: Acquired the name org.freedesktop.UDisks2 on the system message bus ``` If more info is required, feel free to ask. Sorry if this issue isn't valid. Thanks!

TriumphOfDeath · September 25, 2023, 9:29am

OK, danke, das schau ich mir mal an !!!

TriumphOfDeath · September 25, 2023, 9:55am

… das scheint tatsächlich der Fehler zu sein, aber ich weis die Befehle nicht um diese 2 Pakete downzugraden ???

joekamprad · September 25, 2023, 11:43am

sudo downgrade udisks2 libblockdev

Und wähle die vorhergehenden Versionen

TriumphOfDeath · September 26, 2023, 10:07am

… dieser Befehl hat bei mir das Problem beseitigt ohne downzugraden:

sudo ntfsfix -d /dev/sdb1

joekamprad · September 27, 2023, 9:09pm

besser als ein workaround

priten · October 16, 2023, 11:34pm

Thank you very much for this command. It helped solve my problem as well!

Adifix · November 26, 2023, 3:08pm

Sehr schön! Ich hatte das gleiche Problem und der Befehl hat es gelöst.
Vielen Dank.

joekamprad · December 1, 2023, 5:17pm

Herzlich willkommen im Forum und im deutschen subForum natürlich besonders.