LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices


Reply
  Search this Thread
Old 02-23-2016, 03:39 PM   #1
Uruz42
LQ Newbie
 
Registered: Aug 2015
Posts: 17

Rep: Reputation: Disabled
cannot mount usb stick, unknown filesystem 'vfat'


Hey folks,

I am trying to mount a usb stick with a fat32 fs (formatted in windows). When I try to do that however I get the message:
Code:
# mount /dev/sdj1 /mnt/usb
mount: unknown filesystem type 'vfat'
The same happened when I use:
Code:
mount --verbose -t vfat /dev/sdj1 /mnt/usb
mount: unknown filesystem type 'vfat'
dmesg | tail outputs:
Code:
[ 2340.904402] fat: Unknown symbol __bread_gfp (err 0)
[ 2340.904447] fat: Unknown symbol __getblk_gfp (err 0)
A search gave several results stating I should reboot, but that did not help, unfortunately.

The output from fdisk -l is:
Code:
Disk /dev/sdj: 14.7 GiB, 15728640000 bytes, 30720000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x04a1febf

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdj1  *     2048 30719999 30717952 14.7G  c W95 FAT32 (LBA)
 
Old 02-23-2016, 06:03 PM   #2
aus9
LQ 5k Club
 
Registered: Oct 2003
Location: Australia
Distribution: Devuan
Posts: 5,476

Rep: Reputation: Disabled
Hi

the request to reboot refers mainly to people who just installed another kernel. I assume you have not installed another kernel.

Can you check that module for vfat exists first or is built in by looking at your current kernel config found in /boot/config<kernel-version>
and mine is
# DOS/FAT/NT Filesystems

CONFIG_VFAT_FS=y

2) if yours is a m then try running a modprobe with root powers first
Code:
modprobe vfat
3) what is your distro and there appears to be a bug related to Debian kernels
https://labs.riseup.net/code/issues/10928
 
Old 02-24-2016, 01:38 AM   #3
Uruz42
LQ Newbie
 
Registered: Aug 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
Hey,
Thanks for the reply. I indeed have CONFIG_VFAT_FS=m. So I tried running modprobe:
Code:
# modprobe vfat
modprobe: ERROR: could not insert 'vfat': Unknown symbol in module, or unknown parameter (see dmesg)
And dmesg gives once again:
Code:
[  861.378677] fat: Unknown symbol __bread_gfp (err 0)
[  861.378721] fat: Unknown symbol __getblk_gfp (err 0)
3.
I'm running Debian 8.3

Last edited by Uruz42; 02-24-2016 at 07:42 AM.
 
Old 02-24-2016, 07:34 AM   #4
oldtechaa
Member
 
Registered: May 2015
Location: US
Distribution: Fedora
Posts: 364

Rep: Reputation: 83
This is interesting because I once couldn't mount a FAT stick on Debian either. I might have to re-test it sometime.
 
Old 02-24-2016, 07:42 AM   #5
Uruz42
LQ Newbie
 
Registered: Aug 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
Do you remember how you fixed it?

Also it might be worth noting that I for a fact have been able to mount usb's before on this install.
 
Old 02-24-2016, 08:06 AM   #6
oldtechaa
Member
 
Registered: May 2015
Location: US
Distribution: Fedora
Posts: 364

Rep: Reputation: 83
I don't know if I did fix it. After all, who wants compatibility with Microsoft technologies anyway?

What kernels do you have installed, though? It probably happened after a kernel upgrade.
 
Old 02-24-2016, 08:29 AM   #7
Uruz42
LQ Newbie
 
Registered: Aug 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by oldtechaa View Post
I don't know if I did fix it. After all, who wants compatibility with Microsoft technologies anyway?
Actually I do, even though in an ideal world, everyone uses Linux, Windows has several advantages due the shear amount of people running it.

Quote:
Originally Posted by oldtechaa View Post
What kernels do you have installed, though? It probably happened after a kernel upgrade.
Linux debian-name 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux

Don't recall upgrading recently, but then again, last time I mounted a usb has been some time as well.

Last edited by Uruz42; 02-25-2016 at 05:49 AM.
 
Old 02-24-2016, 09:45 AM   #8
oldtechaa
Member
 
Registered: May 2015
Location: US
Distribution: Fedora
Posts: 364

Rep: Reputation: 83
Is that your only kernel? If it is Jessie, I would think so, if you migrated from Wheezy, I wouldn't be sure of it.
 
Old 02-24-2016, 09:51 AM   #9
Uruz42
LQ Newbie
 
Registered: Aug 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
As far as I can see it's indeed my only kernel. I did do a fresh install around half a year ago iirc. So I'd presume I indeed started with Jessie
 
Old 02-24-2016, 09:59 AM   #10
oldtechaa
Member
 
Registered: May 2015
Location: US
Distribution: Fedora
Posts: 364

Rep: Reputation: 83
I just tested it, and a newly created (under Linux) vfat partition on my USB stick is working fine. This is my only kernel upgrade I've done on this install:
linux-image-3.16.0-4-amd64:amd64 (3.16.7-ckt11-1+deb8u3, 3.16.7-ckt20-1+deb8u3)
That was on the 25th of January I upgraded that. Have you done an upgrade since then and not rebooted?
 
Old 02-24-2016, 10:07 AM   #11
Uruz42
LQ Newbie
 
Registered: Aug 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
Nope, rebooted before posting here, and a fresh reboot this morning. Not helping.
 
Old 02-24-2016, 05:40 PM   #12
aus9
LQ 5k Club
 
Registered: Oct 2003
Location: Australia
Distribution: Devuan
Posts: 5,476

Rep: Reputation: Disabled
hmm I wonder if this old bug has relevance?
https://bugs.debian.org/cgi-bin/bugr...cgi?bug=708965

Basically it claims that the bootloader has not truly updated and booted the new kernel....ignoring the fact you appear to claim you have only one?
altho you said only kernel upgrade.

one way to check would be just run a kernel version command
Code:
uname -r
secondly the poster did a manual bootloader command assuming grub with root powers
Code:
update-grub
grub-install /dev/sda
changing sda to what ever mbr you are using

altho I am reluctant to suggest re-embed grub in mbr by doing it we at least eliminate any bootloader issues.

Let me know your thoughts if this does not appeal to you

oh found another entry
http://unix.stackexchange.com/questi...-obvious-fixes

here the poster thought he was using grub but was using lilo so update kernel was not going thru bootloader process.

There appears to be a trend here?

Last edited by aus9; 02-24-2016 at 05:45 PM.
 
Old 02-24-2016, 05:58 PM   #13
Uruz42
LQ Newbie
 
Registered: Aug 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
As far as the old bug goes, the dmesg log seems to be different.
uname gave the following result, so I'm still guissing just 1 kernel, as expected.
Code:
# uname -r
3.16.0-4-amd64
I also updated grub as you suggested, and after doing that, which gave me some errors regarding the null disk, although I dont think that's relevant:
Code:
# grub-install /dev/sdi
Installing for i386-pc platform.
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may be missing fr                                                                                                om core image..
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may be missing fr                                                                                                om core image..
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may be missing fr                                                                                                om core image..
grub-install: warning: Couldn't find physical volume `(null)'. Some modules may be missing fr                                                                                                om core image..
I couldn't get the mount command to work. Still the same error and dmseg

EDIT:
The trend indeed seems to be kernel issues. Regarding bootloader, I'm fairly sure grub is being used, after all, that's what it sais on bootup at the boot selection. Also checked for errors or failed messages like the person in the post had, but I couldn't find any that I can imagine relating to this problem.
Not sure what the danger of re-embedding grub is, If it could help, i'm willing to try it though.

Last edited by Uruz42; 02-25-2016 at 01:45 AM.
 
Old 02-25-2016, 05:38 AM   #14
aus9
LQ 5k Club
 
Registered: Oct 2003
Location: Australia
Distribution: Devuan
Posts: 5,476

Rep: Reputation: Disabled
Quote:
grub-install /dev/sdi
Are we sure about this?

sdi means you have attempted to use a MBR of the ninth drive unless I am mistaken?
how many drives do you have....not partitions but actual drives available at boot up please

Code:
blkid
as root might help. Most people either dual boot with windows on first drive and Linux on second or linux on first drive
so I was expecting sda or sdb
 
Old 02-25-2016, 05:53 AM   #15
Uruz42
LQ Newbie
 
Registered: Aug 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
I do indeed have 9 drives:
-5 actual hard drives that form a raid6 data array
-4 usb drives that run in a raid1 config to run os. (planning to change this to actual drives somewhere in the future). although at the moment it seems like one of those 4 is out, will try to fix it when at home.
-the 1 usb drive im trying to mount. sdh at the moment

for some reason I decided it was a good idea to try and install grub on the usb trying to mount... so no I'm not sure about this. I do recall having some challenges installing grub in such a way that my 4 usb raid1 could boot even with only 1 usb present. So grub should be installed in all 4 I think. This construction however, does sound like the problem could be here.

the output from blkid is:
Code:
# blkid
/dev/sda1: UUID="cb730507-61ae-d11d-c780-40668a28886b" UUID_SUB="effa36ca-5d24-b16d-0843-9a6c2a00814a" LABEL="debian-names:2" TYPE="linux_raid_member" PARTUUID="b9611cfc-991c-4a9a-b335-676c7c9a6f2b"
/dev/md2: UUID="8d3bcd59-1962-488d-b156-a297527e5cf1" TYPE="ext4"
/dev/sdf2: UUID="b5818955-0715-d493-c502-6b5ada28a2d0" UUID_SUB="9403b43c-b47a-e09c-4f12-84881c11f6fe" LABEL="debian-names:3" TYPE="linux_raid_member" PARTUUID="dbd9772f-02"
/dev/sdf3: UUID="a16b3c36-1948-d4f6-8344-fc2cdade87f4" UUID_SUB="9022872d-d2d8-d358-87d6-be56cefbf31a" LABEL="debian-names:4" TYPE="linux_raid_member" PARTUUID="dbd9772f-03"
/dev/sdf5: LABEL="EFIBOOT" UUID="CCC0-18AE" TYPE="vfat" PARTUUID="dbd9772f-05"
/dev/sdb1: UUID="cb730507-61ae-d11d-c780-40668a28886b" UUID_SUB="0070d364-3af0-21bd-18fe-033f59c4dfcf" LABEL="debian-names:2" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="8b9de8bc-6822-488d-b542-4ae5c80e89bd"
/dev/sde1: UUID="cb730507-61ae-d11d-c780-40668a28886b" UUID_SUB="97d8524f-ae11-d5a0-6e89-ddf08c322f70" LABEL="debian-names:2" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="cce79554-49b1-418f-b27c-7e41e6e59163"
/dev/sdd1: UUID="cb730507-61ae-d11d-c780-40668a28886b" UUID_SUB="2ff18fdf-dee4-c496-ec7e-1347b6900c06" LABEL="debian-names:2" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="f7376ddc-9c8f-4480-a116-a73437768f70"
/dev/sdc1: UUID="cb730507-61ae-d11d-c780-40668a28886b" UUID_SUB="8f2380c6-e591-eea2-7ff0-0fe0b4a095e3" LABEL="debian-names:2" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="83e23a78-0f00-4f8c-ae43-49b18a747872"
/dev/md3: UUID="b2ff2de4-59bc-42ec-92e5-c8fc996d4068" TYPE="ext4"
/dev/sdh1: LABEL="16GB" UUID="FE04-9160" TYPE="vfat" PARTUUID="04a1febf-01"
/dev/sdi2: UUID="b5818955-0715-d493-c502-6b5ada28a2d0" UUID_SUB="b7a7eddc-bc24-0885-912d-e0659e60605a" LABEL="debian-names:3" TYPE="linux_raid_member" PARTUUID="62b7f816-02"
/dev/sdi3: UUID="a16b3c36-1948-d4f6-8344-fc2cdade87f4" UUID_SUB="0537a1f5-234c-dd04-809c-94157c4186db" LABEL="debian-names:4" TYPE="linux_raid_member" PARTUUID="62b7f816-03"
/dev/sdg2: UUID="b5818955-0715-d493-c502-6b5ada28a2d0" UUID_SUB="934994eb-0f02-413f-d564-f31099fea8f4" LABEL="debian-names:3" TYPE="linux_raid_member" PARTUUID="8bde4f03-02"
/dev/sdg3: UUID="a16b3c36-1948-d4f6-8344-fc2cdade87f4" UUID_SUB="eb0670d9-35da-ffbe-372d-a9faa6f3622a" LABEL="debian-names:4" TYPE="linux_raid_member" PARTUUID="8bde4f03-03"
/dev/sdg5: UUID="8C96-6C58" TYPE="vfat" PARTUUID="8bde4f03-05"
/dev/sdi5: PARTUUID="62b7f816-05"
EDIT:
I am starting to suspect that somehow the data raid might be screwing stuff up, especially as that raid is migrated from an earlier system and might indeed be cousing some sort of bootloader kernel conflict. Will try to disconnect the raid and see if it solves it later today.

Last edited by Uruz42; 02-25-2016 at 06:24 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
unknown vfat filesystem trever Linux - Newbie 5 07-21-2011 04:42 AM
[SOLVED] mount: unknown filesystem type 'vfat' zorro_kwh SUSE / openSUSE 1 04-27-2011 04:20 AM
mount does not detect a vfat filesystem in my usb stick ernesto_cgf Linux - Hardware 3 12-07-2005 07:19 AM
Can't boot XP, can only mount ntfs filesystem as vfat bsm80 Linux - Hardware 4 05-06-2005 05:56 PM
Can't mount Vfat or Msdos Filesystem!! RKris Linux - Software 6 06-19-2002 04:58 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 05:06 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration