Changes to Read-only file system #782
Unanswered
mabruzzo3169
asked this question in
Q&A
Replies: 6 comments 4 replies
-
|
File owner/permissions are probably not being properly established. Had the same problem some time ago but forget exactly how I corrected it. There's a tip in #430 that may help. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thanks. I’ll take a look. |
Beta Was this translation helpful? Give feedback.
-
Ah..., the card is being reported as read only, not the file. Probably is, then. Stick it in a card reader on your Ubuntu box and double check/correct it. May want to reformat anyway just because..., and ensure the read/write status is appropriate before committing it to the task at hand. Simpler oversights seem to occur around here on a regular basis. I've certainly contributed my share! |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
So I reformatted the SD cards this way. And now I get a whole list of errors on the Diagnostics page but it's working. For the record, I tried a brand new sd as well. |
Beta Was this translation helpful? Give feedback.
-
|
There obviously still appears to be a filesystem error..., perhaps additional content or paths. The pertinent files should be butt naked in the root directory of the card in the wz-mini directory along with the factory T20 ID string by itself. /wz_mini and /FACTORY T20************ (or similar). Nothing else should exist anywhere in the root directory for initial boot and subsequent configuration. Haven't done one from scratch in quite some time but this is my recollection. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Chiming in as I am also having the issue across two different Wyze 2 cameras with different makes/ages of SD cards, and even different firmware versions.(One is latest and one is the version referenced in the scripts. Both work well enough, both do this and go read only. It can be remounted and repaired temporarily with My own investigation into the issue is ongoing, trying to see if recording, selfhosted mode, etc can affect the issue but would appreciate any input from more knowledgeable folks. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I'm investigating here as well. It happens reliably when I use defaults and turn on go2rtc, and is not dependent on microSD card quality. My suspicions are that it either has to do with swap or with shutdown. For me, fsck.vfat on the device doesn't work reliably — I have to do so offline. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Regarding fsck.vfat not working reliably: it seems that fsck.vfat does not work with larger microSD cards due to limited RAM. There are some un-merged patches on the upstream Github repo that resolve this. How does one rebuild dosfstools here? |
Beta Was this translation helpful? Give feedback.
-
Unfortunately, I have tried running without swap, and this issue occurs after some hours of uptime without shutdown. I do think disk writes encourage the issue, whether they be from swap, native Wyze recording or just gortc logging, the more aggressive writing triggering the fault quicker. Makes me feel like the issue could be as high up as the filesystem formatting or the filesystem driver... but I lack the skills to pursue this line of thought. |
Beta Was this translation helpful? Give feedback.
-
|
I encountered the same issue last week. I won't bore you with a long diagnostic story, but I can share what worked for me. For some reason, I initially used the latest version of demo_wcv3 (4.61.0.1) for the camera setup and then switched to the latest version of wz_mini (4.36.13.0416) for RTSP. After this setup I encountered SD read-only issue, and spent many days to resolve this issue. Here's what ultimately resolved the issue for me: I reformatted the SD card. So far, this approach has been working without any "read-only" SD card issues. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey Everyone. First time poster here.
I followed the instructions to setup my cards with a Cam2 and Cam Pan 1 as per the instructions. I am able to login, configure the go2rtc server and reboot fine. Something happens after a reboot and the entire system becomes read-only. Changes via the Gui and via terminal (wz_mini_edit.sh) no longer work.
This happened on an install from January and I let it go because it was working with BlueIris and Frigate. I redid the cards last night and by this morning edits are locked.
I see posts on hear regarding the card not being FAT32 but mine was formatted on Ubuntu to FAT32 so I am sure that is OK.
Have you seen this before?
Beta Was this translation helpful? Give feedback.
All reactions