Otto Moerbeek wrote:
On Mon, Apr 05, 2010 at 11:18:35PM +0200, bdz wrote:
Otto Moerbeek wrote:
On Tue, Apr 06, 2010 at 12:12:04AM +0200, bdz wrote:
hi!
i installed my system with the automated disklabel layout, i
just made some size modifications. the disk is a 500G sata. i
got a lot of space at the end of the disk that now i want to use
as storage. i can not add the new label 'l' because disklabel
says:
a l
offset: [0]
The offset must be >= 0 and < 0, the limits of the OpenBSD portion
of the disk. The 'b' command can change these limits.
the response is the same for any specified number.
here is the current layout:
p
OpenBSD area: 0-0; size: 0; free: 63
# size offset fstype [fsize bsize cpg]
a: 2104452 63 4.2BSD 2048 16384 1 # /
b: 2104515 2104515 swap
c: 976773168 0 unused
d: 530145 4209030 4.2BSD 2048 16384 1 #
/tmp
e: 10490445 4739175 4.2BSD 2048 16384 1 # /var
f: 4209030 15229620 4.2BSD 2048 16384 1 # /usr
g: 2104515 19438650 4.2BSD 2048 16384 1
# /usr/X11R6
h: 12594960 21543165 4.2BSD 2048 16384 1
# /usr/local
i: 4209030 34138125 4.2BSD 2048 16384 1 # /usr/src
j: 4209030 38347155 4.2BSD 2048 16384 1 # /usr/obj
k: 2104515 42556185 4.2BSD 2048 16384 1 # /home
it displays the OpenBSD area: 0-0 wrong. what do you suggest to
help with this situation?
Show you fdisk output. Likely the A6 partiton is funny.
could the following work?
- use disklabel -e
- make a new line with label 'l':
l: SIZE OFFSET RAID 2048 16384 1 # /home/storage
- SIZE: c size - (sizes a,b,d-k + 63)
- OFFSET: size k + offset k
- RAID for softraid crypto
- :x
If your fdisk settings are ok, you can fisk the openbsd area wit the b
command. But first check what fdisk reports.
-Otto
hi Otto,
strange thing happened. i did as you suggested, used the 'b' command
w/ 63, * parameters. then i could add the new 'l' partition with no
problem and the starting and ending sectors are fine (63-976773168).
after i quit i went back for checking things out and the
starting/ending sectors are 0 again but the 'l' partition is in
place. so i send you the disklabel to see if you can find any odd
things.
Very strange. I cannot see what this would happen, and this is the
first report describining anything like it. Anyway, thanks for the
info, and I'll investigate what could be going on.
In the meantime, I think your disk is good to use. The bounds are only
used for editing, and will not influence runtime operations.
everything is all right. the new partition is working good so thank you
for your help.
-Otto
thank you
Adam
# /dev/rwd0c:
type: ESDI
disk: ESDI/IDE disk
label: SAMSUNG HD502IJ
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 60801
total sectors: 976773168
rpm: 3600
interleave: 1
boundstart: 0
boundend: 0
drivedata: 0
16 partitions:
# size offset fstype [fsize bsize cpg]
a: 2104452 63 4.2BSD 2048 16384 1 # /
b: 2104515 2104515 swap
c: 976773168 0 unused
d: 530145 4209030 4.2BSD 2048 16384 1 # /tmp
e: 10490445 4739175 4.2BSD 2048 16384 1 # /var
f: 4209030 15229620 4.2BSD 2048 16384 1 # /usr
g: 2104515 19438650 4.2BSD 2048 16384 1 # /usr/X11R6
h: 12594960 21543165 4.2BSD 2048 16384 1 # /usr/local
i: 4209030 34138125 4.2BSD 2048 16384 1 # /usr/src
j: 4209030 38347155 4.2BSD 2048 16384 1 # /usr/obj
k: 2104515 42556185 4.2BSD 2048 16384 1 # /home
l: 932112468 44660700 RAID
