After a few reboots using a Samsung EVO 16GB class 10 card, the partition corrupts and is not recoverable without serious work, it just boots to a command line.
I have experienced this with the latest version of openelec 5.0.5 and rasplex 0.5.1
if I put rasplex on a boring old 1GB unbranded crappy Sd card left over from a phone, not even class 4 or otherwise indicated, it boots like a gun and never fails after I tested it about 40 times to be sure.
Just thought I would leave a note here in case anyone else is experiencing this issue.
This is an issue with openelec, which (at least for me) appears to affect rasPlex as well (rasplex is based on openelec, so it makes sense)
There is a thread on the openelec forums working on a fix here that seems resolved in their latest non-stable patch:
Funny, I’m currently running on a new 32gb, class 10 Samsung card (obviously overkill, but I had it sitting around) and haven’t had any stability issues at all with 0.5.1 on a RPi 2.
I have to agree. I started with a 16GB class 10 Samsung card I already had whilst waiting for the 8GB card to arrive. It worked flawlessly. The same is true when I got the 8GB card and used that.
The Vilross kit you can buy with the pi2 comes with a Samsung 8GB class 10 card I believe.
It may be more likely you have a card with bad sectors.
No problems with Transcend Cards either, had two in RPi1’s running 24/7 for nearly 6 months, overclocked and rock steady.
Any SD card will fail eventually if you use reboot from command line as it doesn’t provide a safe shutdown, safer to use the Restart option in Rasplex, or if turning off use the Shutdown option and then power off.
Don’t believe everything you read, experience is the thing! Look at my sig.
I have two brand new Samsung 8GB class10 cards that I bought with the Pi 2's. One got corrupted after a few reboots. Reloaded Rasplex, and it happened again a few days later. I have two Sandisks on order now.
Any SD card will fail eventually if you use reboot from command line as it doesn't provide a safe shutdown, safer to use the Restart option in Rasplex, or if turning off use the Shutdown option and then power off.
I am using a 16G transcent card. Occasionally I see some strange issues, like the pi2 rebooting while trying to play a movie. It's not consistently reproducible, sometimes it simply displays a blank screen.
Can you elaborate on why reboot from command line is bad? Is there a safe way to reboot from command line? Is there a way for me to find out if my sd card has any issues?
I am using a 16G transcent card. Occasionally I see some strange issues, like the pi2 rebooting while trying to play a movie. It's not consistently reproducible, sometimes it simply displays a blank screen.
Can you elaborate on why reboot from command line is bad? Is there a safe way to reboot from command line? Is there a way for me to find out if my sd card has any issues?
Use 'shutdown -r now' to reboot, if you want to turn off the Pi, then 'shutdown now', then switch of the power.
Use 'shutdown -r now' to reboot, if you want to turn off the Pi, then 'shutdown now', then switch of the power.
Thank you!
Why would there be a difference between 'reboot' and 'shutdown -r now'? Is this only applicable to rasplex? raspberry? I recall both work as intended on regular Linux systems.
I also noticed restart via the plex menu is a lot faster than openelec 5.05's restart which seems to have a very slight delay (to sync filesystem?) That makes me wonder if plex's menu restart is actually doing everything it's supposed to do. :)
Why would there be a difference between 'reboot' and 'shutdown -r now'? Is this only applicable to rasplex? raspberry? I recall both work as intended on regular Linux systems.
I also noticed restart via the plex menu is a lot faster than openelec 5.05's restart which seems to have a very slight delay (to sync filesystem?) That makes me wonder if plex's menu restart is actually doing everything it's supposed to do. :)
Having used Linux systems for more years than I care to remember it was always a case of in Linux the Reboot command does a very quick reboot, it doesn’t execute any kill scripts, but just unmounts filesystems and restarts the system. Whereas, the shutdown command gracefully reboots the system running all the K* shutdown scripts first, before rebooting, particularly useful for systems running multiple processes (and especially db processes).
However, having done a bit of searching this morning it would appear that modern implementations of Linux the Reboot command now calls the Shutdown command, however, I'll continue using Shutdown, because it's something I've always done!
