Solaris Volume Manger SVM - Metadevices Going Into Maintenance Mode Without Any Related Disk/Component I/O Errors
Last updated on FEBRUARY 26, 2018
Applies to:Sun Solaris Volume Manager (SVM) - Version 11.9.0 to 11.11 [Release 11.0]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on x86 (32-bit)
Oracle Solaris on SPARC (32-bit)
After putting the boot disk under Solaris Volume Manager (SVM) control, md_write and md_read errors are seen during reboot and the metadevices are placed into maintenance.
You may see similar messages as these snippets shown below:
These are simple SVM '1-way mirrors' and as such, SVM will put them into 'last erred' state and allow I/O's to continue. Attempts to recover by attaching another submirror fail.
Recent Live-Upgrade from 5.9 -> 5.10 using c0t1d0 slice 4 (new_root) and 5 (new_var) for the alternate boot environment (ABE).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms