Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Mount Linux filesystem not defined in etc/fstab Post 303040168 by Neo on Thursday 24th of October 2019 10:40:38 AM
Old 10-24-2019
Yes, you can use the mount command.

Here is a simple example:

Code:
mount /dev/sdb1  /mnt/data

Check out your Linux man pages for mount.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Mount nfs filesystem

I try to share a directory from a wortstation to a server. the share command was no problem. Solaris 8 on mars share -F nfs -o rw /dir/dir2 on the server mount mars:/dir/dir2 /mount_point RPC: Program not registered <--- What is the meaning of this ? Thanks for you help ! (2 Replies)
Discussion started by: joerg
2 Replies

2. UNIX for Dummies Questions & Answers

Mount a Filesystem

I want help about mount a filesystem to use a cdrom to install a software that be in the cd cdrom.. you can send a mail ::removed emails:: (5 Replies)
Discussion started by: amauryrgrullon
5 Replies

3. Linux

how to mount ntfs filesystem

:) Hi frds ..i hope i can get some help for this.. I am unable to mount ntfs/hpfs file system which contain my XP o/s. As per the information collected on net i found tht my kernel i.e 2.4.xx does not support ntfs ..? Now I dont knwo where to get upgraded kernel and how to deploy it ..can anyone... (0 Replies)
Discussion started by: nicknihal
0 Replies

4. Solaris

How can I mount a ufs filesystem on a solaris 10 sparc onto a Linux server

Hi there, I am trying to mount a SAN volume (which is mapped to solaris sparc) partitioned with ufs filesystem onto a linux (intel processor 64bit) server. *I have re-compiled the linux kernel t support ufs fstype with ro mount support. filesystem on solaris:... (3 Replies)
Discussion started by: ilan
3 Replies

5. Solaris

Mount old zfs filesystem

Hey all, I have a machine with 16 drive slots. Two of the drives have a ZFS mirror of the operating system, the other 14 contain the storage raidz. So, after installing Opensolaris on the OS drives, how can I remount the storage raid? TIA (11 Replies)
Discussion started by: PatrickBaer
11 Replies

6. AIX

Mount Filesystem in AIX Unable to read /etc/filesystem

Dear all, We are facing prolem when we are going to mount AIX filesystem, the system returned the following error 0506-307The AFopen call failed : A file or directory in the path name does not exist. But when we ls filesystems in the /etc/ directory it show -rw-r--r-- 0 root ... (2 Replies)
Discussion started by: m_raheelahmed
2 Replies

7. UNIX for Dummies Questions & Answers

Can't mount filesystem

I have 2 Linux servers. rcwlo-ods10g and rcwlo-10gdev I can mount one filesystem from rcwlo-ods10g onto rcwlo-10gdev fine: RCWLO-10gDev:/ # mount -F rcwlo-ods10g:/SAN /backup but when I try another one I get: RCWLO-10gDev:/ # mount -F rcwlo-ods10g:/backup /backup mount:... (0 Replies)
Discussion started by: jamie_collins
0 Replies

8. Red Hat

Mount /etc/fstab

Can you please help me mount below filesystem in fstab ( I have rhel 5 ) as the line is long - it is not taking as single line How can break this in 2 line and act as one ....please help ... (4 Replies)
Discussion started by: saurabh84g
4 Replies

9. Shell Programming and Scripting

Mount/fstab Question . . .

Greetings! Got another basic question for the community :) After wiping a drive with dd, and calling mkfs.ext4 to set things up again, fstab seems to need to be refreshed somehow to allow a call to mount for the volume. What might the "secret handshake" be to pull this off without first... (6 Replies)
Discussion started by: LinQ
6 Replies

10. UNIX for Dummies Questions & Answers

/etc/fstab mount issue

I have a virtual machine with Redhat installed . I am trying to link CD/DVD Drive 1 to /media/cdrom1 and CD/DVD Drive 0 to /media/cdrom0 I tried making these changed in /etc/fstab by adding the below line to it /dev/sr0 /media/cdrom0 iso9660 user,noauto,exec,utf8 0 0... (2 Replies)
Discussion started by: walterthered
2 Replies
SYSTEMD-FSTAB-GENERATOR(8)                                    systemd-fstab-generator                                   SYSTEMD-FSTAB-GENERATOR(8)

NAME
systemd-fstab-generator - Unit generator for /etc/fstab SYNOPSIS
/lib/systemd/system-generators/systemd-fstab-generator DESCRIPTION
systemd-fstab-generator is a generator that translates /etc/fstab (see fstab(5) for details) into native systemd units early at boot and when configuration of the system manager is reloaded. This will instantiate mount and swap units as necessary. The passno field is treated like a simple boolean, and the ordering information is discarded. However, if the root file system is checked, it is checked before all the other file systems. See systemd.mount(5) and systemd.swap(5) for more information about special /etc/fstab mount options this generator understands. One special topic is handling of symbolic links. Historical init implementations supported symlinks in /etc/fstab. Because mount units will refuse mounts where the target is a symbolic link, this generator will resolve any symlinks as far as possible when processing /etc/fstab in order to enhance backwards compatibility. If a symlink target does not exist at the time that this generator runs, it is assumed that the symlink target is the final target of the mount. systemd-fstab-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-fstab-generator understands the following kernel command line parameters: fstab=, rd.fstab= Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any mounts or swap devices configured in /etc/fstab. rd.fstab= is honored only by the initial RAM disk (initrd) while fstab= is honored by both the main system and the initrd. root= Takes the root filesystem to mount in the initrd. root= is honored by the initrd. rootfstype= Takes the root filesystem type that will be passed to the mount command. rootfstype= is honored by the initrd. rootflags= Takes the root filesystem mount options to use. rootflags= is honored by the initrd. mount.usr= Takes the /usr filesystem to be mounted by the initrd. If mount.usrfstype= or mount.usrflags= is set, then mount.usr= will default to the value set in root=. Otherwise, this parameter defaults to the /usr entry found in /etc/fstab on the root filesystem. mount.usr= is honored by the initrd. mount.usrfstype= Takes the /usr filesystem type that will be passed to the mount command. If mount.usr= or mount.usrflags= is set, then mount.usrfstype= will default to the value set in rootfstype=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrfstype= is honored by the initrd. mount.usrflags= Takes the /usr filesystem mount options to use. If mount.usr= or mount.usrfstype= is set, then mount.usrflags= will default to the value set in rootflags=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrflags= is honored by the initrd. systemd.volatile= Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the special value state. If false (the default), this generator makes no changes to the mount tree and the system is booted up in normal mode. If true the generator ensures systemd-volatile-root.service(8) is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to the host system, so that a volatile memory file system ("tmpfs") is used as root directory, with only /usr mounted into it from the configured root file system, in read-only mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and lost at shutdown, as /etc and /var will be served from the (initially unpopulated) volatile memory file system. If set to state the generator will leave the root directory mount point unaltered, however will mount a "tmpfs" file system to /var. In this mode the normal system configuration (i.e. the contents of "/etc") is in effect (and may be modified during system runtime), however the system state (i.e. the contents of "/var") is reset at boot and lost at shutdown. Note that in none of these modes the root directory, /etc, /var or any other resources stored in the root file system are physically removed. It's thus safe to boot a system that is normally operated in non-volatile mode temporarily into volatile mode, without losing data. Note that enabling this setting will only work correctly on operating systems that can boot up with only /usr mounted, and are able to automatically populate /etc, and also /var in case of "systemd.volatile=yes". SEE ALSO
systemd(1), fstab(5), systemd.mount(5), systemd.swap(5), systemd-cryptsetup-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-FSTAB-GENERATOR(8)
All times are GMT -4. The time now is 12:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy