Help for add disk on solaris8

UNIX Solaris
1

Hi, boss
i have a question about the system add the new disk. I add 6 disks in Sunfire 880, i want to put these 6 disks in to service but i do not want re-install the system, some guys can give me some advie on this case?
thanks very much

the follow is detail
0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000870f13a8,0
1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000870fa094,0
2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000870f3e6d,0
3. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000870faf1e,0
4. c1t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w210000008710d0c6,0
5. c1t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100000087120971,0
6. c1t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871381c9,0
7. c1t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w210000008713700a,0
8. c1t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100000087137f97,0
9. c1t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100000087136623,0
10. c2t1d0 <SUN-T300-0201 cyl 34901 alt 2 hd 224 sec 128>
/pci@9,700000/SUNW,qlc@2/fp@0,0/ssd@w50020f2300010d6e,0
11. c3t1d0 <SUN-T300-0201 cyl 34901 alt 2 hd 224 sec 128>
/pci@9,700000/SUNW,qlc@3/fp@0,0/ssd@w50020f23000111a6,0

the red part is new disk, and now the disks is recongnized by system.

thanks very much!

2

where is your problem? your system is on c1t0d0? the new disks can be seen by solaris.... label them, give them a filesystem, mount them and you are done...

3

The problem is i dont know whether the new 6 disks can be used....from the mount informat as below...i can not find the C1t8 to C1t13
and how to label them how to give them a file sysetem...and...mount....

/ on /dev/dsk/c1t0d0s0 read/write/setuid/intr/largefiles/logging/onerror=panic/dev=1d80018 on Wed Apr 13 16:39:21 2005
/usr on /dev/dsk/c1t0d0s3 read/write/setuid/intr/largefiles/logging/onerror=panic/dev=1d8001b on Wed Apr 13 16:39:22 2005
/proc on /proc read/write/setuid/dev=40c0000 on Wed Apr 13 16:39:21 2005
/dev/fd on fd read/write/setuid/dev=4180000 on Wed Apr 13 16:39:23 2005
/etc/mnttab on mnttab read/write/setuid/dev=4280000 on Wed Apr 13 16:39:24 2005
/var on /dev/dsk/c1t0d0s5 read/write/setuid/intr/largefiles/logging/onerror=panic/dev=1d8001d on Wed Apr 13 16:39:24 2005
/var/run on swap read/write/setuid/dev=1 on Wed Apr 13 16:39:25 2005
/opt on /dev/dsk/c1t0d0s4 read/write/setuid/intr/largefiles/logging/onerror=panic/dev=1d8001c on Wed Apr 13 16:39:27 2005
/home on /dev/dsk/c1t0d0s6 read/write/setuid/intr/largefiles/logging/onerror=panic/dev=1d8001e on Wed Apr 13 16:39:27 2005
/tmp on swap read/write/setuid/dev=2 on Wed Apr 13 16:39:27 2005
/OMCbase on /dev/dsk/c1t1d0s0 read/write/setuid/intr/largefiles/logging/onerror=panic/dev=1d80010 on Wed Apr 13 16:39:27 2005
/MISCELLANEOUS on /dev/dsk/c1t1d0s1 read/write/setuid/intr/largefiles/logging/onerror=panic/dev=1d80011 on Wed Apr 13 16:39:27 2005
/CMN/base on /OMCbase/CMN/base read/write/setuid/dev=1d80010 on Wed Apr 13 16:39:27 2005
/OMC/base on /OMCbase/OMC/base read/write/setuid/dev=1d80010 on Wed Apr 13 16:39:28 2005
/MD/base on /OMCbase/MD/base read/write/setuid/dev=1d80010 on Wed Apr 13 16:39:28 2005
/SDO/base on /OMCbase/SDO/base read/write/setuid/dev=1d80010 on Wed Apr 13 16:39:28 2005
/OMCdata on /dev/md/DISKSET1/dsk/d5 read/write/setuid/intr/largefiles/logging/onerror=panic/dev=1542005 on Wed Apr 13 16:41:51 2005
/OMC/data on /OMCdata/OMC/data read/write/setuid/dev=1542005 on Wed Apr 13 16:41:52 2005
/OMC/obs on /OMCdata/OMC/obs read/write/setuid/dev=1542005 on Wed Apr 13 16:41:52 2005
/OMC/maps on /OMCdata/OMC/maps read/write/setuid/dev=1542005 on Wed Apr 13 16:41:52 2005
/CMN/data on /OMCdata/CMN/data read/write/setuid/dev=1542005 on Wed Apr 13 16:41:52 2005
/MD/data on /OMCdata/MD/data read/write/setuid/dev=1542005 on Wed Apr 13 16:41:52 2005
/MD/ssn on /OMCdata/MD/ssn read/write/setuid/dev=1542005 on Wed Apr 13 16:41:52 2005
/MD/notif on /OMCdata/MD/notif read/write/setuid/dev=1542005 on Wed Apr 13 16:41:52 2005
/MD/obs on /OMCdata/MD/obs read/write/setuid/dev=1542005 on Wed Apr 13 16:41:52 2005
/MD/trace_function on /OMCdata/MD/trace_function read/write/setuid/dev=1542005 on Wed Apr 13 16:41:52 2005
/MD/restored on /OMCdata/MD/restored read/write/setuid/dev=1542005 on Wed Apr 13 16:41:52 2005
/MD/scse on /OMCdata/MD/scse read/write/setuid/dev=1542005 on Wed Apr 13 16:41:52 2005
/SDO/data on /dev/md/DISKSET1/dsk/d10 read/write/setuid/intr/largefiles/logging/onerror=panic/dev=154200a on Wed Apr 13 16:41:52 2005
/PCUOAM on /dev/md/DISKSET1/dsk/d15 read/write/setuid/intr/largefiles/logging/onerror=panic/dev=154200f on Wed Apr 13 16:41:52 2005
4

As DukeNuke2 has stated, you need to label the disks (and maybe alter the partitions to suit your needs), create filesystems on the new slices, and then mount them (adding them to /etc/vfstab if you want the mounts to persist across reboots). Of course, you'd probably want to configure volume management to take care of these filesystems and ensure data redundancy.

There is plenty of documentation at docs.sun.com detailing the procedures.

Cheers,
ZB