I have three 8 GB RPi 5s running Bookworm. All are configured each using a 1TB Samsung SSD as the boot device as well as storage. All are running the BOINC application. I was running all of them headless, using VNC Viewer to connect to them via my Windows machine. However, one of them has developed a problem. It will no longer run headless; it will run fine, but I cannot access it remotely. I now have to connect a monitor, etc. in order to see what is going on. The option for VNC will not hold. I can set it on, and it will then turn itself off.
I even copied the boot device from one of the working devices, renamed it, and used it for the "bad" rpi 5. No go. It still will not keep the VNC option on. So, what is going on? Is the rpi now defective? If so, is this a defect such that I may ask for a replacement? I welcome any suggestions as to how this issue can be addressed.
Incidentally, all of these devices are powered via a UPS, and I have had no power interruptions that I know of since they've been operational.
Many thanks,
Bill
I even copied the boot device from one of the working devices, renamed it, and used it for the "bad" rpi 5. No go. It still will not keep the VNC option on. So, what is going on? Is the rpi now defective? If so, is this a defect such that I may ask for a replacement? I welcome any suggestions as to how this issue can be addressed.
Incidentally, all of these devices are powered via a UPS, and I have had no power interruptions that I know of since they've been operational.
Many thanks,
Bill
Statistics: Posted by wlathan — Sun Jan 21, 2024 1:25 pm — Replies 1 — Views 73