Why doesn't my internal drive appear in Dolphin?

[Qqmike]

Yeah, and I can't help but feel this has a lot to do with btrfs, but not sure why it would.

[oshunluvr]

I've been using btrfs since 2009 and never had a file system error that wasn't caused by a hardware failure - like a bad SATA cable for example.

[Qqmike]

I've been using btrfs since 2009 and never had a file system error that wasn't caused by a hardware failure - like a bad SATA cable for example.

Well, yeah.
It would seem that a systematic plan is needed, like
(1) Check the filesystems (with fsck).
(2) Check hardware -- cables and hard drive (maybe with SMART? think there's how-to's on that, and maybe the self-checking feature may be helpful, not sure as I haven't looked into it for a very long time).

However, there is one thing that I'm not sure of. He said he copied the root fs over? Not sure what's involved with that, unless somehow it could bring some bad stuff with it, being detected by that Emergency Mode deal?

[oshunluvr]

However, there is one thing that I'm not sure of. He said he copied the root fs over? Not sure what's involved with that, unless somehow it could bring some bad stuff with it, being detected by that Emergency Mode deal?

Sounds like he meant he copied the subvolume over which can cause booting problems because our version of GRUB looks for specific kernel versions rather than the symlinks by default.

[Qqmike]

Hmmm. Hopefully he will see your posts. He has already re-installed GRUB. Little bit of a puzzle here! ha-ha
Maybe run some sort of diagnostics to see what that "Emergency mode" might be upset about?

[Qqmike]

Just noticed:
Kubuntu 22.04
K (Start) > System > Info Center > Devices > Smart status

[oldgeek]

I ran the GSMART analysis which said that the disk passed. So I guess it isn't the disk. My guess is that something happened when sending my btrfs snapshot of @ from the external HD to the internal one, as I ran into a glitch in the @home subv of the same date and time and had to use an earlier snapshot on the new install. I'm considering re-installing 24.04 again and using the @ subv which is installed and then try to re-install what is missing. I don't particularly want to do that, but if I have to I will, as I'm still getting the error message, and the suggestions from fsck don't seem to be working at all.

[oldgeek]

If anyone is still reading this, I solved my problem by re-installing 24.04 and only changing the @home subvolume. No more error messages!

[Qqmike]

It's good you found a doable solution!
Probably should mark your thread "Solved."