search

n0bel / PiClock

A Fancy Clock built around a monitor and a Raspberry Pi
MIT License
566 stars 182 forks source link

New install corrupting file system #129

Closed cyptex16403 closed 5 years ago

cyptex16403 commented 5 years ago

On an new PI 3 B, fresh PiClock install with base config, very slow to launch and upon exit file system is corrupted and having to run fsck to recover. Not sure what could be causing this? Any Suggestions?

ScottChapman commented 5 years ago

Seriously doubt it has anything to do with this app; it is just a bunch of files.

Perhaps you had a bad microSD?

cyptex16403 commented 5 years ago

Thanks for the reply, it had occurred to me the mSD could be bad...will replace that....

David dproman@gmail.com

On Tue, Jan 22, 2019, 7:24 PM Scott Chapman <notifications@github.com wrote:

Seriously doubt it has anything to do with this app; it is just a bunch of files.

Perhaps you had a bad microSD?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/n0bel/PiClock/issues/129#issuecomment-456630288, or mute the thread https://github.com/notifications/unsubscribe-auth/AsxRI6rFych8HWnGRodP_ZaiGcW43aOsks5vF7ndgaJpZM4aNvOc .

billskeen68 commented 5 years ago

I updated to the new PiClock using DarkSky and now having the same issue.

Also getting this error when ssh in:

/usr/bin/xauth: error in locking authority file /home/pi/.Xauthority

Read somewhere it might have to do with being root in pi home directory...looking into setup to see if I missed a step.

n0bel commented 5 years ago

PiClock2 is not updated to the replacement weather and maps apis. You need to stick with PiClock, not PiClock2. As far as things being slow, and the other error you're getting, I'd save your configs to some other computer, then start from scratch with a new SD card.

billskeen68 commented 5 years ago

Apologies, I updated my comment. I meant the new version using DarkSky.

n0bel commented 5 years ago

I updated to the new PiClock using DarkSky and now having the same issue.

Also getting this error when ssh in:

/usr/bin/xauth: error in locking authority file /home/pi/.Xauthority

Read somewhere it might have to do with being root in pi home directory...looking into setup to see if I missed a step.

This can happen if you run some things as root. If you're quite familiar with linux, or search alot around the internet you may be able to fix it. But from my perspective, I'd just start with a new SD card, because that could be the issue anyway.

But really, root should not have been required to update.

cyptex16403 commented 5 years ago

The new SC recommendations did the trick....thank you all! It must have been defective from the start...even though it was new as well....no matter....back running as expected....