So I’m new to using pi as well as linux programming in general. I’m an academic that’s in a new lab that a previous user built a pi system for monitoring experimental samples, and since they’ve left we’ve all been using it, but not really understanding what’s going on under the hood. Recently the pi failed to load. When trying to boot it, the desktop failed to boot, and went immediately to terminal environment. When running startx, I got the following errors
Could not create lock file in /tmp/.tX0-lock
Error in locking authority file /home/pi/.Xauthority
I spent all today combing forums and troubleshooting, and have tried a lot of things, but am seemingly stuck. I think I've identified a few potential components in this problem. Firstly, our building had an electrical shutdown and I’ve read that crashed sessions (potentially caused by the shutdown) can lead to problems like this. I’ve also read that having a completely full pi can cause similar problems and df shows that dev/root is at 100% capacity. While I would try to delete these files, the whole system has been locked into read-only, so it seems like I can’t really do anything.
I’ve also read that the system can lock into read only when the SD card is crapping out, which I don’t know if related to these problems or not.
We have a lot of coding infrastructure built into this pi, as the pi is connected to a lot of other pieces of moving hardware. However, I think we’ve lost the personal and experience to recreate this so we’re afraid that just moving code bases to the new pi will require a lot of work. Given we want to continue this infrastructure I thought I might just be able to make a flash copy of the SD card and put it on a new card and things would be fine, but the same issues persisted.
I’m hoping there’s a way to rescue this card, or if anyone has thoughts on how to transfer everything to a new card for an easy plug and play.
Could not create lock file in /tmp/.tX0-lock
Error in locking authority file /home/pi/.Xauthority
I spent all today combing forums and troubleshooting, and have tried a lot of things, but am seemingly stuck. I think I've identified a few potential components in this problem. Firstly, our building had an electrical shutdown and I’ve read that crashed sessions (potentially caused by the shutdown) can lead to problems like this. I’ve also read that having a completely full pi can cause similar problems and df shows that dev/root is at 100% capacity. While I would try to delete these files, the whole system has been locked into read-only, so it seems like I can’t really do anything.
I’ve also read that the system can lock into read only when the SD card is crapping out, which I don’t know if related to these problems or not.
We have a lot of coding infrastructure built into this pi, as the pi is connected to a lot of other pieces of moving hardware. However, I think we’ve lost the personal and experience to recreate this so we’re afraid that just moving code bases to the new pi will require a lot of work. Given we want to continue this infrastructure I thought I might just be able to make a flash copy of the SD card and put it on a new card and things would be fine, but the same issues persisted.
I’m hoping there’s a way to rescue this card, or if anyone has thoughts on how to transfer everything to a new card for an easy plug and play.
Statistics: Posted by kdrik — Thu May 09, 2024 10:44 pm — Replies 0 — Views 38