Someone fixed the machine, duh. Something was funky with the RAID-0 configuration linking the 3 drives together in a disk group (2 disk groups = 6 total drives). He randomly pulled drives out of the bay and randomly played around with the RAID configuration utility and then it worked again!
I decided to redo the conversion with the same source and target. Results? I broke it again, bweeeee ^_^
... anyways, to have this occur 2/2 really tells something about the cause and effect of the conversion. People are now getting excited as to what happened during the conversion. They continuously claim that the software component in no way interferes with the BIOS and stuff, but something weird is definitely going on here. One of my co-workers told me how once, a bug appeared only on the hour. The developers constantly closed it as "unreproducible" and no one knew what was going on. When the hour is hit, some event log thing crashed and it took them almost forever to realize the reproduction steps!
Anyhow, I decided to switch sources and do a conversion with a SLES9 SP4. If this failed, it would be quite a story. Luckily (or unfortunately), the conversion completed successfully. Tomorrow, I am going to try a conversion with SLES10 SP0 to determine whether this is only a SLES10 problem. Nonetheless, this issue is quite high in the priority, so hopefully I can get it done soon.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment