| Summary: | HDDs conected to plug-in SATA card classified by Dolphin as Removable Devices rather than Devices | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-solid | Reporter: | Scott <shagooserver> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kdelibs-bugs, lukas, meven29, nate, stefan.bruens |
| Priority: | NOR | ||
| Version: | 5.110.0 | ||
| Target Milestone: | --- | ||
| Platform: | RedHat Enterprise Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
udiskctl-dump.txt
copy of user-places.xbel solid-hardware5 sdj1 sdi1 user-places.ebel after edit & reboot copy of /etc/udev/rules.d/70-snap.snapd.rules udevadm info --export-db udevadm info --export-db |
||
|
Description
Scott
2023-11-14 04:49:25 UTC
Please share the file obtained udiskctl-dump.txt with `udisksctl dump > udiskctl-dump.txt`. AND `solid-hardware list` result, it might be `solid-hardware5 list` on your system, with the output of `solid-hardware5 details <UDI>` where UDI is one of the disks connected using through SATA expansion card. Created attachment 163169 [details]
udiskctl-dump.txt
Attached is the dump requested.
Following is, solid-hardware5 details sdm
scott@scottlounge:~$ solid-hardware5 details sdm
udi = 'sdm'
parent = '' (string)
vendor = '' (string)
product = '' (string)
description = '' (string)
icon = '' (string)
(In reply to Scott from comment #2) > Created attachment 163169 [details] > udiskctl-dump.txt > > Attached is the dump requested. > Following is, solid-hardware5 details sdm > > scott@scottlounge:~$ solid-hardware5 details sdm > udi = 'sdm' > parent = '' (string) > vendor = '' (string) > product = '' (string) > description = '' (string) > icon = '' (string) An UDI for a drive would look like "/org/freedesktop/UDisks2/drives/ST32000542AS_6XW1QK6W", this does not correspond to a drive. For instance: ``` solid-hardware5 details /org/freedesktop/UDisks2/drives/ST32000542AS_6XW1QK6W udi = '/org/freedesktop/UDisks2/drives/ST32000542AS_6XW1QK6W' parent = '/org/freedesktop/UDisks2' (string) vendor = '' (string) product = 'ST32000542AS' (string) description = 'Disque dur interne 1,8 Tio (sda1)' (string) icon = 'drive-harddisk' (string) Block.major = 8 (0x8) (int) Block.minor = 1 (0x1) (int) Block.device = '/dev/sda1' (string) StorageDrive.bus = 'Sata' (0x4) (enum) StorageDrive.driveType = 'HardDisk' (0x0) (enum) StorageDrive.removable = false (bool) StorageDrive.hotpluggable = false (bool) StorageDrive.inUse = false (bool) StorageDrive.size = 2000398934016 (0x1d1c1116000) (qulonglong) ``` Hopefully this what you after: scott@scottlounge:~$ solid-hardware5 details '/org/freedesktop/UDisks2/drives/TOSHIBA_MG07ACA12TE_71T0A1E2F95G' udi = '/org/freedesktop/UDisks2/drives/TOSHIBA_MG07ACA12TE_71T0A1E2F95G' parent = '/org/freedesktop/UDisks2' (string) vendor = '' (string) product = 'TOSHIBA MG07ACA12TE' (string) description = 'TOSHIBA MG07ACA12TE' (string) icon = 'drive-removable-media' (string) Block.major = 8 (0x8) (int) Block.minor = 145 (0x91) (int) Block.device = '/dev/sdj1' (string) StorageDrive.bus = 'Sata' (0x4) (enum) StorageDrive.driveType = 'HardDisk' (0x0) (enum) StorageDrive.removable = true (bool) StorageDrive.hotpluggable = false (bool) StorageDrive.inUse = true (bool) StorageDrive.size = 12000138625024 (0xaea00000000) (qulonglong) It should work, I don't understand why. Could send the content of your file `~/.local/share/user-places.xbel` ? Created attachment 163457 [details]
copy of user-places.xbel
Requested file attached.
I have yet another question. Since I don't have a similar setup I need all of information from you, thanks again for following through I couldn't fix this without your input. Could you send me the return of of both: solid-hardware5 details /org/freedesktop/UDisks2/block_devices/sdj1 solid-hardware5 details /org/freedesktop/UDisks2/block_devices/sdi1 Created attachment 163595 [details]
solid-hardware5 sdj1 sdi1
Mevan, you have it arse about, it's me that owes you thanks. You have the knowledge to fix this problem which I alerted you to so therefore any information you need from me is a duty on me to provide it to you. Please feel free to ask away for anything you need and thank you for your time.
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/1495 (In reply to Bug Janitor Service from comment #9) > A possibly relevant merge request was started @ > https://invent.kde.org/frameworks/kio/-/merge_requests/1495 The MR should fix the issue. I may be able to backport it. To confirm this will work, I can offer you a workaround that if it works confirms my patch will fix the issue: Could you try edit any entry in the place panel (for instance renaming Entertainment to Entertainmen). You can rename it back afterwards. And then post here the `~/.local/share/user-places.xbel` file again, (it should have been updated). It should then contain many more <uuid></uuid> entries, if so the workaround worked and my patch will fix it the issue. Now the ordering should be consistent in next reboot. My patch will make this workaround unnecessary. Created attachment 163622 [details]
user-places.ebel after edit & reboot
It appears the opposite of what you expected occurred, the new xbel file is 10 lines shorter but does reflect the edited change. There is no change in the contents of Devices in Dolphin after reboot.
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/solid/-/merge_requests/148 The "removable" classification is done by the kernel (based on flags set by the hardware), and forwarded via udisks2 to solid. http://storaged.org/doc/udisks2-api/latest/gdbus-org.freedesktop.UDisks2.Drive.html#gdbus-property-org-freedesktop-UDisks2-Drive.Removable > Note that this is only a guess. But as this is a somewhat common problem, it is possible to override it, and already for 12 years now: https://bugs.freedesktop.org/show_bug.cgi?id=22879#c9 Please try adding a file "/etc/udev/rules.d/70-fixup-removable.conf" with the following contents (without the "---"): --- # PCI SATA misclassified all drives as removable (probably eSATA), mark as internal SUBSYSTEMS=="pci", ENV{PCI_SLOT_NAME}=="0000:03:00.1", ENV{UDISKS_SYSTEM_INTERNAL}="1" # Probably better, use vendor/product ID of SATA expansion card: # SUBSYSTEMS=="pci", ATTR{vendor}=="0x0123", ATTR{device}=="0xabcd", ENV{UDISKS_SYSTEM_INTERNAL}="1" --- Afterwards, reload the udev configuration: $> sudo udevadm control --reload In case this does not work, please provide the output of: $> udevadm info --export-db Created attachment 163647 [details]
copy of /etc/udev/rules.d/70-snap.snapd.rules
Here is the edited file, I have added the lines at line 1137.
Created attachment 163648 [details]
udevadm info --export-db
As there was no change to the Dolphin list, the file requested.
(In reply to Scott from comment #14) > Created attachment 163647 [details] > copy of /etc/udev/rules.d/70-snap.snapd.rules > > Here is the edited file, I have added the lines at line 1137. Thats the reason I asked you to create a *new* file, with just the given contents. 1. The added lines will never be executed when added at the position you have used 2. The changes will be removed: "# This file is automatically generated. ... # do not edit this file, it will be overwritten on update" Please try adding a file "/etc/udev/rules.d/70-fixup-removable.conf" I correctly followed your instructions this time with the same result. (In reply to Scott from comment #18) > I correctly followed your instructions this time with the same result. Have you reload'ed the udev configuration? Is the UDISK_SYSTEM_INTERNAL env variable set in the udevadm output? If you mean: 1/ did I run, sudo udevadm control --reload, yes 2/ Is the UDISK_SYSTEM_INTERNAL env variable set in the udevadm output?, I have no idea, how to tell? The udevadm info --export-db should have an "E: UDISKS_SYSTEM_INTERNAL=1" in each block for the controller and attached disks. If unsure, append the output here again. Created attachment 163696 [details]
udevadm info --export-db
I see only 1 line that you mentioned. I am travelling until 12/12/23.
Currently, only the host adapter self matches.
Can you try the following two variants (remove the # comment character from one line at a time):
---
# SUBSYSTEMS=="pci", SUBSYSTEM=="block", ATTRS{vendor}=="0x1022", ATTRS{device}=="0x43c8", ENV{UDISKS_SYSTEM_INTERNAL}="1"
# SUBSYSTEM=="block", ENV{ID_PATH}=="pci-0000:03:00.1*", ENV{UDISKS_SYSTEM_INTERNAL}="1"
---
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! (In reply to Stefan Brüns from comment #23) > Currently, only the host adapter self matches. > Can you try the following two variants (remove the # comment character from > one line at a time): > > --- > # SUBSYSTEMS=="pci", SUBSYSTEM=="block", ATTRS{vendor}=="0x1022", > ATTRS{device}=="0x43c8", ENV{UDISKS_SYSTEM_INTERNAL}="1" > # SUBSYSTEM=="block", ENV{ID_PATH}=="pci-0000:03:00.1*", > ENV{UDISKS_SYSTEM_INTERNAL}="1" > --- From which file? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |