Skip to content
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

Corrupt disk #802

Open
cybercop23 opened this issue Dec 6, 2024 · 15 comments
Open

Corrupt disk #802

cybercop23 opened this issue Dec 6, 2024 · 15 comments
Assignees

Comments

@cybercop23
Copy link

Running either Aug 17, Sep 23 or Oct 21 versions of v4 and uploading to an SD card from xLights, when I tried to delete a file from the GUI File Management, it corrupted the filesystem and got the ESP into a continous boot. Once I replaced the card it was fine. This happened twice on 2 diff HW and 2 diff versions. Using Chrome Version 131.0.6778.109 (Official Build) (64-bit)

@MartinMueller2003
Copy link
Collaborator

This is part of the same issue that is causing the xLights updates to fail. I had to slow things down a bit and I am getting a bit more reliability in the updates. I should have the changes added to the experimental build soon.

@MartinMueller2003
Copy link
Collaborator

Webflasher has been updated with a new experimental version that has increased (but not perfect) transfer reliability and fewer SD card hangs. FYI: For me, putting the SD card into a PC and formatting tends to correct the issues.

@cybercop23
Copy link
Author

FYI: For me, putting the SD card into a PC and formatting tends to correct the issues.

Right.. that's how I got it to come back to life... well.. first replaced the card and then it worked so I thought I had 2 bad cards and that seemed odd and then reformatted. I'll try it today. Thanks much.

@joe8012
Copy link

joe8012 commented Dec 6, 2024

chkdsk /f also works if you don't want to re-upload all your sequences again. After many uploads over the past year, I found that having the espixelstick UI closed during the fpp connect upload, greatly reduces the upload failures.

@cybercop23
Copy link
Author

Yeah, same here, and that's what I did. But wanted to delete a file manaually and test some changes from xLights and then it went poof.

@cybercop23
Copy link
Author

@MartinMueller2003 I don't see the new ver? Refreshed and still nada...
image

@dutch-anykey
Copy link

dutch-anykey commented Dec 7, 2024

I had that too.
But you need to select this I found out:
image

It doesn't show any version there, but after I flashed it I got:

FW Version4.0-ci12088826635
Build DateNov 29 2024 - 17:46:35

(already an older version when I flashed that one)

@MartinMueller2003
Copy link
Collaborator

The CI builds have been updated with some additional changes to prevent corruption of the SD card. PR has been generated.

@cybercop23
Copy link
Author

Thank you very much.

@dutch-anykey
Copy link

@MartinMueller2003

I'm testing with SD-card and Xlights.
But still can't get it stable, bust guess from my side that it is related to this ticket.

When I startup SD is present, even a manual upload of a big seq. file succeeded (took a while as known)

Also I did a controller config upload from Xlights (still not working correctly and @xlights github so far not responded to my question)
(Could it be that this upload mangles something in the ESPixelstick?)

But anyway the SD card stopped working also a few reboots didn't help
I attached the logfile with the events. A few extra reboots are there because wifi sometimes doesn't connect immediately

espixelstick_log.txt

@MartinMueller2003
Copy link
Collaborator

There is an issue in the SD code that sometimes causes the SD to lockup. You need to turn off power (IE reseat) the SD. I am still working to find a way to avoid that state. On my other projects I added a power control for the SD card so it can be hard reset.

@dutch-anykey
Copy link

Well I wasn't even able to connect to a fpp player so far. But I made some changes in my test setup:

  • got rid of the SD card reader and soldered directly to the SD card adapter.
  • used very short wires
  • since webflasher site is down, copied your latest version and changed the GPIO-default file (made sure nothing overlaps)
  • upload filesystem and b the just built sw.

Now it is running like a charm :) So most problems were related to my test setup is my guess.
Got that multisync finally running now. For now I keep testing and see how it holds up here

I also have a new feature request....there is a fpp plugin called "Brightness control" Would be a big plus to have that on Espixelstick
So all outputs can be set to a certain level. Or maybe you can say now already to better leave that request? :)

IMG_5831
IMG_5830

@MartinMueller2003
Copy link
Collaborator

ESPS V4 has a brightness control setting for each port.

@dutch-anykey
Copy link

ESPS V4 has a brightness control setting for each port.

Yes, but I'm looking for a way to increase/decrease brightness on a global level like the brightness plugin in fpp.
The controllers will be used for led suits. And to adjust for ambient light (dark/light indoor/outdoor) it would be nice to have one "main" slider to adjust all controllers. But in worst case I can make different fseq files with different brightness settings in xlights.

Anyway, for now i'm happy that this SD problem seems to be gone at the moment. Still up and running here. this evening I want to test with 4 ports and led's atached.

thanks!

@cybercop23
Copy link
Author

Like a "Lock" button to move all ports brightnesses together

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants