Re: [gentoo-user] son of can't mount vfat part.
--- Benno Schulenberg [EMAIL PROTECTED] wrote: maxim wexler wrote: I created a fat32, ID 'b' partition w/fdisk. Formatted w/ mkdosfs -F 32 Please show the output of cfdisk or parted. Using /dev/hda (parted) print Disk geometry for /dev/hda: 0kB - 3229MB Disk label type: msdos Number Start End SizeType File system Flags 1 32kB91MB91MBprimary ext2 boot 2 91MB3229MB 3138MB primary fat32 (parted) But can't be mounted in gentoo: unknown filesytem type 'vfat'. In fact the same error occurs w/ -t vfat, -t auto or no specified fs at all. Then you're still missing something in the kernel. Turn on anything vaguely fattish and dossish in the kernel config. Also maybe try to mount it with -t fat32. And please paste the exact command and output given. [EMAIL PROTECTED] ~ $ grep FAT /usr/src/linux/.config # CONFIG_X86_MCE_NONFATAL is not set # DOS/FAT/NT Filesystems CONFIG_FAT_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET=iso8859-1 reflex pindar # mount -t fat32 /dev/hda2 /mnt/hda2 mount: unknown filesystem type 'fat32' reflex pindar # mount -t vfat /dev/hda2 /mnt/hda2 mount: unknown filesystem type 'vfat' reflex pindar # mount -t auto /dev/hda2 /mnt/hda2 mount: unknown filesystem type 'vfat' reflex pindar # mount /dev/hda2 /mnt/hda2 mount: unknown filesystem type 'vfat' Also try creating a dos file system on a dummy file and mounting it on a loop device and see if that works. And try creating and using a fat16 file system instead. ...to be cont'd Benno -- gentoo-user@gentoo.org mailing list __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] son of can't mount vfat part.
maxim wexler schreef: [EMAIL PROTECTED] ~ $ grep FAT /usr/src/linux/.config # CONFIG_X86_MCE_NONFATAL is not set # DOS/FAT/NT Filesystems CONFIG_FAT_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET=iso8859-1 reflex pindar # mount -t fat32 /dev/hda2 /mnt/hda2 mount: unknown filesystem type 'fat32' reflex pindar # mount -t vfat /dev/hda2 /mnt/hda2 mount: unknown filesystem type 'vfat' reflex pindar # mount -t auto /dev/hda2 /mnt/hda2 mount: unknown filesystem type 'vfat' reflex pindar # mount /dev/hda2 /mnt/hda2 mount: unknown filesystem type 'vfat' Now, what I notice about this is the unknown file system. Since you have the vfat module compiled into the kernel, it seems to me that this can only mean that the module is not loaded (as it might not be if a FAT32 filesystem did not need to be mounted at boot, because it was not detected, and/or the partition is not set to autoload at boot via /etc/fstab, and/or the module is not set to autoload at boot via /etc/modules.autoload.d/kernel-2.*). What happens if you modprobe vfat before attempting to mount? If this works, at least you know what the problem is (and that it's not that the filesystem just *says* it's FAT32 but actually isn't, which is another possible cause of such an issue-- I've had that happen to me, just not with fat32). If it's just that the module needs to be loaded, then put it in /etc/modules.autoload.d/kernel-2.*, so you don't have to worry about it anymore. If you get an error when attempting to modprobe, or after modprobing mounting still returns an error, then we've at least got more information (in the case of an error), or eliminated one possible cause (if mounting still fails after successfully modprobing the module). HTH, Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] son of can't mount vfat part.
On 2005-12-18 18:18:34 +0100 (Sun, Dec), Holly Bostick wrote: [EMAIL PROTECTED] ~ $ grep FAT /usr/src/linux/.config # CONFIG_X86_MCE_NONFATAL is not set # DOS/FAT/NT Filesystems CONFIG_FAT_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET=iso8859-1 Since you have the vfat module compiled into the kernel, it seems to me that this can only mean that the module is not loaded (as it might not be if a FAT32 filesystem did not need to be mounted at boot, because it was not detected, and/or the partition is not set to autoload at boot via /etc/fstab, and/or the module is not set to autoload at boot via /etc/modules.autoload.d/kernel-2.*). If you get an error when attempting to modprobe, or after modprobing mounting still returns an error, then we've at least got more information (in the case of an error), or eliminated one possible cause (if mounting still fails after successfully modprobing the module). As I can see the VFAT is compiled in the kernel, not as a module. Compare: [EMAIL PROTECTED] ~ $ zcat /proc/config.gz | grep -i fat CONFIG_X86_MCE_NONFATAL=y # DOS/FAT/NT Filesystems CONFIG_FAT_FS=m CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=852 CONFIG_FAT_DEFAULT_IOCHARSET=iso8859-2 I wonder what is in your /proc/filesystems and /etc/filesystems ? Could you post their contents here? And are you sure that /usr/src/linux/.config belongs to the kernel you actualy run? It would not hurt to modprobe, anyway. ;-) -- No virus found in this outgoing message. Checked by grep -i virus $MESSAGE pgpzvgBYo7LCX.pgp Description: PGP signature
Re: [gentoo-user] son of can't mount vfat part.
--- Holly Bostick [EMAIL PROTECTED] wrote: maxim wexler schreef: [EMAIL PROTECTED] ~ $ grep FAT /usr/src/linux/.config # CONFIG_X86_MCE_NONFATAL is not set # DOS/FAT/NT Filesystems CONFIG_FAT_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET=iso8859-1 reflex pindar # mount -t fat32 /dev/hda2 /mnt/hda2 mount: unknown filesystem type 'fat32' reflex pindar # mount -t vfat /dev/hda2 /mnt/hda2 mount: unknown filesystem type 'vfat' reflex pindar # mount -t auto /dev/hda2 /mnt/hda2 mount: unknown filesystem type 'vfat' reflex pindar # mount /dev/hda2 /mnt/hda2 mount: unknown filesystem type 'vfat' Now, what I notice about this is the unknown file system. Since you have the vfat module compiled into the kernel, it seems to me that this can only mean that the module is not loaded (as it might not be if a FAT32 filesystem did not need to be mounted at boot, because it was not detected, and/or the partition is not set to autoload at boot via /etc/fstab, and/or the module is not set to autoload at boot via /etc/modules.autoload.d/kernel-2.*). What happens if you modprobe vfat before attempting to mount? Arrrgghh! Why do I have to keep telling people it's NOT a module? So naturally modprobing is useless! As for fstab, if the dir can't be mounted the console starts shooting off red exclamation marks before login is even reached. If this works, at least you know what the problem is (and that it's not that the filesystem just *says* it's FAT32 but actually isn't, which is another possible cause of such an issue-- I've had that happen to me, just not with fat32). If it's just that the module needs to be loaded, then put it in /etc/modules.autoload.d/kernel-2.*, so you don't have to worry about it anymore. If you get an error when attempting to modprobe, or after modprobing mounting still returns an error, then we've at least got more information (in the case of an error), or eliminated one possible cause (if mounting still fails after successfully modprobing the module). blecch! HTH, Holly -- gentoo-user@gentoo.org mailing list __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] son of can't mount vfat part.
--- Mariusz Pêkala [EMAIL PROTECTED] wrote: On 2005-12-18 18:18:34 +0100 (Sun, Dec), Holly Bostick wrote: [EMAIL PROTECTED] ~ $ grep FAT /usr/src/linux/.config # CONFIG_X86_MCE_NONFATAL is not set # DOS/FAT/NT Filesystems CONFIG_FAT_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET=iso8859-1 Since you have the vfat module compiled into the kernel, it seems to me that this can only mean that the module is not loaded (as it might not be if a FAT32 filesystem did not need to be mounted at boot, because it was not detected, and/or the partition is not set to autoload at boot via /etc/fstab, and/or the module is not set to autoload at boot via /etc/modules.autoload.d/kernel-2.*). If you get an error when attempting to modprobe, or after modprobing mounting still returns an error, then we've at least got more information (in the case of an error), or eliminated one possible cause (if mounting still fails after successfully modprobing the module). As I can see the VFAT is compiled in the kernel, not as a module. Compare: [EMAIL PROTECTED] ~ $ zcat /proc/config.gz | grep -i fat CONFIG_X86_MCE_NONFATAL=y # DOS/FAT/NT Filesystems CONFIG_FAT_FS=m CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=852 CONFIG_FAT_DEFAULT_IOCHARSET=iso8859-2 I wonder what is in your /proc/filesystems and /etc/filesystems ? Could you post their contents here? reflex pindar # cat /proc/filesystems nodev sysfs nodev rootfs nodev bdev nodev proc nodev sockfs nodev debugfs nodev pipefs nodev futexfs nodev tmpfs nodev inotifyfs nodev eventpollfs nodev devpts reiserfs ext2 nodev ramfs iso9660 ntfs nodev mqueue nodev usbfs hmm, no vfat reflex pindar # cat /etc/filesystems # /etc/filesystems # # This file defines the filesystems search order used by a # 'mount -t auto' command. # # Uncomment the following line if your modular kernel has vfat # support and you want mount to try vfat. #vfat aha! Well, I removed the comment but nothing changed. I'll try etc-update...nope oh, wait, it says to use -t auto...nope. OK, that's all I got. And are you sure that /usr/src/linux/.config belongs to the kernel you actualy run? no alternatives It would not hurt to modprobe, anyway. ;-) FATAL: Module vfat not found. naturally -- No virus found in this outgoing message. Checked by grep -i virus $MESSAGE __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] son of can't mount vfat part.
maxim wexler wrote: --- Mariusz Pêkala [EMAIL PROTECTED] wrote: On 2005-12-18 18:18:34 +0100 (Sun, Dec), Holly Bostick wrote: [EMAIL PROTECTED] ~ $ grep FAT /usr/src/linux/.config # CONFIG_X86_MCE_NONFATAL is not set # DOS/FAT/NT Filesystems CONFIG_FAT_FS=y CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET=iso8859-1 Since you have the vfat module compiled into the kernel, it seems to me that this can only mean that the module is not loaded (as it might not be if a FAT32 filesystem did not need to be mounted at boot, because it was not detected, and/or the partition is not set to autoload at boot via /etc/fstab, and/or the module is not set to autoload at boot via /etc/modules.autoload.d/kernel-2.*). If you get an error when attempting to modprobe, or after modprobing mounting still returns an error, then we've at least got more information (in the case of an error), or eliminated one possible cause (if mounting still fails after successfully modprobing the module). As I can see the VFAT is compiled in the kernel, not as a module. Compare: [EMAIL PROTECTED] ~ $ zcat /proc/config.gz | grep -i fat CONFIG_X86_MCE_NONFATAL=y # DOS/FAT/NT Filesystems CONFIG_FAT_FS=m CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=852 CONFIG_FAT_DEFAULT_IOCHARSET=iso8859-2 I wonder what is in your /proc/filesystems and /etc/filesystems ? Could you post their contents here? reflex pindar # cat /proc/filesystems nodev sysfs nodev rootfs nodev bdev nodev proc nodev sockfs nodev debugfs nodev pipefs nodev futexfs nodev tmpfs nodev inotifyfs nodev eventpollfs nodev devpts reiserfs ext2 nodev ramfs iso9660 ntfs nodev mqueue nodev usbfs hmm, no vfat reflex pindar # cat /etc/filesystems # /etc/filesystems # # This file defines the filesystems search order used by a # 'mount -t auto' command. # # Uncomment the following line if your modular kernel has vfat # support and you want mount to try vfat. #vfat aha! Well, I removed the comment but nothing changed. I'll try etc-update...nope oh, wait, it says to use -t auto...nope. OK, that's all I got. And are you sure that /usr/src/linux/.config belongs to the kernel you actualy run? no alternatives It would not hurt to modprobe, anyway. ;-) FATAL: Module vfat not found. naturally -- No virus found in this outgoing message. Checked by grep -i virus $MESSAGE OK. I haven't followed this thread letter by letter but noticed something that I ran into after I did my gcc upgrade a bit ago. I upgraded my kernel but it did NOT make my modules. I went back and did a make modules make modules_install and they were there then. May be worth a try since you are using modules for this. Me, I compile everything but my temp sensors *in* the kernel. Another command that may help shead some light: [EMAIL PROTECTED] / # modprobe -l /lib/modules/2.6.14-gentoo-r2/kernel/drivers/hwmon/w83627hf.ko /lib/modules/2.6.14-gentoo-r2/kernel/drivers/hwmon/hwmon-vid.ko /lib/modules/2.6.14-gentoo-r2/kernel/drivers/i2c/busses/i2c-isa.ko /lib/modules/2.6.14-gentoo-r2/video/nvidia.ko [EMAIL PROTECTED] / # It lists what is available even if it is not loaded up yet. Dale :-) -- To err is human, I'm most certainly human. I have four rigs: 1: Home built; Abit NF7 ver 2.0 w/ AMD 2500+ CPU, 1GB of ram and right now two 80GB hard drives. 2: Home built; Iwill KK266-R w/ AMD 1GHz CPU, 256MBs of ram and a 4GB drive. 3: Home built; Gigabyte GA-71XE4 w/ 800MHz CPU, 128MBs of ram and a 2.5GB drive. 4: Compaq Proliant 6000 Server w/ Quad 200MHz CPUs, 128MBs of ram and a 4.3GB SCSI drive. All run Gentoo Linux, all run folding. #1 is my desktop, 2, 3, and 4 are set up as servers. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] son of can't mount vfat part.
maxim wexler schreef: --- Mariusz Pêkala [EMAIL PROTECTED] wrote: It would not hurt to modprobe, anyway. ;-) FATAL: Module vfat not found. naturally Maybe it would be worthwhile to recompile your kernel with vfat *as* a module, to see what the effect of modprobing and mounting thereafter would be. You might get more useful error messages, anyway. Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] son of can't mount vfat part[SOLVED].
crow eaten Mariusz was on the right track when he asked if it was right kernel. Turns out I had copied the kernel to /boot as itself(bzImage) and not as vmlinuz as per usual. So the older one was still active /crow eaten A stupid mistake, but ironically, one that greatly increased my linux lore :) --- Holly Bostick [EMAIL PROTECTED] wrote: maxim wexler schreef: --- Mariusz Pêkala [EMAIL PROTECTED] wrote: It would not hurt to modprobe, anyway. ;-) FATAL: Module vfat not found. naturally Maybe it would be worthwhile to recompile your kernel with vfat *as* a module, to see what the effect of modprobing and mounting thereafter would be. You might get more useful error messages, anyway. Holly -- gentoo-user@gentoo.org mailing list __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
[gentoo-user] son of can't mount vfat part.
Hello everybody, I'm recycling this former subject hoping it'll catch the eye of some worthy gentoo afficianado. I created a fat32, ID 'b' partition w/fdisk. Formatted w/ mkdosfs -F 32 Partition is visible from windows: Properties - FAT32 But can't be mounted in gentoo: unknown filesytem type 'vfat'. In fact the same error occurs w/ -t vfat, -t auto or no specified fs at all. Yes, ide-disk and vfat support is IN the kernel. mount has no problem w/ ext2, reiserfs or NTFS. There are no messages in the logs. -mw __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] son of can't mount vfat part.
maxim wexler wrote: I created a fat32, ID 'b' partition w/fdisk. Formatted w/ mkdosfs -F 32 Please show the output of cfdisk or parted. But can't be mounted in gentoo: unknown filesytem type 'vfat'. In fact the same error occurs w/ -t vfat, -t auto or no specified fs at all. Then you're still missing something in the kernel. Turn on anything vaguely fattish and dossish in the kernel config. Also maybe try to mount it with -t fat32. And please paste the exact command and output given. Also try creating a dos file system on a dummy file and mounting it on a loop device and see if that works. And try creating and using a fat16 file system instead. Benno -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] son of can't mount vfat part.
On Fri, 16 Dec 2005 22:04:50 +0100, Benno Schulenberg wrote: Then you're still missing something in the kernel. Turn on anything vaguely fattish and dossish in the kernel config. Also maybe try to mount it with -t fat32. And please paste the exact command and output given. You could also compile vfat and fat as modules, then the output from modprobe -v vfat may give some clues. -- Neil Bothwick Time is the best teacher; unfortunately it kills all its students. signature.asc Description: PGP signature
