Okay. Not sure what the significance of 0 is in his example, and wondering if he meant -c and not -C. The -b 32768 should be valid, but you can try without that and use -B 4096, since that is the reported block size.
EDIT: I didn't read the man page completely.
Quote:
If the file descriptor specified is 0, e2fsck will print a completion bar as it goes about its business. This requires that e2fsck is running on a video console or terminal.
Thanks kernel-panic69, i'll try with -B 4096. If not successful, there's still an option to scan/repair on a computer. I was reluctant to do this because of the thousands of media files that i have on this drive.
However, i'm a bit lost and confused by message when executing e2fsck /mnt/sda2 (or sda1, same message, even whith command e2fsck -f -C 0 /mnt/sda2, same result:
Quote:
root@DD-WRT:~# e2fsck -b 32768 /mnt/sda2
e2fsck 1.46.5 (30-Dec-2021)
e2fsck: Is a directory while trying to open /mnt/sda2
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
What is this superblock thing ? knowing that the files are accessible on the drive that seems to work properly ? The suggested commands e2fsck -b 8193 and e2fsck -b 32768 didn't help
/mnt/sda2 is a directory and not a drive, the drive would be /dev/sda2
By the way, you cannot check /dev/sdb2 (/opt) if you have installed the e2fsprogs on it.
but if the file system is "clean" then it is "clean" and you do not need to check it as I have written before
Milax wrote:
After formatting flash drive with opt and jffs (sdb1, sdb2) (ext 4), there is no more issues at this stage on dmesg but running e2fsck is still recommended for the separate hard drive (sda 1, sda2), that's why i unmounted it and ran the scan. I'll try to run it with -c, thanks
You can still set the reserved blocks to 0.
This is a default setting for multiuser systems and for filesystems used as rootfs.
5% of the total capacity is reserved for processes running with root privileges.
Since neither of these applies, you can also set the reserved blocks to 0 and unlock the total capacity.
Code:
tune2fs -m 0 /dev/sda1
tune2fs -m 0 /dev/sda2
It might be noticeable if you connect the hard disk to a PC and try to copy data to it with a "non-root user".
