fsck problems

perry · 07-30-2004, 05:32 AM

if you run fsck as root and get this message:

Code:

root@slackware:/mnt/maxtor# fsck /dev/sda1
fsck 1.35 (28-Feb-2004)
fsck: fsck.vfat: not found
fsck: Error 2 while executing fsck.vfat for /dev/sda1

what does this mean? is fsck.vfat a program that is suppose to be installed. seems like standard issue if you ask me. i'm running slackware 10 with all the trimmings.

anybody know what direction to point me in?

i got an external hard disk and it just failed on this huge 1/2 GB file copy and now it's giving me this error:

Code:

perry@slackware:/mnt/maxtor$ md test
mkdir: cannot create directory `test': Read-only file system

i don't want to go out to winblows only to run chkdsk again, there's got to be a better way...

here's the fstab entry in case you are wondering:

Code:

/dev/sda1        /mnt/maxtor      vfat        noauto,users     1   0

interestingly, running whereis yields these results:

Code:

root@slackware:/mnt/maxtor# whereis fsck.vfat
fsck: /sbin/fsck /sbin/fsck.cramfs /sbin/fsck.umsdos /sbin/fsck.reiserfs 
/sbin/fsck.jfs /sbin/fsck.xfs /sbin/fsck.ext2 /sbin/fsck.ext3 /sbin/fsck.hpfs 
/sbin/fsck.minix /sbin/fsck.msdos /usr/man/man8/fsck.8.gz 
/usr/share/man/man8/fsck.8.gz

thanks much

- perry

trickykid · 07-30-2004, 06:03 AM

Dude... Linux can't fsck vfat or FAT filesystems. Turn your mount to look like this so fsck won't ever check this partition:

Code:

/dev/sda1        /mnt/maxtor      vfat        noauto,users     0   0

arnold · 07-30-2004, 07:57 AM

I have mandrake, redhat and fedora installed. They all include
/sbin/fsck.vfat

man sck.vfat begins:
NAME
dosfsck - check and repair MS-DOS file systems

SYNOPSIS
dosfsck [-aAflrtvVwy] [-d path -d ...] [-u path -u ...] device

DESCRIPTION
dosfsck verifies the consistency of MS-DOS file systems and optionally tries to repair them.

On some distros fsck.vfat is linked to dosfsckd

You probably have not installed "dosfstools".

perry · 07-31-2004, 11:05 PM

Quote:

Originally posted by trickykid
Dude... Linux can't fsck vfat or FAT filesystems. Turn your mount to look like this so fsck won't ever check this partition:

Code:

/dev/sda1 /mnt/maxtor vfat noauto,users 0 0

tk,

thanks for getting back to me and you are correct however dosfsck does exist on my machine, i guess they kept it unlinked for some reason

in the meantime, i'm going to give it whirl and i'll be soooo thrilled if it fixes it... ofcourse, if it nails it instead i'll cry a bucket of tears....

- perry

perry · 07-31-2004, 11:22 PM

Quote:

Originally posted by arnold
I have mandrake, redhat and fedora installed. They all include
/sbin/fsck.vfat

man sck.vfat begins:
NAME
dosfsck - check and repair MS-DOS file systems

SYNOPSIS
dosfsck [-aAflrtvVwy] [-d path -d ...] [-u path -u ...] device

DESCRIPTION
dosfsck verifies the consistency of MS-DOS file systems and optionally tries to repair them.

On some distros fsck.vfat is linked to dosfsckd

You probably have not installed "dosfstools".

wow, a simple dosfsck /dev/sda1 seems to have solved all my problems....

i did a test by creating a couple directorys, the first md paused for about 10 seconds, the 2nd went in just fine and then ls came back immediately. not only that....! but the error it detected matched precisely what i was doing when things went bad.....

Code:

root@slackware:/etc/rc.d# cat /etc/fstab
/dev/hda6        swap             swap        defaults         0   0
/dev/hda5        /                reiserfs    defaults         1   1
/dev/hda10       /opt             reiserfs    defaults         1   2
/dev/hda11       /var/www         ext2        defaults         1   2
/dev/hda7        /usr             reiserfs    defaults         1   2
/dev/hda8        /tmp             ext2        defaults         1   2
/dev/hda9        /home            ext2        defaults         1   2
/dev/hda2        /mnt/windows     vfat        noauto,users     1   0
/dev/sda1        /mnt/maxtor      vfat        noauto,users     1   0
/dev/sdb1        /mnt/flashcard   vfat        noauto,users     1   0
/dev/cdrom       /mnt/cdrom       iso9660     users,noauto,ro  0   0
/dev/sdc1        /mnt/backpack    iso9660     users,noauto,ro  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
root@slackware:/etc/rc.d# man dosfsck
root@slackware:/etc/rc.d# dosfsck /dev/sda1
dosfsck 2.10, 22 Sep 2003, FAT32, LFN
/Starcraft/install.exe
  Contains a free cluster (682368). Assuming EOF.
/Starcraft/install.exe
  File size is 346841088 bytes, cluster chain length is 331038720 bytes.
  Truncating file to 331038720 bytes.
Reclaimed 148159 unused clusters (606859264 bytes).
Free cluster summary wrong (9234566 vs. really 9220273)
1) Correct
2) Don't correct
? 1
Leaving file system unchanged.
/dev/sda1: 8164 files, 534207/9754480 clusters
root@slackware:/etc/rc.d#

my only question now is how to correct the problem from occuring in the first place, the install.exe is actually a 1/2 gig in size so something must have choked....

but thats another problem....

but isn't sooooo cool to have the source code for everything, to fix it yourself and to have a board like this where you ask a simple question and someone, somewhere has the answer...

this is how it was meant to be....

you know, perhaps fixing computers will be the wave of the future as far as world peace is concerned, who knows....

cheers

- perry