Mounting problem, mount: unknown filesystem type 'vfat'

Can't mount vfat partition.
Mounting problem, mount: unknown filesystem type 'vfat'

takavar wrote:sorry for the necromancy, but this is the top result on Google search with no answer.
I am going to close this thread because (a) the thread is more than two years old, abd (b) may or may not be related to your problem.
Please open a new thread detailing your problem.  Define what is "Solved" by rebooting.  Does the drive mount during a reboot?  Tell us how you are trying to mount the drive, and provide us your /etc/fstab.  You may want to share the the output of sudo fdisk -l /dev/sda
If you still think it relevant. provide a link back to this thread.
Thanks

Similar Messages

  • BTRFS not mounting (unknown filesystem type)

    Hi everyone,
    From a USB drive I have been trying to install Arch in the fashion given in https://wiki.archlinux.org/index.php/In … Btrfs_root, I have upgraded the system to the newest kernel (3.3.6) and using the instructions created 2 partitions on /dev/sda. One being for Grub to boot the system, and the other being the btrfs.
    I have been unable to mount the btrfs device (/dev/sda2), I keep getting the error
    [root@archiso ~]# mount -o defaults,noatime /dev/sda2 /mnt/btrfs-root
    mount: unknown filesystem type 'btrfs'
    mount, i.e. util-linux is the newest version 2.21.1
    any help is really appreciated

    Well, I think the problem is caused by the loaded kernel being unable to find it's modules (the btrfs module included) because they got uninstalled when you upgraded the kernel package. You could try manually loading the module with modprobe (using -f if you get errors regarding versions), but I can't recommend that course of action, nor can I guarantee that it will fix your mounting problem.

  • [SOLVED] mount: unknown filesystem type 'ext2'

    I probably have the most complicated first-time arch setup that you'll ever hear a n00b post.  XD
    I just finished setting up an encrypted arch box with a usb boot drive (it contains the key-file), but when I go to boot, the system reports the following:
    mount: unknown filesystem type 'ext2'
    Of all the things to break!  Ext2???!
    This is for the default boot mode, when boot into the fallback initramfs mode, the arch box boots up fine (although it takes 2 whole minutes).  I think that the issue is that I'm missing a module in my mkinitcpio.conf file.
    /etc/fstab file:
    UUID=1245ASDF / btrfs discard,autodefrag,compress=lzo,rw,relatime,ssd,space_cache 0 0
    UUID=2245ASDF /boot ext2 rw,noatime 0 2
    UUID=3245ASDF none swap defaults 0 0
    /etc/mkinitcpio.conf file:
    HOOKS="base btrfs udev autodetect modconf block encrypt lvm2 filesystems keyboard fsck"
    /etc/default/grub file:
    GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda:enc cryptkey=/dev/sdb2:ext2:/keyfile crypto=sha512:twofish-xts-plain64:512:0:"
    Last edited by a-jamesregan (2015-04-13 19:15:48)

    Wow, there was literally a note about the exact issue I was having on the wiki...
    https://wiki.archlinux.org/index.php/Mkinitcpio#MODULES
    Note: If using reiser4, it must be added to the modules list. Additionally, if you will be needing any file system during the boot process that is not live when you run mkinitcpio — for example, if your LUKS encryption key file is on an ext2 file system but no ext2 file systems are mounted when you run mkinitcpio — that file system module must also be added to the MODULES list. See Dm-crypt/System configuration#cryptkey for more details.
    PS: How do I mark an issue as solved?
    Last edited by a-jamesregan (2015-04-13 10:28:20)

  • Mount: unknown filesystem type 'LVM2_member'

    I recently did a pacman -Syu with some consequences.  I still had grub1 running and it was automatically upgraded to grub2, which is fine, but apparently grub-install was run on the mbr (I really think that was very inappropriate as that did break my system).  Anyhow, on to chroot, I update /etc/default/grub as I have an LVM on top of an encrypted root and add this:
    GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda5:VGarch"
    and this to mkinitcpio.conf:
    HOOKS="base udev autodetect fsck modconf block encrypt lvm2 filesystems"
    then update both:
    mkinitcpio -p linux
    grub-mkconfig -o /boot/grub/grub.conf
    and then update again for good measure while we're still in the chroot.  However, upon reboot I get the ominous error message:
    mount: unknown filesystem type ‘LVM2_member’
    EDIT: i moved fsck behind filesystems in hooks with no effect
    Last edited by thoth (2013-07-03 01:31:06)

    Post the entire kernel command line you are using (/proc/cmdline).
    Note that the upgrade to grub2 will not have automatically installed grub to disk. So if you have not installed grub to disk, you need to do that in order to configure it correctly.
    i.e. grub-install was *not* run on the mbr as part of the package upgrade.
    See /var/lib/pacman/local/grub-2.00.5043-2/install.
    But your config file for the old grub will have been moved to a .pacsave when that package was removed by pacman.
    Last edited by cfr (2013-07-07 23:28:53)

  • Unknown filesystem type crypto_LUKS

    Hi, I have spare space on my HD so I decided to experiment with encryption following this wiki:
    https://wiki.archlinux.org/index.php/dm-crypt_with_LUKS
    In summary:
    created boot (sda6) and root (sda7) partitions
    formatted boot as ext2 and root with passphrase and then with ext4
    installed the base system
    generated a new initramfs as explained in the wiki:
    MODULES="dm_mod ext4"
    HOOKS="base udev autodetect modconf block keymap encrypt filesystems keyboard fsck"
    added cryptdevice=<device>:<dmname> to kernel boot options:
    linux /vmlinuz-linux cryptdevice=/dev/sda7:cryptroot root=UUID=d3505fe1-4a29-4841-8e80-e953442d8d30 ro quiet
    restarted pc
    On boot it asks for passphrase, but after that it stops with an error regarding crypto_LUKS; here the complete message:
    A password is required to access the cryptroot volume:
    Enter passphrase for /dev/sda7
    fsck: fsck.crypto_LUKS: not founf
    fsck: error 2 while executing fsck.crypto_LUKS for /dev/sda7
    ERROR: fsck failed on '/dev/sda7'
    ********************* WARNING ***********************
    * The root device is not configured to be mounted *
    * read-write! It may be fsck'd again later. *
    mount: unknown filesystem type 'crypto_LUKS'
    You are now being dropped into an emergency shell.
    sh: can't access tty: job control turned off
    [rootfs /]#
    Here it is my fstab: http://pastebin.archlinux.fr/474004
    and lsblk output: http://pastebin.archlinux.fr/474005
    Any idea about the problem?
    Thanks for your time.

    There are two discrepencies between your kernel parameters and fstab:
    1) The kernel parameter UUID for real root differs from the UUID given for /dev/mapper/cryptroot in your fstab; if cryptroot is your real root partition, the UUIDs should be the same.
    2) Your fstab instructs the system to mount the root partition as read-write, while the kernel parameters specify read-only. (the kernel parameter should be read-write, which is what the warning in the output above is about).
    Change those and see if it helps.

  • Can't boot after system update: unknown filesystem type

    After running a system update, including updating the kernel, I can't boot to the new kernel.
    On booting, grub loads the kernel image, runs/loads udev, but then fails to mount the root partition with error:
    mount: unknown filesystem type 'ext4'
    I have tried reinstalling the 'linux' package via packman several times, also trying the --recursive argument to make sure all my dependencies were there, and after days of googling and tweaking my system, I'm at a loss.
    Thank goodness I happened to keep a spare kernel laying around in /boot.
    Thanks in advance.
    Last edited by jackrabbit (2012-03-22 23:25:28)

    The OP can read their partition initially though, it's only after udev that they can't.
    Also, try adding "rootfstype=ext4" to your grub kernel line. Is your /boot on a separate partition or part of your / partition?

  • Unknown filesystem type 'nilfs2'

    Got this error
    Module nilfs2 packed to initrd via MODULES='nilfs2' in /etc/mkinitcpio.conf.
    How can I fix this?

    A few questions....
    What exactly was the problem to begin with? 
    It was a bit unclear as to whether ot not you wanted or did not wnat nilfs2 in your initramfs, or if it was simply throwing some kind of error at you or what.
    What did you do to fix it? 
    Simply saying that you fixed it and then ending the thread discussion is not very cool.  It does nothing for the community, or future users in search of help.  So please indicate what you did to fix the problem.
    If it is solved, could you mark the thread as such?
    Edit the first post and prepend [Solved] to the title.  This will help those future seekers of help in finding threads that actually have solutions.  Though I would strongly encourage you to actually put a solution before doing this.  I guess I would also encourage you to clarify the question as well.

  • USB disks no longer mount, unknown filesystem

    Ran a routine weekly update on an arch box this morning, didn't think anything of it as usual. Until Thunar started spitting errors at me whenever I tried to mount a USB device. gvfs makes the devices appear in the left pane for one-click mounting... usually.
    A partition on the hard drive attached has started telling me I don't have permissions to mount it any more - never had issues before, I'm in storage so I don't see why.
    The other issue comes with a USB hard drive, and when trying to mount it as above, Thunar throws this at me:
    Error mounting /dev/sdb1 at /run/media/pip/HD-PVU2: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid-100,shortname=mixed,dmask=0077,utf8=1,showexec" "/dev/sdb1" "/run/media/pip/HD-PVU2"' exited with non-zero exit status 32: mount: unknown filesystem type 'vfat'
    Searching both pacman and AUR gave me no packages to do with vfat filesystems, and the wiki article "USB Storage Devices" provided no solutions at all.
    Using XFCE4 DE on 32-bit Arch. All packages have been updated to latest versions as of the time of this post.

    I probably experience the same kind of problem as you guys. I'm using udisksvm to mount USB drives and when I plug one, I get something like that:
    $ udisksvm
    Automounting for non optical devices enabled
    Added object : /org/freedesktop/UDisks2/drives/Intenso_Basic_10011100031138
    Added object : /org/freedesktop/UDisks2/block_devices/sdb
    Added object : /org/freedesktop/UDisks2/block_devices/sdb1
    Automounting /dev/sdb1...
    Mounting failed with error:
    GDBus.Error:org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to perform operation
    traydvm for /org/freedesktop/UDisks2/block_devices/sdb1 now running with pid : 2694
    /usr/lib/python2.7/site-packages/gi/types.py:47: Warning: g_variant_unref: assertion `value->ref_count > 0' failed
    return info.invoke(*args, **kwargs)
    $ udisksvm
    Automounting for non optical devices enabled
    Added object : /org/freedesktop/UDisks2/drives/Nokia_S60_359557013658840
    Added object : /org/freedesktop/UDisks2/block_devices/sdb
    Added interface on object : /org/freedesktop/UDisks2/block_devices/sdb
    Automounting /dev/sdb...
    Mounting failed with error:
    GDBus.Error:org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to perform operation
    traydvm for /org/freedesktop/UDisks2/block_devices/sdb now running with pid : 3025
    /usr/lib/python2.7/site-packages/gi/types.py:47: Warning: g_variant_unref: assertion `value->ref_count > 0' failed
    return info.invoke(*args, **kwargs)
    And the device is not mounted automatically. I have the packages dosfstools, ntfs-3g, systemd-sysvcompat installed (I use systemd). Mounting manually from console works well.

  • Unknown filesystem error [solved]

    I just updated arch and now when I try to mount my usb harddrive I get this error:
    # mount /mnt/usbdrive
    mount: unknown filesystem type 'vfat'
    Anyone know whats up?

    I met the same problem. 
    the key is that the kernel is updated ( e.g. from 2.23 -> 2.24 ).
    the  vfat kernel module reside in difference directory (/lib/modules/XXXx-2.24/)after update.
    but the kernel version in /proc  is the old one ,  until you reboot.
    if you don't reboot, when load the vfat module, the insmod will search the  /lib/modules/`uname -r` , which can found nothing to load.  well,  what you get is nothing but some string like
    # modprobe vfat
    FATAL: Could not load /lib/modules/2.6.23-ARCH/modules.dep: No such file or directory.
    so, you can understand why you are happy now.

  • [Solved]Wont boot after installing syslinux; unknown filesystem 'swap'

    After installing syslinux to be my boot manager I can no longer boot into Arch, I can however boot into Windows 7. When I try to boot into Arch I get the following error.
    Loading ../vmlinuz-linux......
    Loading ../initramfs-linux.img......ready.
    Probing EDD (edd=off to disable)... ok
    Decompressing Linux... Parsing ELF... done
    Booting the kernel.
    :: running early hook [udev]
    :: running hook [udev]
    :: Triggering uevents...
    :: performing fsck on '/dev/sda3'
    fsck: fsck.swap: not found
    fsck: error 2 while executing fsck.swap for /dev/sda3
    ERROR: fsck failed on 'dev/sda3'
    :: mounting '/dev/sda3' on real root
    mount: unknown filesystem type 'swap'
    You are now being dropped into an emergency shell.
    sh: can't access tty; job control turned off
    [rootfs /]#
    What's going on?
    Last edited by slughappy1 (2012-07-05 22:50:35)

    loafer wrote:Can you post your syslinux.cfg please.
    Surely
    # Config file for Syslinux -
    # /boot/syslinux/syslinux.cfg
    # Comboot modules:
    # * menu.c32 - provides a text menu
    # * vesamenu.c32 - provides a graphical menu
    # * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
    # * hdt.c32 - hardware detection tool
    # * reboot.c32 - reboots the system
    # * poweroff.com - shutdown the system
    # To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
    # If /usr and /boot are on the same file system, symlink the files instead
    # of copying them.
    # If you do not use a menu, a 'boot:' prompt will be shown and the system
    # will boot automatically after 5 seconds.
    # Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
    # The wiki provides further configuration examples
    DEFAULT arch
    PROMPT 1 # Set to 1 if you always want to display the boot: prompt
    TIMEOUT 50
    # You can create syslinux keymaps with the keytab-lilo tool
    #KBDMAP de.ktl
    # Menu Configuration
    # Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
    UI menu.c32
    #UI vesamenu.c32
    # Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
    MENU TITLE Arch Linux
    #MENU BACKGROUND splash.png
    MENU COLOR border 30;44 #40ffffff #a0000000 std
    MENU COLOR title 1;36;44 #9033ccff #a0000000 std
    MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
    MENU COLOR unsel 37;44 #50ffffff #a0000000 std
    MENU COLOR help 37;40 #c0ffffff #a0000000 std
    MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
    MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
    MENU COLOR msg07 37;40 #90ffffff #a0000000 std
    MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
    # boot sections follow
    # TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
    LABEL arch
    MENU LABEL Arch Linux
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sda3 ro
    INITRD ../initramfs-linux.img
    LABEL archfallback
    MENU LABEL Arch Linux Fallback
    LINUX ../vmlinuz-linux
    APPEND root=/dev/sda3 ro
    INITRD ../initramfs-linux-fallback.img
    LABEL windows
    MENU LABEL Windows7
    COM32 chain.c32
    APPEND hd0 1
    LABEL hdt
    MENU LABEL HDT (Hardware Detection Tool)
    COM32 hdt.c32
    LABEL reboot
    MENU LABEL Reboot
    COM32 reboot.c32
    LABEL off
    MENU LABEL Power Off
    COMBOOT poweroff.com

  • Problems mounting windows (vfat) partition

    Hi,
    Im having this problem, i mount the vfat partition because i have some mp3 overthere and i want to listen with XMMS while in Arch.
    Then, when i try to browse through XMMS file browser, i cant browse the vfat partition, the directories and files, all of them, appear at the right panel, like if they were all files, so i cant get "inside" the mp3 folder...
    any clues??
    mount command:
    mount -t vfat /dev/hda1 /mnt/win

    since you are using /mnt as your destination directory, you need to make sure that you have changed permissions for that so that a user can access it if you haven't already. I usually mount mine in my /home/user/ directory to save the hassle and because it is more convenient.
    here is some info on how to do it:
    /dev/hda1 /home/user/windows vfat user,uid=500,gid=500 0 0
    /dev/hdb1 /home/user/winmusic vfat user,uid=500,gid=500 0 0
    *this will allow you to write to those directories. All you need to do in either case is save this as your new fstab file.
    *to make sure your id's are 500, type "id" in your terminal, if they are something different than 500, substitute that number instead for both uid and gid.
    In Arch, the primary user is usually uid=1000 and gid=100

  • First boot fails - Filesystem type unknown, partition type 0x7

    Just done a straight forward install of Arch onto it's own disk drive, however there are two other drives present in the system.
    Grub menu comes up ok but then Arch errors with:
    root (hd2,0)
    Filesystem type unknown, partition type 0x7
    Error 17: Cannot mount selected partition
    Any suggestions?
    Thanks,

    hokasch wrote:
    What you still did not really tell us - how are you booting up? I.e. where is your first grub stage installed? How did you manage things with the debian install? Your problem is the root(x,x) line, not the kernel line. This line specifies the boot partition (grub's root/ where to find the kernel).
    Coming from the windows world where for years we have just relied on changing the boot order of drives in the BIOS to choose which MBR to boot from I simply assumed it was just as easy in the Linux world, this is obviously not the case.
    If you want to continue that way, just install grub to the MBR of each disk with a linux install and configure grub to use that drive as the first drive (e.g. set the root line to hd(0,0) if /boot is the first partition). IIRC, changing the boot order in the Bios will pull the selected drive to the beginning. That would fit your inital error (but you did not say how you booted into grub then...). You can double-check that behaviour by using the find commands in the grub shell (see my earlier post).
    Going with grub2/grub's root by uuid only really makes sense if you put grub2 on the MBR of a drive which is always installed and selected as primary in Bios (obviously, all other grub2 files must be on that drive too).
    Just done another completely clean install and noticed that even though I select 'Partition access method - uuid' it doesn't seem to actually work that way, at least checking menu.lst showed no signs of any uuids.  What is the point of having an install option if it is then ignored.
    This refers to your fstab, not the bootloader config.
    Sorry hokasch, it got a bit difficult to answer your earlier post as by the time I read it Debian had been trashed and I think I had redone the Arch install a few times by then as well.
    If I have understand you correctly what you are saying is that if I were to install arch on a drive which at install time is the only drive in the machine then root(x,x) would refer to hd0 in my case root (hd0,1) as I have an NTFS partition at the beginning of the drive.  Alternatively I could just edit grub's menu.lst afterwards.  That way as long as the drive is first in the BIOS boot order it will boot ok.  My mistake seems to have been trying to install the first grub stage to somewhere other than the MBR, I may have missunderstood the capabilities of partition identification by uuid.
    Ok lets go back to a single drive environment
    hd0,0 = NTFS boot partition
    hd0,1 = Arch /Boot - this contains grub & vmlinuz-linux
    hd0,2 = Arch swap
    hd0,3 = Arch /
    If I want to boot Windows I set hd0,0 as active/bootable, if I want to boot arch I set hd0,1 as active/bootable.  Actually not sure how to change the active partition to a linux one but come back to that later.  For the moment hd0,1 is the bootable partition.  This is the only drive in the system.  I have a by-uuid entry in menu.lst which allows me to boot if the other entries fail.  menu.lst looks like this:
    # (0) Arch Linux
    title Arch Linux
    root (hd0,1)
    kernel /vmlinuz-linux root=/dev/sda4 ro
    initrd /initramfs-linux.img
    Now I see part of the confusion, as you advised, the root (hdx,x) line actually refers to the 'grub root' / 'linux boot' not the 'linux root'.  And the other confusion is that the kernel line root= does not refer to the location of /vmlinuz-linux but to the actual linux root.  Now I think I understand that bit.
    Now to add another disk to the system.  Change drive order in BIOS so that arch disk is top of the boot order.
    Fails to boot: Unable to find root device /dev/sda4!
    Boot to knoppix to see the disk & partition layout:
    hd0,0 = NTFS
    hd0,1 = NTFS
    hd0,2 = NTFS
    hd0,3 = NTFS
    hd0,4 = NTFS
    hd0,4 = NTFS
    hd0,4 = NTFS
    hd1,0 = NTFS boot partition
    hd1,1 = Arch /Boot - this contains grub & vmlinuz-linux
    hd1,2 = Arch swap
    hd1,3 = Arch /
    So clearly /dev/sda4 is now an NTFS partition.
    If appears that grub & linux do not see disk drives in the same order as the BIOS boot order causing /dev/sda4 to point towards the wrong partition.
    Off at a bit of a tangent here but while I think of it is there a way of regenerating the menu.lst to search for instances of windows on NTFS partitions now that I have access to ntfs-3g.
    Thanks,
    Last edited by NickC_UK (2012-02-21 14:25:04)

  • NFS4: Problem mounting NFS mount onto a Solaris 10 Client

    Hi,
    I am having problems mounting NFS mount point from a Linux-Server onto a Solaris 10 Client.
    In the following
    =My server IP ..*.120
    =Client IP ..*.100
    Commands run on Client:
    ==================
    # mount -o vers=3 -F nfs 172.25.30.120:/scratch/pvfs2 /scratch/pvfs2
    nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive
    nfs mount: retrying: /scratch/pvfs2
    nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive
    nfs mount: 172.25.30.120: : RPC: Rpcbind failure - RPC: Unable to receive
    # mount -o vers=4 -F nfs 172.25.30.120:/scratch/pvfs2 /scratch/pvfs2
    nfs mount: 172.25.30.120:/scratch/pvfs2: No such file or directory
    # rpcinfo -p
    program vers proto port service
    100000 4 tcp 111 rpcbind
    100000 3 tcp 111 rpcbind
    100000 2 tcp 111 rpcbind
    100000 4 udp 111 rpcbind
    100000 3 udp 111 rpcbind
    100000 2 udp 111 rpcbind
    1073741824 1 tcp 36084
    100024 1 udp 42835 status
    100024 1 tcp 36086 status
    100133 1 udp 42835
    100133 1 tcp 36086
    100001 2 udp 42836 rstatd
    100001 3 udp 42836 rstatd
    100001 4 udp 42836 rstatd
    100002 2 tcp 36087 rusersd
    100002 3 tcp 36087 rusersd
    100002 2 udp 42838 rusersd
    100002 3 udp 42838 rusersd
    100011 1 udp 42840 rquotad
    100021 1 udp 4045 nlockmgr
    100021 2 udp 4045 nlockmgr
    100021 3 udp 4045 nlockmgr
    100021 4 udp 4045 nlockmgr
    100021 1 tcp 4045 nlockmgr
    100021 2 tcp 4045 nlockmgr
    100021 3 tcp 4045 nlockmgr
    100021 4 tcp 4045 nlockmgr
    # showmount -e 172.25.30.120 (Server)
    showmount: 172.25.30.120: RPC: Rpcbind failure - RPC: Unable to receive
    Commands OnServer:
    ================
    program vers proto port
    100000 2 tcp 111 portmapper
    100000 2 udp 111 portmapper
    100021 1 tcp 49927 nlockmgr
    100021 3 tcp 49927 nlockmgr
    100021 4 tcp 49927 nlockmgr
    100021 1 udp 32772 nlockmgr
    100021 3 udp 32772 nlockmgr
    100021 4 udp 32772 nlockmgr
    100011 1 udp 796 rquotad
    100011 2 udp 796 rquotad
    100011 1 tcp 799 rquotad
    100011 2 tcp 799 rquotad
    100003 2 udp 2049 nfs
    100003 3 udp 2049 nfs
    100003 4 udp 2049 nfs
    100003 2 tcp 2049 nfs
    100003 3 tcp 2049 nfs
    100003 4 tcp 2049 nfs
    100005 1 udp 809 mountd
    100005 1 tcp 812 mountd
    100005 2 udp 809 mountd
    100005 2 tcp 812 mountd
    100005 3 udp 809 mountd
    100005 3 tcp 812 mountd
    100024 1 udp 854 status
    100024 1 tcp 857 status
    # showmount -e 172.25.30.120
    Export list for 172.25.30.120:
    /scratch/nfs 172.25.30.100,172.25.24.0/4
    /scratch/pvfs2 172.25.30.100,172.25.24.0/4
    Thank you, ~al

    I also tried to run Snoop on the client and wireshark on Server and following is what I see:
    One Server: Upon issuing mount command on client:
    # tshark -i eth1
    Running as user "root" and group "root". This could be dangerous.
    Capturing on eth1
    0.000000 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    0.205570 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(100005) V:3 UDP
    0.205586 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
    0.207863 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(100005) V:3 UDP
    0.207869 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
    2.005314 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    4.011005 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    5.206109 Dell_70:ad:29 -> SunMicro_70:ff:17 ARP Who has 172.25.30.100? Tell 172.25.30.120
    5.206277 SunMicro_70:ff:17 -> Dell_70:ad:29 ARP 172.25.30.100 is at 00:14:4f:70:ff:17
    5.216157 172.25.30.100 -> 172.25.30.120 Portmap V2 GETPORT Call MOUNT(100005) V:3 UDP
    5.216170 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
    On Clinet Upon issuing mount command on client:
    # snoop -d bge1
    Using device /dev/bge1 (promiscuous mode)
    ? -> * ETHER Type=9000 (Loopback), size = 60 bytes
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    atlas-pvfs2 -> pvfs2-io-0-3 PORTMAP C GETPORT prog=100005 (MOUNT) vers=3 proto=UDP
    pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (UDP port 111 unreachable)
    atlas-pvfs2 -> pvfs2-io-0-3 PORTMAP C GETPORT prog=100005 (MOUNT) vers=3 proto=UDP
    pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (UDP port 111 unreachable)
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    ? -> * ETHER Type=9000 (Loopback), size = 60 bytes
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    pvfs2-io-0-3 -> * ARP C Who is 172.25.30.100, atlas-pvfs2 ?
    atlas-pvfs2 -> pvfs2-io-0-3 ARP R 172.25.30.100, atlas-pvfs2 is 0:14:4f:70:ff:17
    atlas-pvfs2 -> pvfs2-io-0-3 PORTMAP C GETPORT prog=100005 (MOUNT) vers=3 proto=UDP
    pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (UDP port 111 unreachable)
    Also I see the following on Client:
    # rpcinfo -p pvfs2-io-0-3
    rpcinfo: can't contact portmapper: RPC: Rpcbind failure - RPC: Failed (unspecified error)
    When I try the above rpcinfo command on Client and Server Snoop And wireshark(ethereal) outputs are as follows:
    Client # snoop -d bge1
    Using device /dev/bge1 (promiscuous mode)
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    atlas-pvfs2 -> pvfs2-io-0-3 TCP D=111 S=872 Syn Seq=2065245538 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK>
    pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (TCP port 111 unreachable)
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    ? -> (multicast) ETHER Type=2004 (Unknown), size = 48 bytes
    ? -> (multicast) ETHER Type=0003 (LLC/802.3), size = 90 bytes
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    ? -> * ETHER Type=9000 (Loopback), size = 60 bytes
    pvfs2-io-0-3 -> * ARP C Who is 172.25.30.100, atlas-pvfs2 ?
    atlas-pvfs2 -> pvfs2-io-0-3 ARP R 172.25.30.100, atlas-pvfs2 is 0:14:4f:70:ff:17
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    atlas-pvfs2 -> pvfs2-io-0-3 TCP D=111 S=874 Syn Seq=2068043912 Len=0 Win=49640 Options=<mss 1460,nop,wscale 0,nop,nop,sackOK>
    pvfs2-io-0-3 -> atlas-pvfs2 ICMP Destination unreachable (TCP port 111 unreachable)
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    ? -> (multicast) ETHER Type=0000 (LLC/802.3), size = 52 bytes
    ? -> * ETHER Type=9000 (Loopback), size = 60 bytes
    Server # tshark -i eth1
    Running as user "root" and group "root". This could be dangerous.
    Capturing on eth1
    0.000000 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    0.313739 Cisco_3d:68:10 -> CDP/VTP/DTP/PAgP/UDLD CDP Device ID: MILEVA Port ID: GigabitEthernet1/0/16
    2.006422 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    3.483733 172.25.30.100 -> 172.25.30.120 TCP 865 > sunrpc [SYN] Seq=0 Win=49640 Len=0 MSS=1460 WS=0
    3.483752 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
    4.009741 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    6.014524 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    6.551356 Cisco_3d:68:10 -> Cisco_3d:68:10 LOOP Reply
    8.019386 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    8.484344 Dell_70:ad:29 -> SunMicro_70:ff:17 ARP Who has 172.25.30.100? Tell 172.25.30.120
    8.484569 SunMicro_70:ff:17 -> Dell_70:ad:29 ARP 172.25.30.100 is at 00:14:4f:70:ff:17
    10.024411 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    12.030956 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    12.901333 Cisco_3d:68:10 -> CDP/VTP/DTP/PAgP/UDLD DTP Dynamic Trunking Protocol
    12.901421 Cisco_3d:68:10 -> CDP/VTP/DTP/PAgP/UDLD DTP Dynamic Trunking Protocol
    ^[[A 14.034193 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00  Cost = 0  Port = 0x8010
    15.691119 172.25.30.100 -> 172.25.30.120 TCP 866 > sunrpc [SYN] Seq=0 Win=49640 Len=0 MSS=1460 WS=0
    15.691138 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
    16.038944 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    16.550760 Cisco_3d:68:10 -> Cisco_3d:68:10 LOOP Reply
    18.043886 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    20.050243 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    21.487689 172.25.30.100 -> 172.25.30.120 TCP 867 > sunrpc [SYN] Seq=0 Win=49640 Len=0 MSS=1460 WS=0
    21.487700 172.25.30.120 -> 172.25.30.100 ICMP Destination unreachable (Port unreachable)
    22.053784 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    24.058680 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    26.063406 Cisco_3d:68:10 -> Spanning-tree-(for-bridges)_00 STP Conf. Root = 32770/00:0a:b8:3d:68:00 Cost = 0 Port = 0x8010
    26.558307 Cisco_3d:68:10 -> Cisco_3d:68:10 LOOP Reply
    ~thank you for any help you can provide!!!

  • Problems mounting at boot...

    I just installed Arch and know that I must have done something wrong. Here is the error message:
    Booting 'Arch Linux'
    root (hd1,0)
    Filesystem type unknown, partition type 0x7
    kernel /vmlinuz 26 root= /dev/disk/by-uuid/53fe... ro
    Error 17: cannot mount selected partition
    Press any key to continue...
    After I press a key it takes me back to the boot menu. Any help is much appreciated.

    Preston C. wrote:kernel /vmlinuz 26 root= /dev/disk/by-uuid/53fe... ro
    No spaces, I think. Not sure if it makes a difference with the one after root=, though.
    kernel /vmlinuz26 root=/dev/disk/by-uuid/blahblah ro
    Hope that works. If not, check to make sure that vmlinuz26 exists in the root directory of that disk's first partition (/dev/sdb1 for instance). If it's on a different partition on that disk, change the first line from (hd1,0) to (hd1,x) where X is precisely one less than the number of the partition it's on.
    Oh, and just in case you're unaware, you can edit /boot/grub/menu.lst like any regular text file. I personally don't trust automagical configurizers, but that's just me. Oh, and if you hit the 'E' key on a menu item in grub, you can edit the line so you can trial-and-error your way to a boot, and edit your changes into menu.lst afterward to make them permanent.
    Last edited by Seleucius (2009-09-14 10:50:23)

  • Solaris Volume Manager - mount problems

    hi.
    first i set up a raid on a StorEdge 5100 :
    metainit d4 -r c2t1d0s0 c2t2d0s0 .............. (13 devices) -i 64k
    works fine now i want to create a fs on d4:
    newfs /dev/md/rdsk/d4
    works fine.
    i insert this line in vfstab:
    /dev/md/dsk/d4 /dev/md/rdsk/d4 /d4 ufs 1 yes -
    now after a reboot the system hangs in maintanance mode and want a fsck . after a fsck and control+d
    the system coming up. after a next reboot The same Problem... !!
    without any problems i run two mirror disksets / and /var on d0 and d3 and the swap on d1.
    is it a problem with the size of 101GB on the raid5 (A5100)
    yes i know i can run veritas volume manager on the A5100 (a license is on the machine) but i was not able to install the vm bacause the vm cant find the A5100 and the license. So please help me .

    Duplicate slicing: prtvtoc /dev/rdsk/c1t0d0s7|fmthard -s - /dev/rdsk/c1t1d0s7
    Lather, rinse, repeat for each file system:
    metainit the bootable side of the mirror: metainit -f d71 1 1 c1t0d0s7.
    metainit the other side: metainit d72 1 1 c1t1d0s7.
    Attach one side of the mirror: metainit d70 -m d71
    When done: lockfs -fa;init 6
    Lather, rinse, repeat for each file system:
    After reboot attach the other side of the mirror: metattach d70 d72
    bash-3.00# metastat -p
    d70 -m d71 d72 1
    d71 1 1 c1t0d0s7
    d72 1 1 c1t1d0s7
    d50 -m d51 d52 1
    d51 1 1 c1t0d0s5
    d52 1 1 c1t1d0s5
    d10 -m d11 d12 1
    d11 1 1 c1t0d0s1
    d12 1 1 c1t1d0s1
    d0 -m d1 d2 1
    d1 1 1 c1t0d0s0
    d2 1 1 c1t1d0s0
    d60 -m d61 d62 1
    d61 1 1 c1t0d0s6
    d62 1 1 c1t1d0s6
    bash-3.00# cat /etc/vfstab
    #device         device          mount           FS      fsck    mount   mount
    #to mount       to fsck         point           type    pass    at boot options
    fd      -       /dev/fd fd      -       no      -
    /proc   -       /proc   proc    -       no      -
    /dev/md/dsk/d10 -       -       swap    -       no      -
    /dev/md/dsk/d0  /dev/md/rdsk/d0 /       ufs     1       no      -
    /dev/md/dsk/d70 /dev/md/rdsk/d70        /usr    ufs     1       no      -
    /dev/md/dsk/d50 /dev/md/rdsk/d50        /var    ufs     1       no      -
    /dev/md/dsk/d60 /dev/md/rdsk/d60        /opt    ufs     2       yes     -
    /devices        -       /devices        devfs   -       no      -
    ctfs    -       /system/contract        ctfs    -       no      -
    objfs   -       /system/object  objfs   -       no      -
    swap    -       /tmp    tmpfs   -       yes     -

Maybe you are looking for