Bug 95165

Hi,

And of course you read the notes...
http://www.freebsd.org/releases/6.0R/relnotes-i386.html#UPGRADE

Of course this is for source upgrade, but there was a lotof changes since 4.9 and you should 
reinstall for a 4.x. :(

Regards,
Andrej

Christoph Weber-Fahr wrote:
>> Number:         95165
>> Category:       i386
>> Synopsis:       6.1 Beta 4 ISO (386) fails upgrade and destroys old install
>> Confidential:   no
>> Severity:       critical
>> Priority:       medium
>> Responsible:    freebsd-i386
>> State:          open
>> Quarter:        
>> Keywords:       
>> Date-Required:
>> Class:          sw-bug
>> Submitter-Id:   current-users
>> Arrival-Date:   Fri Mar 31 20:00:31 GMT 2006
>> Closed-Date:
>> Last-Modified:
>> Originator:     Christoph Weber-Fahr
>> Release:        FreeBSD 6.1 beta4
>> Organization:
> Arcor AG
>> Environment:
> no environment string available - system is unusable until 
> completely reinstalled (or possibly manually repaired.)
> 
> HW is a HP Proliant DL380 G3
> 
>> Description:
> 	The upgrade function fails to complete and renders the system 
> 	unusable.
> 	I tried to binary ugrade a 4.11-RELEASE-p9 system which was 
> 	working fine.
> 	Precise problem is that is complains about a write error with
> 	the base install set. Looking at F2 reveals that the "error" is 
> 	a "permission denied" while trying to unpack/move /stand/gunzip
> 	One thing I noted is that the install set uses leading "/" - 	
> 	maybe it tries to overwrite the cd or the mfs instead of writing to 
> 	the target disk.
> 
> 	whatever you do the base distribution install is aborted here and 
> 	sysinstall continues with the bin distribution.
> 
> 	later it retries with the same problem. After reboot the system
> 	is unusable.
> 
> 	trying the same with the 5.4-RELEASE cd works just fine.
> 
> 	Another issue: apparently the beta4 ISOs do not conatain any 
> 	packages. for X.org sysinstall complains about a missing 
> 	index file.
> 		
>> How-To-Repeat:
>> Fix:
> 
> 
> 
>> Release-Note:
>> Audit-Trail:
>> Unformatted:
> _______________________________________________
> freebsd-i386@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-i386
> To unsubscribe, send any mail to "freebsd-i386-unsubscribe@freebsd.org"
>

Comment 2 Remko Lodder 2006-04-02 11:36:29 UTC

State Changed
From-To: open->closed

I am very sorry but this is not a Problem.  There were a lot 
of changes between 4.X and 6.X, amongst them differently 
coded bootloaders (/stand got removed for example) and 
different binary approaches which is why there is a migration 
guide.

Hello,

please repone this PR. I gave it another hour, cloned
one of my 5.4-RELEASE-p12 images and tested with that.

And - suprise - the exact same error happened there, too.

I didn't bother to check if X.org install fails there,
too, but I wouldn't be surprised, either.

As for those funny peole who try to convince me that
/usr/src/UPDATING for version 6.1 should be read
by someone before attempting to binary upgrade
something else to that level, this logic is faulty on
multiple levels. First, before the upgrade you do
not have that file, second, it only talks about
source upgrades (if I wanted to do those in this case
I wouldn't go for binary) and third, a simple RTFM
as an answer to a legitimate installation program
option resulting in complete loss of data is
simply unacceptable.

Yes. we expect software to do the Right Thing -
which it does not do here in any conceivable way.
The Right Thing here is either to upgrade the system
or to claim incompetence and refuse to do anything.

Regards

Christoph Weber-Fahr