Cannot Open Mirrored Root Device Error 19 Solaris 10
OS Previous to Solaris Express 4/06 ReleaseSolaris Express Developer Edition Release NotesPrevious: Solaris Express 7/06 IssuesNext: smosservice add Command Does Not Install Designated ARCH=all Packages (4871256)Solaris Volume Manager Not Starting on Systems That Revert to Solaris OS Previous to Solaris Express 4/06 Release You encounter problems with starting the Solaris Volume Manager if you perform the following procedures on your system: Upgrade to the Solaris Express 4/06 OS or a subsequent release that contains the new Solaris Volume Manager support for descriptive names. Create volumes and hot-spare pools, which Solaris Volume Manager automatically configures with descriptive names. Without removing these components, revert to a Solaris OS previous to the Solaris Express 4/06 release currently in the system. The Solaris Volume Manager in the previous Solaris OS does not recognize the components with descriptive names. Consequently, in the reverted Solaris release, the Solaris Volume Manager does not start. The following error message is displayed: svc:/system/mdmonitor:default: Method "/lib/svc/method/svc-mdmonitor" failed with exit status 1. system/mdmonitor:default failed The system also panics and displays a message similar to the following: Cannot open mirrored root device, error 19 Cannot remount root on /pseudo/md@0:0,10,blk fstype ufs panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root 000000000180b950 genunix:vfs_mountroot+344 (18831f0, 2021, 18831f0, 18621a8, 18362c0, 185d760) %l0-3: 00000000018362c0 000000000185d400 000000000183b400 00000000011e6400 %l4-7: 0000000000000001 0000000000008025 000000000185d518 00000000018831f0 000000000180ba10 genunix:main+98 (18141a0, 1013400, 18362c0, 18aa000, 180e000, 1814000) %l0-3: 0000000070002000 0000000000000001 000000000180c000 000000000180e000 %l4-7: 0000000000000001 0000000001074400 0000000000000060 0000000000000000 Workaround: All Solaris Volume Manager components that you created subsequent to the OS upgrade use descriptive names. Remove these components first before performing the OS reversion. Follow these steps: Become superuser. With the metastat -D command, list the metadevices and hot-spare pools that use descriptive names.
briefly discussing the three most frequent causes : malware, uncontrolled applications, and lack of care, because several readers write about their computer reacting slowly. Malware Perhaps the greatest factor to a badly performing computer is malware. Usually this is associated with downloading an application that contains spyware, by not having browser security settings large enough, by carelessly downloading P2P files, or by declining to install security patches regularly. Step 1. Revise https://docs.oracle.com/cd/E19082-01/820-0543/gcwfh/index.html the explanations of your anti-virus and operate a complete scan of your hard disk in Safe Mode. Solve any unfixable problems. Notice that some infections require additional steps until they could be removed; typically a web search will locate specific instructions or a particular removal tool. If you fail to find a solution, use the BC forums http://www.nonabyte.net/cannot-open-mirrored-root-device-error-19/ to obtain help. 2. If the sluggishness is abrupt, and you've recently downloaded an application, the issue might reside there. Test this by completely eliminating it. A sensible user will usually perform a internet search about the application before installing because in most cases, any potential difficulty with malware or inferior performance will have surfaced. Step 3. Adware and Spyware can drastically impact your personal computer's functionality, and these are throughout the Net. Revise the definitions of your anti spyware programs and scan your hard drives in Safe Mode. Seasoned users will consistently run two or three of these programs, because each company has its own standards for what constitutes spyware and will simply search against their own established. (A listing of really good, free anti-spyware programs is given by BC). Again, solve any open issues before proceeding to the next phase. For further reading about Malware and some malware removal applications, use BC's Tutorial section; most of the programs have very good Help files that clarify how th
is a Sun Fire V125 and the version of the OS is 06/06. A non-mirrored Jumpstart is http://unix.derkeiler.com/Newsgroups/comp.unix.solaris/2007-03/msg01025.html fine. The profile of the working install looks like this: install_type initial_install system_type standalone cluster SUNWCreq partitioning explicit filesys c1t0d0s0 16384 / filesys c1t0d0s1 16384 swap http://schalwad.blogspot.com/2013/11/server-panic.html filesys c1t0d0s3 16384 /var filesys c1t0d0s4 free /opt filesys c1t0d0s5 4096 /tmp filesys c1t0d0s7 4096 /meta The config when I attempt to mirror the root disk cannot open at install time looks like this: install_type initial_install system_type standalone metadb c1t0d0s7 size 8192 count 2 metadb c1t1d0s7 size 8192 count 2 cluster SUNWCreq partitioning explicit filesys mirror:d10 c1t0d0s0 c1t1d0s0 16384 / filesys mirror:d20 c1t0d0s1 c1t1d0s1 16384 swap filesys mirror:d30 c1t0d0s3 c1t1d0s3 16384 /var filesys mirror:d40 c1t0d0s4 c1t1d0s4 free /opt filesys mirror:d50 cannot open mirrored c1t0d0s5 c1t1d0s5 4096 /tmp The install appears to go through okay, but when the system reboots, I get a panic: Rebooting with command: boot Boot device: /pci@1c,600000/scsi@2/disk@0,0:a File and args: SunOS Release 5.10 Version Generic_118833-17 64-bit Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Cannot open mirrored root device, error 19 Cannot remount root on /pseudo/md@0:0,10,blk fstype ufs panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root 000000000180b950 genunix:vfs_mountroot+310 (8025, 1882fb0, 185d400, 18621a0, 1883000, 185d760) %l0-3: 0000060000835a40 0000000000000003 0000000000000002 00000000011e5400 %l4-7: 00000000018362c0 000000000183b400 000000000185d400 0000000000000001 000000000180ba10 genunix:main+98 (18141a0, 1013800, 18362c0, 18ab800, 180e000, 1814000) %l0-3: 0000000070002000 0000000000000001 000000000180c000 000000000180e000 %l4-7: 0000000000000001 0000000001074800 0000000000000060 0000000000000000 syncing file systems... done skipping system dump - no dump device configured rebooting... I'm not sure if this is a misconfiguration on my part, or a bug I've stumbled upon. Does anyone have any ideas? Thanks in advance. JR . Follow-Ups: Re: Jumpstart problem with mirrored root From: T
having exposure on VXVM, Clustering, Virtualization etc.,. If you find something useful, a comment would be appreciated to let other viewers also know that the solution/method work(ed) for you. Monday, November 18, 2013 server panic Problem System will panic after encapsulation of the boot disk with error NOTICE: VxVM vxio V-5-0-74 Cannot open disk ROOTDISK: kernel error 6 Cannot open mirrored root device, error 6 Cannot remount root on /pseudo/vxio@0:0 fstype ufs Error NOTICE: VxVM vxio V-5-0-74 Cannot open disk ROOTDISK: kernel error 6 Cannot open mirrored root device, error 6 Cannot remount root on /pseudo/vxio@0:0 fstype ufs panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root 000000000180b950 genunix:vfs_mountroot+380 (21, 2000, 18d21d0, 18aedf8, 18a9800, 18a9a80) %l0-3: 0000000000000001 0000000000008025 00000600530b2080 000000000127b800 %l4-7: 00000000018a9838 00000600530b2080 00000000018d21d0 0000000000002021 000000000180ba10 genunix:main+9c (0, 180c000, 185ed90, 182b768, 1831b48, 18f3800) %l0-3: 000000000180c000 000000000180c000 0000000070002000 0000000000000000 %l4-7: 0000000001866400 0000000000000000 000000000180c000 0000000000000001 syncing file systems... done Environment Storage Foundation Version 5.x, 4.x on Solaris 10, 9, 8 Solution MPXIO in Solaris 10 allow the multipathing to the disk and have same function as Veritas Vxdmp. When the below dmp_tpd_root_device="/pseudo/vxio@0:0"; was added to /kernel/drv/vxdmp.conf , the system reboot with MPXIO enable on the boot disk, vxvm can not find the boot device on the 2nd boot and hence it panic. No core file will be collected because root was not mounted. Comment out or delete the above line in /kernel/drv/vxdmp.conf will allow the system boot up normally # dmp_tpd_root_device="/pseudo/vxio@0:0"; <=== comment out this entry. Posted by santosh chalwad at 5:14 PM Reactions: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Archive Blog Archive September (4) June (10) April (3) March (2) February (5) January (4) November (39) October (17) August (3) June (14) April (13) January (19) December (297) November (71) Search Translate Follow