<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hi Michel,<br>
<br>
the Probe ID is 25993.<br>
There are so many cheap USB sticks with extremely low write speed,
even USB 3.0 sticks.<br>
What made me think that the sticks speed could cause the tag is,
that my probe had it tagged for a long time, but still the probe
did it's job. It was online, delivering results, etc.<br>
<br>
I have replaced the broken USB stick with a fast one from
Transcend 6 days ago. Since then, the tag did not appear again. I
haven't checked for the blink patterns, sorry. If the Tag will
appear again, i will try a different power supply and cable, as
you suggested.<br>
<br>
BR,<br>
Simon<br>
<br>
<br>
On 11.01.23 12:39, Michel Stam wrote:<br>
</div>
<blockquote type="cite"
cite="mid:A3C811F4-DB10-43A2-BEA3-767F2B31240C@ripe.net">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Hi Simon,
<div><br>
</div>
<div>I would expect a more recent USB stick to complete a write /
read operation more quickly than one of its older counterparts.
Thats not a guarantee, I know. Funny enough, I actually used an
old stick on one of my development V3 the other week and was
surprised how slow the performance was (but the system did still
work).</div>
<div><br>
</div>
<div>When the V3 probes have issues, usually its either:</div>
<div>
<ul class="MailOutline">
<li>Power supply failing</li>
<li>Cabling failing</li>
<li>USB stick corrupt (unlikely after 3 units).</li>
</ul>
</div>
<div><br>
</div>
<div>Working setups sometimes degrade over time. Something I’ve
seen with a USB analyser a good few years back is that some USB
sticks don’t report write errors when the stick dies.</div>
<div><br>
</div>
<div>I will dig a bit where the flash filesystem corrupted tag
comes from and get back to you.</div>
<div><br>
</div>
<div>Can you message me the probe ids that are causing issues?
(Privately if you want to keep it off-list).</div>
<div><br>
</div>
<div>And if you have the possibility, please humour me and try a
completely different power supply and cable. It has resolved
issues for me before. Just to get it out of the way.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Michel</div>
<div>
<div><br>
<blockquote type="cite">
<div>On 9 Jan 2023, at 20:36, <a class="moz-txt-link-abbreviated" href="mailto:ripe.net@toppas.net">ripe.net@toppas.net</a> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div>
<div class="moz-cite-prefix">Hi Michel,<br>
<br>
Thanks for you answer. I'm using an Ikea KOPPLA (<span
class="pip-product-identifier"
data-ga-action="article_number_click"
data-ga-label="details_204.150.27"><span
class="pip-product-identifier__value">204.150.27</span></span>)
which provides 17W. It's powering two v3 probes and
one v4 probe. The other probes work well, so i don't
think that the power supply is causing this.<br>
<br>
What i meant was, that maybe some USB sticks are to
slow and thus not able to perform writing of a big
chunk of data in the expected time, and therefore the
USB flash/filesystem is considered broken? Can you
tell the exact cause for the "Flash drive filesystem
corrupted"-tag is? What triggers this?<br>
<br>
I am aware that USB 3.0 is backwards compatible, but
since USB 3.0 sticks are faster, maybe it makes sense
to stick with them (hehe), to ensure that at least the
full USB 2.0 potential is used.<br>
<br>
BR,<br>
Simon<br>
<br>
<br>
On 09.01.23 12:26, Michel Stam wrote:<br>
</div>
<blockquote type="cite"
cite="mid:0D24D941-93AD-44F0-BEE1-9AD5B80EC00E@ripe.net">
<pre class="moz-quote-pre" wrap="">Hi Simon,
First thing that comes to mind to me, do you maybe have a power problem? If the unit receives just enough power to boot the base TP-Link, but not to power the USB stick this may trigger these problems. Would you be able to boot the unit with a different power supply (try 5W at the least or 10W), to see if this makes a difference?
Speed shouldn’t be much of an issue, USB to my knowledge is backwards compatible.
Cheers,
Michel
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On 31 Dec 2022, at 22:31, <a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:ripe.net@toppas.net" moz-do-not-send="true">ripe.net@toppas.net</a> wrote:
Hello,
i have two v3 probes and i'm experiencing issues: "USB Flash Drive Filesystem Corrupted"
I have tried multiple USB Sticks, including brand new ones and also sticks from "good" brands like Lexar and Sandisk.
The issue is not permanent, the error appears and disappears from time to time:
2022-12-22 @ 12:14:04 UTC Probe auto-tagged Your probe #xxxxx was automatically tagged as "system: Flash drive filesystem corrupted"
2022-12-22 @ 18:14:42 UTC Probe auto-untagged Your probe #xxxxx was automatically untagged as "system: Flash drive filesystem corrupted"
This leads me to the thought, that the flash storage is not the real problem. It's unlikely, since i tried multiple dongles. Could it be possible, that not the flash storage is broken, but the speed of the USB dongles is too low?
All dongles I tried were USB 2.0, not 3.0, since the TP-Link TL-MR3020 is not USB 3.0 capable anyway. But maybe USB 3.0 is a better choice?
What do you think?
BR,
Simon
--
ripe-atlas mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:ripe-atlas@ripe.net" moz-do-not-send="true">ripe-atlas@ripe.net</a>
<a class="moz-txt-link-freetext" href="https://lists.ripe.net/mailman/listinfo/ripe-atlas" moz-do-not-send="true">https://lists.ripe.net/mailman/listinfo/ripe-atlas</a>
</pre>
</blockquote>
</blockquote>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>