Re: GEOM prevents bootblocks writing
Since I haven't seen any response to this, I'll me too it in hopes that it will get some attention drawn to it. Not only do I have seem to somehow broken my bootblocks so boot0 beeps at me when I select F1 FreeBSD, I am now no longer able to write new bootblocks: edgemaster# disklabel -r ad1s1 ... 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 1024000 62914564.2BSD 2048 1638490 # (Cyl. 391*- 455*) b: 62914560 swap# (Cyl.0 - 391*) c: 1172262420unused0 0# (Cyl.0 - 7296*) e: 10485760 73154564.2BSD 2048 1638489 # (Cyl. 455*- 1108*) f: 99425026 178012164.2BSD 2048 1638489 # (Cyl. 1108*- 7296*) edgemaster# disklabel -r ad1s1 ... 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 1024000 62915194.2BSD 2048 1638490 # (Cyl. 391*- 455*) b: 6291456 63 swap# (Cyl.0*- 391*) c: 117226242 63unused0 0# (Cyl.0*- 7296*) e: 10485760 73155194.2BSD 2048 1638489 # (Cyl. 455*- 1108*) f: 99425026 178012794.2BSD 2048 1638489 # (Cyl. 1108*- 7296*) partition c: partition extends past end of unit Warning, partition c doesn't start at 0! Warning, An incorrect partition c may cause problems for standard system utiliti es partition f: partition extends past end of unit edgemaster# disklabel -B ad1s1 partition c: partition extends past end of unit Warning, partition c doesn't start at 0! Warning, An incorrect partition c may cause problems for standard system utilities partition f: partition extends past end of unit edgemaster# I'm not even sure what is going on here, but something is clearly not right. Like I said, I can't even boot this anymore. F1 FreeBSD F5 Disk 0 Selecting F1 just beeps at me. Fortunately I can still go to disk 0 and boot via boot2. Help :( On Sun, Dec 22, 2002 at 03:38:37AM +0300, Andrey A. Chernov wrote: Now I can't update my bootblocks to new ones using 'disklabel -B da0s1', checklabel() disklabel function return error preventing actual write with following diagnostic: partition b: partition extends past end of unit partition c: partition extends past end of unit Warning, partition c doesn't start at 0! Warning, An incorrect partition c may cause problems for standard system utilities Warning, partition d: size 0, but offset 32 Warning, partition e: size 0, but offset 32 Warning, partition f: size 0, but offset 32 Warning, partition g: size 0, but offset 32 Warning, partition h: size 0, but offset 32 In fact, this is exact the same diagnostic as from 'disklabel -r da0s1': # /dev/da0s1c: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 17500 sectors/unit: 35842016 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0# milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 34611200 324.2BSD 2048 1638464 # (Cyl.0*- 16900) b: 1230816 34611232 swap # (Cyl. 16900*- 17500*) c: 35842016 32unused0 0 # (Cyl.0*- 17500*) partition b: partition extends past end of unit partition c: partition extends past end of unit Warning, partition c doesn't start at 0! Warning, An incorrect partition c may cause problems for standard system utilities Warning, partition d: size 0, but offset 32 Warning, partition e: size 0, but offset 32 Warning, partition f: size 0, but offset 32 Warning, partition g: size 0, but offset 32 Warning, partition h: size 0, but offset 32 For comparison see just 'disklabel da0s1' output which indicate no errors and no mysterious offset 32 in the data: # /dev/da0s1c: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 17500 sectors/unit: 35842016 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0# milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 3461120004.2BSD 2048 1638464 # (Cyl.0 - 16899) b: 1230816 34611200 swap # (Cyl. 16900 - 17500*) c: 358420160unused0 0 # (Cyl.0 - 17500*) Please fix this GEOM bug, to allow to update bootblocks at least. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Sean Kelly | PGP KeyID: D2E5E296 [EMAIL PROTECTED] | http://www.zombie.org msg50029/pgp0.pgp
Re: GEOM prevents bootblocks writing
In message [EMAIL PROTECTED], Sean Kelly writes: Since I haven't seen any response to this, I'll me too it in hopes that it will get some attention drawn to it. boot0cfg and fdisk should work as advertised. There is an erratum on disklabel -B for 5.0-RELEASE. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: GEOM prevents bootblocks writing
On Sun, Jan 12, 2003 at 12:49:46PM +0100, [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Sean Kelly writes: Since I haven't seen any response to this, I'll me too it in hopes that it will get some attention drawn to it. boot0cfg and fdisk should work as advertised. edgemaster# boot0cfg -B ad1 boot0cfg: /dev/ad1: ioctl DIOCSMBR: Operation not permitted edgemaster# fdisk -B ad1 ... fdisk: can't write fdisk partition table: Operation not permitted edgemaster# disklabel -B ad1s1 partition c: partition extends past end of unit Warning, partition c doesn't start at 0! Warning, An incorrect partition c may cause problems for standard system utilities partition f: partition extends past end of unit I've tried doing fdisk and boot0cfg even in singleuser with / mounted readonly. Is this really the way it is supposed to work? I do not remember it behaving like this pre-GEOM. There is an erratum on disklabel -B for 5.0-RELEASE. So how the hell do I make it so I can boot my system again? I don't know what I/it did to make it no longer boot, but I can't. Boot0 shows me a list F1 FreeBSD, F5 Disk 1. If i choose F1, it just beeps at me. I don't even know why it is beeping at me, because that same FreeBSD partition/slice mounts and works if booted via other methods. -- Sean Kelly | PGP KeyID: D2E5E296 [EMAIL PROTECTED] | http://www.zombie.org msg50051/pgp0.pgp Description: PGP signature
Re: GEOM prevents bootblocks writing
Sean Kelly wrote: --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 12, 2003 at 12:49:46PM +0100, [EMAIL PROTECTED] wrote: There is an erratum on disklabel -B for 5.0-RELEASE. So how the hell do I make it so I can boot my system again? I don't know what I/it did to make it no longer boot, but I can't. For the short term until the problem is fixed you should be able to edit the disklabel and bootblocks using a floppy fixit disk or the bootable install CD. The problem, IIRC, is that you can't edit a disklabel on a disk with mounted partitions, or somesuch. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
GEOM prevents bootblocks writing
Now I can't update my bootblocks to new ones using 'disklabel -B da0s1', checklabel() disklabel function return error preventing actual write with following diagnostic: partition b: partition extends past end of unit partition c: partition extends past end of unit Warning, partition c doesn't start at 0! Warning, An incorrect partition c may cause problems for standard system utilities Warning, partition d: size 0, but offset 32 Warning, partition e: size 0, but offset 32 Warning, partition f: size 0, but offset 32 Warning, partition g: size 0, but offset 32 Warning, partition h: size 0, but offset 32 In fact, this is exact the same diagnostic as from 'disklabel -r da0s1': # /dev/da0s1c: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 17500 sectors/unit: 35842016 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 34611200 324.2BSD 2048 1638464 # (Cyl.0*- 16900) b: 1230816 34611232 swap# (Cyl. 16900*- 17500*) c: 35842016 32unused0 0 # (Cyl.0*- 17500*) partition b: partition extends past end of unit partition c: partition extends past end of unit Warning, partition c doesn't start at 0! Warning, An incorrect partition c may cause problems for standard system utilities Warning, partition d: size 0, but offset 32 Warning, partition e: size 0, but offset 32 Warning, partition f: size 0, but offset 32 Warning, partition g: size 0, but offset 32 Warning, partition h: size 0, but offset 32 For comparison see just 'disklabel da0s1' output which indicate no errors and no mysterious offset 32 in the data: # /dev/da0s1c: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 17500 sectors/unit: 35842016 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 3461120004.2BSD 2048 1638464 # (Cyl.0 - 16899) b: 1230816 34611200 swap# (Cyl. 16900 - 17500*) c: 358420160unused0 0 # (Cyl.0 - 17500*) Please fix this GEOM bug, to allow to update bootblocks at least. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
