I have RetroPie 4.8 (Raspbian Buster). I cloned it from 32Gb SD Card to 128Gb SD Card (using dd). Checked sha512sum of the partitions (original and cloned). Then I resized the retropie partition (main ext4 partition) using Gparted (I know that there is build-in feature in raspi-config to expand the filesystem, but I wanted to use not all available space). When I booted from that 128Gb SD Card, there was fsck check of the retropie partition (previously I cloned SD Card without expanding the partition and there wasn't fsck check).
Is it normal to have fsck check after resizing partition?
In which log file can I watch this fsck check results (it just run from 0 to 100% and then boot continued)?
Is fsck writes to the log about corrupted files (names of the files)?
I want to be sure that there is no data corruption.
Is it normal to have fsck check after resizing partition?
In which log file can I watch this fsck check results (it just run from 0 to 100% and then boot continued)?
Is fsck writes to the log about corrupted files (names of the files)?
I want to be sure that there is no data corruption.
Statistics: Posted by POPEYE — Wed May 29, 2024 8:15 am