USB Storage Slow?

[DonC52]

I have been wondering why the following occurs on my Windows 10 laptop and the Pi USB. I am using a 128G SanDisk Extreme Plus UHS so I would think it rather fast.

I put in an old "slow" USB stick into my Laptop port and copy a Sentry Mode directory, I get about 20MB/Sec transfer rate.

I put the Pi USB in with power applied from external source and copy the same directory, I get like 1.5MB/s to 2.5MB/s transfer rate.

Looking at top, there is a LOT of wait time going on. Is there anything that can be done to speed things up?

[ZeFrenchBibster]

AND, now I found out how to post code, give it a try peeps:

#!/bin/bash
#
while(true); do
    now=$(date +%Y%m%d-%H:%M:%S)

    echo "-----------------------------------"
    echo ${now}
    # Write 3 (not 4. 5 is right out !) files like our car would do in one go...
    # /r/unexpectedmontypython
    # Then, shalt thou count to three. No more. No less. 
    # Three shalt be the number thou shalt count, and the number of the counting shall be three. 
    # Four shalt thou not count, nor either count thou two, excepting that thou then proceed to three. 
    # Five is right out. 

    mkdir -p ${now}
    time (
        (dd if=/dev/zero of=${now}/front         bs=1m count=35) > /dev/null 2>&1
        (dd if=/dev/zero of=${now}/leftrepeater  bs=1m count=35) > /dev/null 2>&1
        (dd if=/dev/zero of=${now}/rightrepeater bs=1m count=35) > /dev/null 2>&1
        # uncomment for V10 
        # (dd if=/dev/zero of=${now}/rear          bs=1m count=35) > /dev/null 2>&1
    ) &
    sleep 60
done

[itsrainingben]

lol r/unexpectedmontypython indeed!

to clarify, with your test were you running 3 or 4 files simultaneously? because if your pi is slowing down on 3 files, then I think you're right and there's something on the pi-side.

I'm sure my performance will be the same but I'll give this a try later tonight (pacific coast).

On Wed, Oct 2, 2019 at 12:34 PM ZeFrenchBibster notifications@github.com wrote:

AND, now I found out how to post code, give it a try peeps:

!/bin/bash

# while(true); do now=$(date +%Y%m%d-%H:%M:%S)

echo "-----------------------------------"
echo ${now}
# Write 3 (not 4. 5 is right out !) files like our car would do in one go...
# /r/unexpectedmontypython
# Then, shalt thou count to three. No more. No less.
# Three shalt be the number thou shalt count, and the number of the counting shall be three.
# Four shalt thou not count, nor either count thou two, excepting that thou then proceed to three.
# Five is right out.

mkdir -p ${now}
time (
    (dd if=/dev/zero of=${now}/front         bs=1m count=35) > /dev/null 2>&1
    (dd if=/dev/zero of=${now}/leftrepeater  bs=1m count=35) > /dev/null 2>&1
    (dd if=/dev/zero of=${now}/rightrepeater bs=1m count=35) > /dev/null 2>&1
    # uncomment for V10
    # (dd if=/dev/zero of=${now}/rear          bs=1m count=35) > /dev/null 2>&1
) &
sleep 60

done

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/marcone/teslausb/issues/239?email_source=notifications&email_token=AGE3NGRP7P6M2DN7TX7DTBTQMTZTDA5CNFSM4IUEPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAF5EVY#issuecomment-537645655, or mute the thread https://github.com/notifications/unsubscribe-auth/AGE3NGTQJEKJTOZJNUQOZH3QMTZTDANCNFSM4IUEPZCA .

[ZeFrenchBibster]

LoadAverage started at 0.34. After one go: 2.34 (took 40.69 seconds) after the second: no response, the third one went off before!!! ---> 1m11 for #2, LA is > 5 !!!

3rd: LA is already >7.6
--> 1m37 !!!

Ok fellows, we're sure it's the pi...

[ZeFrenchBibster]

just to make sure, my g_mass_storage settings:

pi@teslausb-Model3:~ $ cat /etc/modprobe.d/g_mass_storage.conf
options g_mass_storage file=/backingfiles/music_disk.bin,/backingfiles/cam_disk.bin removable=1,1 ro=0,0 stall=0 iSerialNumber=123456 nofua=1,1
pi@teslausb-Model3:~ $

cheers, Paul

[vita10gy]

I think people have confirmed the pi4 works ok, so I guess we have to figure out if

a) it's something the older version on the pi0w is doing (we're still on strech, right? and the pi4 needs buster?)

b) it's something the teslausb stuff is doing (or can do something about, even if it's not "doing" anything wrong, maybe we can all disable the right thing and viola)

c) the "problem" exists on both hardwares/versions, but just like we potentially used to be able to power through with 3 videos, despite the issue with a pi0, the pi4 just has enough horsepower to keep the bottoming out high enough for 4 vids.

Is there any integrity checking, virus scanning, etc that can be overwhelmed when files get added to a raspian instance? I'd rather have the occasional corrupt video that didn't transfer to the card perfectly than no videos of anything.

[KeithHHill]

Just to throw in my two cents. I drove around with V10 for about 5 days before updating the teslausb and had zero issues. Immediately after updating teslausb I started getting this issue every 10 min of driving or so.

The 4 videos were recording just fine on the old version so I don't think it has to do with that change. My guess is there is some background process that runs that is chewing resources intermittently.

[gacevedo]

This is just a guess, but... reviewing the PRs merged in the last few days/week, I noticed the addition of the dwc2 driver, with the module being enabled during boot: https://github.com/marcone/teslausb/pull/275/files#diff-f2f1deecc95955c40f89dd131c363444. What is the impact of this change? Any chance it could affect USB performance?

Edit: it was merged only 5 days ago, so maybe not related or a cause of the issue.

[marcone]

I needed to make a few changes to that script before it worked for me:

• replace ":" with "-" in date string, because ":" is not a valid character in FAT
• replace "1m" with "1M" in the "dd" command, because "1m" is not a valid size specifier

#!/bin/bash
#
while(true); do
    now=$(date +%Y%m%d-%H-%M-%S)

    echo "-----------------------------------"
    echo ${now}
    # Write 3 (not 4. 5 is right out !) files like our car would do in one go...
    # /r/unexpectedmontypython
    # Then, shalt thou count to three. No more. No less. 
    # Three shalt be the number thou shalt count, and the number of the counting shall be three. 
    # Four shalt thou not count, nor either count thou two, excepting that thou then proceed to three. 
    # Five is right out. 

    mkdir -p ${now}
    time (
        (dd if=/dev/zero of=${now}/front         bs=1M count=35) > /dev/null 2>&1
        (dd if=/dev/zero of=${now}/leftrepeater  bs=1M count=35) > /dev/null 2>&1
        (dd if=/dev/zero of=${now}/rightrepeater bs=1M count=35) > /dev/null 2>&1
        # uncomment for V10 
        # (dd if=/dev/zero of=${now}/rear          bs=1M count=35) > /dev/null 2>&1
    ) &
    sleep 60
done

Each iteration takes a fairly consistent 5 seconds for me with a Sandisk Extreme 128GB in a Pi0 connected to a Chromebook running linux.

[marcone]

Adding "conv=fdatasync" ensures that the file is actually fully written to disk before "dd" finishes, and increases the time to 11 seconds for 3 files, and 15 seconds for 4 files.

[gacevedo]

@marcone @ZeFrenchBibster do I run that script on my laptop? If so, I assume I need to adjust /dev/zero to the actual Pi CAM device? This is running on a MacBook Pro, using a Pi0w, with a "SanDisk Extreme 32GB microSDHC UHS-3 Card - SDSQXAF-032G-GN6MA".

-----------------------------------
20191002-18-09-19

real    0m0.019s
user    0m0.005s
sys 0m0.010s
-----------------------------------
20191002-18-10-19

real    0m0.016s
user    0m0.005s
sys 0m0.009s
-----------------------------------
20191002-18-11-19

real    0m0.017s
user    0m0.005s
sys 0m0.010s
-----------------------------------
20191002-18-12-19

real    0m0.015s
user    0m0.005s
sys 0m0.008s
-----------------------------------
20191002-18-13-20

real    0m0.016s
user    0m0.005s
sys 0m0.008s
-----------------------------------
20191002-18-14-20

real    0m0.016s
user    0m0.005s
sys 0m0.009s
-----------------------------------
20191002-18-15-20

real    0m0.016s
user    0m0.005s
sys 0m0.009s
-----------------------------------
20191002-18-16-20

real    0m0.016s
user    0m0.005s
sys 0m0.009s
-----------------------------------

[marcone]

Run it on the laptop, in the mounted CAM drive. You don't need to adjust the script.

[itsrainingben]

Just getting to this - why am I only writing out ‘rear’ files?

Script looks good to me, I copy/pasta’d @marcone ’s adjustments, unpounded for V10 and made executable.

On Oct 2, 2019, at 6:45 PM, marcone notifications@github.com wrote:

Run it on the laptop, in the mounted CAM drive. You don't need to adjust the script.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/marcone/teslausb/issues/239?email_source=notifications&email_token=AGE3NGUMJYNV2762CQ4BWHLQMVFC7A5CNFSM4IUEPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAGW34A#issuecomment-537751024, or mute the thread https://github.com/notifications/unsubscribe-auth/AGE3NGUQONJOAJ4SIZ3OY3TQMVFC7ANCNFSM4IUEPZCA.

[gacevedo]

Okay. I'm getting 16 seconds, including the rear file. Is that good or bad? What is Tesla's expectation?

Edit: Looks like the error says "Use a drive that can write at 4 MB/s or higher".

[marcone]

That's 8.75 MB/sec, which is more than enough in theory. We don't know how the car actually measures or decides that the drive is too slow though.

[DineshCyanam]

There are others who are not using TeslaUSB but seeing the same USB drive speed errors on V10. https://www.reddit.com/r/teslamotors/comments/dck7jw/dashcam_error_following_update_to_20193211_model_3/

[ZeFrenchBibster]

@itsrainingben for v10, you should indeed un-comment the indicated line, but keep the other ones above! --> Remove the comment saying to uncomment as well!

I've incorporated the modifications that were suggested by @marcone by a quick hack.

#!/bin/bash
#
# Go to your mounted CAM drive, and run this script for a while
# Control-c to stop it :-)

uname -a | grep Darwin 2>&1 >/dev/null # MacOS or something else?
if [ -z $? ]; then
    # Linux etc.
    M='M'
    opt='conv=fdatasync'
else
    # MacOS
    M='m'
fi
while(true); do
    now=$(date +%Y%m%d-%H%M%S)

    echo "-----------------------------------"
    echo ${now}
    # Write 4 files like our car would do in one go...

    mkdir -p ${now}
    time (
        (dd if=/dev/zero of=${now}/front         bs=1${M} count=35 ${opt}) > /dev/null 2>&1
        (dd if=/dev/zero of=${now}/leftrepeater  bs=1${M} count=35 ${opt}) > /dev/null 2>&1
        (dd if=/dev/zero of=${now}/rightrepeater bs=1${M} count=35 ${opt}) > /dev/null 2>&1
        (dd if=/dev/zero of=${now}/rear          bs=1${M} count=35 ${opt}) > /dev/null 2>&1
    ) &
    sleep 60
done

[ZeFrenchBibster]

Hi, is there a spot in the filesystem somewhere that's RW and has several KB of space? I'd like to check & write to a log file, the LoadAvg of the pi every minute for exemple, via crontab, like this:

date +%Y%m%d-%H%M%S" - $(cat /proc/loadavg)" >>/wherever/loadavg.log

Paul

[itsrainingben]

@zefrenchbibster - yeah of course, did that and for some reason it was only writing one file.

¯_(ツ)_/¯

On Oct 2, 2019, at 11:11 PM, ZeFrenchBibster notifications@github.com wrote:

 @itsrainingben for v10, you should indeed un-comment the indicated line, but keep the other ones above! --> Remove the comment saying to uncomment as well!

I've incorporated the modifications that were suggested by @marcone by a quick hack.

!/bin/bash

#

Go to your mounted CAM drive, and run this script for a while

Control-c to stop it :-)

uname -a | grep Darwin 2>&1 >/dev/null # MacOS or something else? if [ -z $? ]; then

Linux etc.

M='M'
opt='conv=fdatasync'

else

MacOS

M='m'

fi while(true); do now=$(date +%Y%m%d-%H%M%S)

echo "-----------------------------------"
echo ${now}
# Write 4 files like our car would do in one go...

mkdir -p ${now}
time (
    (dd if=/dev/zero of=${now}/front         bs=1${M} count=35 ${opt}) > /dev/null 2>&1
    (dd if=/dev/zero of=${now}/leftrepeater  bs=1${M} count=35 ${opt}) > /dev/null 2>&1
    (dd if=/dev/zero of=${now}/rightrepeater bs=1${M} count=35 ${opt}) > /dev/null 2>&1
    (dd if=/dev/zero of=${now}/rear          bs=1${M} count=35 ${opt}) > /dev/null 2>&1
) &
sleep 60

done — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[vita10gy]

@ZeFrenchBibster You managed to make the pi spin out with your script. Did you happen to check top to see if any unexpected process(es) were out of control once it starts choking?

[ZeFrenchBibster]

file-storage was on top, did not have a closer look on waits however...

On 3 Oct 2019, at 17:57, vita10gy <notifications@github.com mailto:notifications@github.com> wrote:

@ZeFrenchBibster https://github.com/ZeFrenchBibster You managed to make the pi spin out with your script. Did you happen to check top to see if any unexpected process(es) were out of control once it starts choking?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/marcone/teslausb/issues/239?email_source=notifications&email_token=ANJICITEZRUE7LHOUJ4FQG3QMYI57A5CNFSM4IUEPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAIVVAA#issuecomment-538008192, or mute the thread https://github.com/notifications/unsubscribe-auth/ANJICIQKQITBSY3PK735CKLQMYI57ANCNFSM4IUEPZCA.

[dadealus]

So are we thinking the Pi0 isnt strong enough?

[itsrainingben]

Seems to be definitely on the Pi0 side of things but unsure if it's a software or hardware limitation.

Waiting for someone with a bigger brain than I to take a look at it and chime in.

On Thu, Oct 3, 2019 at 11:04 AM dadealus notifications@github.com wrote:

So are we thinking the Pi0 isnt strong enough?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/marcone/teslausb/issues/239?email_source=notifications&email_token=AGE3NGXB7ZXWWS3IO6MFXBDQMYXZDA5CNFSM4IUEPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAJCBDA#issuecomment-538058892, or mute the thread https://github.com/notifications/unsubscribe-auth/AGE3NGQFEFW3MTW5JJ7UNVDQMYXZDANCNFSM4IUEPZCA .

[vita10gy]

The zero worked fine before, and it works fine now for like 10 minutes. Hopefully it's just something that needs to be hunted down in the software that needs to be enabled or disabled. I too have no idea what it could be though.

If NOTHING else I wonder if we could detect when the write speed drops or the car disconnects and reboot. Less than ideal, because the drive "goes missing" after every camera dump and might miss something in the interim, but better to miss the occasional minute than have it shit the bed and not save anything for 5 hours.

(Or would the Tesla interpret this as someone stealing the drive and set off the alarm? Wouldn't that be something.)

[marcone]

Could also be limited to certain specific Pi's, cars, cards, cables, etcetera. I have never had this problem with either v9 or v10, even during all-day drives, and have been using the same Pi, 128GB Sandisk Extreme and cable for months.

[prathiraj]

Just curious, all who have this problem, what is the camsize set to in conf? I don't have this problem and I have camsize set to 100%

[dadealus]

My camsize is set to 100%. running Pi0 with 128gb Samsung Pro Endurance in 2019 Model X (Raven) and 2019 M3 SR+ both having same issue both have AP3 hardware.

[itsrainingben]

Mine was set to 50/50 Music and Cam partitions. 256GB SanDisk Ultra.

On Thu, Oct 3, 2019 at 12:03 PM dadealus notifications@github.com wrote:

My camsize is set to 100%. running Pi0 with 128gb Samsung Pro Endurance in 2019 Model X (Raven) and M3 SR+ both having same issue both have AP3 hardware.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/marcone/teslausb/issues/239?email_source=notifications&email_token=AGE3NGXK2ES7OHI4A3QYKLTQMY6XZA5CNFSM4IUEPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAJHRVQ#issuecomment-538081494, or mute the thread https://github.com/notifications/unsubscribe-auth/AGE3NGSQRQYM2U7V2PJJIHTQMY6XZANCNFSM4IUEPZCA .

[vita10gy]

I don't remember how to look at the ratio, but I definitely have some music on it. I have this card. https://www.amazon.com/gp/product/B06XX29S9Q/ref=ppx_yo_dt_b_asin_title_o08_s00?ie=UTF8&psc=1

Edit: I just ordered a new cable. I wanted to anyway because despite having 29834 micro usb cables from back in the day, the only one I could find that did data was way too long to keep stuffed in the center console. I should know tomorrow if a different cable helps anything.

[dogsbody]

Wow, nothing new to add other than +1 and here to help with testing if you need any. UK (right hand drive) Model 3 - built in August 2019 Pi Zero W with a Samsung 64 GB PRO Endurance Issue was happening with v9 (20190615 release) and v10 (buster-20190922 release)

[gacevedo]

What is the recommended cable? I got the one listed on here: https://github.com/marcone/teslausb#hardware (the USB A/Micro B from Adafruit)

[wwwb0n3zcom]

On Discord tonight some where mentioning to change the following setting: https://github.com/marcone/teslausb/blob/main-dev/setup/pi/create-backingfiles.sh#L83 Change to this with 4096 or possibly higher 16384 mkfs.vfat /dev/loop0 -F 32 -S 4096 -c -n "$label"

I haven't tried it yet as I just upgraded to this which so far I haven't received the error (limited testing tonight): SanDisk 256GB High Endurance MicroSD

[dadealus]

Is anyone having this issue on the Pi4?

[itsrainingben]

Sounds like only a handful have tested on the Pi4 and have reported back positively. I just got my first Pi4 last night, hoping to have time this weekend to set it up.

Additionally @marcone/teslausb teslausb@noreply.github.com I imaged a new card with your June https://github.com/marcone/teslausb/releases/tag/v1.3 release and rolled with it this morning into work. While not a long commute, half hour, I had no reported issue with read/write. This was a spare 64GB SanDisk Ultra (same make as the 256GB card) allocating 95% of available space to CAM.

What does this indicate? I have no clue, likely not much of anything. The only differences between this card and my problematic one are -

1) Updated problematic card with your wiki instructions immediately prior to behavior 2) Problematic card has equal (split 50/50) partitions for Music / Cam storage. I recall you indicating somewhere it's best to leave some space available on the card but can't track down that comment currently. This card was 95% CAM, no Music. 3) Problematic card is 256GB, this is 64GB. I sincerely doubt that to be a factor but including it for posterity.

I'm going to blow away the 256GB and rerun the June release with 49/49% split and see if there's any difference in behavior. I'll report back once I do.

Curious what you think of the above Discord comment making the block size 4096.

On Fri, Oct 4, 2019 at 8:08 AM dadealus notifications@github.com wrote:

Is anyone having this issue on the Pi4?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/marcone/teslausb/issues/239?email_source=notifications&email_token=AGE3NGX6TMZSWBE3XOQBAF3QM5L5FA5CNFSM4IUEPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAL6OCY#issuecomment-538437387, or mute the thread https://github.com/notifications/unsubscribe-auth/AGE3NGUXVTZMJ3SMXYR54FLQM5L5FANCNFSM4IUEPZCA .

[miles267]

Sorry if it's already been covered, but how are RP4's being powered? I have one that's unopened, but can't imagine it can be powered off the same power/data USB cable we're using for RP0.

[vita10gy]

The new cable did not help. (It's the right angled cousin of the suggested one. Same look/brand.)

Nice to not have that older 5 foot cord jammed in there though, so worth the chance.

Saved fine for a while, but eventually the car decided it was too slow.

[th3fallen]

This has only started happening to me after updating for the v10 changes no idea what's going on :(

[itsrainingben]

Anyone else that's having the same trouble - can you try re-imaging your rPi0 with @marcone/teslausb teslausb@noreply.github.com 's June release and see if the same problem persists? Looking for more data points.

On Fri, Oct 4, 2019 at 11:17 AM Clark Tomlinson notifications@github.com wrote:

This has only started happening to me after updating for the v10 changes no idea what's going on :(

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/marcone/teslausb/issues/239?email_source=notifications&email_token=AGE3NGSEZIVBHBOG63TMMLLQM6CBXA5CNFSM4IUEPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAMPOVA#issuecomment-538507092, or mute the thread https://github.com/notifications/unsubscribe-auth/AGE3NGRPN2EXPG6YOTJJVXLQM6CBXANCNFSM4IUEPZCA .

[vita10gy]

@th3fallen It was either always happening, it just didn't matter with 3 videos, or something important changed. Either way it's a bummer. It's funny, my car didn't even ship with the feature, but I feel like I may as well park it in the middle of a tire fire in downtown Crimeville without it on. We took my wife's car the other day mainly because I knew sentry mode was on the fritz.

@itsrainingben Does one have to literally reimage to that to be running it? I did the update process the other day. (Though now that I think about it I didn't even get the Pi until august, so presumably I was already running the june release.)

[itsrainingben]

I did a full reimage with the June release and in a very limited capacity I can say it’s again.

On Oct 4, 2019, at 11:47 AM, vita10gy notifications@github.com wrote:

 @th3fallen It was either always happening, it just didn't matter with 3 videos, or something important changed. Either way it's a bummer. It's funny, my car didn't even ship with the feature, but I feel like I may as well park it in the middle of a tire fire in downtown Crimeville without it on. We took my wife's car the other day mainly because I knew sentry mode was on the fritz.

@itsrainingben Does one have to literally reimage to that to be running it? I did the update process the other day. (Though now that I think about it I didn't even get the Pi until august, so presumably I was already running the june release.)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[pman07]

I did a full reimage with the June release and in a very limited capacity I can say it’s again. … On Oct 4, 2019, at 11:47 AM, vita10gy @.***> wrote:  @th3fallen It was either always happening, it just didn't matter with 3 videos, or something important changed. Either way it's a bummer. It's funny, my car didn't even ship with the feature, but I feel like I may as well park it in the middle of a tire fire in downtown Crimeville without it on. We took my wife's car the other day mainly because I knew sentry mode was on the fritz. @itsrainingben Does one have to literally reimage to that to be running it? I did the update process the other day. (Though now that I think about it I didn't even get the Pi until august, so presumably I was already running the june release.) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

I reimaged with the June release last night and no issues over an hour of driving so far.

Edit: Full Background. I was originally using the May Image with no issues, upgrade to V10 started seeing USB too slow error. Tried upgrading to latest release without reimaging, same issue. Last night did a reimaged clean install and so far it's working.

[elight]

I was using the June image and suffered this problem.

On Fri, Oct 4, 2019 at 2:43 PM Ben Tucker notifications@github.com wrote:

Anyone else that's having the same trouble - can you try re-imaging your rPi0 with @marcone/teslausb teslausb@noreply.github.com 's June release and see if the same problem persists? Looking for more data points.

On Fri, Oct 4, 2019 at 11:17 AM Clark Tomlinson notifications@github.com wrote:

This has only started happening to me after updating for the v10 changes no idea what's going on :(

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/marcone/teslausb/issues/239?email_source=notifications&email_token=AGE3NGSEZIVBHBOG63TMMLLQM6CBXA5CNFSM4IUEPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAMPOVA#issuecomment-538507092 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AGE3NGRPN2EXPG6YOTJJVXLQM6CBXANCNFSM4IUEPZCA

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/marcone/teslausb/issues/239?email_source=notifications&email_token=AAACPAAU2TKAOJ7YTR4NBU3QM6FFNA5CNFSM4IUEPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAMRWQA#issuecomment-538516288, or mute the thread https://github.com/notifications/unsubscribe-auth/AAACPAAGDYZNW4MISESME3TQM6FFNANCNFSM4IUEPZCA .

-- Poor typing attributable to use of iPhone keyboard.

[curiousgrge]

Reimaged last night using latest buster beta release 20190922 after having USB drive write speed too slow. On latest 2019.32.11.1 firmware applied two nights ago. Applied updating instructions and ran teslausb-setup again.

Applied nofua=1,1 this time and didn't notice a change since the last time I copied my music files over. Took about 32 minutes compared to what I reported the last time which was about 30 minutes. I have since added another couple hundred files and I think mostly this time it was MP3 rather than FLAC so files are much smaller. So I think modifying the Windows disk device driver makes a bigger impact than nofua=1,1 with it still hoving around 15-20MB/sec during the copy process.

Didn't have a problem this morning with the error message but the day isn't done yet.

[itsrainingben]

@Evan Light - to give you context I was using the June release as well, updated with the internal updater, then had problems. I dont know if it was due to the updater or the V10 release but I can report that after re-imaging with that same release and not running the internal updater I haven't yet had any issues today.

On Fri, Oct 4, 2019 at 12:12 PM Evan Light notifications@github.com wrote:

I was using the June image and suffered this problem.

On Fri, Oct 4, 2019 at 2:43 PM Ben Tucker notifications@github.com wrote:

Anyone else that's having the same trouble - can you try re-imaging your rPi0 with @marcone/teslausb teslausb@noreply.github.com 's June release and see if the same problem persists? Looking for more data points.

On Fri, Oct 4, 2019 at 11:17 AM Clark Tomlinson < notifications@github.com> wrote:

This has only started happening to me after updating for the v10 changes no idea what's going on :(

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <

https://github.com/marcone/teslausb/issues/239?email_source=notifications&email_token=AGE3NGSEZIVBHBOG63TMMLLQM6CBXA5CNFSM4IUEPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAMPOVA#issuecomment-538507092

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AGE3NGRPN2EXPG6YOTJJVXLQM6CBXANCNFSM4IUEPZCA

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/marcone/teslausb/issues/239?email_source=notifications&email_token=AAACPAAU2TKAOJ7YTR4NBU3QM6FFNA5CNFSM4IUEPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAMRWQA#issuecomment-538516288 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AAACPAAGDYZNW4MISESME3TQM6FFNANCNFSM4IUEPZCA

.

-- Poor typing attributable to use of iPhone keyboard.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/marcone/teslausb/issues/239?email_source=notifications&email_token=AGE3NGRUW3ZDF3QZZVJHOUTQM6ISPA5CNFSM4IUEPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAMUBVQ#issuecomment-538525910, or mute the thread https://github.com/notifications/unsubscribe-auth/AGE3NGW6T4UWHIP5YG6AHALQM6ISPANCNFSM4IUEPZCA .

[natrlhy]

I got a faster 128GB card on Monday and no issues until today. I did do an internal update after redoing it on Monday

[miles267]

Reimaged last night using latest buster beta release 20190922 after having USB drive write speed too slow. On latest 2019.32.11.1 firmware applied two nights ago. Applied updating instructions and ran teslausb-setup again.

Applied nofua=1,1 this time and didn't notice a change since the last time I copied my music files over. Took about 32 minutes compared to what I reported the last time which was about 30 minutes. I have since added another couple hundred files and I think mostly this time it was MP3 rather than FLAC so files are much smaller. So I think modifying the Windows disk device driver makes a bigger impact than nofua=1,1 with it still hoving around 15-20MB/sec during the copy process.

Didn't have a problem this morning with the error message but the day isn't done yet.

@curiousgrge Is this still working for you? And how do you add this nofua=1,1 setting to an existing setup?

[itsrainingben]

Reporting back - there were two sentry events that were not recorded due to poor r/w. I'll do some testing tomorrow but at this point I'm leaning more towards a bandwidth issue due to the additional camera on the rPi0.

@marcone/teslausb teslausb@noreply.github.com would be insightful if you could chime in about the block size and other mentions in this chain. Apologies if you've made mention already elsewhere, just trying to take part and socialize your good work in the forum I am a part of.

Also, happy Friday y'all!

On Fri, Oct 4, 2019 at 5:50 PM miles267 notifications@github.com wrote:

Reimaged last night using latest buster beta release 20190922 after having USB drive write speed too slow. On latest 2019.32.11.1 firmware applied two nights ago. Applied updating instructions and ran teslausb-setup again.

Applied nofua=1,1 this time and didn't notice a change since the last time I copied my music files over. Took about 32 minutes compared to what I reported the last time which was about 30 minutes. I have since added another couple hundred files and I think mostly this time it was MP3 rather than FLAC so files are much smaller. So I think modifying the Windows disk device driver makes a bigger impact than nofua=1,1 with it still hoving around 15-20MB/sec during the copy process.

Didn't have a problem this morning with the error message but the day isn't done yet.

Is this still working for you? And how do you add this nofua=1,1 setting to an existing setup?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/marcone/teslausb/issues/239?email_source=notifications&email_token=AGE3NGTIGTLVCNUL46ODVMDQM7QFBA5CNFSM4IUEPZCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEANGPIA#issuecomment-538601376, or mute the thread https://github.com/notifications/unsubscribe-auth/AGE3NGQGF6L2HYONYNSK76LQM7QFBANCNFSM4IUEPZCA .

[wwwb0n3zcom]

If someone could explain (to some less knowledgeable in Linux) how properly test transfer speed. I can run some tests on my this weekend with either/both of the following: nofua=1,1 mkfs.vfat /dev/loop0 -F 32 -S 4096 -c -n "$label" or increasing the block size.

[retinoic]

buster release + updates + nofua=1,1 did not fix write speed error for me.

[miles267]

Me either @torange. After that test I stopped trying for now.

[ice2032]

Anyone running this on a Pi 4 able to confirm it’s still working with no issues?

Seems like Pi 0 is no longer an option.