Date: Tue, 21 Oct 2008 11:42:27 -0400 From: Jerry McAllister <jerrymc@msu.edu> To: Per olof Ljungmark <peo@intersonic.se> Cc: freebsd-questions@freebsd.org Subject: Re: need help with disklabel, "expected rawoffset 0, found 32" Message-ID: <20081021154227.GE43091@gizmo.acns.msu.edu> In-Reply-To: <48FD8A90.5080007@intersonic.se> References: <48FD8A90.5080007@intersonic.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 21, 2008 at 09:53:52AM +0200, Per olof Ljungmark wrote: > Hi, > > I think sysinstall? got it wrong here and I get the complaint in the > subject line on boot. This is amd64 if that matters. Nothing edited by hand. > > I must admit I don't fully understand what is going on here, "found 32" > but the offsets are 63... > > Filesystem on LSI controller amr(4): > > # /dev/amrd0s1a: > type: ESDI > disk: amrd0s1 > label: > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 255 > sectors/cylinder: 16065 > cylinders: 65535 > sectors/unit: 2929674240 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # milliseconds > track-to-track seek: 0 # milliseconds > drivedata: 0 > > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > a: 4194304 63 4.2BSD 2048 16384 28528 > b: 8388608 4194367 swap > c: 2929661532 63 unused 0 0 # "raw" part, > don't edit > d: 31457280 12582975 4.2BSD 2048 16384 28528 > e: 2097152 44040255 4.2BSD 2048 16384 28528 > f: 41943040 46137407 4.2BSD 2048 16384 28528 > g: 2841581148 88080447 4.2BSD 2048 16384 28528 > bsdlabel: partition c doesn't start at 0! > bsdlabel: partition c doesn't cover the whole unit! > bsdlabel: An incorrect partition c may cause problems for standard > system utilities I do not know what is causing this, but I think the offset of the 'c' partition (and the first real partition (a in this case)) should be 0 I have seen this a couple of times a long time ago and don't remember what happened other than I think I just arbitrarily set those offsets to 0 and it worked. Can you try booting up the fixit shell and hitting the disk with a manual fdisk and bsdlabel to see what happens. Also, you might try doing the dd(1) thing dd if=/dev/zero of=/dev/amrd0 bs=512 count=1000 before the fdisk and then another one after creating the slices manually dd if=/dev/zero of=/dev/amrd0s1 bs=512 count=1000 Note, that count value is arbitrary. That should clean up any junk on the drive. Also, I haven't seen/dealt with a disk device called amrd0 before. It appears to be something from one of the raid setups? So, maybe doing the dd thing might mangle that although, once it is a device, it should work the same as a drive. I ain't rich enough to have one of those raids to play with, though, so if someone else says otherwise, believe them. ////jerry > > > Filesystem on SmartArray controller ciss(4): > > # /dev/da0s1d: > type: SCSI > disk: da0s1 > label: > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 255 > sectors/cylinder: 16065 > cylinders: 53544 > sectors/unit: 860192344 > rpm: 3600 > interleave: 1 > trackskew: 0 > cylinderskew: 0 > headswitch: 0 # milliseconds > track-to-track seek: 0 # milliseconds > drivedata: 0 > > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 860184297 63 unused 0 0 # "raw" part, > don't edit > d: 860184297 63 4.2BSD 2048 16384 28528 > bsdlabel: partition c doesn't start at 0! > bsdlabel: partition c doesn't cover the whole unit! > bsdlabel: An incorrect partition c may cause problems for standard > system utilities > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081021154227.GE43091>