I’m a new Volumio user, running Volumio 3.661 (latest version) on an rpi 4. I’m noticing file system errors on the 3rd partition (volumio_data) after powering down and doing a file system check on the SD card’s partitions.
I would like to point out that these file system errors have had no noticeable affect on Volumio running. Everything works fine as best I can tell. I just wanted to make a backup image of the SD card contents with Clonezilla, so I powered down to do that, and then discovered these file system errors occurring on the 3rd partition - which need to be fixed before creating an image.
In any case, the issue can be quite easily recreated with these steps:
- Install Volumio latest version (3.661) on a rpi using an SD card (I’m using rpi 4, with 8 GB RAM))
- Do the initial Volumio config, then power down from the app/web interface (or command prompt)
- Remove the SD card from the rpi and plug it into a Linux PC to run file system check
- The 3rd partition consistently shows fs error(s), (block count and/or inode count)
Below are 2 examples of what I’ve seen here: (SD card is ~64 GB /dev/sdd)
Example 1:
tompfr@bookworm:~$ sudo fsck -fn /dev/sdd3
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free inodes count wrong (14501477, counted=14501470).
Fix? no
volumio_data: 283/14501760 files (2.5% non-contiguous), 1856306/59633664 blocks
Example 2:
tompfr@bookworm:~$ sudo fsck -fn /dev/sdd3
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (47997419, counted=47997283).
Fix? no
Free inodes count wrong (13255868, counted=13255864).
Fix? no
volumio_data: 2884/13258752 files (8.9% non-contiguous), 6528533/54525952 blocks
The errors are always fixed while running ‘fsck -fy’, or of course interactively with just ‘fsck -f’
After I started seeing this, I started over with a new Volumio install using brand new SD card, just to make sure that wasn’t the problem. It made no difference.
Thanks,
Tom P
for pc