Date: Mon, 27 Mar 1995 15:52:27 +1000 From: Bruce Evans <bde@zeta.org.au> To: freebsd-current@freefall.cdrom.com, jmz@cabri.obs-besancon.fr Subject: Re: sd errors Message-ID: <199503270552.PAA08940@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>With a -current kernel (03/25) I get the following messages after boot: >/kernel: sd0: raw partition size != slice size >/kernel: sd0: start 0, end 2065249, size 2065250 >/kernel: sd0c: start 0, end 2390975, size 2390976 >/kernel: sd0: truncating raw partition >/kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice >/kernel: sd0: start 0, end 2065249, size 2065250 >/kernel: sd0d: start 0, end 2390975, size 2390976 >/kernel: sd1: raw partition size != slice size >/kernel: sd1: start 0, end 1075648, size 1075649 >/kernel: sd1c: start 0, end 1075451, size 1075452 >/kernel: sd1: raw partition size != slice size >/kernel: sd1: start 0, end 1075648, size 1075649 >/kernel: sd1c: start 0, end 1075451, size 1075452 >The drives were newfs/labelled a long time ago (1.1.5). On both disks, >the c partition stands the whole disk. It not is not mounted for sd0, >but mounted for sd1. Is there a way to solve this? (NO don't tell me >to newfs my drives!) These errors are probably harmless. The c partitions apparently weren't the whole disk. This may have been caused by rounding their size to a cylinder boundary. The end of the c partition isn't critical for sd drives so fixing it should not do anything except the stop the warnings. The end of the c partition is critical for old wd drives (the bad sector table goes there). If you remove the d partition, 1.1.5 may have problems. The 2.x sd driver silently ignores what the disklabel says about the d partition and replaces it by the whole disk (offset 0 and size reported by the drive), so removing it should not cause any compatibility problems for 2.x. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503270552.PAA08940>