Hi Alok,
On 03/11/09 19:51, Alok Aggarwal wrote: > Hi Jan, > > On Wed, 11 Mar 2009, jan damborsky wrote: > >> The x86 one is suspicious (I have verified that for me >> the behavior is the same if I use official RE 109 x86 AI >> image pulled from nana). >> >> The installation itself went fine, but I have noticed following >> message in install_log file: >> >> $ cat /tmp/install_log (full is attached) >> ... >> <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. You can obtain access to w2100z in following way (it is behind NAT): $ ssh tia.czech $ ssh jack at 192.168.100.78 Password: jack $ su - Password: opensolaris Jan
