Frank Middleton wrote: > On 10/ 6/09 01:18 PM, Evan Layton wrote: > >> What build are you attempting to run this image-update on when >> going to build 124? Also can you send the output from the >> following: > > snv111b. The beadm bug prevented updates from any later release > that has ever been installed here (snv122, snv123). Having successfully > installed snv124, we have no reason to go back to snv111b since the > beadm bug evidently has been fixed (yeah!).
Which beadm bug are you referring to that caused these failures? > >> # export BE_PRINT_ERR=true >> # beadm create newbe > > Which release should be running when this is done? The build that this was failing one is what I was asking for. Since I can now reproduce this on build 124 it's not really necessary but could be helpful to know that what I'm seeing really is the same thing you're hitting. > beadm works > fine on snv124, Perhaps I should have asked if an update from > snv124 to snv125 would fail because of the missing menu.lst > problem, which is quite reproducible and has been a problem > ever since snv111b. The status is unclear from the posts in the > bug reports. Is you system still missing /rpool/boot/menu.lst? If it is missing and you're reliably hitting this then you're likely to hit the issue going from build 124 to 125. As for this being reproducible on build 111b I'm still completely unable to reproduce this there. However I am able to hit this with build 124 now. Because I can now reproduce this I'm reopening bug 7880. Thanks! -evan
