From owner-freebsd-current Sat Apr 1 08:48:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA17059 for current-outgoing; Sat, 1 Apr 1995 08:48:12 -0800 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA17049 for ; Sat, 1 Apr 1995 08:47:55 -0800 Received: from localhost (localhost [127.0.0.1]) by grunt.grondar.za (8.6.11/8.6.9) with SMTP id SAA06261; Sat, 1 Apr 1995 18:46:22 +0200 Message-Id: <199504011646.SAA06261@grunt.grondar.za> X-Authentication-Warning: grunt.grondar.za: Host localhost didn't use HELO protocol To: Bruce Evans cc: Kai.Vorma@hut.fi, current@FreeBSD.org Subject: Re: panic: update: rofs mod Date: Sat, 01 Apr 1995 18:46:21 +0200 From: Mark Murray Sender: current-owner@FreeBSD.org Precedence: bulk > Both the d-partition and any DOS-partitions outside the BSD slice are > now obsolete. The slice code complains about them because it doesn't > know exactly what to do about them. You might want to keep them for > compatibility. This is easy to do by ignoring the warning and not > running disklabel to kill the warning OR to make any other changes. > The label writing routine is fussier than the label reading routine > and won't allow writing the obsolete partitions. You might not even > notice that they were gone if there was no warning. I've been watching this thread for a while, hoping to learn something. I picked up quite a bit, thanks. I had similar problems to Kai, but I remembered the changes, so no panic. what I cannot get round is this: (please bear with me) I am running current (ctm 471) with a 2-3 day old kernel. > Mar 31 12:42:49 grunt /kernel: sd0s4: start 1, end = 412359, size 412359: OK > Mar 31 12:42:49 grunt /kernel: sd0: rejecting partition in BSD label: it isn't entirely within the slice (**) > Mar 31 12:42:50 grunt /kernel: sd0: start 1, end 412359, size 412359 > Mar 31 12:42:50 grunt /kernel: sd0d: start 0, end 415599, size 415600 (x3) (**) This I can fix by getting rid of the "d" partition, right? EXCEPT I get this when I exit disklabel: > # /dev/rsd0c: > type: SCSI > disk: > label: MBR based label > flags: > bytes/sector: 512 > sectors/track: 61 > tracks/cylinder: 4 > sectors/cylinder: 244 > cylinders: 1689 > sectors/unit: 412359 > rpm: 3600 (was zero) > interleave: 1 (was zero) > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # milliseconds > track-to-track seek: 0 # milliseconds > drivedata: 0 > > 4 partitions: (was eight) > # Hsize offset fstype [fsize bsize bps/cpg] > a: 40960 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 167*) > b: 65536 40960 swap # (Cyl. 167*- 436*) > c: 412359 0 unused # (Cyl. 0 - 1689*) > e: 305152 106496 4.2BSD 1024 8192 16 # (Cyl. 436*- 1687*) [exit] > Warning, unused partition e: size 305152 offset 106496 > disklabel: ioctl DIOCSDINFO: Open partition would move or shrink > re-edit the label? [y]: n 1) What does the DIOCSDINFO mean? 2) e is most certainly not unused! The logfile continues: > Mar 31 12:42:50 grunt /kernel: sd1s4: start 1, end = 2045651, size 2045651 > Mar 31 12:42:50 grunt /kernel: sd1s4: C/H/S end 933/6/34 (222291) != end 2045651: invalid (+++) > Mar 31 12:42:51 grunt /kernel: sd1: rejecting partition in BSD label: it isn't entirely within the slice (**) > Mar 31 12:42:51 grunt /kernel: sd1: start 1, end 2045651, size 2045651 > Mar 31 12:42:51 grunt /kernel: sd1d: start 0, end 2056007, size 2056008 (x2) (**) above is the same 'd' partition problem as above, and I cannot get rid of it either for the same reasons. (+++) is wierd. Ths is a 1GB SCSI disk, and the variable (or whatever) used to hold the number of tracks seems a little messed up. Here is an fdisk session > bash# fdisk -u /dev/rsd1c > ******* Working on device /dev/rsd1c ******* > parameters extracted from in-core disklabel are: > cylinders=2981 heads=7 sectors/track=98 (686 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=2981 heads=7 sectors/track=98 (686 blks/cyl) ** These are OK > > Do you want to change our idea of what BIOS thinks ? [n] > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 0 is: > > Do you want to change it? [n] > The data for partition 1 is: > > Do you want to change it? [n] > The data for partition 2 is: > > Do you want to change it? [n] > The data for partition 3 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 1, size 2045651 (998 Meg), flag 80 > beg: cyl 0/ sector 2/ head 0; > end: cyl 933/ sector 34/ head 6 > Do you want to change it? [n] y > Supply a decimal value for "sysid" [165] > Supply a decimal value for "start" [1] > Supply a decimal value for "size" [2045651] > Explicitly specifiy beg/end address ? [n] y > Supply a decimal value for "beginning cylinder" [0] > Supply a decimal value for "beginning head" [0] > Supply a decimal value for "beginning sector" [2] > Supply a decimal value for "ending cylinder" [933] 2981 ** Look here! > Supply a decimal value for "ending head" [6] > Supply a decimal value for "ending sector" [34] > sysid 165,(FreeBSD/NetBSD/386BSD) > start 1, size 2045651 (998 Meg), flag 80 > beg: cyl 0/ sector 2/ head 0; > end: cyl 933/ sector 34/ head 6 ** WTF?? > Are we happy with this entry? [n] ** Of course not! > Supply a decimal value for "sysid" [165] ^C ** Outta here! Any pointers? M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200