Hi,
The file system is clean and un-mounted, but fsck still reports problem.
Any ideas? Thanks.
arc178.alexa.com root 143% df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/ram 92123 73307 16850 82% /
none 158928 0 158928 0% /dev/shm
vectra2:/export/fedora_1.0/usr
19607928 14238400 4373496 77% /usr
vectra2:/export/fedora_1.0/alexa
19607928 14238400 4373496 77% /alexa
barker:/lib0/home 48063808 35722592 11860576 76% /.amd_mnt/barker/lib0/home
arc178.alexa.com root 144% e2label /dev/hda10
/var
arc178.alexa.com root 145% fsck -a
fsck 1.34 (25-Jul-2003)
/: clean, 25228/131328 files, 51855/262144 blocks
/0: clean, 4083/7651328 files, 329408/15291604 blocks
/1: clean, 12/10010624 files, 322337/20010808 blocks
/2: clean, 12/9781248 files, 315144/19537552 blocks
/3: clean, 12/9781248 files, 315144/19537552 blocks
/alexa: clean, 1037/656640 files, 45657/1310720 blocks
/usr: clean, 128634/656640 files, 690656/1310720 blocks
Warning... fsck.ext3 for device LABEL=/var exited with signal 11.
arc178.alexa.com root 146% dumpe2fs /dev/hda10
dumpe2fs 1.34 (25-Jul-2003)
Filesystem volume name: /var
Last mounted on: <not available>
Filesystem UUID: 09e27eea-0f9b-4e93-a7eb-17a7e48d698e
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype sparse_super
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 131328
Block count: 262144
Reserved block count: 13109
Free blocks: 226076
Free inodes: 129792
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16416
Inode blocks per group: 513
Filesystem created: Fri Apr 2 16:56:48 2004
Last mount time: Fri Apr 2 16:57:45 2004
Last write time: Fri Apr 2 17:12:11 2004
Mount count: 1
Maximum mount count: 38
Last checked: Fri Apr 2 16:56:48 2004
Check interval: 15552000 (6 months)
Next check after: Wed Sep 29 17:56:48 2004
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: fb411ff3-47d7-4d16-bd96-a7eb76a2a6dc
Group 0: (Blocks 0-32767)
Primary superblock at 0, Group descriptors at 1-1
Block bitmap at 2 (+2), Inode bitmap at 3 (+3)
Inode table at 4-516 (+4)
23941 free blocks, 16381 free inodes, 10 directories
Free blocks: 518-521, 8831-32767
Free inodes: 36-16416
-----Original Message-----
From: Alexander Dalloz [mailto:alexander.dalloz@xxxxxxxxxxxxxxxx]
Sent: Friday, April 02, 2004 4:21 PM
To: For users of Fedora Core releases
Subject: RE: Strange Fedora Booting problem: can notmount 'LABEL=*' partitions
Am Sa, den 03.04.2004 schrieb Guolin Cheng um 01:50:
> Hi,
>
> I'm not using an initrd.img file to boot. The FC1 can see|mount other
> "LABEL=" partitions listed in fstab except this one. On the system disk
> I have an extended logical partition. The "LABEL=/usr", "LABEL=/alexa",
> "LABEL=/0" and "LABEL=/var" and other 3 swap parititions are all on the
> extended Logical partition, All other 3 "LABEL=*" partitions are
> detected and mounted well, except "LABEL=/var" partitions.
>
> The error message are always:
>
> " ... fsck.ext3 for device LABEL=/var exited with signal 11. ..."
>
> Then I'm in single user mode, while now I can run "mount /var" without
> any problems. Too strange.
To me the problem is not a mount problem at all. The error is a failure
running fsck and _not_ mount. I fear your filesystem is bad on hda10.
Being in single user mode, running fsck.ext3, will that succeed or give
you a signal 11 error too?
Alexander
--
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 1 (Yarrow) on Athlon CPU kernel 2.4.22-1.2174.nptl
Sirendipity 02:18:17 up 14 days, 10:00, load average: 0.01, 0.05, 0.09
[ Γνωθι σ'αυτον - gnothi seauton ]
my life is a planetarium - and you are the stars
