You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fstransform version 0.9.3 - I did a conversion of reiserfs to ext4 on a Debian 10 system. After the conversion it tried to do fsck:
12:43:24 fstransform: running again '/sbin/fsck' (disk check) on device '/dev/sda3'
12:43:24 fsck: fsck from util-linux 2.33.1
12:43:24 fsck: Failed to open the device '/dev/sda3': Unknown code er3k 127
12:43:24 fsck:
12:43:24 fsck:
12:43:24 ERROR! fstransform: command '/sbin/fsck -p -f /dev/sda3' failed (exit status 8)
this is potentially a problem.
you can either quit now by pressing ENTER or CTRL+C,
or, if you know what went wrong, you can fix it yourself,
then manually run the command '/sbin/fsck -p -f /dev/sda3'
(or something equivalent)
and finally resume this script by typing CONTINUE and pressing ENTER:
The problem was that the filesystem was still contained in /etc/fstab and listed as reiserfs there, so fsck used the reiser specific filesystem checking tool for checking.
It would be better if the conversion tool also adjusted the fstab and changed reiserfs to ext3 (because the previous value is now obviously wrong) and didn't fail here.
Or use the filesystem specific way to check for the filesystem like e2fsck in my case.
The text was updated successfully, but these errors were encountered:
fstransform version 0.9.3 - I did a conversion of reiserfs to ext4 on a Debian 10 system. After the conversion it tried to do fsck:
The problem was that the filesystem was still contained in /etc/fstab and listed as reiserfs there, so fsck used the reiser specific filesystem checking tool for checking.
It would be better if the conversion tool also adjusted the fstab and changed reiserfs to ext3 (because the previous value is now obviously wrong) and didn't fail here.
Or use the filesystem specific way to check for the filesystem like e2fsck in my case.
The text was updated successfully, but these errors were encountered: