[arrrghhh]

Originally Posted by ndno

So far so good, a day without any reboots or SOD. Will let it run over the weekend and let you guys know. Yeah, this requires you to pick up some real "Linux" hacking skills. You'll have to install Ubuntu or some other Linux distro and use fdisk to repartition your SD card into the different partitions I was talking about. Nate showed my how to remap the cache directory to another EXT2 partition to allow the SD card to wear out more evenly.

I don't know if putting this on a dedicated partition will resolve the SoD or reboot issue TBH - it certainly should be better overall compared to looped filesystems tho, I would imagine.

Also, I don't think this would require Linux - there's tools for Windows that allow you to partition the SD in all sorts of file systems. It's just easier with Linux because a) the tools are built into the system and b) Windows won't be able to read those newly created partitions anyways, without other 3rd party tools .

Not to take any wind out of your sails, but I wouldn't consider that Linux hacking skills . Certainly got some geek cred, and it's not easy to do without any prior knowledge - but far from what I would consider hacking . Neopeek builds have required this for quite some time... (a separate ext2 partition that is)

Originally Posted by ndno

It could be... I'm currently running at 710. The kernel is not constantly running at 710, it will throttle between the OC speed and the lower speed (122) depending on the processor's load, so it won't waste battery or overheat. I remembered arrrghhh saying that higher OC can cause instabilities so it definitely can be speed related. If you have bad data in your data.img, it can also be related to that too. That's why I'm switching to the EXT2 partition test I'm currently doing now to see if it's more reliable.

hyc said that running on dedicated partitions did localize his corruption - thus not having to blast out his data.img (or in this case partition) as frequently - that doesn't mean that it eliminated the issue.

In theory it should be a little quicker as well - it might not be significant enough to even be noticeable to the end user.

Originally Posted by fishingmedic

Ok, that sounds too confusing, I'm sure you and arrrghhh would ban me with the amount of questions I'd be asking... I'll stick with GBX0A and FRX05 lmao

If there's some demand for it, ndno (or me) can certainly make a how-to do this. The rootfs is already configured to handle it, so AFAIK you just have to setup the partitions and drop the data in - I'm not really sure how much repointing is involved TBH.