Gladys unreachable

Configuration
1

Hi everyone,

During my last vacation, Gladys suddenly became unreachable. When I returned yesterday, I tried to connect to it via the local web interface and then via PuTTY, and it was still unreachable.
I power-cycled the Pi and noticed the activity LED stayed on constantly. After restarting, same.
Has anyone ever experienced this behavior?
Otherwise I suspect an SD card failure but I haven’t had time to test another one. If that’s the case, I’ll migrate to an SSD.

Thanks in advance for your feedback!

2

Hi!
Indeed, it looks like a corrupted SD card…
Can you attach a screen to it to see what your RPi says?

3

Hello,
I’d like to take advantage of this thread to ask whether it’s possible to access the logs from a computer rather than from a screen connected to the Raspberry Pi, and what steps would need to be performed?

4

You can access it via SSH using software such as ‹ PuTTY › on PC, JuiceSSH on Android, etc.
The command to enter is docker logs gladys

5

Thanks @GBoulvin, I’ll try PuTTY to access it from my PC.

6

For the details, if that helps you:

In PuTTY you need to configure a connection; for that you must enter your Raspberry Pi’s IP address (something like 192.168.1.xxx), the username (typically pi) and the password (if you haven’t changed it it’s raspberry).

From there you’ll be able to connect, and once you’re at the command prompt, that’s where you can access the logs with: docker logs gladys

:+1:

7

Nice, and thanks @guim31 for your additional info :+1:

8

Hi,

That’s right. SD card is toast. It’s time to switch to an SSD :grin:

2 Likes
9

I’d even say more…maybe it’s time to switch to a NUC! :wink:

1 Like