Sponsored Content
Operating Systems Solaris Solaris 8 booting from wrong device Post 302206938 by Juha on Wednesday 18th of June 2008 07:50:44 PM
Old 06-18-2008
Hi,

editing the vfstab did the trick... however I still can't boot up the server, I can run fsck when booting from CD, but when I try to boot the server to single user mode without CD it boots up and goes into maintenance mode, but does not let me ctrl+D or type the root password... it just hangs... Smilie

I didn't restore the disk, it was just one very old disk that I would have needed. I've never had such a problem before Smilie

Anyway thanks for your tips!
 

4 More Discussions You Might Find Interesting

1. Solaris

What's wrong with my system? Solaris not booting.

Booting the 32-bit OS ... SunOS Release 5.7 Version Generic_106541-31 Copyright (c) 1983-2002, Sun Microsystems, Inc. configuring network interfaces: le0. Hostname: wz-ultra1 metainit: wz-ultra1: there are no existing databases The system is coming up. Please wait. checking ufs... (2 Replies)
Discussion started by: CollenM
2 Replies

2. Solaris

Booting from wrong SCSI-disk. Error -256 Stack Underflow

Hi. I need to boot on Sun Blade 150 from scsi-disk, that ran on old Sun Ultra 10. It is necessary to take some the information from an old disk and something to study. The workstation is booted and I receive the following issue::mad: Sun Blade 150 (UltraSPARC-IIe 650MHz), No Keyboard (tip... (3 Replies)
Discussion started by: wolfgang
3 Replies

3. Red Hat

This doesn't look like a partition table Probably you selected the wrong device.

Hi, I need to mount the device from this device # fdisk -l . . . Disk /dev/sdas: 2000.4 GB, 2000365289472 bytes 255 heads, 63 sectors/track, 243197 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size... (0 Replies)
Discussion started by: justbow
0 Replies

4. Red Hat

Device-mapper behaviour booting on init=bin/bash

Good morning Recently we needed to change the password from a redhat 6.5 system that no one knew the root password. Starting the system with the init=/bin/bash method took us to the following scenario: system_vg active with only root_lv and tmpfs mounted. our entries at fstab are like... (1 Reply)
Discussion started by: Ikaro0
1 Replies
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)
All times are GMT -4. The time now is 11:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy