I really love the Rasplex and want to use it as my main media center, however I am facing a problem that I don't have with either OpenElec nor Raspbmc. Whenever I perform a non-graceful shutdown (which sadly has to happen occasionally if something is stuck), the SD card is probably getting corrupted. I can still see the contents on the Mac but the PI gives out the following error and the only way to solve it is to write the image again (losing all my settings in the process):
*** Error in mount_storage: mount_common: Could not mount /dev/nmcblk0p2
System halted
I also reverted the SD card frequency (and other settings) to the lowest setting in config.txt, but it makes no difference. I am using an iPad charger as power to verify that it's not a power issue, and still the error occurs.
I would point out again that this only happens with Rasplex, Raspbmc and OpenElec (latest RC) works just fine.
Well at least I'm not alone on this... I would appreciate some feedback from anyone who might have resolved this issue. I don't want to return to Raspbmc after seeing the great features in Rasplex :).
I can confirm that this is happening for me as well with 0.1.35.
0.1.32 does not have this issue, but of course isn't anywhere close to the performance of 0.1.35.
Keep up the good work. Hope this information helps.
I had the same problem with 0.1.35 it occured every time when i wanted to reboot/shutdown the device. After a few tests with 0.1.36 it seems to be fixed for me. Hope this helps, I'm using a SanDisk Class 10 SD Card.
Anyone have any luck with this in the end? I've tried five different SD cards and three power supplies. I've tried using the automated installer and flashing the image manually. I've tried repairing after the error using fsck. All to no avail. Works fine on first boot, then I get the mount_storage error on second boot, every time.
Same here, had 2-3 freezes within an hour of Rasplex (used AirPlay and tried to access shared content and it frooze. Power off/on, and suddenly corruption. Seen it on older and newer version as well as raspbmc.
Same here, had 2-3 freezes within an hour of Rasplex (used AirPlay and tried to access shared content and it frooze. Power off/on, and suddenly corruption. Seen it on older and newer version as well as raspbmc.
An acceptable work around for sure, but I'd much rather leverage the SD card slot than loose a USB slot. I'm keeping my fingers crossed that this becomes a priority for our already hard working developers (thank you again for your time). Especially since I finally got the wife to sign off on Plex and replace our monthly DVR's with a Plex client. This and the deep sleep (http://forums.plexapp.com/index.php/topic/67331-rasplex-37-deep-sleep-issue/) issue are the only things standing in my way from having Rasplexes throughout my home. It will prob. force me to get the more expensive Roku's just for Plex. blah :(
First things first,well done to the devs for an amazing product.
Unfortunately i can only get this to run from a usb drive due to the mount storage error i get whenever i reboot after the pi is shutdown.
512 MB Pi
Things tried
16gb Transcend class 10
4gb transcend class 6
8gb micro SD .
0.1.36
0.1.37
All tried with 2 different SD readers/writers.
All tried on both mac and windows rasplex installers.
All suffer from exactly the same problem.
Only way i get it to work is to install to 4GB USB Cruzer edge thumb drive,it works like a champ!
Are the devs actually even looking at this problem as there seems to be no feedback whatsoever ?
Can anyone shine a bit of light on what is likely to be causing the error?
Any help is massively appreciated.This is the only issue stopping me getting a plexpass.
Edit2: changed the standard overclock to stock pi settings and it seems to have cured this error…performance struggles a little but this is expected,will investigate further when I get time.
Edit2: changed the standard overclock to stock pi settings and it seems to have cured this error....performance struggles a little but this is expected,will investigate further when I get time.
This also solved the issue for me a while back. Especially the default overclock of the core by 100MHz (40%) seems to cause a lot of errors while working with the SD.
