Very clarifying. For the moment I am trying to get rid of one error message per day. They just make me nervous ;-). I am using kernel 2.4.4-4GB on a system with DrDos on hda1. For the solutions I would like to opt for the third because I would not like to go back to kernel 2.2 and on recompiling I have not yet bitten out my teeth ;-). Here is my fstab which for clarity I have put into columns. In reality the columns can not so easily detected ;-). As far as I can see it the relevant parts are noauto. Could you tell me what I should change? Man fstab did not help ;-(. /hda2 / ext2 defaults /dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0 /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 devpts /dev/pts devpts defaults 0 0 /dev/hdd1 /home auto defaults 1 2 /dev/fd0 /media/floppy auto noauto,user,sync 0 0 /dev/fd1 /media/floppy_b auto noauto,user,sync 0 0 proc /proc proc defaults 0 0 /dev/hdc1 /usr ext2 defaults 1 2 /dev/hda1 /windows/C msdos noauto,user 0 0 /dev/hda3 swap swap pri=42 0 0 /dev/sda4 /media/zip vfat noauto,users 0 0 Constant Brouerius van Nidek wrote:

Booting Suse 7.2 I get everytime and again a failed message

on the screen.

Looking for the reason I found that "fatfs bogus cluster <snip> How can I get rid of the failure message and of the bogus cluster size

1. Use a 2.2 kernel, or 2. Edit /usr/src/linux/fs/fat/inode.c and delete the line that prints the message, then recompile, or 3. Don't mount any vfat filesystems during boot.

(whatever that may be ;-))

You can safely ignore the message. The explanation (from inode .c) is given below. JDL * The DOS3 partition size limit is *not* 32M as many people think. <big snip>/ -- NTReader v0.35w(P)/Beta (Registered) in conjunction with Net-Tamer.