File system check, what the heck!!

[Ant2ne]

I tried booting kubuntu and it wouldn't load. It gave me some message about the file system is messed up and I had to check it. [I never take good enough notes, I just jump in and fix stuff, I gotta break that habit] So I grabbed my system rescue CD and booted off it. Loaded up Gparted and used it to check all my partitions. It succeeded and I rebooted into kubuntu. Poof! All of my personal settings seem to have vanished. Well, not all, but a lot of them. Like my desktop is still there, but the buttons I added to the bar at the top of my screen are gone. I'm just about to try to impress my friend and convince him to go kubuntu, and he is gonna expect me to be able to tell him how stable it is.


Here is the output of gparted. BTW sda2 is my kubuntu root partition

GParted 0.3.4

Libparted 1.7.1


Check and repair filesystem (ext3) on /dev/sda2 01:17 ( SUCCES )

calibrate /dev/sda2 00:01 ( SUCCES )

path: /dev/sda2
start: 30716280
end: 81915434
size: 51199155 (24.41 GiB)
check filesystem on /dev/sda2 for errors and (if possible) fix them 01:16 ( SUCCES )

e2fsck -f -y -v /dev/sda2

Superblock last mount time is in the future. Fix? yes

Superblock last write time is in the future. Fix? yes

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

/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****

143863 inodes used (4%)
2311 non-contiguous inodes (1.6%)
# of inodes with ind/dind/tind blocks: 6846/62/0
864447 blocks used (13%)
0 bad blocks
1 large file

118295 regular files
18504 directories
133 character device files
26 block device files
2 fifos
468 links
6894 symbolic links (6171 fast symbolic links)
0 sockets
--------
144322 files

e2fsck 1.39 (29-May-2006)

grow filesystem to fill the partition 00:00 ( SUCCES )

resize2fs /dev/sda2

resize2fs 1.39 (29-May-2006)
The filesystem is already 6399894 blocks long. Nothing to do!



========================================


Check and repair filesystem (ntfs) on /dev/sda1 00:05 ( SUCCES )

calibrate /dev/sda1 00:00 ( SUCCES )

path: /dev/sda1
start: 63
end: 30716279
size: 30716217 (14.65 GiB)
check filesystem on /dev/sda1 for errors and (if possible) fix them 00:05 ( SUCCES )

ntfsresize -P -i -f -v /dev/sda1

ntfsresize v1.13.1.1 (libntfs 9:0:0)
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 512 bytes
Current volume size: 15726703104 bytes (15727 MB)
Current device size: 15726703104 bytes (15727 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 12963 MB (82.4%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 13033 MB 0
Multi-Record : 14268 MB 50318
$MFTMirr : 9 MB 1
Compressed : 6136 MB 43650
Sparse : 13051 MB 51484
Ordinary : 14494 MB 43599
You might resize at 12962873344 bytes or 12963 MB (freeing 2764 MB).
Please make a test run using both the -n and -s options before real resizing!

grow filesystem to fill the partition 00:00 ( SUCCES )

run simulation 00:00 ( SUCCES )

ntfsresize -P --force --force /dev/sda1 --no-action

ntfsresize v1.13.1.1 (libntfs 9:0:0)
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 512 bytes
Current volume size: 15726703104 bytes (15727 MB)
Current device size: 15726703104 bytes (15727 MB)
New volume size : 15726703104 bytes (15727 MB)
Nothing to do: NTFS volume size is already OK.

real resize 00:00 ( SUCCES )

ntfsresize -P --force --force /dev/sda1

ntfsresize v1.13.1.1 (libntfs 9:0:0)
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 512 bytes
Current volume size: 15726703104 bytes (15727 MB)
Current device size: 15726703104 bytes (15727 MB)
New volume size : 15726703104 bytes (15727 MB)
Nothing to do: NTFS volume size is already OK.


========================================


Check and repair filesystem (fat32) on /dev/sda7 00:07 ( SUCCES )

calibrate /dev/sda7 00:00 ( SUCCES )

path: /dev/sda7
start: 81915561
end: 102398309
size: 20482749 (9.77 GiB)
check filesystem on /dev/sda7 for errors and (if possible) fix them 00:02 ( SUCCES )

dosfsck -a -w -v /dev/sda7

dosfsck 2.11 (12 Mar 2005)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "mkdosfs"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
8192 bytes per cluster
32 reserved sectors
First FAT starts at byte 16384 (sector 32)
2 FATs, 32 bit entries
5115904 bytes per FAT (= 9992 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 10248192 (sector 20016)
1278920 data clusters (10476912640 bytes)
63 sectors/track, 255 heads
0 hidden sectors
20482748 sectors total
Reclaiming unconnected clusters.
Checking free cluster summary.
/dev/sda7: 7161 files, 301812/1278920 clusters

grow filesystem to fill the partition 00:05 ( SUCCES )

using libparted

========================================


Check and repair filesystem (ext3) on /dev/sda8 00:08 ( SUCCES )

calibrate /dev/sda8 00:00 ( SUCCES )

path: /dev/sda8
start: 102398373
end: 122881184
size: 20482812 (9.77 GiB)
check filesystem on /dev/sda8 for errors and (if possible) fix them 00:08 ( SUCCES )

e2fsck -f -y -v /dev/sda8

Superblock last write time is in the future. Fix? yes

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

/dev/sda8: ***** FILE SYSTEM WAS MODIFIED *****

22 inodes used (0%)
1 non-contiguous inode (4.5%)
# of inodes with ind/dind/tind blocks: 1/1/0
123683 blocks used (4%)
0 bad blocks
1 large file

5 regular files
8 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
13 files

e2fsck 1.39 (29-May-2006)

grow filesystem to fill the partition 00:00 ( SUCCES )

resize2fs /dev/sda8

resize2fs 1.39 (29-May-2006)
The filesystem is already 2560351 blocks long. Nothing to do!



========================================


Check and repair filesystem (ext3) on /dev/sda6 00:27 ( SUCCES )

calibrate /dev/sda6 00:00 ( SUCCES )

path: /dev/sda6
start: 136215198
end: 156296384
size: 20081187 (9.58 GiB)
check filesystem on /dev/sda6 for errors and (if possible) fix them 00:27 ( SUCCES )

e2fsck -f -y -v /dev/sda6

Superblock last write time is in the future. Fix? yes

Pass 1: Checking inodes, blocks, and sizes

Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 16224: 52404
Multiply-claimed block(s) in inode 16244: 57433
Multiply-claimed block(s) in inode 16354: 51487
Multiply-claimed block(s) in inode 16361: 51483
Multiply-claimed block(s) in inode 16371: 52404
Multiply-claimed block(s) in inode 16392: 57433
Multiply-claimed block(s) in inode 16457: 51483 51487
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1D: Reconciling multiply-claimed blocks
(There are 7 inodes containing multiply-claimed blocks.)

File /ant2ne/.kde/share/apps/kdesktop/IconPositions (inode #16224, mod time Tue May 22 20:47:37 2007)
has 1 multiply-claimed block(s), shared with 1 file(s):
/ant2ne/.kde/share/config/kmixctrlrc (inode #16371, mod time Tue May 22 20:47:28 2007)
Clone multiply-claimed blocks? yes

File /ant2ne/.kde/share/apps/ksysguard/KSysGuardApplet.xml (inode #16244, mod time Tue May 22 20:47:28 2007)
has 1 multiply-claimed block(s), shared with 1 file(s):
/ant2ne/.kde/share/config/kickerrc (inode #16392, mod time Tue May 22 18:42:13 2007)
Clone multiply-claimed blocks? yes

File /ant2ne/.kde/share/config/konquerorrc (inode #16354, mod time Tue May 22 20:47:28 2007)
has 1 multiply-claimed block(s), shared with 1 file(s):
... (inode #16457, mod time Tue May 22 20:47:27 2007)
Clone multiply-claimed blocks? yes

File ... (inode #16361, mod time Tue May 22 20:47:28 2007)
has 1 multiply-claimed block(s), shared with 1 file(s):
... (inode #16457, mod time Tue May 22 20:47:27 2007)
Clone multiply-claimed blocks? yes

File /ant2ne/.kde/share/config/kmixctrlrc (inode #16371, mod time Tue May 22 20:47:28 2007)
has 1 multiply-claimed block(s), shared with 1 file(s):
/ant2ne/.kde/share/apps/kdesktop/IconPositions (inode #16224, mod time Tue May 22 20:47:37 2007)
Multiply-claimed blocks already reassigned or cloned.

File /ant2ne/.kde/share/config/kickerrc (inode #16392, mod time Tue May 22 18:42:13 2007)
has 1 multiply-claimed block(s), shared with 1 file(s):
/ant2ne/.kde/share/apps/ksysguard/KSysGuardApplet.xml (inode #16244, mod time Tue May 22 20:47:28 2007)
Multiply-claimed blocks already reassigned or cloned.

File ... (inode #16457, mod time Tue May 22 20:47:27 2007)
has 2 multiply-claimed block(s), shared with 2 file(s):
/ant2ne/.kde/share/config/konquerorrc (inode #16354, mod time Tue May 22 20:47:28 2007)
... (inode #16361, mod time Tue May 22 20:47:28 2007)
Multiply-claimed blocks already reassigned or cloned.

Pass 2: Checking directory structure
Entry 'kwallet_101a014311510d000117976019200000056290016 _1179762205_699147' in /ant2ne/.kde/share/config/session (16070) has deleted/unused inode 16449. Clear? yes

Entry 'kdeglobals' in /ant2ne/.kde/share/config (16042) has deleted/unused inode 16435. Clear? yes

Entry 'kicker_menubarpanelrc' in /ant2ne/.kde/share/config (16042) has deleted/unused inode 16375. Clear? yes

Entry 'kbluetoothdrc' in /ant2ne/.kde/share/config (16042) has deleted/unused inode 16438. Clear? yes

Entry '.DCOPserver_ant2ne-laptop_:0' in /ant2ne (16033) has deleted/unused inode 16232. Clear? yes

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached inode 16361
Connect to /lost+found? yes

Inode 16361 ref count is 2, should be 1. Fix? yes

Unattached inode 16381
Connect to /lost+found? yes

Inode 16381 ref count is 2, should be 1. Fix? yes

Unattached inode 16441
Connect to /lost+found? yes

Inode 16441 ref count is 2, should be 1. Fix? yes

Unattached inode 16443
Connect to /lost+found? yes

Inode 16443 ref count is 2, should be 1. Fix? yes

Unattached inode 16456
Connect to /lost+found? yes

Inode 16456 ref count is 2, should be 1. Fix? yes

Unattached inode 16457
Connect to /lost+found? yes

Inode 16457 ref count is 2, should be 1. Fix? yes

Pass 5: Checking group summary information
Block bitmap differences: +33947 -33948 -(33950--33951) +33975 -36942 +(36943--36944) -36949 -(36952--36957) +(36958--36963) -36966 +36968 -(36970--36980) +(36985--36986) -40934 -40999 +45072 -47116 +(51483--51484) +51487 +(52404--52405) +59467 +68990 +68999 +69121 +69313 +69315 +69317 -69318 +69319 -(69328--69331) +69333 +69337
Fix? yes

Free blocks count wrong for group #0 (21882, counted=21878).
Fix? yes

Free blocks count wrong for group #1 (4612, counted=4618).
Fix? yes

Free blocks count wrong for group #2 (35, counted=32).
Fix? yes

Free blocks count wrong for group #8 (29, counted=30).
Fix? yes

Inode bitmap differences: +16220 -16232 -16375 +16381 -16435 -16438 +16441 +16443 -16449 +(16456--16457)
Fix? yes

Free inodes count wrong for group #1 (10296, counted=10295).
Fix? yes

Free inodes count wrong (1227624, counted=1227623).
Fix? yes


/dev/sda6: ***** FILE SYSTEM WAS MODIFIED *****

6841 inodes used (0%)
275 non-contiguous inodes (4.0%)
# of inodes with ind/dind/tind blocks: 2402/37/0
658766 blocks used (26%)
0 bad blocks
1 large file

6393 regular files
410 directories
0 character device files
0 block device files
0 fifos
0 links
29 symbolic links (29 fast symbolic links)
0 sockets
--------
6826 files

e2fsck 1.39 (29-May-2006)

grow filesystem to fill the partition 00:00 ( SUCCES )

resize2fs /dev/sda6

resize2fs 1.39 (29-May-2006)
The filesystem is already 2510148 blocks long. Nothing to do!



========================================

Questions:
1> What happend when I did the fs check? Why did my settings change?
2> Is this a sign of hard drive failure? ie sectors going bad. The laptop is still under warranty so I need to know. I'm not running anti viri on this partition (only on my windows sda1 partition.) so is that a possibility?
What are inodes?
3> t says it was modified, but not really what was changed or what was wrong in the first place.

I'm eager to learn about this.

[mchuskie]

Re: File system check, what the heck!!

I think the best way to answer your questions is all at once... plus I have an exam with a question on filesystems in two weeks, so it's revision

Kubuntu is set up to automatically check filesystems after ~30 mounts (in most cases this means every 30 boots). These automatic checks interrupt the normal boot process and, if they don't find any problems, return you to it.

If the check finds a problem, it will either fix it automatically or dump you at a root shell (like Recovery Mode), and ask you to run fsck manually.

If either of these checking methods fixes errors, it may be necessary to reboot Linux (it'll give you a nice CAPITALISED MESSAGE) or remount the filesystem.

In your case, the directory structure was mucked up under your KDE config directory, which explains why your settings have changed. This could just be caused by a bad shutdown (if you hit the power without shutting down properly).

If you're familiar with the programming concept of pointers, that's essentially what an inode is: a pointer to where the data is actually stored. Each inode can contain pointers to other inodes - think of an upside-down tree, with the root "/" at the top and your directories/files branching out from that. Someone comes along with a stick and whacks your ~/.kde/share directory; some twigs fall off (unattached inodes, deleted/removed inode errors) while others are bent to point to the wrong place (multiply-claimed blocks).

NB This is not the answer I would use in my exam! Though I wonder what the examiners would make of it... Hope that makes things a little clearer, and I wouldn't worry too much about HDD failure unless it starts happening more often.

[Ant2ne]

Re: File system check, what the heck!!

The shutdown statement makes sense. My Fiesty doesn't like to shut down completely. It gets hung up and sits there. So sometimes I gotta hit the power switch to get it to shut down. But I never heard of the fs getting damaged on a quick shut down. Is this something a person needs to worry about in the event of a power outage?

I wasn't allowed to manually run fsck manually during the boot, as I booted from the files system that needed checking. I had to boot from another location, be sure sda2 was unmounted and checked then.