[OpenIndiana-discuss] boot-archive timing out after 3ware driverinstall

[Mike La Spina]

The only thing I can think of is ... did you refresh the active service
manifest?

e.g.

svcadm refresh boot-archive:default

-----Original Message-----
From: Ian Levesque [mailto:ian at crystal.harvard.edu] 
Sent: Thursday, May 10, 2012 1:07 PM
To: Discussion list for OpenIndiana
Subject: [OpenIndiana-discuss] boot-archive timing out after 3ware
driverinstall

Hello,

I have a file server with OpenIndiana 151a4 installed. It has a 3ware
9750 SAS card installed with 13 drives attached. I configured each drive
as a "single" disk (there's no JBOD/passthrough), and then setup a zpool
with said drives. 

When I rebooted the server, however, it appears that activating the
individual drives is taking too long for the boot-archive to finish
loading. Here's what I see during boot:

WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=11
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=7
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=1
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=6
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=8
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=5 May
10 12:55:06 svc.startd[10]: svc:/system/boot-archive:default: Method or
service exit timed out. Killing contract 19.
May 10 12:55:06 svc.startd[10]: svc:/system/boot-archive:default: Method
"/lib/svc/method/boot-archive" failed due to signal KILL.
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=12
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=2
WARNING: tw0: tw_aen_task AEN 0x0090 Unit now in active mode unit=0

This causes some 70-odd services to thereby fail, leaving the system
pretty much in maintenance mode.

If I remove the 3ware drivers from /kernel/drv/amd64/ and /kernel/drv/
then reboot, there are no errors with the boot-archive. Unfortunately,
there are also no storage drives for my zpool.

The closest google turns up is here:
http://www.unix.com/solaris/155331-system-stuck-up-maintanence-mode.html
I did run `svccfg -s boot-archive setprop start/timeout_seconds=180` but
the /var/svc/log/system-boot-archive:default.log seems to indicate that
I'm only getting 60 seconds:

[ May 10 12:54:03 Enabled. ]
[ May 10 12:54:06 Executing start method
("/lib/svc/method/boot-archive"). ] [ May 10 12:55:06 Method or service
exit timed out. Killing contract 19. ]

# svccfg -s boot-archive listprop | grep timeout

start/timeout_seconds	count	180
stop/timeout_seconds	count	3

Any advice other than throw away my $500 HBA? :)

Best,
Ian
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss at openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss