unable to boot afer restoring root partion manages by veritas
Hi all,
After restoring the / FS on a netra 240. It is unable to boot the system.
The message displayed is the following: "The file just loaded does not appear to be executable"
Bellow, the content of /etc/vfstab before restoring:
Hi everyone, so i have a 40Gb disk with Windows XP and Solaris 10 Installed... windows has once again become unoperable for virus and stufff, and i need to reinstall it, but when i do that the MBR will be overwriten right? and i wont be able to access solaris10 anymore, is there a way, like a... (1 Reply)
Hi there,
My task is to replace the two 73 G disks with two 143 G disks , which has vxvm 4.1 running on it. I would like to know whether the steps iam following are correct.
1. Break the sub-disks, plexes of the root mirror.
2. Remove the sub-disks,plexes of the root mirror.
3. Remove one of... (10 Replies)
Hey Guys,
I am using a Sun sparc server and had 6 disks.
The root was loaded on c0t10d0s0 disk.
I made an image or mirrored the root to another disk c0t9d0s0.
But during the process instead of attaching submirrors to main mirror
(d0 <--- d01 and d11) i attached d0 <--- d01 and... (1 Reply)
Dear All,
In our environment we use SDS (Solaris Vlume Manager) for root file system.So, I am wondering why Veritas is not use for the same.
root@abc # df -kh
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d10 30G 22G 6.9G 77% /
/devices ... (3 Replies)
Hello I use Solaris 10. I need to restore the root file system, but I don't know how . i can only boot the server in safe mode or with the cd (ok boot cdrom -s)
Do you guys know a good procedure, I don't want to break the mirrors.
( the server is not a cluster).
Its an emergency, i would... (4 Replies)
Hi all,
I'm fairly new to Solaris and am just getting to grips with using LU (Live Upgrade) for OS patching purposes.
worcester#uname -a
SunOS worcester 5.10 Generic_144488-12 sun4v sparc SUNW,SPARC-Enterprise-T5220I have successfully created and patched a new BE (boot environment) using the... (5 Replies)
Hi All,
We are using Solaris 10 x86, and Veritas Storage Foundation Software version 6.0.1 and faced the following issues after mirroring and during boot from mirror.
1) VTOC has been changed after mirroring the rootdisk with this command - " /opt/VRTS/bin/vxrootmir <disk to be mirrored>".... (0 Replies)
I need to increase the /var (UFS) filesystem and root disk under veritas control or root disk is encapsulated
# df -k /var
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/var 13241195 12475897 674524 96% /var
# fstyp /dev/vx/dsk/var
ufs
# pkginfo... (1 Reply)
Discussion started by: amity
1 Replies
LEARN ABOUT REDHAT
vfstab
vfstab(4) File Formats vfstab(4)NAME
vfstab - table of file system defaults
DESCRIPTION
The file /etc/vfstab describes defaults for each file system. The information is stored in a table with the following column headings:
device device mount FS fsck mount mount
to mount to fsck point type pass at boot options
The fields in the table are space-separated and show the resource name (device to mount), the raw device to fsck (device to fsck), the
default mount directory (mount point), the name of the file system type (FS type), the number used by fsck to decide whether to check the
file system automatically (fsck pass), whether the file system should be mounted automatically by mountall (mount at boot), and the file
system mount options (mount options). (See respective mount file system man page below in SEE ALSO for mount options.) A '-' is used to
indicate no entry in a field. This may be used when a field does not apply to the resource being mounted.
The getvfsent(3C) family of routines is used to read and write to /etc/vfstab.
/etc/vfstab can be used to specify swap areas. An entry so specified, (which can be a file or a device), will automatically be added as a
swap area by the /sbin/swapadd script when the system boots. To specify a swap area, the device-to-mount field contains the name of the
swap file or device, the FS-type is "swap", mount-at-boot is "no" and all other fields have no entry.
EXAMPLES
The following are vfstab entries for various file system types supported in the Solaris operating environment.
Example 1: NFS and UFS Mounts
The following entry invokes NFS to automatically mount the directory /usr/local of the server example1 on the client's /usr/local directory
with read-only permission:
example1:/usr/local - /usr/local nfs - yes ro
The following example assumes a small departmental mail setup, in which clients mount /var/mail from a server mailsvr. The following entry
would be listed in each client's vfstab:
mailsvr:/var/mail - /var/mail nfs - yes intr,bg
The following is an example for a UFS file system in which logging is enabled:
/dev/dsk/c2t10d0s0 /dev/rdsk/c2t10d0s0 /export/local ufs 3 yes logging
See mount_nfs(1M) for a description of NFS mount options and mount_ufs(1M) for a description of UFS options.
Example 2: pcfs Mounts
The following example mounts a pcfs file system on a fixed hard disk on an x86 machine:
/dev/dsk/c1t2d0p0:c - /win98 pcfs - yes -
The example below mounts a Jaz drive on a SPARC machine. Normally, the volume management daemon (see vold(1M)) handles mounting of remov-
able media, obviating a vfstab entry. If you choose to specify a device that supports removable media in vfstab, be sure to set the mount-
at-boot field to no, as below. Such an entry presumes you are not running vold.
/dev/dsk/c1t2d0s2:c - /jaz pcfs - no -
For removable media on a SPARC machine, the convention for the slice portion of the disk identifier is to specify s2, which stands for the
entire medium.
For pcfs file systems on x86 machines, note that the disk identifier uses a p (p0) and a logical drive (c, in the /win98 example above) for
a pcfs logical drive. See mount_pcfs(1M) for syntax for pcfs logical drives and for pcfs-specific mount options.
Example 3: CacheFS Mount
Below is an example for a CacheFS file system. Because of the length of this entry and the fact that vfstab entries cannot be continued to
a second line, the vfstab fields are presented here in a vertical format. In re-creating such an entry in your own vfstab, you would enter
values as you would for any vfstab entry, on a single line.
device to mount: svr1:/export/abc
device to fsck: /usr/abc
mount point: /opt/cache
FS type: cachefs
fsck pass: 7
mount at boot: yes
mount options:
local-access,bg,nosuid,demandconst,backfstype=nfs,cachedir=/opt/cache
See mount_cachefs(1M) for CacheFS-specific mount options.
Example 4: Loopback File System Mount
The following is an example of mounting a loopback (lofs) file system:
/export/test - /opt/test lofs - yes -
See lofs(7FS) for an overview of the loopback file system.
SEE ALSO fsck(1M), mount(1M), mount_cachefs(1M), mount_hsfs(1M), mount_nfs(1M), mount_tmpfs(1M), mount_ufs(1M), swap(1M), getvfsent(3C)
System Administration Guide: Basic Administration
SunOS 5.10 21 Jun 2001 vfstab(4)