Ubuntu Linux mount移动硬盘、U盘、SD卡_Linux教程_Linux公社-Linux系统门户网站
你好，游客
Ubuntu Linux mount移动硬盘、U盘、SD卡
来源：Linux社区&
作者：Linux编辑
首先将USB设备插到USB口上，我在我的机器上插入了一个USB硬盘，和一个SD卡，其中SD卡已经挂接到 Linuxx系统。然后在终端中输入
$ sudo fdisk -l
会看到以下显示：
Disk /dev/sda: 160.0 GB,
bytes255 heads, 63 sectors/track, 19457 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesDisk identifier: 0xc9c6c9c6
&& Device Boot&&&&& Start&&&&&&&& End&&&&& Blocks&& Id& System/dev/sda1&& *&&&&&&&&&& 1&&&&&&& 2550&&& +&& 7& HPFS/NTFS/dev/sda2&&&&&&&&&&& 2551&&&&&& 19457&& +&& f& W95 Ext'd (LBA)/dev/sda5&&&&&&&&&&& 2551&&&&&&& 6374&&& +&& b& W95 FAT32/dev/sda6&&&&&&&&&&& 6375&&&&&& 10198&&& +&& b& W95 FAT32/dev/sda7&&&&&&&&&& 10199&&&&&& 19457&&& &&& 7& HPFS/NTFS
Disk /dev/sdb: 120.0 GB,
bytes255 heads, 63 sectors/track, 14593 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesDisk identifier: 0xbfcf3908
&& Device Boot&&&&& Start&&&&&&&& End&&&&& Blocks&& Id& System/dev/sdb1&& *&&&&&&&&&& 1&&&&&&& 3824&&& +&& 7& HPFS/NTFS/dev/sdb2&&&&&&&&&&& 3825&&&&&& 14592&&& &&& f& W95 Ext'd (LBA)/dev/sdb5&&&&&&&&&&& 3825&&&&&&& 8923&&& &&& 7& HPFS/NTFS/dev/sdb6&&&&&&&&&&& 8924&&&&&& 14592&&& &&& 7& HPFS/NTFS
Disk /dev/sdc: 2032 MB,
bytes41 heads, 40 sectors/track, 2420 cylindersUnits = cylinders of 1640 * 512 = 839680 bytesDisk identifier: 0x
&& Device Boot&&&&& Start&&&&&&&& End&&&&& Blocks&& Id& System/dev/sdc1&&&&&&&&&&&&&& 1&&&&&&& 2421&&&& 1984899+&& 6& FAT16
其中：Disk /dev/sdb: 120.0 GB是我的移动硬盘Disk /dev/sdc: 2032 MB是我的SD卡
会看到一下显示
/host/ubuntu/disks/root.disk on / type ext3 (rw,errors=remount-ro)proc on /proc type proc (rw,noexec,nosuid,nodev)/sys on /sys type sysfs (rw,noexec,nosuid,nodev)varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)udev on /dev type tmpfs (rw,mode=0755)devshm on /dev/shm type tmpfs (rw)devpts on /dev/pts type devpts (rw,gid=5,mode=620)lrm on /lib/modules/2.6.24-19-generic/volatile type tmpfs (rw)/host/ubuntu/disks/boot on /boot type none (rw,bind)securityfs on /sys/kernel/security type securityfs (rw)gvfs-fuse-daemon on /home/guandl/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=guandl)/dev/sdc1 on /media/disk type vfat (rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush)
从以上内容可以看到/dev/sdc1（SD卡）挂接在/media/disk，下面我们将/dev/sdb1到Linux首先创建一个挂接点，也就是目录
$ sudo mkdir /mnt/mvdisk-1
然后执行mount挂接
$ sudo mount /dev/sdb1 /mnt/mvdisk-1/
查看挂接点的内容
$ ls -l /mnt/mvdisk-1/
会看到类似一下内容
总用量 64drwxrwxrwx 1 root root -09-23 20:43 booksdrwxrwxrwx 1 root root& -06 17:07 System Volume Information
再查看所有挂接设备
$ mount/host/ubuntu/disks/root.disk on / type ext3 (rw,errors=remount-ro)proc on /proc type proc (rw,noexec,nosuid,nodev)/sys on /sys type sysfs (rw,noexec,nosuid,nodev)varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)udev on /dev type tmpfs (rw,mode=0755)devshm on /dev/shm type tmpfs (rw)devpts on /dev/pts type devpts (rw,gid=5,mode=620)lrm on /lib/modules/2.6.24-19-generic/volatile type tmpfs (rw)/host/ubuntu/disks/boot on /boot type none (rw,bind)securityfs on /sys/kernel/security type securityfs (rw)gvfs-fuse-daemon on /home/guandl/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=guandl)/dev/sdc1 on /media/disk type vfat (rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush)/dev/sdb1 on /mnt/mvdisk-1 type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)
可以看到，/dev/sdb1已经挂接到了/mnt/mvdisk-1
$ sudo umount /mnt/mvdisk-1
再查看所有挂接设备
/host/ubuntu/disks/root.disk on / type ext3 (rw,errors=remount-ro)proc on /proc type proc (rw,noexec,nosuid,nodev)/sys on /sys type sysfs (rw,noexec,nosuid,nodev)varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)udev on /dev type tmpfs (rw,mode=0755)devshm on /dev/shm type tmpfs (rw)devpts on /dev/pts type devpts (rw,gid=5,mode=620)lrm on /lib/modules/2.6.24-19-generic/volatile type tmpfs (rw)/host/ubuntu/disks/boot on /boot type none (rw,bind)securityfs on /sys/kernel/security type securityfs (rw)gvfs-fuse-daemon on /home/guandl/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=guandl)/dev/sdc1 on /media/disk type vfat (rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush)
可以看到，/dev/sdb1已经不在挂接范围了
相关资讯 & & &
& (12/18/:16)
& (11/15/:50)
& (11/03/:47)
& (11/27/:47)
& (11/05/:34)
& (10/12/:38)
　　　同意评论声明
　　　发表
尊重网上道德，遵守中华人民共和国的各项有关法律法规
承担一切因您的行为而直接或间接导致的民事或刑事法律责任
本站管理人员有权保留或删除其管辖留言中的任意内容
本站有权在网站内转载或引用您的评论
参与本评论即表明您已经阅读并接受上述条款mount() - Unix, Linux System Call
Advertisements
mount, umount - mount and unmount filesystems
#include &sys/mount.h&
int mount(const char *source, const char *target,
const char *filesystemtype, unsigned long mountflags,
const void *data);
int umount(const char *target);
int umount2(const char *target, int flags);
DESCRIPTION
mount() attaches the filesystem specified by
source (which is often a device name, but can also be a directory name
or a dummy) to the directory specified by
umount() and
umount2() remove the attachment of the (topmost) filesystem mounted on
Appropriate privilege (Linux: the
CAP_SYS_ADMIN capability) is required to mount and unmount filesystems.
Since Linux 2.4 a single filesystem can be visible at
multiple mount points, and multiple mounts can be stacked
on the same mount point.
Values for the
filesystemtype argument supported by the kernel are listed in
/proc/filesystems (like "minix", "ext2", "msdos", "proc", "nfs", "iso9660" etc.).
Further types may become available when the appropriate modules
are loaded.
mountflags argument may have the magic number 0xC0ED (MS_MGC_VAL)
in the top 16 bits (this was required in kernel versions prior to 2.4, but
is no longer required and ignored if specified),
and various mount flags (as defined in &linux/fs.h& for libc4 and libc5
and in &sys/mount.h& for glibc2) in the low order 16 bits:
TagDescription
(Linux 2.4 onwards)
Perform a bind mount, making a file or a directory subtree visible at
another point within a file system.
Bind mounts may cross file system boundaries and span
filesystemtype, mountflags, and data arguments are ignored.
MS_DIRSYNC (since Linux 2.5.19) &
Make directory changes on this file system synchronous.
(This property can be obtained for individual directories
or subtrees using
chattr(8).)
MS_MANDLOCK &
Permit mandatory locking on files in this file system.
(Mandatory locking must still be enabled on a per-file basis,
as described in
fcntl(2).)
Move a subtree.
source specifies an existing mount point and
target specifies the new location.
The move is atomic: at no point is the subtree unmounted.
filesystemtype, mountflags, and data arguments are ignored.
MS_NOATIME &
Do not update access times for (all types of) files on this file system.
MS_NODEV &
Do not allow access to devices (special files) on this file system.
MS_NODIRATIME &
Do not update access times for directories on this file system.
MS_NOEXEC &
Do not allow programs to be executed from this file system.
MS_NOSUID &
Do not honour set-user-ID and set-group-ID bits when executing
programs from this file system.
MS_RDONLY &
Mount file system read-only.
MS_REMOUNT &
Remount an existing mount.
This is allows you to change the
mountflags and
data of an existing mount without having to unmount and remount the file system.
source and
target should be the same values specified in the initial
filesystemtype is ignored.
The following
mountflags can be changed:
MS_RDONLY, MS_SYNCHRONOUS, MS_MANDLOCK; before kernel 2.6.16, the following could also be changed:
MS_NOATIME and
MS_NODIRATIME; and, additionally, before kernel 2.4, the following could also be changed:
MS_NOSUID, MS_NODEV, MS_NOEXEC.
MS_SYNCHRONOUS &
Make writes on this file system synchronous (as though
O_SYNC flag to
was specified for all file opens to this file system).
From Linux 2.4 onwards, the
MS_NODEV, MS_NOEXEC, and MS_NOSUID flags are settable on a per-mount-point basis.
From kernel 2.6.16 onwards,
MS_NOATIME and
MS_NODIRATIME are also settable on a per-mount-point basis.
data argument is interpreted by the different file systems.
Typically it is a string of comma-separated options
understood by this file system.
for details of the options available for each filesystem type.
Linux 2.1.116 added the
umount2() system call, which, like
umount(), unmounts a target, but allows additional
flags controlling the behaviour of the operation:
MNT_FORCE (since Linux 2.1.116) &
Force unmount even if busy.
(Only for NFS mounts.)
MNT_DETACH (since Linux 2.4.11) &
Perform a lazy unmount: make the mount point unavailable for
new accesses, and actually perform the unmount when the mount point
ceases to be busy.
MNT_EXPIRE (since Linux 2.6.8) &
Mark the mount point as expired.
If a mount point is not currently in use, then an initial call to
umount2() with this flag fails with the error
EAGAIN, but marks the mount point as expired.
The mount point remains expired as long as it isn’t accessed
by any process.
umount2() call specifying
MNT_EXPIRE unmounts an expired mount point.
This flag cannot be specified with either
MNT_FORCE or
MNT_DETACH.
RETURN VALUE
On success, zero is returned.
On error, -1 is returned, and
errno is set appropriately.
The error values given below result from filesystem type independent
errors. Each filesystem type may have its own special errors and its
own special behavior.
See the kernel source code for details.
TagDescription
A component of a path was not searchable. (See also
path_resolution(2).)
Or, mounting a read-only filesystem was attempted without giving the
MS_RDONLY flag.
Or, the block device
source is located on a filesystem mounted with the
MS_NODEV option.
umount2() specifying
MNT_EXPIRE successfully marked an unbusy file system as expired.
source is already mounted. Or, it cannot be remounted read-only,
because it still holds files open for writing.
Or, it cannot be mounted on
target because
target is still busy (it is the working directory of some task,
the mount point of another device, has open files, etc.).
Or, it could not be unmounted because it is busy.
One of the pointer arguments points outside the user address space.
source had an invalid superblock.
Or, a remount
(MS_REMOUNT) was attempted, but
source was not already mounted on
target. Or, a move
(MS_MOVE) was attempted, but
source was not a mount point, or was ’/’.
Or, an unmount was attempted, but
target was not a mount point.
umount2() was called with
MNT_EXPIRE and either
MNT_DETACH or
MNT_FORCE.
Too many link encountered during pathname resolution.
Or, a move was attempted, while
target is a descendant of
(In case no block device is required:)
Table of dummy devices is full.
ENAMETOOLONG &
A pathname was longer than MAXPATHLEN.
filesystemtype not configured in the kernel.
A pathname was empty or had a nonexistent component.
The kernel could not allocate a free page to copy filenames or data into.
source is not a block device (and a device was required).
The second argument, or a prefix of the first argument, is not
a directory.
The major number of the block device
source is out of range.
The caller does not have the required privileges.
CONFORMING TO
These functions are Linux-specific and should not be used in
programs intended to be portable.
The original
umount() function was called as umount(device) and would return ENOTBLK
when called with something other than a block device.
In Linux 0.98p4 a call umount(dir) was added, in order to
support anonymous devices.
In Linux 2.3.99-pre7 the call umount(device) was removed,
leaving only umount(dir) (since now devices can be mounted
in more than one place, so specifying the device does not suffice).
The original MS_SYNC flag was renamed MS_SYNCHRONOUS in 1.1.69
when a different MS_SYNC was added to &mman.h&.
Before Linux 2.4 an attempt to execute a set-user-ID or set-group-ID program
on a filesystem mounted with
MS_NOSUID would fail with
EPERM. Since Linux 2.4 the set-user-ID and set-group-ID bits are
just silently ignored in this case.
Advertisements
AdvertisementsAccess denied | www.computerhope.com used Cloudflare to restrict access
Please enable cookies.
What happened?
The owner of this website (www.computerhope.com) has banned your access based on your browser's signature (40bafcfeffbe51a0-ua98).& 相关文章 &
: sda1 sda: p1 exceeds device capacity sd 1:0:0:0: [sda] Attached SCSI removable disk
U盘的设备名称为sda1，执行命令挂载： #mount -t vfat sda1 /mnt 提示错误信息： Unable to load NLS charset cp437 FAT: codepage cp437 not found mount: mounting sda1 on /mnt failed: Invalid
usb 问题解决方法.txt
Chinese charset (CP936, GB2312)
NLS UTF8 以下是挂载usb设备后的显示： [root@Emux /]# mount -t vfat -o iocharset=cp936 /dev/ub/a/part1 /mnt [root@Emux /]# ls /mnt
4.移植小结 &如果想知道内核有没有识别出u盘的话可以执行命令：cat /proc/partitions ，看看插入USB前后分区
三星 2440 开发版 USB U盘 常见问题 解决
： Unable to load NLS charset iso8859-1
FAT: IO charset iso8859-1 not found 添加 File systems--& Native language support--& NLS ISO 8859-1
(Latin 1; Western European Languages) 如果出现以下问题： usb 1-1: device
in Windows. 则需要挂在windows下对硬盘进行磁盘检查。 3.
如果需要支持中文字符，则需要在内核配置中选上 File systems
-*- Native language support
以上步骤执行完毕后，可以挂载NTFS格式的USB HDD，但只能读不能写，写NTFS需要用到ntfs-3g，下载链接： 链接地址 在安装ntfs-3g之前，还需要用到fuse
mini2440 usb设备支持
NLS ISO 8859-1
(Latin 1; Western European Languages)
3. 测试 重新编译内核并下载内核到板子上，等系统启动之后，插上u盘，使用下面的命令进行挂载： mount -t vfat /dev/sda1 /mnt/udisk
这样虽然能够正常挂载u盘，但是中文会显示乱码（包括文件名和文件里面的内容）。 4. usb hid类设备支持 配置如下：
Device Drivers
Input device
系统：RHEL5.4 内核：2.6.18-164 起因：因系统资源不足，强行关机，后重启报错
Volume group "VolGroup00" not found Unable to access resume device (/dev/VolGroup00/LogVol01) mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: No such file or directory
Unable to load NLS charset，U盘挂载不了，USB挂载时提示“No Such Device”，mount: Mounting /dev/sda1 on /mnt failed: No such device
其实这是内核配置问题，主要是文件系统不全，当然，USB驱动和Mass storage/SCSI disk/VFat支持要选上，如果还不行，请参考如下： 1、提示 Unable to load NLS charset
cp437 FAT: codepage cp437 not found 则进入 File systems－－》
Native language support－－》
Codepage 437
Linux-2.6.32.2内核在mini2440上的移植(九)---配置USB外设
: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] Attached SCSI removable disk [root@mini2440 /]# 根据上面的提示信息，U盘对应的是/dev/sda1，现在可以挂载它了
[root@mini2440 /]#mount -t vfat /dev/sda1 /mnt/udisk [root@mini2440 /]#cd /mnt/udisk [root@mini2440
一. NTFS 写问题： resolv the problem that can't write file in NTFS file system on Linux: mount -t ntfs-3g /dev/sda3 /mnt/wind FATAL: Module fuse not found. NTFS signature is missing. Failed to mount '/dev/sda3': Invalid argument The device '/dev/sda3
linux挂载U盘和光盘
linux挂载U盘
一，先进入 cd /mnt 目录下
fdisk -l 查看是否找到usb盘
显示：多出sda1 这一搬是usb盘
二，在mnt目录下建文件usb
mnt]# mkdir usb
mount /dev/sda1 /mnt/usb
四，进入新建usb
cd /mnt/usb
ll 查找区动文件
五，进入目录
cd /装驱动的文件夹
make clean 清空原始文件
是/mnt/shared，如果共享文件夹的名字也是shared的话，在挂载的 时候就会出现如下的错误信息(看链接地址)： /sbin/mount.vboxsf: mounting failed with the error: Protocol error 挂载共享文件夹错误 ： /sbin/mount.vboxsf: mounting failed with the error: No such device 出现该错误的原因是没有载入内核模块 vboxvfs 如果提示: /sbin
在安装gcc时，可能会提示要求安装下面几个软件包： binutils-2.13.90.0.18-9.i386.rpm cpp-3.2.2-5.i386.rpm glibc-devel-2.3.2-11.9.i386.rpm 首先在red hat 第一张光盘中查找以上三个软件包，并安装它们。 [root@RedHat9 mnt]# mount /dev/cdrom /mnt/cdrom/ mount: block device /dev/cdrom is write-protected
在安装 gcc 时，可能会提示要求安装下面几个软件包： binutils-2.13.90.0.18-9.i386.rpm cpp-3.2.2-5.i386.rpm glibc-devel-2.3.2-11.9.i386.rpm 首先在 red hat
第一张光盘中查找以上三个软件包，并安装它们。 [root@RedHat9 mnt]# mount /dev/cdrom /mnt/cdrom/ mount: block device /dev/cdrom is write-protected
1、挂载光盘 #
mount /dev/cdrom/ /mnt/
mount: block device /dev/sr0 is write-protected, mounting read-only 设置开机自动挂载 vi /etc/fstab /dev/cdrom
0 2、配置yum源 #
/etc/yum.repos.d/rhel-source.repo
/etc/yum.repos.d
解决nfs error: No such device
# mount -o nolock,rw -t nfs 172.16.0.6:/home/leon/nfs
/mnt mount: mounting 172.16.0.6:/home/leon/nfs on /mnt failed: No such device 网上查阅可能是内核开nfs的编译选项， 但是实际上我用的内核是开着的。 想到可能是启动时ctrl+c按早了，nfs模块没有加载上。 等ipanel启动完成后，ctrl+c，再mount，ok。
v0.3: implementor 41 architecture 1 part 20 variant b rev 5
VFS: Mounted root (cramfs filesystem) readonly on device 31:2.
Freeing init memory: 108K
mount: mounting none on /proc/bus/usb failed: No such file or directory
hwclock: can't open '/dev/misc
not responding, timed out Root-NFS: Server returned error -5 while mounting /work/nfs/rootfs_bluetooth_omap VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "nfs" or unknown-block(2,0) Please append a correct "root=" boot
fedora 挂载 小米手机 （估计其它android设备也是类似操作）
this is safe, use the 'nonempty' mount option 一开始打不开 ，后来过了一段时间自动打开了。。。。。可能需要等待一段时间 2 断开，重新挂载buxing Listing File Information on Device with name: (NULL) fuse: bad mount point `/media/mtp': Transport endpoint is not connected 另外 建立一个挂载点 例如 sudo mtpfs
: No such file or directory
while trying to create journal mount -t ext3 /dev/ide/host0/bus0/target0/lun0/part1 /mnt mount: Mounting /dev/ide/host0/bus0/target0/lun0/part1 on /mnt failed: Invalid argument 解决办法： 在U盘小系统中加入空文件mtab和mke2fs.conf 其他网络资料
中添加一项。share /mnt/share vboxsf rw,gid=100,uid=1000,auto 0 0 这样就可以自动挂载了。 注意：一定要在mount之前，确定已经加载了vboxsf模块。 如果不加载的话，会出现mount出错的情况。 /sbin/mount.vboxsf: mounting failed with the error: No such device 删除共享
sudo umount -f /mnt/share
& 2012 - 2016 & aiuxian.com &All Rights Reserved. &
/*爱悠闲图+*/
var cpro_id = "u1888441";