Ethan Quach wrote:
> This sounds extremely similar to 6346353.
>
> Does patch 118855-19 deliver "/lib/svc/method/devices-local" ?  If it 
> does, its overwriting the miniroot version of the file.  (See an 
> unpatched miniroot for what the miniroot version looks like).
It does deliver /lib/svc/method/devices-local. So, it sounds like the 
same bug.

thanks,
sarah
>
>
> -ethan
>
>
> Sarah Jelinek wrote:
>>
>>
>> ------------------------------------------------------------------------
>>
>> Subject:
>> RE:devfsadm message during miniroot boot
>> From:
>> Sarah Jelinek <Sarah.Jelinek at Sun.COM>
>> Date:
>> Tue, 03 Oct 2006 14:49:23 -0600
>> To:
>> Jill.Manfield at Sun.COM, Paul.Buckley at Sun.COM
>>
>> To:
>> Jill.Manfield at Sun.COM, Paul.Buckley at Sun.COM
>>
>>
>> Hi Jill and Paul,
>>
>> I am the install POC for the week and I just saw this email. The 
>> error message you are seeing indicates that someone is trying to run 
>> devfsadm on a read only root fs. During the install process we use 
>> /tmp/dev to do our work, and normally would not see this happen. I 
>> notice that you said you applied patch 118855-19 to the miniroot. How 
>> exactly did you do this?
>>
>> Also, I note that there is a begin.sh script being run, is there any 
>> devfsadm calls in this script?
>>
>> Have you tried to run this jumpstart install with the base s10u2 
>> miniroot, without the patch data? If so, was this message present as 
>> well?
>>
>> Yes, this message is a concern, so I need a bit more data to see how 
>> we got there.
>>
>> thanks,
>> sarah
>> ****
>>
>>
>>
>>> Can anyone answer this please please????  My customer has been 
>>> waiting for an answer and is getting antsy to whether this error 
>>> could be ignored as benign.  Please read Paul's description  
>>> thanks!  He is a top account Time Warner customer and his deployment 
>>> is being held up by my response.
>>> =========================================================================== 
>>>              
>>>        S U N  M I C R O S Y S T E M S  I N C.
>>>                   Jill Manfield - TSE-X64 Support Team
>>>        email: jill.manfield at sun.com
>>>   phone: (800)USA-4SUN (Reference your case #)
>>>        address:  1617 Southwood Drive Nashua,NH 03063
>>>        mailstop: NSH-01- B287           Mgr: Dave O'Connor: 
>>> dave.oconnor at sun.com
>>>       Submit, View and Update tickets at 
>>> http://www.sun.com/service/online
>>>
>>> This email may contain confidential and privileged material for the 
>>> sole use of the intended recipient. Any review or distribution by 
>>> others is strictly prohibited.  If you are not the intended 
>>> recipient please contact the sender and delete all copies.
>>> =============================================================================
>>>  
>>>
>>>
>>> ----- Original Message -----
>>> From: Paul Buckley <Paul.Buckley at Sun.COM>
>>> Date: Thursday, September 28, 2006 11:27 am
>>> Subject: Re: devfsadm message during miniroot boot
>>> To: install-interest at sun.com
>>> Cc: Jill Manfield <Jill.Manfield at Sun.COM>
>>>
>>>  
>>>
>>>> > Can some please give a quick verification if the message encountered
>>>> > during the miniroot boot will have any effect on the final > 
>>>> installationafter flash deployment?
>>>> > > Thanks,
>>>> > > Paul
>>>> > > Paul Buckley wrote:
>>>> >   
>>>>> > >Hello,
>>>>> > >
>>>>> > >Any reason that the following message during the boot process 
>>>>> to       
>>>>
>>>> > miniroot during an jumpstart install would effect the final 
>>>> install > environment. This is just a concern not a problem that we 
>>>> know of. > Deployment of the flash archive is successful.
>>>>   
>>>>> > >
>>>>> > >---------------------
>>>>> > >Custom JumpStart
>>>>> > >Configuring devices.
>>>>> > >devfsadm: mkdir failed for /dev 0x1ed: Read-only file system
>>>>> > >---------------------
>>>>> > >
>>>>> > >This is a s10u2 miniroot (x86) patched with 118855-15.
>>>>> > >
>>>>> > >Thanks, Paul
>>>>> > >
>>>>> > >
>>>>> > >
>>>>> > >
>>>>> > >Console boot text follows:
>>>>> > >
>>>>> > >
>>>>> > >
>>>>> > >module misc/krtld: text at [0xfe873690, 0xfe881827] data at       
>>>>
>>>> > 0xfec40a38>module /kernel/genunix: text at [0xfe881828, 
>>>> 0xfe98cc27] > data at
>>>>   
>>>>> > >0xfec45a60
>>>>> > >SunOS Release 5.10 Version Generic_118855-15 32-bit
>>>>> > >Copyright 1983-2005 Sun Microsystems, Inc.  All rights reserved.
>>>>> > >Use is subject to license terms.
>>>>> > >features:
>>>>> > 
>>>>> >1067fdf<cpuid,sse3,nx,sse2,sse,sep,pat,cx8,pae,mca,mmx,cmov,pge,mtrr,msr 
>>>>>
>>>>> > >,tsc,lgpg>
>>>>> > >Using default device instance data
>>>>> > >cpuid 0: initialized cpumod: cpu.AuthenticAMD.15
>>>>> > >mem = 2096696K (0x7ff8e000)
>>>>> > >root nexus = i86pc
>>>>> > >pseudo0 at root
>>>>> > >pseudo0 is /pseudo
>>>>> > >scsi_vhci0 at root
>>>>> > >scsi_vhci0 is /scsi_vhci
>>>>> > >isa0 at root
>>>>> > >ramdisk0 at root
>>>>> > >ramdisk0 is /ramdisk
>>>>> > >SMBIOS v2.3 loaded (3017 bytes)SMI polling disabled in favor of 
>>>>>       
>>>>
>>>> > Solaris>Fault Management for AMD Processors
>>>>   
>>>>> > >pseudo-device: dld0
>>>>> > >dld0 is /pseudo/dld at 0
>>>>> > >pci0 at root: space 0 offset 0
>>>>> > >pci0 is /pci at 0,0
>>>>> > >PCI-device: pci1022,7450 at 1, pci_pci0
>>>>> > >pci_pci0 is /pci at 0,0/pci1022,7450 at 1
>>>>> > >Ethernet address = 0:14:4f:1:93:dc
>>>>> > >PCI-device: pci1022,7460 at 6, pci_pci2
>>>>> > >pci_pci2 is /pci at 0,0/pci1022,7460 at 6
>>>>> > >ISA-device: asy0
>>>>> > >asy0 is /isa/asy at 1,3f8
>>>>> > >8042 device:  keyboard at 0, kb8042 # 0
>>>>> > >kb80420 is /isa/i8042 at 1,60/keyboard at 0
>>>>> > >PCI-device: pci1022,7464 at 0, ohci0
>>>>> > >ohci0 is /pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0
>>>>> > >PCI-device: pci1022,7464 at 0,1, ohci1
>>>>> > >ohci1 is /pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0,1
>>>>> > >cpu0: x86 (AuthenticAMD family 15 model 37 step 1 clock 2792 MHz)
>>>>> > >cpu0: AMD Opteron(tm) Processor 254
>>>>> > >cpu1: x86 (AuthenticAMD family 15 model 37 step 1 clock 2792 MHz)
>>>>> > >cpu1: AMD Opteron(tm) Processor 254
>>>>> > >cpuid 1: initialized cpumod: cpu.AuthenticAMD.15
>>>>> > >pci1 at root: isa 0x0
>>>>> > >pci1 is /pci at 1,0
>>>>> > >Configuring devices.
>>>>> > >USB 1.10 device (usb46b,ff10) operating at full speed (USB 1.x) 
>>>>> on       
>>>>
>>>> > USB>1.10 root hub: device at 3, usb_mid0 at bus address 2
>>>>   
>>>>> > >        American Megatrends Inc. Virtual Keyboard and Mouse
>>>>> > >usb_mid0 is /pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0/device at 3
>>>>> > >/pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0/device at 3 (usb_mid0) 
>>>>> > >online
>>>>> > >USB 1.10 interface (usbif46b,ff10.config1.0) operating at full 
>>>>> speed
>>>>> > >(USB 1.x) on USB 1.10 root hub: keyboard at 0, hid0 at bus address 2
>>>>> > >        American Megatrends Inc. Virtual Keyboard and Mouse
>>>>> > >hid0 is /pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0/device at 
>>>>> > >3/keyboard at 0
>>>>> > >/pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0/device at 3/keyboard 
>>>>> > >at 0 
>>>>> (hid0)       
>>>>
>>>> > online>USB 1.10 interface (usbif46b,ff10.config1.1) operating at 
>>>> > full speed
>>>>   
>>>>> > >(USB 1.x) on USB 1.10 root hub: mouse at 1, hid1 at bus address 2
>>>>> > >        American Megatrends Inc. Virtual Keyboard and Mouse
>>>>> > >hid1 is /pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0/device at 
>>>>> > >3/mouse at 1
>>>>> > >/pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0/device at 3/mouse at 1 
>>>>> > >(hid1) 
>>>>> online
>>>>> > >USB 1.10 device (usb46b,ff20) operating at full speed (USB 1.x) 
>>>>> on       
>>>>
>>>> > USB>1.10 root hub: storage at 1, scsa2usb0 at bus address 2
>>>>   
>>>>> > >        American Megatrends Inc. Virtual Cdrom Device
>>>>> > >scsa2usb0 is /pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0,1/storage 
>>>>> > >at 1
>>>>> > >/pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0,1/storage at 1 
>>>>> > >(scsa2usb0) 
>>>>> online
>>>>> > >USB 1.10 device (usb46b,ff40) operating at full speed (USB 1.x) 
>>>>> on       
>>>>
>>>> > USB>1.10 root hub: storage at 2, scsa2usb1 at bus address 3
>>>>   
>>>>> > >        American Megatrends Inc. Virtual Floppy Device
>>>>> > >scsa2usb1 is /pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0,1/storage 
>>>>> > >at 2
>>>>> > >/pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0,1/storage at 2 
>>>>> > >(scsa2usb1) 
>>>>> online
>>>>> > >USB 1.10 device (usb3eb,3301) operating at full speed (USB 1.x) 
>>>>> on       
>>>>
>>>> > USB>1.10 root hub: hub at 3, hubd0 at bus address 4
>>>>   
>>>>> > >hubd0 is /pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0,1/hub at 3
>>>>> > >/pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0,1/hub at 3 (hubd0) 
>>>>> > >online
>>>>> > >sd0 at scsa2usb0: target 0 lun 0
>>>>> > >sd0 is /pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0,1/storage at 
>>>>> > >1/disk at 0,0
>>>>> > >/pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0,1/storage at 1/disk at 
>>>>> > >0,0 
>>>>> (sd0)       
>>>>
>>>> > online>sd1 at scsa2usb1: target 0 lun 0
>>>>   
>>>>> > >sd1 is /pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0,1/storage at 
>>>>> > >2/disk at 0,0
>>>>> > >/pci at 0,0/pci1022,7460 at 6/pci1022,7464 at 0,1/storage at 2/disk at 
>>>>> > >0,0 
>>>>> (sd1)       
>>>>
>>>> > online>pseudo-device: devinfo0
>>>>   
>>>>> > >devinfo0 is /pseudo/devinfo at 0
>>>>> > >xsvc0 at root
>>>>> > >xsvc0 is /xsvc
>>>>> > >PCI-device: pci1022,7450 at 2, pci_pci1
>>>>> > >pci_pci1 is /pci at 0,0/pci1022,7450 at 2
>>>>> > >PCI-device: pci1022,7450 at 1, pci_pci3
>>>>> > >pseudo-device: pseudo1
>>>>> > >pci_pci3 is /pci at 1,0/pci1022,7450 at 1
>>>>> > >pseudo1 is /pseudo/zconsnex at 1
>>>>> > >PCI-device: pci1022,7450 at 2, pci_pci4
>>>>> > >pci_pci4 is /pci at 1,0/pci1022,7450 at 2
>>>>> > >/pci at 0,0/pci1022,7450 at 2/pci1000,3060 at 3 (mpt0):
>>>>> > >        Rev. 2 LSI, Inc. 1064 found.
>>>>> > >/pci at 0,0/pci1022,7450 at 2/pci1000,3060 at 3 (mpt0):
>>>>> > >        mpt0 supports power management.
>>>>> > >        ATAPI device at targ 0, lun 0 lastlun 0x0
>>>>> > >        model DV-28SL
>>>>> > >        ATA/ATAPI-5 supported, majver 0x3c minver 0x0
>>>>> > >/pci at 0,0/pci1022,7450 at 2/pci1000,3060 at 3 (mpt0):
>>>>> > >        mpt0 Firmware version v1.4.0.0 (IR)
>>>>> > >/pci at 0,0/pci1022,7450 at 2/pci1000,3060 at 3 (mpt0):
>>>>> > >        mpt0: IOC Operational.
>>>>> > >PCI-device: ide at 0, ata0
>>>>> > >ata0 is /pci at 0,0/pci-ide at 7,1/ide at 0
>>>>> > >        ATA DMA off: disabled.  Control with 
>>>>> "atapi-cd-dma-enabled"
>>>>> > >property
>>>>> > >        PIO mode 4 selected
>>>>> > >        ATA DMA off: disabled.  Control with 
>>>>> "atapi-cd-dma-enabled"
>>>>> > >property
>>>>> > >        PIO mode 4 selected
>>>>> > >        ATA DMA off: disabled.  Control with 
>>>>> "atapi-cd-dma-enabled"
>>>>> > >property
>>>>> > >        PIO mode 4 selected
>>>>> > >pseudo-device: fssnap0
>>>>> > >fssnap0 is /pseudo/fssnap at 0
>>>>> > >pseudo-device: ramdisk1024
>>>>> > >ramdisk1024 is /pseudo/ramdisk at 1024
>>>>> > >pseudo-device: fcp0
>>>>> > >fcp0 is /pseudo/fcp at 0
>>>>> > >pseudo-device: winlock0
>>>>> > >winlock0 is /pseudo/winlock at 0
>>>>> > >pseudo-device: fcsm0
>>>>> > >fcsm0 is /pseudo/fcsm at 0
>>>>> > >pseudo-device: llc10
>>>>> > >llc10 is /pseudo/llc1 at 0
>>>>> > >pseudo-device: lofi0
>>>>> > >lofi0 is /pseudo/lofi at 0
>>>>> > >pseudo-device: pool0
>>>>> > >pool0 is /pseudo/pool at 0
>>>>> > >sd2 at ata0: target 0 lun 0
>>>>> > >sd2 is /pci at 0,0/pci-ide at 7,1/ide at 0/sd at 0,0
>>>>> > >pseudo-device: bmc0
>>>>> > >bmc0 is /pseudo/bmc at 0
>>>>> > >pseudo-device: zfs0
>>>>> > >zfs0 is /pseudo/zfs at 0
>>>>> > >pseudo-device: power0
>>>>> > >power0 is /pseudo/power at 0
>>>>> > >/pci at 0,0/pci1022,7450 at 2/pci1000,3060 at 3 (mpt0):
>>>>> > >        Volume 1 is optimal
>>>>> > >/pci at 0,0/pci1022,7450 at 2/pci1000,3060 at 3 (mpt0):
>>>>> > >        Volume 0 is optimal
>>>>> > >PCI-device: pci1000,3060 at 3, mpt0
>>>>> > >mpt0 is /pci at 0,0/pci1022,7450 at 2/pci1000,3060 at 3
>>>>> > >sd3 at mpt0: target 0 lun 0
>>>>> > >sd3 is /pci at 0,0/pci1022,7450 at 2/pci1000,3060 at 3/sd at 0,0
>>>>> > >sd4 at mpt0: target 1 lun 0
>>>>> > >sd4 is /pci at 0,0/pci1022,7450 at 2/pci1000,3060 at 3/sd at 1,0
>>>>> > >Custom JumpStart
>>>>> > >Configuring devices.
>>>>> > >devfsadm: mkdir failed for /dev 0x1ed: Read-only file system
>>>>> > >        ATA DMA off: disabled.  Control with 
>>>>> "atapi-cd-dma-enabled"
>>>>> > >property
>>>>> > >        PIO mode 4 selected
>>>>> > >        ATA DMA off: disabled.  Control with 
>>>>> "atapi-cd-dma-enabled"
>>>>> > >property
>>>>> > >        PIO mode 4 selected
>>>>> > >        ATA DMA off: disabled.  Control with 
>>>>> "atapi-cd-dma-enabled"
>>>>> > >property
>>>>> > >        PIO mode 4 selected
>>>>> > >Beginning system identification...
>>>>> > >Searching for configuration file(s)...
>>>>> > >Using sysid configuration file
>>>>> > >65.185.233.84:/autocfg/clients/0193dc/sysidcfg
>>>>> > >Search complete.
>>>>> > >Discovering additional network configuration...
>>>>> > >Completing system identification...
>>>>> > >Starting remote procedure call (RPC) services: done.
>>>>> > >System identification complete.
>>>>> > >Starting Solaris installation program...
>>>>> > >Searching for JumpStart directory...
>>>>> > >Using rules.ok from 65.185.233.84:/autocfg/clients/0193dc.
>>>>> > >Checking rules.ok file...
>>>>> > >Using begin script: begin.sh
>>>>> > >Using derived profile: begin.sh
>>>>> > >Using finish script: finish.sh
>>>>> > >/sbin/dhcpinfo: primary interface requested but no primary       
>>>>
>>>> > interface is
>>>>   
>>>>> > >set
>>>>> > >Executing JumpStart preinstall phase...
>>>>> > >Executing begin script "begin.sh"...
>>>>> > >mounting filesystems from 65.185.233.84...
>>>>> > >mounting complete
>>>>> > >INFO   Jumpstart.Global - starting telnet daemon...
>>>>> > >INFO   Jumpstart.Global - started telnet daemon
>>>>> > >INFO   Jumpstart.Global.Network - preparing chroot area for       
>>>>
>>>> > ifspeed...>INFO   Jumpstart.Global.Network - current interface 
>>>> states:
>>>>   
>>>>> > >e1000g0: up, autonegotiated 100/half
>>>>> > >   capabilities: auto 1000/full 100/full 100/half 10/full 10/half
>>>>> > >   link partner capabilities: auto 100/half
>>>>> > >e1000g1: down
>>>>> > >   capabilities: auto 1000/full 100/full 100/half 10/full 10/half
>>>>> > >e1000g2: down
>>>>> > >   capabilities: auto 1000/full 100/full 100/half 10/full 10/half
>>>>> > >e1000g3: down
>>>>> > >   capabilities: auto 1000/full 100/full 100/half 10/full 10/half
>>>>> > >INFO   Jumpstart.Global.Network - setting speed for e1000g0 (best-
>>>>>       
>>>>
>>>> > guess)>INFO   Jumpstart.Global.Network - set speed completed
>>>>   
>>>>> > >INFO   Jumpstart.Global.Profile - Determining Server Hardware type
>>>>> > >INFO   Jumpstart.Global.Profile - RAID relationship for 
>>>>> c0t0d0       
>>>>
>>>> > already>established
>>>>   
>>>>> > >INFO   Jumpstart.Global.Profile - creating Solaris partition on 
>>>>>       
>>>>
>>>> > c0t0d0>INFO   Jumpstart.Global.Profile - rereading disk information
>>>>   
>>>>> > >INFO   Jumpstart.Global.Profile - creating Solaris label on c0t0d0
>>>>> > >INFO   Jumpstart.Global.Profile - constructed derived 
>>>>> profile       
>>>>
>>>> > using root
>>>>   
>>>>> > >disk c0t0d0
>>>>> > >INFO   Jumpstart.Global.Profile - decided to use 4196 megabytes 
>>>>> of       
>>>>
>>>> > swap>Begin script begin.sh execution completed.
>>>>   
>>>>> > >Searching for SolStart directory...
>>>>> > >Checking rules.ok file...
>>>>> > >Using begin script: install_begin
>>>>> > >Using finish script: patch_finish
>>>>> > >/sbin/dhcpinfo: primary interface requested but no primary       
>>>>
>>>> > interface is
>>>>   
>>>>> > >set
>>>>> > >Executing SolStart preinstall phase...
>>>>> > >Executing begin script "install_begin"...
>>>>> > >Begin script install_begin execution completed.
>>>>> > >
>>>>> > >Processing profile
>>>>> > >
>>>>> > >
>>>>> > >  > >
>>>>>       
>>>>
>>>> > >     
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> install-discuss mailing list
>> install-discuss at opensolaris.org
>> http://opensolaris.org/mailman/listinfo/install-discuss
>


Reply via email to