[SOLVED] e2fsck

business_kid · 10-11-2023, 02:03 PM

I'm getting this from an sdcard. It's no disaster if I lose it, but I'd like the way out, if there is one.

Code:

dec@Ebony:~$sudo e2fsck -f /dev/sdb2
e2fsck 1.46.5 (30-Dec-2021)
The filesystem size (according to the superblock) is 7556347 blocks
The physical size of the device is 7556096 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? yes
dec@Ebony:~$sudo e2fsck -f -b 98304 /dev/sdb2
e2fsck 1.46.5 (30-Dec-2021)
The filesystem size (according to the superblock) is 7556347 blocks
The physical size of the device is 7556096 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>?

Pressing 'yes' dumps you out. Pressing no ignores the problem & checks the rest, but the thing won't mount. As the second exchange shows, the superblock looks OK.

pan64 · 10-11-2023, 02:26 PM

the physical size of the device is smaller than the filesystem on it (as I see). I would save everything and reformat it (either the partition or the whole sdcard).

mrmazda · 10-11-2023, 10:14 PM

The physical size of the sdb device is 7556096 blocks, or the physical size of the sdb2 device is 7556096 blocks? If sdb2, how many blocks is sdb, so perhaps you could delete sdb2 and recreate it larger?

colorpurple21859 · 10-11-2023, 10:47 PM

Resize the file system with resize2fs to fit inside the partition or use parted to resize the partition large enough to hold the file system.

business_kid · 10-12-2023, 04:49 AM

Quote:

Originally Posted by colorpurple21859

Resize the file system with resize2fs to fit inside the partition or use parted to resize the partition large enough to hold the file system.

Well, I resized the disk (again), and that did it. It had started life as a disk image of ~14G with an ext2 file system. So I've already resized it to 100%, but tried again and got there. Extending an ext? filesystem is a much less controlled process

Thanks to all.