[no subject]

Thanks for the links, now I just need the time.

> 
> Yeah, i had some more funny messages like "lost interrupt" and also this: 
> 
> Dec 17 00:01:26 cobalt3 kernel: hdg: write_intr error1: nr_sectors=1, 
> stat=0xd0
> Dec 17 00:01:26 cobalt3 kernel: hdg: write_intr: status=0xd0 { Busy }
> Dec 17 00:01:26 cobalt3 kernel: ide3: reset: success
> Dec 17 00:01:26 cobalt3 kernel: hdg: write_intr error1: nr_sectors=1, 
> stat=0xd0
> Dec 17 00:01:26 cobalt3 kernel: hdg: write_intr: status=0xd0 { Busy }
> Dec 17 00:01:27 cobalt3 kernel: ide3: reset: success 
> 
> whateverthehell that means ... 

Not sure, but doesn't look good. Something in RAID does not seem happy.
  
> > I wonder if someone from Sun/Cobalt will care to comment, or remain
> > anonymous cowards. ;)
> 
> Yes, there is already an escalation running. There is a very kind technician
> of Sun Cobalt EMEA support in Netherlands who helped me a lot. 

Wonder why they have not pulled it or done something about it. I assume
the will and are?
 
-- 
Sincerely,
William L. Thomson Jr.
Support Group
Obsidian-Studios Inc.
439 Amber Way
Petaluma, Ca. 94952
Phone  707.766.9509
Fax    707.766.8989
http://www.obsidian-studios.com