Run cleanup command if SD card was not unmounted properly #70

New Issue

muellerr · 2021-07-29T19:31:42+02:00

muellerr commented

2021-07-29 19:31:42 +02:00

If the OBSW is restarted and the SD card was not unmounted, an error can occur when remounting the SD card. I have issue reproducing the issue right now, but I think the error can be detected by piping the output of mount /dev/mmcblk<0/1>p1 /mnt/sd<0/1> to a file and checking whether it is empty or not in the OBSW.

The simple solution would be to check whether this error occured and then repair the system with the command

fsck -a /dev/mmcblk<0/1>p1

to remove the dirty bit

If the OBSW is restarted and the SD card was not unmounted, an error can occur when remounting the SD card. I have issue reproducing the issue right now, but I think the error can be detected by piping the output of `mount /dev/mmcblk<0/1>p1 /mnt/sd<0/1>` to a file and checking whether it is empty or not in the OBSW. The simple solution would be to check whether this error occured and then repair the system with the command ```sh fsck -a /dev/mmcblk<0/1>p1 ``` to remove the dirty bit

muellerr changed title from ~~Run `fsck -a /dev/mmcblk<sd>p2` if SD card was not unmounted~~ to Run cleanup command if SD card was not unmounted properly

2021-07-29 19:33:29 +02:00

muellerr commented

2021-08-03 14:50:09 +02:00

After performing some research, I found out that the output is produced by the kernel, and can
be queried with

journalctl -t kernel -n 3

after mounting the SD card.
Now the question remains whether this outout is always checked directly after mounting the SD card or whether the fsck command is just run everytime..

Also, remember this for #68 , getting the kernel output log requires using -t instead of -u

After performing some research, I found out that the output is produced by the kernel, and can be queried with ``` journalctl -t kernel -n 3 ``` after mounting the SD card. Now the question remains whether this outout is always checked directly after mounting the SD card or whether the `fsck` command is just run everytime.. Also, remember this for #68 , getting the kernel output log requires using `-t` instead of `-u`

muellerr commented

2023-02-17 12:25:01 +01:00

This was solved by using an ext4 journaling filesystem

This was solved by using an `ext4` journaling filesystem

muellerr closed this issue

2023-02-17 12:25:02 +01:00

Sign in to join this conversation.