If so, the manufacturer (Oracle) has issued instructions to be followed in the event of this crash.
Ref:
Or have you already tried that and are telling us it didn't work?
This is a known problem (you're not on your own here) and you will find other helpful information if you search the web for the error "SMF_EXIT_ERR_FATAL"
Did you have spare unallocated space on the RAID 1 volume immediately after the root filesystem location? AKAIK, you cannot dynamically expand a RAID 1 volume on the on-board RAID controller on the T5220.
Did you use Volume Manager to expand a ZFS root volume? AFAIK, you cannot do that whilst booted from that root filesystem. You would need to boot from CD/DVD to do that.
That link refers to Sun Volume Manager if that is what you are using? Being a T5220 it has an onboard hardware RAID controller configured using the 'raidctl' command so I thought it would be using that. Do you know which the system is using??
If yes then...
If your growfs command did not give an error then I suspect a bug in the Solaris volume manager.
The following article suggests to run a forced fsck, and that would be
bash-3.2# mount -o rw,remount /dev/md/dsk/d10 /
mount: The state of /dev/md/dsk/d10 is not okay
and it was attempted to be mounted read/write
mount: Please run fsck and try again
bash-3.2#
But after reboot system starting to maintenance mode
Boot device: rootdisk File and args:
SunOS Release 5.10 Version Generic_150400-44 64-bit
Copyright (c) 1983, 2016, Oracle and/or its affiliates. All rights reserved.
Hostname: saromea4
Dec 16 16:55:06 svc.startd[9]: svc:/system/sysevent:default: Method "/lib/svc/method/svc-syseventd start" failed with exit status 95.
Dec 16 16:55:06 svc.startd[9]: system/sysevent: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):
I think the problem is in the file system, but I can't find how to see what the problem is.
# metadb
flags first blk block count
a m p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
a p luo 16400 8192 /dev/dsk/c1t0d0s7
a p luo 16 8192 /dev/dsk/c1t1d0s7
a p luo 8208 8192 /dev/dsk/c1t1d0s7
a p luo 16400 8192 /dev/dsk/c1t1d0s7
#
____________________________________________________________________________
# metastat d10
d10: Mirror
Submirror 0: d11
State: Needs maintenance
Submirror 1: d12
State: Needs maintenance
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 286596864 blocks (136 GB)
d11: Submirror of d10
State: Needs maintenance
Invoke: metasync d10
Size: 286596864 blocks (136 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t0d0s0 0 No Okay Yes
Stripe 1:
Device Start Block Dbase State Reloc Hot Spare
c1t0d0s1 0 No Okay Yes
d12: Submirror of d10
State: Needs maintenance
Invoke: metasync d10
Size: 286596864 blocks (136 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t1d0s0 0 No Okay Yes
Stripe 1:
Device Start Block Dbase State Reloc Hot Spare
c1t1d0s1 0 No Okay Yes
Device Relocation Information:
Device Reloc Device ID
c1t0d0 Yes id1,sd@n5000cca00a1932fc
c1t1d0 Yes id1,sd@n5000c50032388e17
#
And /etc/system contain only mirror device
# cat /etc/system
*ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
*
* SYSTEM SPECIFICATION FILE
*
* moddir:
*
* Set the search path for modules. This has a format similar to the
* csh path variable. If the module isn't found in the first directory
* it tries the second and so on. The default is /kernel /usr/kernel
*
* Example:
* moddir: /kernel /usr/kernel /other/modules
* root device and root filesystem configuration:
*
* The following may be used to override the defaults provided by
* the boot program:
*
* rootfs: Set the filesystem type of the root.
*
* rootdev: Set the root device. This should be a fully
* expanded physical pathname. The default is the
* physical pathname of the device where the boot
* program resides. The physical pathname is
* highly platform and configuration dependent.
*
* Example:
* rootfs:ufs
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
*
* (Swap device configuration should be specified in /etc/vfstab.)
* exclude:
*
* Modules appearing in the moddir path which are NOT to be loaded,
* even if referenced. Note that `exclude' accepts either a module name,
* or a filename which includes the directory.
*
* Examples:
* exclude: win
* exclude: sys/shmsys
* forceload:
*
* Cause these modules to be loaded at boot time, (just before mounting
* the root filesystem) rather than at first reference. Note that
* forceload expects a filename which includes the directory. Also
* note that loading a module does not necessarily imply that it will
* be installed.
*
* Example:
* forceload: drv/foo
* set:
set msgsys:msginfo_msgtql=1024
set msgsys:msginfo_msgmnb=65536
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmni=400
set semsys:seminfo_semmns=2048
set semsys:seminfo_semmni=126
set semsys:seminfo_semmsl=260
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
set rlim_fd_cur=8193
set rlim_fd_max=8193
* Set an integer variable in the kernel or a module to a new value.
* This facility should be used with caution. See system(4).
*
* Examples:
*
* To set variables in 'unix':
*
* set nautopush=32
* set maxusers=40
*
* To set a variable named 'debug' in the module named 'test_module'
*
* set test_module:debug = 0x13
set md:mirrored_root_flag = 1
* Begin MDD root info (do not edit)
rootdev:/pseudo/md@0:0,10,blk
* End MDD root info (do not edit)
I don't know what else I can do.
Because it all looks kind of weird.
I have another disk in this server.
Can I transfer everything to it and make the disk bootable and then, and then rebuild the raid?
# prtvtoc /dev/md/rdsk/d10
* /dev/md/rdsk/d10 partition map
*
* Dimensions:
* 512 bytes/sector
* 848 sectors/track
* 24 tracks/cylinder
* 20352 sectors/cylinder
* 14082 cylinders
* 14082 accessible cylinders
*
* Flags:
* 1: unmountable
* 10: read-only
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 0 00 0 286596864 286596863
# mount
/ on /pseudo/md@0:0,10,blk read/write/setuid/devices/rstchown/dev=154000a on Thu Jan 1 03:00:00 1970
/devices on /devices read/write/setuid/devices/rstchown/dev=5840000 on Fri Dec 16 17:57:44 2022
/system/contract on ctfs read/write/setuid/devices/rstchown/dev=5880001 on Fri Dec 16 17:57:44 2022
/proc on proc read/write/setuid/devices/rstchown/dev=58c0000 on Fri Dec 16 17:57:44 2022
/etc/mnttab on mnttab read/write/setuid/devices/rstchown/dev=5900001 on Fri Dec 16 17:57:44 2022
/etc/svc/volatile on swap read/write/setuid/devices/rstchown/xattr/dev=5940001 on Fri Dec 16 17:57:44 2022
/system/object on objfs read/write/setuid/devices/rstchown/dev=5980001 on Fri Dec 16 17:57:44 2022
/etc/dfs/sharetab on sharefs read/write/setuid/devices/rstchown/dev=59c0001 on Fri Dec 16 17:57:44 2022
/platform/sun4v/lib/libc_psr.so.1 on /platform/SUNW,SPARC-Enterprise-T5220/lib/libc_psr/libc_psr_hwcap2.so.1 read/write/setuid/devices/rstchown/dev=154000a on Fri Dec 16 17:58:01 2022
/platform/sun4v/lib/sparcv9/libc_psr.so.1 on /platform/SUNW,SPARC-Enterprise-T5220/lib/sparcv9/libc_psr/libc_psr_hwcap2.so.1 read/write/setuid/devices/rstchown/dev=154000a on Fri Dec 16 17:58:01 2022
/dev/fd on fd read/write/setuid/devices/rstchown/dev=5b40001 on Fri Dec 16 17:58:04 2022
/tmp on swap read/write/setuid/devices/rstchown/xattr/dev=5940002 on Fri Dec 16 17:58:05 2022
/var/run on swap read/write/setuid/devices/rstchown/xattr/dev=5940003 on Fri Dec 16 17:58:05 2022
#
#
#
# pwd
/
# touch test.txt
touch: cannot create test.txt: Read-only file system
#