From: Alan Stern <stern@rowland.harvard.edu>
To: James Dutton <james.dutton@gmail.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: usb disk drive disconnect making readonly
Date: Thu, 5 May 2022 10:16:58 -0400 [thread overview]
Message-ID: <YnPcWuhpFrqjeIIs@rowland.harvard.edu> (raw)
In-Reply-To: <CAAMvbhGURWPbHUw5gOirJer7-+VwWFL4tTtiSYSJW=3y1G92mw@mail.gmail.com>
On Wed, May 04, 2022 at 09:16:55PM +0100, James Dutton wrote:
> Hi,
>
> Use case:
> Boot from a USB disk and run for a day.
> Sometimes the USB link disconnects and reconnects.
> When it reconnects, Linux cannot use it, and the Linux kernel has set
> the device mount to read only.
> Is there any way to allow a USB disk to disconnect and then reconnect
> it, and Linux carry on using it, and not set it to a read-only mount,
> provided of course, that it knows that the same disk was reconnected
> without being changed.
> For example, I have a usb disk device that goes into power save mode
> if not accessed for more than 15 mins. When I come back to unlock the
> screensaver, it does not wake up the disk, but instead places it in
> read-only mode. This necessitates me to reboot the PC to get it
> working again.
>
> Any ideas?
There is no way to know what is going on unless you provide a lot more
information. The dmesg log showing what happens during one of these
disconnect/reconnect events would be a good start (although it probably
won't be enough).
Alan Stern
next prev parent reply other threads:[~2022-05-05 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 20:16 usb disk drive disconnect making readonly James Dutton
2022-05-05 14:16 ` Alan Stern [this message]
[not found] ` <CAAMvbhHsUL6gQ365wZW4J8RCbnhwEt0RDUc5NA4=RSS2bjnK_A@mail.gmail.com>
2022-05-06 14:35 ` Alan Stern
2022-05-06 20:48 ` James Dutton
2022-05-07 15:39 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YnPcWuhpFrqjeIIs@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=james.dutton@gmail.com \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox