Home.... | log in.... | Pub my question! | Sign-up....

Java-index >> General >> Talk to the Sysop

Which disk is being used?

I'm doing testing with Solaris 8 & 10 and Veritas Volume Manager 4.1. Everything is working, and I'm verifying that both my rootdisk and rootmirror are capable of successfull booting. I rebooted the server with 'reboot -- rootmirror' (aliases already configured in eeprom). However, I want to verify that I'm actually useing the disk I requested to boot from. How would I go about checking that the rootmirror disk is the currently booted disk? Thanks in advance.

Tyler

[498 byte] By [blacknight4573] at [2007-11-25 23:38:25]

«« equivalent to inetd.sec
»» a very weird problem (solaris or app issue?)

# 1

Check /var/adm/messages for booting from device vx-rootmir (or whatever your alias is) file and args:

You can grep for args or your alias. After it boots, and VXVM starts, you are using the the volumes which will be both disks, unless one of them fails, and you stay up on the other, regardless of which one you booted from.

jdstoon at 2007-7-5 18:22:17 >

top of Java-index,General,Talk to the Sysop...

# 2

Thank you for the response.

However, I have already looked at the messages log, and searched and searched. But to no avail. I have attatched the reboot process of the messages log...(maybe I'm missing something). I have arrowed the two disks comming online. Is the order of initialization (upon boot time) which decides on the boot disk? Such as ssd1 initialized before ssd0 --> booting with ssd1 as active boot disk?

Nov 15 15:12:00 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.8 Version Generic_117350-08 64-bit

Nov 15 15:12:00 genunix: [ID 678236 kern.info] Ethernet address = 0:3:ba:9:5:56

Nov 15 15:12:00 unix: [ID 389951 kern.info] mem = 4194304K (0x100000000)

Nov 15 15:12:00 unix: [ID 930857 kern.info] avail mem = 4095188992

Nov 15 15:12:00 rootnex: [ID 466748 kern.info] root nexus = Sun Fire 280R (2 X UltraSPARC-III)

Nov 15 15:12:00 rootnex: [ID 349649 kern.info] pcisch0 at root: SAFARI 0x8 0x700000

Nov 15 15:12:00 genunix: [ID 936769 kern.info] pcisch0 is /pci@8,700000

Nov 15 15:12:00 rootnex: [ID 349649 kern.info] pcisch1 at root: SAFARI 0x8 0x600000

Nov 15 15:12:00 genunix: [ID 936769 kern.info] pcisch1 is /pci@8,600000

Nov 15 15:12:00 qlc: [ID 171021 kern.info] Qlogic FCA Driver v20050209-1.40 (0)

Nov 15 15:12:00 qlc: [ID 637753 kern.info] NOTICE: qlc(0): Firmware version 2.1.140

Nov 15 15:12:01 qlc: [ID 686697 kern.info] NOTICE: Qlogic qlc(0): Loop ONLINE

Nov 15 15:12:01 pcisch: [ID 370704 kern.info] PCI-device: SUNW,qlc@4, qlc0

Nov 15 15:12:01 genunix: [ID 936769 kern.info] qlc0 is /pci@8,600000/SUNW,qlc@4

Nov 15 15:12:01 genunix: [ID 936769 kern.info] fp0 is /pci@8,600000/SUNW,qlc@4/fp@0,0

Nov 15 15:12:01 scsi: [ID 799468 kern.info] ssd1 at fp0: name w500000e01073be51,0, bus address e8

--> Nov 15 15:12:01 genunix: [ID 936769 kern.info] ssd1 is /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w500000e01073be51,0

Nov 15 15:12:01 scsi: [ID 365881 kern.info]<SUN72G cyl 14087 alt 2 hd 24 sec 424>

Nov 15 15:12:01 genunix: [ID 408114 kern.info] /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w500000e01073be51,0 (ssd1) online

--> Nov 15 15:12:01 scsi: [ID 799468 kern.info] ssd0 at fp0: name w500000e0107698c1,0, bus address ef

Nov 15 15:12:01 genunix: [ID 936769 kern.info] ssd0 is /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w500000e0107698c1,0

Nov 15 15:12:01 scsi: [ID 365881 kern.info]<SUN72G cyl 14087 alt 2 hd 24 sec 424>

Nov 15 15:12:01 genunix: [ID 408114 kern.info] /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w500000e0107698c1,0 (ssd0) online

Nov 15 15:12:01 scsi: [ID 365881 kern.info] /pci@8,700000/scsi@6 (glm0):

Nov 15 15:12:01 glm0 supports power management.

Nov 15 15:12:01 scsi: [ID 365881 kern.info] /pci@8,700000/scsi@6 (glm0):

Nov 15 15:12:01 Rev. 7 Symbios 53c875 found.

Nov 15 15:12:01 pcisch: [ID 370704 kern.info] PCI-device: scsi@6, glm0

Nov 15 15:12:01 genunix: [ID 936769 kern.info] glm0 is /pci@8,700000/scsi@6

Nov 15 15:12:01 scsi: [ID 365881 kern.info] /pci@8,700000/scsi@6,1 (glm1):

Nov 15 15:12:01 glm1 supports power management.

Nov 15 15:12:01 scsi: [ID 365881 kern.info] /pci@8,700000/scsi@6,1 (glm1):

Nov 15 15:12:01 Rev. 7 Symbios 53c875 found.

Nov 15 15:12:01 pcisch: [ID 370704 kern.info] PCI-device: scsi@6,1, glm1

Nov 15 15:12:01 genunix: [ID 936769 kern.info] glm1 is /pci@8,700000/scsi@6,1

Nov 15 15:12:03 scsi: [ID 193665 kern.info] sd6 at glm0: target 6 lun 0

Nov 15 15:12:03 genunix: [ID 936769 kern.info] sd6 is /pci@8,700000/scsi@6/sd@6,0

Nov 15 15:12:06 swapgeneric: [ID 308332 kern.info] root on /pseudo/vxio@0:0 fstype ufs

Nov 15 15:12:06 pcisch: [ID 370704 kern.info] PCI-device: ebus@5, ebus0

Nov 15 15:12:06 ebus: [ID 521012 kern.info] todds12870 at ebus0: offset 1,300070

Nov 15 15:12:06 genunix: [ID 936769 kern.info] todds12870 is /pci@8,700000/ebus@5/rtc@1,300070Nov 15 15:12:06 rootnex: [ID 349649 kern.info] mc-us30 at root: SAFARI 0x0 0x400000 ...

Nov 15 15:12:06 genunix: [ID 936769 kern.info] mc-us30 is /memory-controller@0,400000

Nov 15 15:12:06 rootnex: [ID 349649 kern.info] mc-us31 at root: SAFARI 0x1 0x400000 ...

Nov 15 15:12:06 genunix: [ID 936769 kern.info] mc-us31 is /memory-controller@1,400000

Nov 15 15:12:06 ebus: [ID 521012 kern.info] se0 at ebus0: offset 1,400000

Nov 15 15:12:06 genunix: [ID 936769 kern.info] se0 is /pci@8,700000/ebus@5/serial@1,400000

Nov 15 15:12:07 unix: [ID 270833 kern.info] cpu0: UltraSPARC-III (portid 0 impl 0x14 ver 0x34 clock 750 MHz)

Nov 15 15:12:07 unix: [ID 270833 kern.info] cpu1: UltraSPARC-III (portid 1 impl 0x14 ver 0x34 clock 750 MHz)

Nov 15 15:12:07 unix: [ID 721127 kern.info] cpu 1 initialization complete - online

Nov 15 15:12:07 ebus: [ID 521012 kern.info] su0 at ebus0: offset 1,3062f8

Nov 15 15:12:07 genunix: [ID 936769 kern.info] su0 is /pci@8,700000/ebus@5/rsc-control@1,3062f8

Nov 15 15:12:07 ebus: [ID 521012 kern.info] su1 at ebus0: offset 1,3083f8

Nov 15 15:12:07 genunix: [ID 936769 kern.info] su1 is /pci@8,700000/ebus@5/rsc-console@1,3083f8

Nov 15 15:12:09 vxdmp: [ID 803759 kern.notice] NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk

Nov 15 15:12:10 pcisch: [ID 370704 kern.info] PCI-device: network@5,1, eri0

Nov 15 15:12:10 genunix: [ID 936769 kern.info] eri0 is /pci@8,700000/network@5,1

Nov 15 15:12:15 eri: [ID 517527 kern.info] SUNW,eri0 : 100 Mbps full duplex link up

Nov 15 15:12:48 /sbin/dhcpagent[39]: [ID 976717 daemon.info] setting IP netmask on eri0 to 255.255.255.0

Nov 15 15:12:48 /sbin/dhcpagent[39]: [ID 752476 daemon.info] setting IP address on eri0 to 10.224.44.157

Nov 15 15:12:48 /sbin/dhcpagent[39]: [ID 929444 daemon.warning] configure_if: no IP broadcast specified for eri0, making best guess

Nov 15 15:12:48 /sbin/dhcpagent[39]: [ID 689373 daemon.info] setting broadcast address on eri0 to 10.224.44.255

Nov 15 15:12:48 /sbin/dhcpagent[39]: [ID 636875 daemon.info] added default router 10.224.44.28 on eri0

Nov 15 15:12:48 /sbin/dhcpagent[39]: [ID 223560 daemon.info] eri0 acquired lease, expires Tue Nov 15 17:12:47 2005

Nov 15 15:12:48 /sbin/dhcpagent[39]: [ID 519943 daemon.info] eri0 begins renewal at Tue Nov 15 16:13:59 2005

Nov 15 15:12:48 /sbin/dhcpagent[39]: [ID 151238 daemon.info] eri0 begins rebinding at Tue Nov 15 16:56:35 2005

Nov 15 15:12:52 syseventconfd[96]: [ID 898775 daemon.error] process 115 exited with status 3

Nov 15 15:12:52 syseventconfd[96]: [ID 898775 daemon.error] process 114 exited with status 3

Nov 15 15:12:53 pseudo: [ID 129642 kern.info] pseudo-device: devinfo0

Nov 15 15:12:53 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0

Nov 15 15:12:54 vxesd[159]: [ID 360244 daemon.notice] Event Source daemon started

Nov 15 15:12:54 syseventd[92]: [ID 617319 daemon.error] SIGHUP caught - reloading modules

Nov 15 15:12:55 syseventd[92]: [ID 661968 daemon.error] Daemon restarted

Nov 15 15:12:55 genunix: [ID 454863 kern.info] dump on /dev/dsk/c1t0d0s1 size 10230 MB

Nov 15 15:13:04 /usr/lib/nfs/lockd[431]: [ID 599441 daemon.info] Number of servers not specified. Using default of 20.

Nov 15 15:13:04 statd[433]: [ID 514559 daemon.error] svc_tp_create: Could not register prog 100024 vers 1 on udp

Nov 15 15:13:04 statd[433]: [ID 514559 daemon.error] svc_tp_create: Could not register prog 100024 vers 1 on tcp

Nov 15 15:13:04 statd[433]: [ID 514559 daemon.error] svc_tp_create: Could not register prog 100024 vers 1 on ticlts

Nov 15 15:13:04 statd[433]: [ID 514559 daemon.error] svc_tp_create: Could not register prog 100024 vers 1 on ticotsord

Nov 15 15:13:04 statd[433]: [ID 514559 daemon.error] svc_tp_create: Could not register prog 100024 vers 1 on ticots

Nov 15 15:13:04 statd[433]: [ID 447212 daemon.error] statd: unable to create (SM_PROG, SM_VERS) for netpath.

Nov 15 15:13:04 ntpd[439]: [ID 702911 daemon.notice] ntpd 4.1.1a@1.791 Mon Jun 3 05:01:56 EDT 2002 (1)

Nov 15 15:13:04 ntpd[439]: [ID 702911 daemon.info] precision = 10 usec

Nov 15 15:13:04 ntpd[439]: [ID 702911 daemon.notice] kernel time discipline status 0040

Nov 15 15:13:04 ntpd[439]: [ID 702911 daemon.info] frequency initialized 0.000 from /var/ntp/ntp.drift

blacknight4573 at 2007-7-5 18:22:17 >

# 3

> However, I want to verify that

> I'm actually useing the disk I requested to boot

> from. How would I go about checking that the

> rootmirror disk is the currently booted disk? Thanks

> in advance.

Realize that after the volume manager kicks in you're always using both disks. Only the initial poritions of the boot came from one side. So in most senses, there is no such thing as the "currently booted disk".

Since you used the alias explicitly, you already know which disk was used for the first portion of the boot. You can also run 'prtconf -vp | grep bootpath' as one more piece.

Darren

ddunham@sunforum at 2007-7-5 18:22:17 >

# 4

Thank you both for answering. The 'prtconf -vp | grep bootpath' command is what I was explicitly looking for. Just to verify that my rootmirror disk was working, granted that it doesn't matter which disk it is booted from. I am very thankful for your responses. My question has been answered.

Respectively sent,

Tyler

blacknight4573 at 2007-7-5 18:22:17 >

# 5

I apologize. The intializing memory and the boot device do not get logged into /var/adm/messages. I'm just so use to watching the console messages as systems boot to make sure they are doing what I want them to do.

jdstoon at 2007-7-5 18:22:17 >

Java programming resources: FAQs, tutorials, compiler and browser download sites, documentation, books lists, IDEs, etc.

Which disk is being used?

General New Topic

General Hot Topic

General

All Classified