Sponsored Content
Full Discussion: /usr unable to mount
Operating Systems Solaris /usr unable to mount Post 302247059 by mailbox80 on Tuesday 14th of October 2008 11:36:53 PM
Old 10-15-2008
I already run all of it and all show no error. but when boot up time. failed.

after I found /etv/vfstab all goes wrong to md but i use vx instead of md.

restore it and boot it up.

never using SVM but don't know why all path change to /dev/md.
 

10 More Discussions You Might Find Interesting

1. Solaris

Boot problem: failed to mount /usr

My Solaris10 cannot boot after I made an error when apending the vfstab to: dev to mount======/dev/dsk/c0d0p1:1 device to fsck====== <blank> mount pt=========/Data FS Type==========pcfs fsck pass=========- mount at boot=====yes mount options===== <blank> My 'Data' partition is a... (3 Replies)
Discussion started by: maag
3 Replies

2. Post Here to Contact Site Administrators and Moderators

/usr/openwin/bin/xinit: unable to connect to Xserver

Hi Gents, I have downloaded Sol 8 2/04 from Sun's web page and I have tried to install it into a V890. I can boot from a CD 1of 2 without any problem. After the selection of the language and the Locale, the TWM (Sol Install Console window) cannot starts up. The following are the errors... (0 Replies)
Discussion started by: mmakhol
0 Replies

3. Solaris

Mount /usr as a separate filesystem

Hi All, I have mount /usr directory as a seperate filesystem.The /usr directory includedd in / root file system.I have to mount it as seperate. Please Help me, Thanks and Regards, (7 Replies)
Discussion started by: lbreddy
7 Replies

4. Solaris

smf fails to mount svc:/system/filesystem/usr:default

http://i44.tinypic.com/2cmq7vn.jpg Please help me on this issue i'm using solaris on vmware x86 even i runed fsck on root disk like 'fsck -Y /dev/rdsk/c0d0s0 ' but again after reboot it is going to maintanance mode reply soon (6 Replies)
Discussion started by: knl.sundeep
6 Replies

5. HP-UX

/usr out of disk space need to unmount/ expand volume /mount

Greetings, I am running HP-UX 10.2 and /usr is out of disk space already. I installed IE 5.0 for UNIX on my machine under /usr and browsed the Internet for a while and presto no more disk space. I have plenty of hard disk space on my computer so would like to expand the size of the volume. The... (5 Replies)
Discussion started by: Dirk_
5 Replies

6. Solaris

Unable to create or delete a directory in /usr with root user

Hi All, I am trying to uninstall jdk 1.5 from my Solaris 10 64 bit but some how was not successful.so tried to delete the folder of jdk from /usr but its throughing error as: Unable to remove directory jdk: Read-only file system Even I tried to create a dir in /usr but its not allowing me... (4 Replies)
Discussion started by: Pshah
4 Replies

7. Ubuntu

Unable to mount disk

I am running Ubuntu Server, I recently added a new hard drive to the machine When I run fdisk -l I see both drives. The recently added drive is present but it's listed as extended. when I try to mount the drive it says you must specify the file system type. I can't mount this drive, I was... (2 Replies)
Discussion started by: NelsonC
2 Replies

8. Solaris

Failed to mount /usr

I recently ran the Solaris 10 upgrade 10 and everything went fine. About 2 months later after rebooting and getting ready to load the latest upgrade that came out, I am getting this error. ERROR: svc:/system/filesytem/root: default failed to mount /usr (see 'svc -x' for details) ... (6 Replies)
Discussion started by: drew_1980
6 Replies

9. Red Hat

Unable to mount.

Hi, I am unable to mount the AIX share on Red Hat Linux 5.5 getting below error on linux server while mounting. reason given by server: unknown nfs status return value: -1 I have checked on AIX side. lssrc -g nfs showing below output. bash-3.00# lssrc -g nfs Subsystem ... (2 Replies)
Discussion started by: manoj.solaris
2 Replies

10. AIX

/usr/sbin/extendvg: Unable to extend volume group

Dear Expret, Help me about my issue, I trying add new disk to volume Group but error: step add new disk to volume group. 1. ~Change a Volume Group Add a Physical Volume to a Volume Group Remove a Physical Volume from a Volume Group Reorganize a Volume Group... (6 Replies)
Discussion started by: williamen
6 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 07:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy