Since I upgraded to 23.10 I have been unable to bak up my system with the
standard ubuntu backup application. On plugging in my drive I get

Unable to access 1.0 terabyte volume

and then

Error mounting/dev/sdd1 at media/jack/0F4690BC#B139EA4: wrong fs type, bad
option, bad superblock on /dev/sdd1, missing codepage of a helper program
or other error

The volume continues to work correctly on my othe , not upgraded computer.

I also run an application called tomboy which now freezes the computer and
I have to reboot.

Any ideas?

Best regards Jack Fearnley

What is your back up drive? I have a 1 Tb Scandisk extreme portable ssd,
and I can not use it with other than copy files to. It is so fast though,
it doesn't matter.

On 3/28/2024 10:18 AM, Jack Fearnley wrote:
> Since I upgraded to 23.10 I have been unable to bak up my system with the
> standard ubuntu backup application. On plugging in my drive I get
>
> Unable to access 1.0 terabyte volume
>
> and then
>
> Error mounting/dev/sdd1 at media/jack/0F4690BC#B139EA4: wrong fs type, bad
> option, bad superblock on /dev/sdd1, missing codepage of a helper program
> or other error
>
> The volume continues to work correctly on my othe , not upgraded computer.
>
> I also run an application called tomboy which now freezes the computer and
> I have to reboot.
>
> Any ideas?
>
> Best regards Jack Fearnley
>

sudo apt install disktype

sudo disktype /dev/sdd

and that will give you a review of the file systems on the disk drive.

File system support depends on the kernel build. A "genkernel" will
likely have a number of things turned on, and it's unlikely that
"something is missing there". But that remains a mechanism where
there can be a support issue caused by bad configuration edits.

If you have built a kernel before, you'll get some exposure to
how some of the switches in the menu interact, and for one file
system, there are a couple places it has to be turned on.

The treeherders at Canonical know all this stuff of course.
They should actually be running test cases, to verify that
a freshly baked kernel, can mount everything OK.

I've had problems before, because the swap partition did not
mount, and that causes some weird "searching" behavior in dmesg.
(It started probing for RAID arrays [mdadm?], BTRFS and shit.)
Make sure your swap is wired properly, and fix the BLKID if you
broke it. Look at your /etc/fstab, and the output of blkid and so on.
I've broken stuff like that, more than once.

You'd be surprised how your install can limp along,
"with a leg missing" :-) I discovered this the hard way
(noticing a lot of mdadm and btrfs messages kinda bothered me).

If "dmesg" doesn't work for you, try "sudo dmesg". Shooting
video of the boot screen (disable "quiet" and "splash") can
also be used as a way to get the details properly. You would
be surprised how the screen version, differs from the logs.
At least I was surprised.

Paul