>Number:         11727
>Category:       bin
>Synopsis:       Sysinst has a fit on upgrade with ccd devices
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 13 09:36:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     Tim Rightnour
>Release:        1.5<NetBSD-current source date>
>Organization:
	
>Environment:
	
System: NetBSD polaris 1.5_ALPHA2 NetBSD 1.5_ALPHA2 (POLARIS) #1: Wed Dec 13 00:45:28 MST 2000 root@polaris:/usr/src/sys/arch/i386/compile/POLARIS i386


>Description:
When upgrading my machine, which has a few ccd's sysinst's upgrade procedure
reacted quite poorly to the ccd's.  Not only does it fail to configure ccd's,
but it then attempts to fsck them, and will refuse to allow you to upgrade
the machine.

In addition, dropping out to a shell to fix things, doesn't work, because 
sysinst reads the fstab into memory, and tries it again even if you edit the
file, requiring you to quit sysinst and restart it to fsck.

	
>How-To-Repeat:
Attempt to upgrade a machine with ccd's on board.

	
>Fix:
The real fix is to include the ccd driver and ccdconfig in the install kernel.
However there might be space issues.  In the very least, it should warn you
that it's not going to work, or possibly ask the user if they want to just
ignore the ccd's for now, and continue to upgrade.  (for example, if
non-upgrade related filesystems are on the ccd, as was my case)

This is a serious issue however, and IMHO we should include ccd in the kernel.
I'm sure raidframes will have the same problem.
	
>Release-Note:
>Audit-Trail:
>Unformatted: