-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
is this installer still working? #538
Comments
Can you check whether the same issue occurs with installing Bullseye? |
If you're comfortable building the installer from source, then adding |
I get the same behavior with Here are the logs from
I don't feel confortable enough to build de debug installer (but that could be an idea to release a debug installer in addition to a default installer). Would it be long to release an installer with an updated key from raspbian-archive-keyring? raspbian has recently been renamed raspberry pi os. Does this change has an impact on the install process? |
I build an installer with the
Could you try again? It looks like just a temporary failue. And if it fails again, could you create an |
I'll try that. Is it possible for you to share the installer with the |
Max attachment size (here) is 25MB, but the installer is 38MB. So it looks like that isn't going to work |
You can share it on plik. |
Is there a way to enable debugging? I still have the same error, and no additional verbose log. Here are the logs from
I will now make another try with an |
Exactly the same result with an Here are the logs from
|
I'm having some doubt about the hardware: maybe the raspberry board, or the power supply. But it is strange because I successfully installed raspberry pi os... I need some further testing... Any suggestion is more than welcomed! |
(and the other time setting failures) indicate a network problem and then it makes sense that the network-installer also fails.
cdebootstrap also has a
Why do you think that? I've seen no indication of that. It really looks like a network failure when retrieving the |
Thanks for all the effort that you do to provide me with debug flag. I think it is now time to hold this issue because I need more time to invetigate. I changed the SD card and the USB power supply and it appears that I succeded in installing raspbian. We should maybe read "E: Couldn't download Release!" as "E: Cannot write to downloaded release to the SD card!". In fact, now that I know that the problem does not come from the installer, and now that I have an installer with the debug flag enabled, I need more time to find out what was the root cause of the problem: USB power supply? corrupted SD card? failure on the router? network interruption during install? Once I get more information, I'll come here to tell you what was happening. |
It seems that something is getting wrong in installing a fresh install of
raspbian-ua-netinst
.Here are the logs from
raspbian-ua-netinst-<yyyymmddThhmmss>.log
:When I check the website, I can see that the raspbian mirror still exists on http://mirrordirector.raspbian.org/raspbian/dists/buster/!
What could possibly go wrong?
The text was updated successfully, but these errors were encountered: