Bug 15218

Summary: kernel says: raw partition size != slice size on ext part.
Product: Base System Reporter: Henryk Paluch <paluch>
Component: i386Assignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 3.3-RELEASE   
Hardware: Any   
OS: Any   

Description Henryk Paluch 1999-12-02 10:20:00 UTC
 When installation program attempts to test disks on the start or 
any partition on the 1st drive is mounted, the kernel reports:

 wd0s2: raw partition size != slice size
 wd0s2: start 927360, end 7047935, size 6120576
 wd0s2c: start 927360, end 1991807, size 1064448
                           ^^^^^^^       ^^^^^^^ 500MB ? There is no 500MB
                                                 partition

 Also the installation program hang right after "Starting emergency
 holographic shell...", but it could be easily resolved pressing
 CTRL-ALT-DEL and answering "No" to question about abort of installation.
 

 These problems were seen from 3.0 release. 2.2.x seems to be ok.
 Same installation CD works without problem on another computers.

Fix: 

I don't know any workaround for that message.  It seems to be harmless,
  except that hang on install (I'm unsure, whether it is caused by that
  problem).
How-To-Repeat: 
   Running /stand/sysinstall. Either from Installation disk or
   after install from shell.

   Also mounting any partition causes that message.
Comment 1 iedowse freebsd_committer freebsd_triage 2001-08-12 22:59:50 UTC
State Changed
From-To: open->feedback


Is this still a problem? It looks like a BSD disklabel ended up on 
the second slice, maybe from a previous installation or something. 
If so, you could probably clear it by zeroing the second sector of 
the second slice, though you'd want to be sure that doing so doesn't 
clobber anything important.
Comment 2 iedowse freebsd_committer freebsd_triage 2001-08-13 19:58:53 UTC
State Changed
From-To: feedback->closed


Submitter says this can be closed; the problem went away after a 
reformat, so it was probably a left-over disklabel. A second problem 
mentioned in the PR was not reproducable on other hardware, and 
the submitter is unable to verify if it has been resolved. Thanks 
for the quick response!