-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USB drive not always mounted by the car #11
Comments
Created the issue to track this problem. Discussion can happen here. I'm testing on a USA Model 3 currently on software version |
For those who are interested in assisting, fundamentally this should be simple outside of the drive creation. Unmount drivessudo umount /mnt Mount locally the loopback devicesudo /sbin/losetup -o 1048576 /dev/loop0 /home/pi/teslacam/images/cam0 Mount to Teslasudo /sbin/modprobe g_mass_storage file=/home/pi/teslacam/images/cam1 removable=1 ro=0 stall=0 iSerialNumber=123456 The above assumes you've followed my rough guide in the readme.md file. The above works if you dd a working USB drive. |
So far I have not been able to repo this problem on my m3. Code is now up to I will mess with a splitter again and see if it makes a difference. |
Interesting. Dropbox upload all working? |
I am not using Dropbox integration, I have that disabled. Currently am using |
Cool, if you get bored and wanted to add a SCP service to the codebase that would be great |
Hi, |
Hi Peter,
Could you try out the ext4 branch? You make a good point about the dirty
bit, but then again i've seen similar issues with ext4 usb sticks
…On Tue, Jul 23, 2019 at 8:46 AM Peter Völkl ***@***.***> wrote:
Hi,
i have a similar problem in my model 3. After reboot the raspi drive ist
mountet correctly. Some times later the Camera-X Icon appears.
Possibly it is an Problem with the FAT32 Dirty Bit?
https://forums.tesla.com/forum/forums/dash-cam-feature-leaves-dirty-bit-fat32-usb-stick-when-going-sleep-mode-making-it
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11?email_source=notifications&email_token=AAJGHM7VWJ4LFEHH3TCI2Z3QA2ZOBA5CNFSM4HZEWSFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2SHLDI#issuecomment-514094477>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJGHMZVD56Z5POZTGLLZ3TQA2ZOBANCNFSM4HZEWSFA>
.
|
Hi, |
Hi, mount: /mnt: special device /dev/loop0p1 does not exist. |
Did you completely delete the original camera images? Either the image was
not generated correctly, or it's not showing up as a partition.
…On Mon, Jul 29, 2019 at 3:20 PM Peter Völkl ***@***.***> wrote:
Hi,
i deleted the teslacam folder, cloned the repo again and switched to the
ext4 branch.
Now the following Errormessage appers after starting dashcam-monitor.js:
mount: /mnt: special device /dev/loop0p1 does not exist.
Failed: code [32]: mount: /mnt: special device /dev/loop0p1 does not exist.
(node:1710) UnhandledPromiseRejectionWarning: Error: Command failed: sudo
/bin/mount /dev/loop0p1 /mnt
...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11?email_source=notifications&email_token=AAJGHM2BNBVI4GFGTGTSLXTQB34CRA5CNFSM4HZEWSFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3A3PNI#issuecomment-516011957>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJGHM54D2AUHEW4VB2UYODQB34CRANCNFSM4HZEWSFA>
.
|
yes I deleted both cam files in the image directory. After running dashcam-monitor.js a new cam0 File was created an the mounting error occurs: The file /dev/loop1p1 does not exist and no size was specified. |
Can you run an ls -l /dev ?
On Mon, Jul 29, 2019 at 7:53 PM Peter Völkl <[email protected]>
wrote:
… Did you completely delete the original camera images? Either the image was
not generated correctly, or it's not showing up as a partition.
… <#m_-5053822910990856251_>
On Mon, Jul 29, 2019 at 3:20 PM Peter Völkl *@*.***> wrote: Hi, i deleted
the teslacam folder, cloned the repo again and switched to the ext4 branch.
Now the following Errormessage appers after starting dashcam-monitor.js:
mount: /mnt: special device /dev/loop0p1 does not exist. Failed: code [32]:
mount: /mnt: special device /dev/loop0p1 does not exist. (node:1710)
UnhandledPromiseRejectionWarning: Error: Command failed: sudo /bin/mount
/dev/loop0p1 /mnt ... — You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#11
<#11>?email_source=notifications&email_token=AAJGHM2BNBVI4GFGTGTSLXTQB34CRA5CNFSM4HZEWSFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3A3PNI#issuecomment-516011957>,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJGHM54D2AUHEW4VB2UYODQB34CRANCNFSM4HZEWSFA
.
yes I deleted both cam files in the image directory. After running
dashcam-monitor.js a new cam0 File was created an the mounting error
occurs: The file /dev/loop1p1 does not exist and no size was specified.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11?email_source=notifications&email_token=AAJGHM5DTWTJLYJISFDICMDQB44BVA5CNFSM4HZEWSFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3BVJQI#issuecomment-516117697>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJGHMZFJXHJBAJJMHG7D4LQB44BVANCNFSM4HZEWSFA>
.
|
crw-r--r-- 1 root root 10, 235 Jul 29 20:17 autofs |
OK so for whatever reason either the image was not created correctly, and isn't showing up as a partition. As an interim fix, what you could do is clone a known working ext4 usb stick then copy it to the images directly, duplicate the image file and rename one cam0, the other cam1. I'm also seeing issues where sometimes it'll work, sometimes it wont. I'm testing the above approach now, then I'll compare the file systems to see if that helps |
You'd be making my life a 100x easier if you could check out the branch I mentioned above and burn that to a fast SDHC card and see what it does.
If you can poke around and see if any changed you make results in a different outcome that would be helpful. Currently I've been comparing a standard USB drive vs. the TeslaCam and I've struggled to see a difference - I did wonder if the USB serial number or other information was bleeding through and maybe Tesla blocked it for security reasons.
Given the car doesn't offer any diagnostics to us mere humans, it's somewhat trial and error.
The car has absolutely mounted the pi with the above branch mounted, but after some time it dropped out. (I've also seen this on standard USB flash drives, so it could be unrelated).
Any help would be appreciated, once this is up and running again it opens up some cool prospects
Originally posted by @milesburton in #9 (comment)
The text was updated successfully, but these errors were encountered: