Проверка диска с помощью fsck

[pylyp]

Стоит Ubuntu 10.10, ядро 2.6.35-24-generic, gnome 2.32.0
/ находится на /dev/sda2 в ext4

notebook:~$ sudo fsck -n /dev/sda2
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
Warning!  /dev/sda2 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sda2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix? no

Inode 144765 was part of the orphaned inode list.  IGNORED.
Inode 144784 was part of the orphaned inode list.  IGNORED.
Inode 928997 was part of the orphaned inode list.  IGNORED.
Deleted inode 940133 has zero dtime.  Fix? no

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -(2781847--2781849) -(2781858--2781867)
Fix? no

Free blocks count wrong (3798641, counted=3798482).
Fix? no

Inode bitmap differences:  -144765 -144784 -928997 -940133
Fix? no

Free inodes count wrong for group #17 (21, counted=19).
Fix? no

Free inodes count wrong (1064723, counted=1064696).
Fix? no


/dev/sda2: ********** WARNING: Filesystem still has errors **********

/dev/sda2: 216397/1281120 files (0.3% non-contiguous), 1322077/5120718 blocks

Вопрос 1. Надо ли это все править?
Вопрос 2. Как запустить проверку / ? При попытке размонтировать пишет

notebook:~$ umount /
umount: лише root може відключити UUID=бла-бла-бла від /

Запускать с LiveCD?

[фирэфохэ]

С livecd.

[pylyp]

С livecd.

У меня после установки обновилось ядро. В системе и на установочном CD теперь они разные. Это не проблема?

[фирэфохэ]

Нет.

[pylyp]

Прогнал проверку, получил заверения, что диск без ошибок и "чистый", после перезагрузки некоторые ошибки появились опять. Насколько это смертельно?
Забить?

notebook:~$ sudo fsck -n /dev/sda2
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
Warning!  /dev/sda2 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sda2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 928795 has zero dtime.  Fix? no

Inodes that were part of a corrupted orphan linked list found.  Fix? no

Inode 931967 was part of the orphaned inode list.  IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -(3960477--3960479) -(3960489--3960498)
Fix? no

Free blocks count wrong (3797274, counted=3797235).
Fix? no

Inode bitmap differences:  -928795 -931967
Fix? no

Free inodes count wrong (1064798, counted=1064768).
Fix? no


/dev/sda2: ********** WARNING: Filesystem still has errors **********

/dev/sda2: 216322/1281120 files (0.3% non-contiguous), 1323444/5120718 blocks