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
rpi-update to 4.14.48 partially killed SD card #1006
Comments
I was experiencing the same. Error occurs on really boot stage, where kernel is unable to mount root device. Outstanding tasks is perhaps to verify issue on proven flawless SD and fresh Raspbian (Lite) image. |
Not sure if the kernel has loaded a HDMI driver by the time it fails, but I get no output on a TV. The green SD activity light doesn’t illuminate at all either. |
Which models of Pi do you both have? |
Mine’s a model 3B. |
Do you (both) know what was the most recent firmware that worked for you? |
[ I'm not asking you (yet) to go back and try them all, I just wondered if you happened to know. ] |
Good question, the one in the release version of DietPi was fine. Pretty sure that uses the latest stable version of Raspbian, so that'd be |
@pelwell |
Looks like it was likely on 4.14.34 before the update. |
Thanks - that narrows it down a bit. |
REF: I was unable to replicate any issues with
|
Indeed as SDcards break fast, it is definitely possible, that mine and TOs SDcard is the issue, not the firmware update. In my case it was not the first SD failure, although the last bad block test run did not find any. |
I found my old 16GB Kingston card that used to show problems with small ERASE commands, and installing the 2018-04-08 Raspbian and You can tell if your card has been detected as one of the bad ones because
(note the If you want to enable the same workaround for any random card, add the following to cmdline.txt:
|
Can you tell us, what the show up of this means, respectively what you mean by Found #601 but could not really find out about the actual issue or how to solve it if actually possible 😉. |
Unless you have included If your card is already reporting the quirk without you manually setting it then setting it manually will have no effect, except perhaps to remove other quirks that may already have been set. If your card is being detected as a bad one and yet the problem persists then either there is a new problem or the workaround isn't working as I expected. |
@pelwell |
I was in the process of imaging my SD card on my Mac to try rpi-update again, but when doing so I started getting read errors. So it does look like in my case at least, the card is dying. It's a 32GB Sandisk Extreme, about a year old. Contacted Sandisk today who are replacing it with a newer A1 rated card. Interestingly erasing it with the SD Association's formatter seems to fix it for a while, only for it to break again a week or so later. Again not sure if this is a Pi thing or a SD thing, since I repeatedly filled the card with data totalling several hundred GB, and didn't have a read or write fail once. But after being in the fairly idle Pi for a few days, it dies. |
@Elijahg Did the new card work OK? Can this issue be closed? |
I've not had a problem with the A1 card so far, so it may well have been the card - or at least the model of the card I had originally. I'm also on 4.14.77 now, which has been perfectly stable, so I think it may well have been the card. |
After updating to 4.14.48 and rebooting, my Pi was unable to boot. Multiple attempts to image the SD card with dd on a Mac resulted in I/O errors at similar byte counts. I low-level formatted the card with the utility from sdcard.org which seemed to fix it. A second attempt to bump to 4.14.48 killed the card again. It's a Sandisk Extreme 32gb card. I've attempted to image the card with the built-in SD card reader on two different Macs, both get I/O errors. Strangely, an ancient USB 2.0 reader doesn't seem to error.
Steps to reproduce:
The text was updated successfully, but these errors were encountered: