Package: util-linux
Version: 2.16.2-0
Severity: important
File: /sbin/fsck

Dear Sir,

I would like to report an error at the boot of the linux testing, at each boot.

==================
PART I : SUMMARY
==================
It happened, after a power cut. The electricity went of and it results taht 
after the first boot.
This error happens:
 "fsck died with exit status 6" 

==================
PART II : DETAILS
==================
So please find my logs:

BEFORE THE POWER CUT /etc/fstab:

# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda1 during installation
UUID=b048a4e6-7397-4c03-ae9c-56945fd46618 /               ext4    
errors=remount-ro 0       1
# /backups was on /dev/sdb1 during installation
UUID=6b8f7a91-55a2-48b3-9840-840950b8af16 /backups        jfs     defaults      
  0       2
# /home was on /dev/sde1 during installation
UUID=31c5d001-07a4-4e3f-90d3-bbc82a1afc88 /home           jfs     defaults      
  0       2
# /toll was on /dev/sda3 during installation
UUID=700ae18e-c633-4542-8156-5bb5d4d379d5 /toll       jfs     defaults        0 
      2
# swap was on /dev/sda2 during installation
UUID=b5d2c56c-3902-449b-af80-86754cdd45ce none            swap    sw            
  0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/sdf1       /mnt/sdf1       vfat    
user,rw,auto,umask=0000,uid=1000,gid=1000  0    2

At this point, all is working great, reboot ,. .. .hte linux and so on. A dream 
Debian LINUX.

So, and well,  the power cut occurs, well very unfortunately.

Everytime I try to boot the PC, the PC says to me 
FSCK error 
and it tells me that a log of error is into /var/log... checkfs

Please find the file as such below
cat /root/checkfs
Log of fsck -C -R -A -a
Sat Jun 19 13:56:48 2010

fsck from util-linux-ng 2.16.2
open: No such file or directory
dosfsck 3.0.9, 31 Jan 2010, FAT32, LFN
fsck.jfs version 1.1.12, 24-Aug-2007
processing started: 6/19/2010 13.56.48
The current device is:  /dev/sde1
Block size in bytes:  4096
Filesystem size in blocks:  488378368
**Phase 0 - Replay Journal Log
Filesystem is clean.
fsck.jfs version 1.1.12, 24-Aug-2007
processing started: 6/19/2010 13.56.48
The current device is:  /dev/sda3
Block size in bytes:  4096
Filesystem size in blocks:  478612992
**Phase 0 - Replay Journal Log
Filesystem is clean.
fsck.jfs version 1.1.12, 24-Aug-2007
processing started: 6/19/2010 13.56.48
The current device is:  /dev/sdb1
Block size in bytes:  4096
Filesystem size in blocks:  488378368
**Phase 0 - Replay Journal Log
Filesystem is clean.
fsck died with exit status 6

Sat Jun 19 13:57:08 2010
----------------


So the error and output of error log file occurs every time I boot the PC.

Is the PC dead, are the other partitions dead too ? what is going on suddenly 
wiht DEBIAN SQUEEZE TESTING?
No one really knows... 

So I thought, hell, my data are crashed and disks are dead... 
so after a testdisk on all partition it seems that data and disks are alive

so ... another try... maybe the file system is corrupted due to the power cut?? 
OK
so ?
hwo to do?

I type (under thsi recovery console of my linux saying to fix manually):
cd /root
touch /forcefsck
reboot

then it fixes the disks... takes long man...

took so long and I liked so much , that I repeated teh operation x3 times.

Well it resulted that no changed occured and this error : "fsck died with exit 
status 6"
is tremendously always there saying to me to fix manually.... 
so what s doin glinux or fsck or going on? 

So I do not know. I google hard and found no solutions.

So another idea? 

Well I came up to change the /etc/fstab

I put this content:
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda1 during installation
UUID=b048a4e6-7397-4c03-ae9c-56945fd46618 /               ext4    
errors=remount-ro 0       1
# /backups was on /dev/sdb1 during installation
#UUID=6b8f7a91-55a2-48b3-9840-840950b8af16 /backups        jfs     defaults     
   0       2
# /home was on /dev/sde1 during installation
UUID=31c5d001-07a4-4e3f-90d3-bbc82a1afc88 /home           jfs     defaults      
  0       2
# /toll was on /dev/sda3 during installation
#UUID=700ae18e-c633-4542-8156-5bb5d4d379d5 /toll       jfs     defaults        
0       2
# swap was on /dev/sda2 during installation
UUID=b5d2c56c-3902-449b-af80-86754cdd45ce none            swap    sw            
  0       0
#/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
###/dev/sdf1       /mnt/sdf1       vfat    
user,rw,auto,umask=0000,uid=1000,gid=1000  0    2

I save it.

I reboot, and ... oh wonder ... 
the PC pass the fsck check! it did a long checking of the / 
and I get into the tty1 !! The PC booted successfully.


So  I type mount to tell you what is running on on this debian testing squeeze, 
that hadnt fsck problem.
# mount
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/sde1 on /home type jfs (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)

So now, I do not understand further what is going on with LINUX.

I wait for your experienced idea, to let me navigate to further fixing of this 
box.

What should I try? Can I restore my /etc/fstab like it was before the power 
cut? 
What happened really?  what is going on? 
I never experience such behavior in debian stable any time in the previous 
years of use.

I hope someone can help, it woudl be great. I read that auto adn noauto can be 
buggy to fsck at boot, if used into /etc/fstab.
No idea.

Hoping for a dreamt solution.

All the best guys and developers !

For further information please do not hesitate to contact me, I will post the 
logs or output you would wish.

Best regards / and thank you for developing for all for making everyday LINUX 
better.

Have a nice day,

Yellow



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages util-linux depends on:
ii  dpkg                    1.15.7.2         Debian package management system
ii  initscripts             2.88dsf-7        scripts for initializing and shutt
ii  install-info            4.13a.dfsg.1-5   Manage installed documentation in 
ii  libblkid1               2.16.2-0         block device id library
ii  libc6                   2.11.1-3         Embedded GNU C Library: Shared lib
ii  libncurses5             5.7+20100313-2   shared libraries for terminal hand
ii  libselinux1             2.0.94-1         SELinux runtime shared libraries
ii  libuuid1                2.16.2-0         Universally Unique ID library
ii  lsb-base                3.2-23.1         Linux Standard Base 3.2 init scrip
ii  tzdata                  2010j-1          time zone and daylight-saving time
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

util-linux recommends no packages.

Versions of packages util-linux suggests:
ii  console-tools              1:0.2.3dbs-69 Linux console and font utilities
ii  dosfstools                 3.0.9-1       utilities for making and checking 
pn  util-linux-locales         <none>        (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to