Hi All
I have a Raspberry pi server which has been running in an Argon M.2 case, largely trouble free for a couple of years. It shut down sometime last week, not sure exactly when but my Alby service was not available.
I have had SD card failure but recovered the server without issue before. Now I can’t get the server to boot with either an old image or the latest asset from Github?
I get the error in the subject line when I look at the boot cosole which I suspect may be something to do with the pi’s firmware and bootloader. Does anybody recognise the fault? Would my Pi have updated/upgraded or installed firmware, I doubt it?
Would it be smart to boot the pi on a stock image without the M.2 drive attached and update the firmware etc?
You may just want to try it again. Make sure you are flashing the correct image. Otherwise, you’re likely experiencing hardware failure. The SD card would be the prime suspect.
I have tried two SD cards but both have failed in service and both have been re-formatted. I will follow the procedure on your link from scratch using a new SD card and let you know what happens.
It is possible I have a bunch of cheap “internet” SD cards which are flaky but I get the same console error using the original Panasonic 32GB card and two new & never used Sandisk 32GB
FYI: I had been using the latest image from Github and Balena Etcher for all debug attempts.
I believe I have a SD Card formatted for a (known good last boot) RPI Desktop application which I may try to boot from but with the M.2 SSD unmounted.
This issue is exactly as before. Does anybody recognise this?
I have now tried four different SD cards since the problem arose (the server just stopped).
Upon flashing a new SD card with the latest stable image for Raspberry Pi I get a usual boot with messages about resizing the disk partitions followed by a reboot.
There is then a console prompt to say it is loading “embassyfs” and then the message in the subject line of this post appears.
I have put a basic Raspberry Pi image on an SD card and the Pi boar will boot from this. I have an image on a bootable USB SSD and the respberry pi will boot straight from the SSD so I believe all is good with regard to the firmware on the Pi
Any suggestions most welcome, I now have a dead server that I can’t even start regardless of revovery from the SSD!
Upon flashing a new SD card with the latest stable image for Raspberry Pi I get a usual boot with messages about resizing the disk partitions followed by a reboot.
Where/how/when do you get “usual” boot messages about resizing disk partitions? This is not normal. You just flash the microSD and insert it, the follow StartOS screens about where the data is located.
There is then a console prompt to say it is loading “embassyfs” and then the message in the subject line of this post appears.
How are you seeing a console prompt in your web browser? you’re supposed to be at http://start.local.
If you have a screen plugged into the Pi 4, then you are not following the guide and what you are doing will not work.
I have put a basic Raspberry Pi image on an SD card and the Pi boar will boot from this. I have an image on a bootable USB SSD and the respberry pi will boot straight from the SSD so I believe all is good with regard to the firmware on the Pi
None of this is in the guide.
Here’s the shortest summary of the guide I think if possible…
1. Flash the microSD and insert it, then connect power 2. Visit http://start.local and choose to use existing data
Beyond that, if your Pi is broken, or if you’re deviating from the guide, there’s probably not much we can do I’m afraid.
Sorry for not feeding back sooner but this whole episode has been a bit deflating tbh!
It turns out that my M.2 SATA SSD that I use in my Argon One M.2 case bit the dust! There is a very remote possibility that there is an issue with the Argon One case or the USB daughter board that carries the physical SSD. I have a new NVMe >> USB daughter board assembly and a couple of 1TB drives in the mail. I will see if I can mount the “failed” ssd on to some device to ascertain if it is actually dead. To make it worse, I have no backup! I have had all sorts of issues with permission to networked machines, nothing making sense.
The loss has been the time I put in to this, luckily only samll lightning liquidity experiments WRT Bitcoin or other stuff likely gone. I ran this small server because it is the right thing to do and to learn as I go.
Thanks for the help trying to solve this problem. I hope to have a couple of Start9 servers running soon. I will restore the RPI4 with the SATA SSD if I can save the SSD. Failing that I will build another using the RPI and new SSD. I also have Start9 installed on Proxmox on a “1 litre class” DELL Optiplex x86. I will put my second NVMe M.2 drive in this VM and let you know if that works.
