Look in /var/adm/messages to see if there is a panic message (sounds
like there will be). If so, post that plus the stack trace which
follows. This should allow people to see whether you've hit a known bug
or not.
The panic message will be of the form:
panic[cpu0]/thread=0xffffffffaf234430: some message
followed by lines of hex. Find the panic line and copy-and-paste
everything up to and including the next "Solaris Release snv_XX" line.
Regards,
Brian
ace wrote:
I am never able to complete a scrub/resilver on the asus p6t ws xeon e5520
12gbecc with re4-gp and wd20eads drives. Opensolaris 134 will restart an hour
or more into a scrub/resilver regardless if I put the most intensively used
disks on the ich10 (ide or ahci) or the 1068e controller. Eon 130 and sxce 130
restart the same.
At first I assumed it was the mpt/1068e driver/chip issue but I exported the
pool and imported it on a dual xeon 5520 supermicro MBD-X8DTH-iF-O motherboard
which completed a resilver successfully on the pool using the same 1068e
controller and onboard ich.
I will search the forum to identify where to look for errors, logs, etc to troubleshoot this.
In the meantime, I would appreciate any recommendations as to troubleshooting
this problem.
--
Brian Ruthven
Solaris Network RPE (Sustaining)
Oracle UK
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
