On Sun, 06 Jan 2019 16:55:52 +0000 Ivan D. Reid wrote:

> On Sun, 6 Jan 2019 14:43:15 -0000 (UTC), Markus Robert Kessler
> 
>  wrote in :
>
>> But after the crash / failure, when I clicked on the "root fs"
>> partition,
>> there only popped up an error alert saying that this partition cannot
>> be mounted. Same symptoms seen when the first Kingston crashed.
>
>> And, after running a fsck / e2fsck now, there is no such partition any
>> more. I can access the whole partition like 'cat /dev/sdc2 | xxd |
>> less',
>> but I only see the first 64 MB. The remaining space seems unavailable.
>> Aaaargh...
>
>  Are you sure they are genuine Kingston cards, from a reputable
> source?  From what I hear this is the classic symptom of fake
> solid-state devices which contain far less than advertised (and reported
> by the modified controller) and only that small fraction can indeed be
> written to.  See, for example,
> https://www.happybison.com/reviews/how-to-check-and-spot-fake-micro-sd-
card-8/


I had 2 identical "Kingston 8GB Class4" cards. Sure they were cheap :-)

And, today's crash may be the result of a power loss, or, caused by
overload due to those constant write cycles. Well. Maybe.

But, the first of those two cards was in a RPi running alone and touched
or plugged out by no one. It was peacefully running more than hundred
miles away from me. It just shot some photos taken from a USB camera and
ssh-ed them to a webserver. And from one hour to the next the machine
crashed and the connection was gone.
First I thought, the RPi crashed and due to that the SD card was
overloaded with write cycles and died. But after what I've seen today, I
doubt it and rather assume that the card died and hence the OS crashed.

Really weird what happened with those "Kingston" cards...

Best regards,

Markus

--
Please reply to group only.
For private email please use http://www.dipl-ing-kessler.de/email.htm

--- SoupGate-Win32 v1.05