Recovery from improper shutdowns

Every once in a while my Force doesn't go through the proper shutdown sequence, for example, when the power cable is accidentally pulled out while the Force was on.

So far it rebooted just fine every time, with no data loss or data corruption, but I want to be proactive about any lingering file system issues (the most likely thing to get corrupted during an improper shutdown). Is there the equivalent of a fsck or CHKDSK to make the Force scan and fix any file system issues that I can trigger?

Timo wrote:Every once in a while my Force doesn't go through the proper shutdown sequence, for example, when the power cable is accidentally pulled out while the Force was on.

So far it rebooted just fine every time, with no data loss or data corruption, but I want to be proactive about any lingering file system issues (the most likely thing to get corrupted during an improper shutdown). Is there the equivalent of a fsck or CHKDSK to make the Force scan and fix any file system issues that I can trigger?

That's a good question. Unfortunately I have no idea, but the only thing I can think of is to put the Force in computer mode & let your PC disk utility scan for errors. If you find a way to do it please post it.

That's good thinking, but that won't work. Disk repair utilities (like CHKDSK on Windows, which I am using) want the disks to be locally mounted to do their thing. Since the Force presumably runs a Linux distribution as its OS, it'll have to be something that triggers that disk check locally. Would be an easy option for Akai to add to the Force, and a nice preventative maintenance thing to do!

My take on it:

The Force is based on relatively recent Linux.

I don't know, but I surmise that its main filesystem is EXT4, which is a journaled filesystem in addition to being pretty stable, and I would imagine that they configure it with write-through caching behaviour on the RAM.

During bootup it should automatically check the coherence of the filesystem, and that should include a run of fsck.

The open question is other, additional file systems. This includes attached USB/SDcard storage as well as the internal SATA drive. Those you can detach and directly check on another system - ideally, a linux system rather than windows. I had the foresight to format my SATA drive with a linux system, so that's also EXT4, which should give me the benefits of that file system on SATA as well.

In short: I doubt that you have much to worry about, but do consider backing your system up from time to time. Drives aren't forever.

I hope you're right! Yeah, if they're using a journaled file systems, and are checking/fixing integrity issues at bootup, I'd feel confident, but not knowing whether they're doing that, I ... don't.

I formatted my internal SATA SSD with NTFS, which is journaled as well, but I doubt they'd be checking NTFS integrity at bootup as well?

Anyway, that's all speculation, sure would be nice to have somebody from Akai on here to jump in and answer these questions

Either way, your suggestion to back up is a very good one, and I do it frequently. So at least I won't lose my projects.