Increase timeout?

[probonopd]

Looks like my ebook reader needs more time:

2022-04-07 07:13:09 /dev/da0: attach
2022-04-07 07:13:10 /dev/da0: wait for device retry 1/3
2022-04-07 07:13:11 /dev/da0: wait for device retry 2/3
2022-04-07 07:13:11 /dev/da0: not a block device

Technically the ebook reader is an Android device which simulates a mass storage device, using Linux File-CD Gadget. So it probably just takes much longer than automount thinks.

When I mount it manually it works fine. I think we'd just need to increase the timeout?

[vermaden]

Set RETRY_DELAY=5 (or more) in your /usr/local/etc/automount.conf config.

[probonopd]

Sure enough, works. Being a bit a "it just works" aficionado, would you consider making this the default?

[vermaden]

That is the first device I know to have this problem.

Fine the lowest working value of RETRY_DELAY and let me know please.

[probonopd]

Well, I only can tell for my device a value of 2 is the lowest that works for me, but there are other models, too, including older/slower ones. Would it make sense to e.g., double the delay for each retry?

dmesg shows:

da0: <Linux File-CD Gadget 0000> Removable Direct Access SCSI-2 device
da0: 40.000MB/s transfers
da0: Attempt to query device size failed: NOT READY, Medium not present
da0: quirks=0x2<NO_6_BYTE>

[vermaden]

Thanks. I will also increase the RETRY_COUNT value a little.

[vermaden]

Will be at that in next release:

: ${RETRY_COUNT='5'}                    # retry count
: ${RETRY_DELAY='2'}                    # retry delay time

[probonopd]

Thanks @vermaden

[vermaden]

Updated.

• https://twitter.com/vermaden/status/1694440196236849227
• https://bsd.network/@vermaden/110940718791974585
• https://mastodon.bsd.cafe/@vermaden/110940719515574245

Thanks.