04-08-2016, 07:20 AM
(This post was last modified: 04-08-2016, 07:32 AM by lenny.raposo-pine64.pro.)
The images are not the factor here as they work for others. There can be 4 possibilities here.
1) Faulty SD Card(s).
2) Faulty PC MMC Drive.
3) Premature ejection of disk before write is completely flushed to disk (likely in most cases).
4) Faulty Pine64 MMC drive.
Try an Android/Remix OS image and see if it is yielding the same results in terms of FS/partition corruption (try multiple cards). Remember to safely eject the cards when using windows (right click on drive > Eject in Explorer). For good measure wait a few minutes after the write to disk is completed.
If you are seeing the same issues on multiple cards even going through the paces of safe image writes then I would have to say the MMC card slot is faulty on either the PC or the Pine (not an uncommon thing). Try writing images from another system with a different MMC slot (this should help rule out your PCs if the same is still occurring leaving the Pine as the culprit)
Just a thought
I wanted to ask if you have resized the RootFS after burning to disk?
If not then when you first login into your pine (linux image)
run
sudo -i
/usr/local/sbin/resize-rootfs.sh
That should resize the rootfs partition.
Let me know if you have any issues with corruption after doing that
1) Faulty SD Card(s).
2) Faulty PC MMC Drive.
3) Premature ejection of disk before write is completely flushed to disk (likely in most cases).
4) Faulty Pine64 MMC drive.
Try an Android/Remix OS image and see if it is yielding the same results in terms of FS/partition corruption (try multiple cards). Remember to safely eject the cards when using windows (right click on drive > Eject in Explorer). For good measure wait a few minutes after the write to disk is completed.
If you are seeing the same issues on multiple cards even going through the paces of safe image writes then I would have to say the MMC card slot is faulty on either the PC or the Pine (not an uncommon thing). Try writing images from another system with a different MMC slot (this should help rule out your PCs if the same is still occurring leaving the Pine as the culprit)
Just a thought
I wanted to ask if you have resized the RootFS after burning to disk?
If not then when you first login into your pine (linux image)
run
sudo -i
/usr/local/sbin/resize-rootfs.sh
That should resize the rootfs partition.
Let me know if you have any issues with corruption after doing that
If you like my work be sure to check out my site or wish to donate to the cause
Cheers
Cheers