I have these mounts on my white light 1TB wdbook drive:
~ # mount /dev/root on / type ext3 (rw,noatime,data=ordered) proc on /proc type proc (rw) sys on /sys type sysfs (rw) /dev/pts on /dev/pts type devpts (rw) securityfs on /sys/kernel/security type securityfs (rw) /dev/md3 on /var type ext3 (rw,noatime,data=ordered) /dev/md2 on /DataVolume type xfs (rw,noatime,uqnoenforce) /dev/ram0 on /mnt/ram type tmpfs (rw) /dev/md2 on /shares/private type xfs (rw,noatime,uqnoenforce) /dev/md2 on /shares/Public type xfs (rw,noatime,uqnoenforce)
When I check the drive I get:
~ # e2fsck -n /dev/sda1 e2fsck 1.38 (30-Jun-2005) Warning: skipping journal recovery because doing a read-only filesystem check. /dev/sda1 contains a file system with errors, check forced. 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 (438285, counted=438266). Fix? no Free inodes count wrong (237179, counted=237180). Fix? no /dev/sda1: ********** WARNING: Filesystem still has errors ********** /dev/sda1: 8101/245280 files (0.3% non-contiguous), 51667/489952 blocks
None of these was checked at startup:
~ # dmesg ... kjournald starting. Commit interval 5 seconds EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3 FS on md0, internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem). Freeing init memory: 108K Adding 256952k swap on /dev/md1. Priority:-1 extents:1 across:256952k Registered led device: oxnas-wd810-leds:switch Registered led device: oxnas-wd810-leds:state Registered led device: oxnas-wd810-leds:activity Registered led device: oxnas-wd810-leds:capacity kjournald starting. Commit interval 5 seconds EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3 FS on md3, internal journal EXT3-fs: mounted filesystem with ordered data mode.
The /dev/sda1 does not seem to be checked, time is stuck at Thu Jan 1 01:00:02 1970. The system has correct time BTW
~ # tune2fs -l /dev/sda1 tune2fs 1.41.4 (27-Jan-2009) Filesystem volume name: <none> Last mounted on: <not available> Filesystem UUID: x Filesystem magic number: x Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype needs_recovery sparse_super large_file Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 245280 Block count: 489952 Reserved block count: 24497 Free blocks: 438285 Free inodes: 237179 First block: 0 Block size: 4096 Fragment size: 4096 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 16352 Inode blocks per group: 511 Filesystem created: Thu Jan 1 01:00:02 1970 Last mount time: Thu Jan 1 01:00:02 1970 Last write time: Thu Jan 1 01:00:02 1970 Mount count: 36 Maximum mount count: 26 Last checked: Thu Jan 1 01:00:02 1970 Check interval: 15552000 (6 months) Next check after: Tue Jun 30 01:00:02 1970 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode: 8 Default directory hash: tea Directory Hash Seed: x Journal backup: inode blocks
I get slow transfers but I do not know if they are related to this. Ho can I run a check on the drive and fix the wrong dates?