Sponsored Content
Operating Systems Solaris vxvm root disk booting problem - solved with boot -a. How? Post 302399151 by badoshi on Friday 26th of February 2010 12:57:46 PM
Old 02-26-2010
vxvm root disk booting problem - solved with boot -a. How?

Hi All,

We had a Sun Netra T1 go down the other day, the root disk was mirrored using vxvm. Upon boot from either disk, we had the following error appear:

Code:
    WARNING: Error writing ufs log state
    WARNING: ufs log for / changed state to Error
    WARNING: Please umount(1M) / and run fsck(1M)
    WARNING: Error writing master during ufs log roll
    WARNING: ufs log for / changed state to Error
    WARNING: Please umount(1M) / and run fsck(1M)
    Cannot mount root on /pseudo/vxio@0:0 fstype ufs
    panic[cpu0]/thread=140a000: vfs_mountroot: cannot mount root

no problems i thought. I'm well aware of this issue with VX. However I discovered I couldn't boot from vx root or mirror (same errors), we tried the cd, and the that failed too (suspected broken cdrom).

having given up all hope, I randomly tried a 'boot -a' (accepting all defaults) which somehow got me into multiuser, but with no vxvm partitions installed, or vx processes running. From there we were able to recover the system.

Can anyone shed any light as to how or why 'boot -a' worked? Not being a VX guy, I'm really scratching my head, and can't recreate this problem.

TIA.

Last edited by badoshi; 02-26-2010 at 02:06 PM..
 

10 More Discussions You Might Find Interesting

1. SCO

sco openserver 5.0.0 boot / root disk

Hi, I have an openserver 5.0.0 machine in the office. The sysad of that machine left years ago without leaving the password to anyone. I was wondering if someone has a copy of the boot / root diskettes (rescue) for this version? Or perhaps if anyone knows a download link / location in the... (0 Replies)
Discussion started by: marcpascual
0 Replies

2. Solaris

Migrate VxVM boot disks to higher capacity disk

Hi, Im getting a downtime of 4 hrs to do porting of bootdisks. Currently, the system is running on Sf4800. 2 internal disk 36G connected to a SE3510 storage. We're getting 72G disks and we want to restore the OS from the current 36G to the 72G disk. System is under veritas volume manager ctrl.... (4 Replies)
Discussion started by: incredible
4 Replies

3. Solaris

( VxVM ) How to add the removed disk back to previous disk group

Previously , i remove the disk by #vxdg -g testdg -k rmdisk testdg02 But i got error when i -k adddisk bash-2.03# vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - online invalid c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies

4. Solaris

Problem by cloning boot disk.

Hello guys! I use the Solaris 10 x86 machine. I need to clone the boot disk. Why, when I copy slice 1 - there is a following: # ufsdump 0f - /dev/rdsk/c0d0s1 | (cd /mnt && ufsrestore rf - ) DUMP: Warning - super-block on device `/dev/rdsk/c0d01` is corrupt - run fsck Dump: The Entire... (6 Replies)
Discussion started by: wolfgang
6 Replies

5. Solaris

Lost Root Password on VXVM Encapsulated Root Disk

Hi All Hope it's okay to post on this sub-forum, couldn't find a better place I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies

6. Solaris

Unable to boot from mirror disk on x86 server configured under VxVM

Hi, Can you help me on booting x86 server configured under VxVM. Server boots fine normally from both the disks but if I try to boot server from mirror disk without starting veritas, then it does not boot. vxplex -g rootdg dis var-02 vxplex -g rootdg dis swapvol-02 vxplex -g rootdg dis... (2 Replies)
Discussion started by: milindphanse604
2 Replies

7. 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

8. Red Hat

Booting 2nd mirrored boot disk

Hi guys, thanks for helping out. If you have two boot disk mirrored and your primary boot disk fails, how will you boot the system from the second disk? Thank you very much for your assistance on this matter. Arrey (5 Replies)
Discussion started by: cjashu
5 Replies

9. UNIX for Dummies Questions & Answers

[Solved] Boot Failure - Openindiana w/ Napp-it - Full Root?

Came home the other day to a Napp-it Gui that would not load. Login would appear but when i attempted I would get the following Set default permissions and reading disk and pool parameter, please wait.. in case of problems, try a reboot after Power-Off or check disk and pool status at CLI.... (1 Reply)
Discussion started by: fastedd27
1 Replies

10. HP-UX

Removing a VxVM disk from a Disk Group

Hello all, So I made a rookie mistake today. I forgot to remove my disk from my disk group, before running the following command:for i in `ioscan -fnN | awk /NO/'{print $3}'` do rmsf -H $i done I am trying to run the following command, but not having any luck obviously:vxdg -g dgvol1 rmdisk... (0 Replies)
Discussion started by: mrkejames2
0 Replies
vxsited(1M)															       vxsited(1M)

NAME
vxsited - site monitoring daemon SYNOPSIS
/etc/vx/bin/vxsited [mail_address...] DESCRIPTION
The vxsited daemon monitors Veritas Volume Manager (VxVM) for disks being attached, and reattaches a detached site if the disks that belong to that site become accessible. vxsited analyzes the output of the vxnotify command, and waits for a failed disk to attach. When a disk is attached, vxsited attempts to online the disk, and tries to reattach the failed site. If a site is successfully reattached, vxsited starts recovery using vxrecover, and sends mail to root (by default) or to other specified users. Mail Notification By default, vxsited sends mail to root with information about the disk status of any attempts to reattach the site. To send mail to other users, add the user login name to the line that starts vxsited in the startup script, /etc/init.d/vxvm-recover, and reboot the system. For example, if the line appears as: nohup vxsited root & and you want mail also to be sent to user1 and user2, change the line to read: nohup vxsited root user1 user2 & Alternatively, kill the vxsite process, and restart it from the command line with the required mail addresses as arguments. The mail notification has a format that is similar to the following: Subject : Volume Manager site reattach on host hostname Reattached site sitename in disk-group diskgroup Reattachment Procedure If a disk from a detached site becomes accessible again, vxsited checks whether the relocation daemon, vxrelocd, is running. If vxrelocd is running, vxsited attempts to reattach the site. The relocation daemon can then try to relocate the failed subdisks using space on the available disks in the disk group. If the failed objects are successfully relocated, vxrelocd changes the state of the site to RECOVER, and starts the recovery of volumes at the site. When all the plexes at a site have been recovered, the plexes are put into the ACTIVE state, and the state of the site is set to ACTIVE. If vxrelocd is not running, vxsited only reattaches a site when all the disks from that site become accessible. After successfully reat- taching a site, vxsited changes the site state to ACTIVE, and initiates recovery using vxrecover. When all the plexes from a site have been recovered, the plexes are put into the ACTIVE state, and the state of the site is set to ACTIVE. vxsited does not attempt to reattach a site that has been explicitly detached by an administrator. The state OFFLINE is set for sites that have been detached by using the following command: vxdg -g dg_name detachsite sitename Disabling vxsited If you do not want a site to be recovered automatically, kill the vxsited daemon, and prevent it from restarting. To kill the daemon, run the following command from the command line, and locate the process table entry for vxsited: ps -ef Execute the command: kill -9 PID Substitute the process ID of the vxsited process for PID. To prevent vxsited from being restarted, comment out the line that starts vxsited in the startup script /sbin/init.d/vxvm-recover. FILES
/sbin/init.d/vxvm-recover The startup file for vxsited. SEE ALSO
kill(1), mailx(1), ps(1), vxdg(1M), vxrelocd(1M), vxintro(1M), vxnotify(1M), vxrecover(1M) VxVM 5.0.31.1 24 Mar 2008 vxsited(1M)
All times are GMT -4. The time now is 09:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy