[SOLVED] Unable to mount USB sticks

[GerardV]

All of a sudden i have been unable to mount any USB stick. The system, 26.04, will see them but when i try to mount any of them i get this error:

gerard@gerard-kubuntu2:~$ udisksctl mount -b /dev/sdc1
Error mounting /dev/sdc1: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting system-managed device /dev/sdc1: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error

I get the same error message when trying to mount it in Dolphin
They all mount just fine in CashyOs and Deepin also installed on the pc so that rules out a hardware error
Has anyone seen this before?

[oshunluvr]

Does it mount without udisksctl?

sudo mount /dev/sdc1 /mnt

Any output in dmesg when it fails?

Do the file systems have labels? I read somewhere about a bug in udisksctl if the file system is unlabled.

[die.boer]

have you tried

sudo apt update && sudo apt full-upgrade

and

sudo dpkg --configure -a

sudo apt --fix-broken install​

[jlittle]

IME (see https://www.kubuntuforums.net/forum/...unt-with-25-10) once udisks gets confused it can remain in that confused state until a reboot. What file systems are on the sticks? Do they all fail after a reboot?

[skyfishgoo]

it's working again now, all up to date.

but still getting this when i try to access the software updates GUI


it starts if i run sudo software-properties-qt in a terminal tho

[skyfishgoo]

the console gives this when i run it

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'

​

should i enter a value for that variable in this field, or is this normal?

[GerardV]

Does it mount without udisksctl?

sudo mount /dev/sdc1 /mnt

Any output in dmesg when it fails?

Do the file systems have labels? I read somewhere about a bug in udisksctl if the file system is unlabled.

This is the output from from both commands:
gerard@gerard-kubuntu2:~$ sudo mount /dev/sdc1
[sudo: authenticate] Password:
mount: /media: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.


gerard@gerard-kubuntu2:~$ sudo dmesg -l err,crit
[ 3.540419] i2c i2c-1: Invalid 7-bit I2C address 0xffff
[ 9.852407] kvm_amd: CPU 1 isn't AMD or Hygon
[ 9.996686] kvm_amd: CPU 0 isn't AMD or Hygon
[ 10.031204] kvm_amd: CPU 11 isn't AMD or Hygon
[ 81.923939] FAT-fs (sdc1): bogus number of reserved sectors
[ 85.084389] FAT-fs (sdc1): bogus number of reserved sectors
[ 129.894739] FAT-fs (sdc1): bogus number of reserved sectors



I have tried the USB sticks on my Lenovo T490 with the same install with no issues. Both the pc and the Lenovo have the backports enabled.

[GerardV]

have you tried

sudo apt update && sudo apt full-upgrade

and

sudo dpkg --configure -a

sudo apt --fix-broken install​

I had a few updates and no errors were found with dpkg.

This came up with sudo dmesg -w
FAT-fs (sdc1): Can't find a valid FAT filesystem

which is odd as it has been formatted to ext 4

[skyfishgoo]

sudo apt --fix-broken install​

should actually be

sudo apt install --fix-broken

[die.boer]

should actually be

sudo apt install --fix-broken

both commands does the same thing , doesn't matter if install comes before or after --fix-broken

[skyfishgoo]

weird, it does on my machine (plasma 5)

E: Command line option --fix-broken is not understood in combination with the other options

apt 2.8.3 (amd64)

and since we are in the 20.04 sub, i think it matters to get the command correct for others to use.

[Snowhog]

since we are in the 20.04 sub

24.04, not 20.04

[oshunluvr]

weird, it does on my machine (plasma 5)

E: Command line option --fix-broken is not understood in combination with the other options

apt 2.8.3 (amd64)

and since we are in the 20.04 sub, i think it matters to get the command correct for others to use.

Weird indeed since both work here...

[GerardV]

I end up doing a system restore from a backup created with Timeshift and all is good now.
Thank you all for your replies and suggestions.

[claydoh]

weird, it does on my machine (plasma 5)

E: Command line option --fix-broken is not understood in combination with the other options

both commands does the same thing , doesn't matter if install comes before or after --fix-broken

Or just use what has worked everywhere for years and uses fewer keystrokes.

sudo apt -f install​

Or

sudo apt install​ -f

it is interesting that the ordering of this switch does not matter, but the longhand version does here.

claydoh@blinken:~$ sudo apt --fix-broken install
E: Command line option --fix-broken is not understood in combination with the other options

claydoh@blinken:~$ sudo apt install --fix-broken
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 to upgrade, 0 to newly install, 0 to remove and 19 not to upgrade.

claydoh@blinken:~$ sudo apt install -f
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 to upgrade, 0 to newly install, 0 to remove and 19 not to upgrade.

claydoh@blinken:~$ sudo apt -f install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 to upgrade, 0 to newly install, 0 to remove and 19 not to upgrade.

I have noticed the significant changes Debian has made to apt, but I thought it was mostly cosmetic.

Even Debian can change things up, it seems
It is easy to assume that their new ways were their old ways lol, though this one is not in the current Stable.