Auto Mount Disc failure?

I have been using KDE for a good while. Everything worked fine.

KDE Plasma 5.27.11, kernel 8.8.0-41
AMD Ryzen 7 5700X 8 core processor, 32G memory
SAMSUNG MZVL4512HBLU-00BH1 (nvme01)
CT1000BX500SSD1 1TB (931Gb)
NVIDIA GeForce RTX 4060/PCIe/SSE2

I originally installed win11 (shudder!), but I reconfigured the drive to dual boot.
All worked fine (well i killed win11 when I tried to put win10 alongside) but eventually I installed win10 (I have legacy ide stuff that didn’t work well in either wine or Virtual box.
I also added another drive CT240BX500SSD1 and installed cinnamon for testing.
All worked fine
I had multiboot, with Ubuntu, Windows Boot Manager and Cinnamon, with the default set to Ubuntu.
All fine.

I needed to tidy up the box itself and properly mount the extra drive (well it did work just hang in space :grinning:)

So the problem. I rerouted the cables and plugged in a more convenient sata cable, effectively swapping places with the 240G & 1TB drive connections.
All fine boot ok but can’t access the 1TB drive. Dolphin returns an error, basically says not sure why …
The other drive (240Gb) is fine, I can access that OK.
Boot into win10 and I can access the 1TB drive.
I can access the ITB drive with KDE Partition Manager and its settings seem to be the same as the 240G drive.
For some reason the 1Tb wont auto mount. I can edit the mount options and mount it manually but once I do that I can’t unmount it.

What am I missing?
All the settings in KDE Partition Manager are the same for each drive. The drive has 1 partition (ntfs so win10 can see it)
The other (240G has 2 one ntfs & one Ext4)

when i want dives to automount, i just use the Disk & Devices icon in the system tray.

uncheck the top row and just go thru and check off the ones in the list you want to have access to in dolphin (check both on login and on attach)

if there are any disconnected drives listed at the bottom you can highlight those and “forget” them, so they don’t cause any confusion with the upper part of the list.

this has been working well enough (if a bit flakey) so that i don’t have to mess with fstab.

Thank you for your reply @skyfishgoo .
Yes that is what I normally do BUT in my case after I changed the physical connection it appears in the list as “mounted” but it is not accessible.
I Thought someone would have come across this sort of thing. Editing the fstab and removing reference to it doesn’t help. It is not mounted but wont auto mount.
It is like the parameters are cached somewhere.

I got around it by recreating the file system (losing the data) though I am almost certain I should not have had to do that.

I will just be aware of it for now, and if it crops up again I will do some digging

Well I started to do a bit of testing.
I have a disk on my system with an older version of windows. Windows took up 13.61G of a 93g disk partition. So I changed its size down to ~15G with KDE Partition Manager and although I can see it with Dolphin I get the following message

An error occurred while accessing ‘temp’, the system responded: The requested operation has failed: Error mounting /dev/sda1 at /media/bernie/temp: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error

BUT (and its a biggy for KDE…) I can access it fine from both win10 AND Cinnamon.

So I changed the mount point to use UUID rather than Device Node, and it now works fine.

So should I use Device Node or UUID and how do I make UUID the default in KDE Partition Manager?

Not sure if it is related but now I can’t see any printers with a similar nondescript message.
Also boot sometimes fails and boots in emergency mode, but if i just continue, it boots up fine.
And no the disk tests as fine. I suspect its a permission problem, I believe Ubuntu is tightening some security settings but trying to decipher what they propose and whether it applies to Kubuntu is just a bit hard.
I did install neon on yet another disk and after the initial Nvidia driver (later model graphics card )install it seems OK. I May have to run in x11 rather than Wayland till a couple of freeby programs catch up but I can live with that.
Normally, I would chase this problem down but I just don’t have the time and need to spend time on a couple of hardware design projects I need to finish.
As such I will mark this as solved.
If that is not appropriate just tell me and I will change it, but I don’t want to waste anyone’s time trying to fix it when I cant contribute