On 2/12/25 17:29, Samuel Sieb wrote:
On 12/1/25 7:31 PM, [email protected] wrote:
I tried a different socket. Same thing.
On another machine (a laptop) I booted 6.12.17-amd64 (from a clonezilla image)
and then did the same
mount/eject dance and got the same errors.
Why are you even ejecting it? Once the umount finishes, you can safely just
unplug it.
May be unnecessary, but is my habit. What is eject for?
It seems that this disk is not accessible after a umount. Maybe specific to
this model (Seagate Expansion SSD)?
Or related to the controller in it?
What do you mean by that? The umount shouldn't cause anything like that, but
you definitely won't be able to access it again after ejecting.
Yes, after umount I can mount again. After eject it cannot be accessed again.
Still, why these errors when ejecting?
--
Eyal at Home ([email protected])
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
