Sponsored Content
Operating Systems Solaris Restoring a Root File System that was on a metadevice Post 302528583 by feg on Tuesday 7th of June 2011 12:23:37 PM
Old 06-07-2011
I get the error bellow, and most of the commands don't work


Quote:
WARNING: system call missing from bind file
WARNING: Cannot mount /etc/dfs/sharetab

Failed to configure IPv4 interface(s): e1000g0
NOTICE: nxge0: xcvr addr:0x0d - link is down
NOTICE: nxge1: xcvr addr:0x0c - link is down
Hostname: tn-06
NOTICE: nxge0: xcvr addr:0x0d - link is up 100 Mbps full duplex
NOTICE: nxge1: xcvr addr:0x0c - link is up 100 Mbps full duplex

WARNING: The following files in / differ from the boot archive:


The recommended action is to reboot to the failsafe archive to correct
the above inconsistency. To accomplish this, on a GRUB-based platform,
reboot and select the "Solaris failsafe" option from the boot menu.
On an OBP-based platform, reboot then type "boot -F failsafe". Then
follow the prompts to update the boot archive. Alternately, to continue
booting at your own risk, you may clear the service by running:
"svcadm clear system/boot-archive"

Jun 7 15:24:41 svc.startd[7]: svc:/system/boot-archive:default: Method "/lib/svc/method/boot-archive" failed with exit status 95.
Jun 7 15:24:41 svc.startd[7]: system/boot-archive:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run

Root password for system maintenance (control-d to bypass): Jun 7 15:24:42 svc.startd[7]: svc:/network/iscsi/initiator:default: Method "/lib/svc/method/iscsid" failed with exit status 255.
Jun 7 15:24:42 svc.startd[7]: svc:/network/iscsi/initiator:default: Method "/lib/svc/method/iscsid" failed with exit status 255.
Jun 7 15:24:42 svc.startd[7]: svc:/network/iscsi/initiator:default: Method "/lib/svc/method/iscsid" failed with exit status 255.
Jun 7 15:24:42 svc.startd[7]: network/iscsi/initiator:default failed: transitioned to maintenance (see 'svcs -xv' for details)
WARNING: ncp0: unable to determine ncp (cpu) binding (ncp)
---------- Post updated at 11:23 AM ---------- Previous update was at 11:22 AM ----------

i tried to do run "svcadm clear system/boot-archive" in falsafe mode, but it didn't work
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

URGENT, root file system is 99%

help, urgently root file is 99% hi, this iptrace causes my root file system to be 99%. iptrace writes to a file but i didn not specify any file so how? and how to reduce my root file system since i suspect that it is iptrace which causes this.? thanks (8 Replies)
Discussion started by: yls177
8 Replies

2. Filesystems, Disks and Memory

root file system full

Hi I have a Solaris 2.5.1 system. Recently my file system is full and i couldn't find what flood my root file system. Anyone can suggext any directories i should look out for. I am using Samba and Patrol agent. I am just usng this server as a file server, users cannot login into the system,... (1 Reply)
Discussion started by: owls
1 Replies

3. HP-UX

Root File system Space

Hi I'm using HP-UX 11.00, the root file system is as shown below. Several time it reach 100% used, to free some space I use to reboot the system. What can I do to free some space without rebooting the machine? Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol3 ... (2 Replies)
Discussion started by: cgege
2 Replies

4. Solaris

Root file system is 82% full

Hi I want to find out the reason that why root partition is 82% full? when i did fu -k / then most of files were created on /var . can you please help me to find out what I need to do in order to find the reason. Regards Ajwat (2 Replies)
Discussion started by: Ajwat
2 Replies

5. Solaris

Why Veritas is not used for root file system.

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)
Discussion started by: Reboot
3 Replies

6. UNIX for Advanced & Expert Users

how to make a full system backup excluding data and restoring it to a new system

Hi, In order to have a sand box machine that I could use to test some system changes before going to production state, I'd like to duplicate a working system to a virtual one. Ideally, I'd like to manage to do it this way : - Make a full system backup excluding the user file system (this... (7 Replies)
Discussion started by: pagaille
7 Replies

7. Solaris

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: #more /etc/vfstab... (0 Replies)
Discussion started by: faberarnold
0 Replies

8. UNIX for Dummies Questions & Answers

Root File System

Hi, Please someone tell me, what are the contents of root file sysytem? and significance of it, what are all possible ways to mount root file system? (5 Replies)
Discussion started by: laxmi Sharma
5 Replies

9. Solaris

Migration of system having UFS root FS with zones root to ZFS root FS

Hi All After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies

10. Solaris

Restoring a system from a backup

I have backed up the contents of my Solaris 10 machine in its entirety, and I'm trying to figure out if I can somehow use this archive to restore my old system just as it was on a new machine. Assuming I have all files from my old machine backed up, is this possible? What I've been trying to do... (6 Replies)
Discussion started by: unblockable
6 Replies
installgrub(1M)                                                                                                                    installgrub(1M)

NAME
installgrub - install GRUB in a disk partition or a floppy SYNOPSIS
/sbin/installgrub [-fm] stage1 stage2 raw-device The installgrub command is an -only program. GRUB stands for GRand Unified Bootloader. installgrub installs GRUB stage 1 and stage 2 files on the boot area of a disk partition. If you specify the -m option, installgrub installs the stage 1 file on the master boot sector of the disk. The installgrub command accepts the following options: -f Suppresses interaction when overwriting the master boot sector. -m Installs GRUB stage1 on the master boot sector interactively. The installgrub command accepts the following operands: stage1 The name of the GRUB stage 1 file. stage2 The name of the GRUB stage 2 file. raw-device The name of the device onto which GRUB code is to be installed. It must be a character device that is readable and writable. For disk devices, specify the slice where the GRUB menu file is located. (For Solaris it is the root slice.) For a floppy disk, it is /dev/rdiskette. Example 1: Installing GRUB on a Hard Disk Slice The following command installs GRUB on a system where the root slice is c0d0s0: example# /sbin/installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c0d0s0 Example 2: Installing GRUB on a Floppy The following command installs GRUB on a formatted floppy: example# mount -F pcfs /dev/diskette /mnt # mkdir -p /mnt/boot/grub # cp /boot/grub/* /mnt/boot/grub # umount /mnt # cd /boot/grub # /sbin/installgrub stage1 stage2 /dev/rdiskette /boot/grub Directory where GRUB files reside. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ boot(1M), fdisk(1M), fmthard(1M), kernel(1M), attributes(5) Installing GRUB on the master boot sector (-m option) overrides any boot manager currently installed on the machine. The system will always boot the GRUB in the Solaris partition regardless of which fdisk partition is active. 24 May 2005 installgrub(1M)
All times are GMT -4. The time now is 04:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy