Sponsored Content
Full Discussion: unable to boot from disk1
Operating Systems Solaris unable to boot from disk1 Post 302097230 by Perderabo on Wednesday 22nd of November 2006 11:08:09 AM
Old 11-22-2006
This is a shot in the dark, but I think you need to change /etc/vfstab to use the new disk.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unable to boot with XP after installing SUSE

Hi, I'm not sure if this is the right forum to post. I had following setup before installing SUSE Linux: Windows 98 installed on Primary partition Windows XP installed on Extended Partition When I installed SUSE, it shared space from primary partition and shrunk the size of Windows... (4 Replies)
Discussion started by: patras
4 Replies

2. OS X (Apple)

unable to boot into MAC OS X86

Hi friends I am newbiee to MACOS ,the thing is that i installed MAC OS X86 10.5.6 into my VAIO-VGN-CR343N series without any problem and after rebooting I was unable to boot into macos and tried options like -v -f but no progress..can somebody help me (1 Reply)
Discussion started by: srinivas2828
1 Replies

3. Hardware

Sun 280R unable to boot

I have a problem with one of my Sun 280R servers. I'm unable to boot it. I've managed to get to the {ok} prompt from the RSC card. Please see output below ok show-devs /virtual-memory /memory /aliases /options /openprom /chosen /packages /openprom/client-services... (2 Replies)
Discussion started by: soliberus
2 Replies

4. Red Hat

Unable to boot Fedora 10

Hello, I have a test PC running Fedora 10. Friday evening it was working fine, I have some perl scripts which are scheduled to run every morning. But when I started work this morning, I found I cannot ping the machine. When I switched on the monitor, I saw the GRUB promt :(. I am not sure... (10 Replies)
Discussion started by: SivaramaRaju
10 Replies

5. Solaris

Solaris 10 init 0 and boot disk1 on same command line

Hello all, Fairly simple question here. I know that in Solaris 10 there is a way to tell a system running solaris 10 to init 0 and then boot disk1 all in the same command line from a SSH window. That way once you hit enter it then performs the init 0 and then does the boot disk1. ... (2 Replies)
Discussion started by: tording99z28
2 Replies

6. Ubuntu

grub problem - unable to boot

I am not able to boot into my ubuntu. Grub gives me this message How do I boot linux? (6 Replies)
Discussion started by: locoroco
6 Replies

7. Solaris

V445 unable to boot because of an error

This is what is displayed on the screen as the system tries to boot and then hangs: 0>Test CPU(s)....Done 0>Interrupt Crosscall....| SC Alert: DHCP negotiation failed, perhaps misconfigured or no DHCP server avail able Done 0>Init Memory....| SC Alert: Host System has Reset 'Done 0>PLL... (2 Replies)
Discussion started by: kenosongo
2 Replies

8. Solaris

Solved: Disk Unable to Boot

Update: The / file system (/dev/rdsk/c1t0d0s0) is being checked fsck unable to stat WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0). Root password for system maintenance (control-d to bypass): I am unable to hit control-d to by pass. I... (50 Replies)
Discussion started by: br1an
50 Replies

9. Ubuntu

Unable to boot Ubuntu server 15.10

Hi; I had Windows Server 2003 and performed a fresh Ubuntu Server 15 installation. After installation, Ubuntu server not booting I guess there is boot problem conflicting with my old Windows Server. This is my pastebin: http://paste.ubuntu.com/13851828/ Any help to start my new... (1 Reply)
Discussion started by: gc_sw
1 Replies

10. Red Hat

Unable to boot up after P2V

Hi, I just P2V an old machine running Redhat 5.5 on a physical server. After P2V was completed, when boot up it got an error. Please refer to the attachment for the error. Please assist. Thanks. (2 Replies)
Discussion started by: freshmeat
2 Replies
metaroot(1M)															      metaroot(1M)

NAME
metaroot - setup system files for root (/) metadevice SYNOPSIS
/usr/sbin/metaroot -h /usr/sbin/metaroot [-n] [-k system-name] [-v vfstab-name] [-c mddb.cf-name] [-m md.conf-name] [-R root-path] device The metaroot command edits the /etc/vfstab and /etc/system files so that the system may be booted with the root file system (/) on an appropriate metadevice. The only metadevices that support the root file system are a stripe with only a single slice or a mirror on a sin- gle-slice stripe. If necessary, the metaroot command can reset a system that has been configured to boot the root file system (/) on a metadevice so that it uses a physical slice. Root privileges are required for all of the following options except -h. The following options are supported: -c mddb.cf-name Use mddb.cf-name instead of the default /etc/lvm/mddb.cf file as a source of metadevice database locations. -h Display a usage message. -k system-name Edit a user-supplied system-name instead of the default /etc/system system configuration information file. -m md.conf-name Edit the configuration file specified by md.conf-name rather than the default, /kernel/drv/md.conf. -n Print what would be done without actually doing it. -R root-path When metaroot modifies system files, it accesses them in their relative location under root-path. The -R option cannot be used in combination with the -c, -k,-m, or -v options. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). -v vfstab-name Edit vfstab-name instead of the default /etc/vfstab table of file system defaults. The following operands are supported: device Specifies either the metadevice or the conventional disk device (slice) used for the root file system (/). Example 1: Specifying Root File System on Metadevice The following command edits /etc/system and /etc/vfstab to specify that the root file system is now on metadevice d0. # metaroot d0 Example 2: Specifying Root File System on SCSI Disk The following command edits /etc/system and /etc/vfstab to specify that the root file system is now on the SCSI disk device /dev/dsk/c0t3d0s0. # metaroot /dev/dsk/c0t3d0s0 /etc/system System configuration information file. See system(4). /etc/vfstab File system defaults. /etc/lvm/mddb.cf Metadevice state database locations. /kernel/drv/md.conf Configuration file for the metadevice driver, md. The following exit values are returned: 0 Successful completion. >0 An error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metarename(1M), metareplace(1M), metaset(1M), metassist(1M), metastat(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), md(7D) 6 Apr 2005 metaroot(1M)
All times are GMT -4. The time now is 03:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy