On Wed, 11 Mar 2009, jan damborsky wrote: [ .. ]
>>> ... >>> <ICT Mar 11 14:41:00> bootadm update-archive output: >>> /a//boot/solaris/bin/create_ramdisk: line 509: /usr/sbin/df: cannot >>> execute [I/O error] >>> ... >>> >>> I have restarted the installation and verified /usr/sbin/df works >>> correctly at the beginning of the installation process. After it >>> finished I can't access it anymore: >>> >>> $ cp /usr/sbin/df /tmp/ >>> /tmp//df: I/O error >>> $ file /usr/sbin/df >>> /usr/sbin/df: cannot read: I/O error >>> >>> There seem to be more files affected: >>> >>> $ find /usr/sbin/ -type f | xargs file | grep cannot >>> /usr/sbin/cron: cannot read: I/O error >>> /usr/sbin/devinfo: cannot read: I/O error >>> /usr/sbin/df: cannot read: I/O error >>> /usr/sbin/dfmounts: cannot read: I/O error >>> /usr/sbin/dfshares: cannot read: I/O error >>> >>> My question if is this known issue, or if somebody else >>> noticed this - it happens only on x86 for me, I haven't >>> seen this on T1000 Sparc machine. >>> >>> If anyone would like to take a look, I can provide >>> access to x2100z machine suffering from this issue. >> >> Could I please get access to this machine? The symptoms >> look to be similar to the ones noted in defect 6804 >> >> http://defect.opensolaris.org/bz/show_bug.cgi?id=6804 >> >> but until now it has been seen only on some sparc machines. > > Yeah, > > I don't see this on Sparc test machine (T1000), but > can reproduce it on w2100z and in Virtual Box as well. It does seem that the machine has also hit defect 6804. The contents of solaris.zlib and solarismisc.zlib changed during the install. solaris.zlib should have an md5 digest of cb020a059f5a08af3c161185652767e8 but after the install has 60080953ab3b4bfa44a45369d3c9d619. Alok
