Juergen,
OOPS! i forgot the attachment :( ..am
attaching it again now ... I'm also copy pasting below
the first few lines of the install_log and also the
end of the file
/*****************************************************/
Installation partially failed
Error: 1332 blocks
Error:
Error: Processing package instance <MYIscsi> from
</tmp/19039>
Error:
Error: My Dummy iSCSI HBA Driver for Solaris(i86pc)
1.0.0
Error: Using </a> as the package base directory.
Error: ## Processing package information.
Error: ## Processing system information.
Error: 3 package pathnames are already properly
installed.
Error: ## Verifying disk space requirements.
Error:
Error: Installing My Dummy iSCSI HBA Driver for
Solaris as <BEIscsi>
Error:
Error: ## Installing part 1 of 1.
Error: /a/kernel/drv/amd64/myiscsi
Error: /a/kernel/drv/myiscsi
Error: [ verifying class <none> ]
Error: ## Executing postinstall script.
Error:
Error: Installation of <MYIscsi> was successful.
Error:
Error: *** IMPORTANT NOTICE ***
Error: This machine must now be rebooted in
order to ensure
Error: sane operation. Execute
Error: shutdown -y -i6 -g0
Error: and wait for the "Console Login:"
prompt.
/*****************************************************/
/************ END OF THE FILE ***********************/
Installing boot information
- Updating boot environment configuration file
- Installing boot blocks (c1t0d0)
- Installing boot blocks (/dev/rdsk/c1t0d0s0)
svc.configd: Fatal error: /a/etc/svc/repository.db:
integrity check failed. Details in
/etc/svc/volatile/db_errors
svccfg: Repository server failed (exit 102).
/**************************************************/
This definitely points to some failure regarding my
package installation off the DU ?
Also even if it is ultimately due a 'disk read' error
..any pointers on how to exactly debug this ?
Thanks
Som
--- Juergen Keil <[EMAIL PROTECTED]> wrote:
> Som,
>
>
> > Thanks for that information,that makes
> things
> > clear.
> > There was one thing i forgot to mention
> yesterday
> > though ,which was the installation screen
> displayed a
> > message saying ' Installation partially failed '
> and
> > look in the /tmp/install_log for details(
> Installation
> > did continue though succesfully and prompted for a
> > reboot too )
> > Today i was able to capture this file and am
> attaching
> > the same, if you look at the beginning of the file
> you
> > will find that there seem to be errors while
> > installing the package ,also pls look at the end
> of
> > the file
> > Could that be the root cause as to why the archive
> is
> > not built correctly and hence on reboot 'error 28'
> msg
> > is showing up ??
> >
> > Btw I am using Solaris 10 8/07 as the installation
> OS
> > and upper memory ~ 2 GB
>
> I just made a quick test with qemu-0.9.0 and a S10
> x86 8/07
> ISO image:
>
> % qemu -m 512 -cdrom sol-10-u4-ga-x86-dvd.iso
> -boot d
>
>
> After selecting the "Solaris" entry from the GRUB
> menu
> I switched to qemu's monitor and ejected the virtual
> cdrom media, while GRUB was loading the
> /boot/x86.miniroot
> file.
>
> S10 8/07 continued to print "..." dots on the screen
> (although the cdrom media was ejected !); and after
> a
> while it failed with the error message "Error 28:
> Selected
> item cannot fit into memory".
>
> Same test with a Nevada build 81 ISO image reported
> "Error 25: Disk read error" - immediatelly after
> ejecting
> the cdrom media.
>
>
> That is, apparently the fix for 6387379 was not
> backported
> to S10 U4 (8/07).
>
>
> > I did take a look at the src code as well and i
> think
> > i should be clera on both the bugs listed below
>
>
> Maybe you should try your iSCSI ITU driver install
> test
> with a current OpenSolaris / Nevada build - I wonder
> if
> you get the same "Error 28" with the GRUB from
> OpenSolaris / Nevada.
>
>
> > Pls advise
> > Thanks
> > Som
> >
> >
> >
> > --- Juergen Keil <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > > Juergen,
> > > > Im not sure i understand when u say
> it
> > > > should contain both 32 and 64-bit drivers
> > >
> > > The compressed cpio driver package in
> > > \DU\sol_210\i86pc\Product\driver.Z
> > > should contain both 32- and 64-bit drivers.
> > >
> > > > ..i.e should
> > > > both the drivers be compressed and stored in
> > > > Tools\boot\ and Tools\boot\amd64 resply?
> > >
> > > No. Only the 32-bit driver module.
> > > (and only for Solaris 10 x86 FCS and older).
> > >
> > >
> > > The \DU\sol_210\i86pc\Tools\boot\ stuff is
> > > used by the old "boot.bin" boot code, which was
> > > used by Solaris 10 x86 (FCS) and older.
> > > The boot code that started with this screen:
> > >
> > >
> > > SunOS Secondary Boot version 4.02
> > >
> > >
> > > Solaris Booting System
> > >
> > > Running Configuration Assistant....
> > >
> > > ...
> > >
> > > Press ESCape to interrupt autoboot in 4
> seconds.
> > >
> > >
> > >
> > > After pressing the ESC key the "Solaris Device
> > > Configuration
> > > Assistant" starts; there you can use the "F4 Add
> > > Driver"
> > > function key to load additional drivers from an
> "ITU
> > > driver
> > > diskette".
> > >
> > > The old boot.bin boot code never supported
> booting
> > > the installation kernel as a 64-bit kernel, so
> it
> > > was
> > > sufficient to only have a 32-bit kernel module
> in
> > > ...\Tools\boot\
> > >
> > > AFAIK, the uncompressed 32-bit driver kernel
> module
> > > from
> > > ...\Tools\boot\ was somehow magically added to
> the
> > > read-only ufs root filesystem on the
> installation CD
> > > on the fly, together with the necessary driver
> > > binding
> > > entries in etc/driver_aliases. I think this was
> > > done
> > > using some hooks / extension in the ufs
> filesystem
> > > code
> > > in the old boot code, in boot.bin.
> > >
> > >
> > > For the new GRUB based boot code,
> ...\Tools\boot\
> > > isn't needed at all. I guess I could add
> something
> > > to my ITU build scripts to remove
> > > DU/sol_211/i86pc/Tools/Boot,
> > > because an OpenSolaris ITU doesn't need it any
> more.
> > >
> > > > Is there a
> > > > standard procedure for this kind of problem
> where
> > > we
> > > > want both 32 and 64-bit versions of the same
> > > driver to
> > > > coexist on the same package? (A sample
> reference
> > > would
> > > > be great)
> > > > Thing is my installation seems to have
> proceeded
> > > > succesfully to 100% and eventually it did
> prompt
> > > me
> > > > for a reboot which i did.Subsequently the
> > > installed OS
> > > > on my LUN shows up on the GRUB menu ,but upon
> > > > selection i get error message saying
> > > >
> > > > 'Error 28: Unable to fit selected image into
> > > memory '
> > > > ( i get same problem even when i choose
> fail-safe
> > > > option on the GRUB menu)
> > >
> > > That is, you do have Solaris installed on an
> iSCSI
> > > disk? And GRUB and the GRUB menu is loaded
> via
> > > iSCSI?
>
=== message truncated ===
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search.
http://tools.search.yahoo.com/newsearch/category.php?category=shopping
install_log.gz
Description: 2879169646-install_log.gz
_______________________________________________ driver-discuss mailing list driver-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/driver-discuss
