Summary: | KDE doesn't detect all the mounted partitions | ||
---|---|---|---|
Product: | [Unmaintained] solid | Reporter: | aditsu <aditsu> |
Component: | libsolid-hal | Assignee: | Alberto Villa <avilla> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | afiestas, kdelibs-bugs-null |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | solid-hardware list on laptop |
Description
aditsu
2009-11-16 12:19:11 UTC
Some further details: after the system suddenly froze and I did a cold reset, storage3 was not mounted but I could see "/dev/sdb4 (not accessible)" in the widget. After mounting it, it still says "/dev/sdb4 (not accessible)" but shows the used/free space. And it looks ok in KInfoCenter. "/" is still missing. The widget has been working better for a long time now. I recently upgraded to kde 4.7.0. The widget configuration lists all the mounted partitions (most of them are RAID now), but it also lists all the raw RAID partitions (array members) for some reason, it doesn't make much sense. And the disk information in KInfoCenter is very confusing now: it has about 30 devices in Device Viewer - Storage Drives; they're all named either "Hard Disk Drive" or a hard disk's model number, but there's absolutely no device name (/dev/something) or mount point (/mnt/something) shown anywhere. So there are still some issues, but maybe not the same bug. Is this still happening with modern linux? Latest Kubuntu/Opensuse/Fedora? Thanks ! (In reply to comment #3) "modern linux? Latest Kubuntu/Opensuse/Fedora?" what in the world are you talking about? I'm using kernel 3.6.11 so it's fairly modern, but what does that have to do with anything? And what's the point in asking me about Kubuntu/Opensuse/Fedora?! I don't use any of those distros, I use Gentoo. And "latest" is not a version number, it doesn't really have any objective meaning. Did you perhaps want to ask about (specific) newer kde versions? I wanted to say anything with KDE 4.10 and recent udisk1/2 recent Kernel (3.7 or 4.8). I'm not using kde 4.10 yet, but will post an update after I upgrade. Partition info is really basic stuff, I don't think the kernel makes any difference, as long as it's not older than 2.4 or something. Even if udev 197 is required, any kernel 3.x should do. Also, kernel 4.8? I haven't heard of that. C'mon it is a typo there is no need to be picky. Execute: solid-hardware list Check if the device is in that list or not. If it is then proceed with: solid-hardware details /path/to/the/device Also compare the result from solid-hardware with "udisk --enumerate" may be useful. Hi, sorry for being "picky", I was probably having a not-so-good day. I'm running KDE 4.10.1 on my laptop now, with kernel 3.7.10. I only have one SSD and an SD card reader. No RAID. KInfoCenter still shows a lot of confusing / not useful information - under "storage devices" I can see two "hard disk drive" items, one of which has 9 identical sub-items (apparently showing the full model number of the SSD). Double-clicking each one shows more information such as file system type, label, UUID and mount point; no device name. Apparently they are supposed to be the drive's partitions?! I can provide more info with a RAID setup once I get my main computer running again and upgrade to KDE 4.10. "solid-hardware list" lists a LOT of low-level things that are not obviously useful. At least 10 of them seem to refer to my SSD or one of its partitions. I'm not sure what to do next. Even if you think the output from the commands requested in comment #7 are not useful, you should add them for further inspection. Created attachment 79531 [details]
solid-hardware list on laptop
Oh you wanted to see the output? Ok, here is "solid-hardware list" on my laptop.
Alex, does comment #10 provide the requested information? Please set the status. Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. Please try again with the latest version and submit a new bug to frameworks-solid if your issue persists. Thank you! |