I have just installed slack 10 and after running dmesg i get this message

FAT: bogus logical sector size 0
UMSDOS: msdos_read_super failed, mount aborted.
FAT: bogus logical sector size 0
FAT: bogus logical sector size 0

I never got this message when i was using 9.1

Anyone has any ideas about this? I have seen that some other people have similiar problems but till now haven't found any good explanation about it or how to fix it.

Please post the contents of /etc/fstab and the results of 'fdisk -l' (lower-case L for list).

Is this error triggered by a zip disk or a fat partition on your hard drive?

I've noticed this error when trying to access access improperly-formatted zip disks. Not sure if it popped up in dmesg, but whenever I tried to mount it, I could swear that was the same error.

Garry

I get that same message on my old pentium 100mhz. It doesn't have any FAT partitions. I don't get the message on my main box, which is a dual boot with Windows. I figured that it must have something to do with not having a fat partition. I've never had any problems besides the error message, though.

I get the same thing on boot, Ive always just ignored it. I had it with 9.1 also.

I get the same msg on Slack 9.1, but never noticed any problems...............I don't have any FAT partitions and recently removed my Zip drive and replaced it with new hdd and noticed no change in the boot msg...........


PS: Found this bit of info which gives an explanation.......UMSDOS and FAT error message at boot...........

What's happening is this: Since umsdosfs support is compiled into the kernel(not as a module), when the kernel finishes loading and goes to look for the / mount it first checks for a FAT partition with a folder called linux, with a file called --linux-.--- . If it finds that it will try to mount the file system inside that folder.
Since your system is not umsdos, then it reports the failure to find a 'pseudo-root'.

Also, if you try to mount a partition without specifying the fs type, linux will go through the list of filesystems in /proc/filesystems, and try to mount using each fs type until it is successful. VFAT comes before the linux fs types, so you may get similar errors if you mount without giving fs type or have an 'auto' entry in fs type in fstab.
You can compile a new kernel with no umsdos support (or compiled as a module) to eliminate the 'error' in the kernel messages.

the word 'error' in the kernel messages shouldn't always be taken too seriously.
it's just that the kernel is not too verbose. if the system boots succesfully, most errors can be safely ignored.