FOGProject / fos

FOG Operating System
30 stars 33 forks source link

BTRFS udev error and exFAT-FS weird messages when capturing/deploying BTRFS partitions #46

Closed Pieshka closed 1 year ago

Pieshka commented 1 year ago

Hello!

I recently installed Fedora on a BTRFS file system and wanted to make an image of it. It turned out that creating a resizable image, was throwing errors. This was caused by a typo in the script, which I have now corrected and sent a pull request. However, when capturing/deploying the image, the screen is flooded with a large number of errors like "udevd[1852]: failed to execute (...)". (as shown in the screenshot). Also, when mounting a partition as /tmp/btrfs, exFAT-FS-related errors appear, which is even stranger, because I do not have any exFAT partitions (sda3 is BTRFS). In the end, these errors do not affect the operation of the whole thing and everything works, but it just looks wrong.

The problem with udev is caused by the eudev package in Buildroot, where additional parameters should be added to the makefile (as here: https://bugs.gentoo.org/show_bug.cgi?id=739268).

As for the exFAT-FS problem, I have no idea. It mounts correctly, so why the problem. Nevertheless, it would be fitting to fix both problems.

I am using: FOG Project: 1.5.175 Kernel: 5.17.68 Init.xz: Custom based on the latest one (added patches from pull request) Captured system: Fedora 36 on BTRFS file system (Virtual Machine)

EXFAT-FS Error EXFAT_ERRORS

Udev Error UDEV_ERROR

Pieshka commented 1 year ago

I have good news on this issue. I managed to solve both problems.

The eudev problem has already been fixed in the latest versions of Buildroot (as of now they use this: https://github.com/eudev-project/eudev). So I used version 2022.02.5 and built a new init.xz. When building the new version, I simply went along with the settings suggested by Buildroot as far as configuration migration is concerned (I only changed the kernel headers to 5.15.X). I will still subject this init.xz, to further testing, although I don't see any problems in operation so far (Unicast, Multicast and Capture work)

UDEV_ERROR_GONE

The solution to this strange problem with exFAT-FS is even simpler. Simply replace in the funcs.sh file: mount $part /tmp/btrfs >>/tmp/btrfslog.txt 2>&1 to: mount -t btrfs $part /tmp/btrfs >>/tmp/btrfslog.txt 2>&1

Specifying a filesystem probably just forces the use of the BTRFS driver and so exFAT-FS does not throw errors.

EXFATERROR_GONE

As for the problem with eudev I leave it to more experienced developers to decide what to do, and as for exFAT-FS I will prepare a proper pull request with the changed command.

Edit: I accidentally pasted the message in my native language instead of English. My mistake. Easier for me to just write everything first and then translate.

Sebastian-Roth commented 1 year ago

This is being worked on in the partclone-0320 branch.

Latest FOS inits currently use buildroot 2022.02.6: https://github.com/FOGProject/fos/releases/tag/20221009

We wait for people to test and report.

Sebastian-Roth commented 1 year ago

The move to buildroot 2022.02.6 has not triggered any related issue reports yet. A fair amount of people are using the latest inits on dev-branch to cover at least some basic testing. So I think we can close this one as solved.

@Piotr86PL Thanks for your work on this topic.