I turned on verbose when running devfsadm in the DC build. Here's a partial output, if you want the full output just ask. It doesn't look good to me.
running devfsadm ... /rpool/dc/Dec3-8am/build_data/bootroot//usr/sbin/devfsadm -v -r /rpool/dc/Dec3-8am/build_data/b ootroot devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/scsi_ vhci:devctl devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/memor y-controller at 0,400000:mc-us3 devfsadm[23781]: verbose: symlink /rpool/dc/Dec3-8am/build_data/bootroot/dev/mc/mc0 -> ../../devices/memory-controll er at 0,400000:mc-us3 devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/memor y-controller at 1,400000:mc-us3 devfsadm[23781]: verbose: symlink /rpool/dc/Dec3-8am/build_data/bootroot/dev/mc/mc1 -> ../../devices/memory-controll er at 1,400000:mc-us3 devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/memor y-controller at 2,400000:mc-us3 devfsadm[23781]: verbose: symlink /rpool/dc/Dec3-8am/build_data/bootroot/dev/mc/mc2 -> ../../devices/memory-controll er at 2,400000:mc-us3 devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/memor y-controller at 3,400000:mc-us3 devfsadm[23781]: verbose: symlink /rpool/dc/Dec3-8am/build_data/bootroot/dev/mc/mc3 -> ../../devices/memory-controll er at 3,400000:mc-us3 devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/pci at 8 ,700000:devctl devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/pci at 8 ,700000:reg devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/pci at 8 ,700000:intr devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/pci at 8 ,600000:devctl devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/pci at 8 ,600000:reg devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/pci at 8 ,600000:intr devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/pci at 9 ,700000:devctl devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/pci at 9 ,700000:reg devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/pci at 9 ,700000:intr devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/pci at 9 ,600000:devctl devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/pci at 9 ,600000:reg devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/pci at 9 ,600000:intr devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/ramdi sk-root:a devfsadm[23781]: verbose: symlink /rpool/dc/Dec3-8am/build_data/bootroot/dev/ramdisk/root -> ../../devices/ramdisk-r oot:a devfsadm[23781]: verbose: no devfs node or mismatched dev_t for /rpool/dc/Dec3-8am/build_data/bootroot/devices/ramdi sk-root:a,raw Jean Jean McCormack wrote: > Tycho Nightingale wrote: > >> On Thu, 4 Dec 2008, Karen Tung wrote: >> >> >>> Hi Sanjay, >>> >>> It turns out that the entry for /etc/system is not there. >>> I am not sure why. Will look at the DC code. >>> >>> We added the entries by hand, now, we don't have >>> the panic. It got much further in the booting process, but >>> it got into an infinite loop with failures on trying to execute the >>> following 2 commands: >>> >>> ----------------------- >>> INIT: Command >>> "exec /sbin/autopush -f /etc/iu.ap" >>> failed to execute. >>> errno = 2 (exec of shell failed) >>> >>> INIT: Command >>> "exec /sbin/soconfig -f >>> /etc/sock2path" >>> >>> failed to execute. errno = 2 (exec of shell failed) >>> ----------------------- >>> >>> I checked the root archive, the /sbin/autopush and /sbin/soconfig are >>> both >>> there, and have the correct permissions. /etc/iu.ap and /etc/sock2path >>> are also there. >>> >>> Thoughts? >>> >> Looks like init is unable to execute the binaries not that the files >> are missing. >> >> What does /dev and /devices look like? Has devfsadm been run? >> > Tycho, > > I believe devfsadm has been run since when I rebuild with a print > statement I see this: > > Build Area mount point: /rpool/dc/Dec3-8am > ==== br-config: Boot root configuration > ==== br-config: Boot root configuration > > Configuring bootroot... > > running devfsadm ... > /rpool/dc/Dec3-8am/build_data/bootroot//usr/sbin/devfsadm -r > /rpool/dc/Dec3-8am/build_data/bootroot > > Preloading SMF repository... > > Loading smf(5) service descriptions: > > > Are we missing any flags or anything? > > Jean > > Jean > > > >> Tycho >> > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >
