Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 05 Aug 2007 12:05:43 -0700
From:      Jason Edward Kocol <mrkocol@cv.org>
To:        Kevin Oberman <oberman@es.net>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: Problem adding new slices
Message-ID:  <46B61F87.3080102@cv.org>
In-Reply-To: <20070805190202.5E14945045@ptavv.es.net>
References:  <20070805190202.5E14945045@ptavv.es.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Kevin Oberman wrote:
>> Date: Sun, 05 Aug 2007 10:24:21 -0700
>> From: Jason Edward Kocol <mrkocol@cv.org>
>> Sender: owner-freebsd-stable@freebsd.org
>>
>> I am running 6.2 STABLE and am having an issue adding new slices to a 
>> disk on a running system.  The drive ad0 is 160GB and my original plan 
>> was to add slices as I needed them.  I have successfully created slice 
>> ad0s1 for all typical mount points, and was even able to create ad0s2d 
>> for mount point /c.  The problem now is that I am unable to create a 
>> third slice, ad0s3d, on mount point /d.  I've tried using sysinstall to 
>> do this, and in the Label editor the final message is:
>>
>> Error mounting /dev/ad0s3d on /d : No such file or directory.
>>
>> I checked /dev, and sure enough ad0s3d is not in there.  It just never 
>> gets created.
>>
>> I have tried doing this in several ways; rebooting after using fdisk to 
>> create the partition, then running Label editor but the result is always 
>> the same.  I even tried moving all the files I had on /c to another 
>> machine, deleting that slice (originally 15GB) and creating a much 
>> larger one in its place (now 60GB), but the end result of that is the 
>> "new" slice is the same size of the old one, even though in the Label 
>> editor it shows the new larger size I created.
>>
>> If anyone has any suggestions, even bypassing sysinstall entirely and 
>> using other utilities, please let me know the exact steps to take.
> 
> A bit of a lack of information in yo9ur report.
> 
> Please provide the output of 'fdisk ad0' and 'bsdlabel /dev/ad0s3'. My
> suspicion is that there is a problem in the slicing, but there is not
> any real data in the report on which I can to base that.

Thank you, here is that information:

/root> fdisk ad0
******* Working on device /dev/ad0 *******
parameters extracted from in-core disklabel are:
cylinders=232581 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=232581 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
     start 63, size 30716217 (14998 Meg), flag 80 (active)
         beg: cyl 0/ head 1/ sector 1;
         end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
     start 30716280, size 122865120 (59992 Meg), flag 80 (active)
         beg: cyl 1023/ head 255/ sector 63;
         end: cyl 1023/ head 254/ sector 63
The data for partition 3 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
     start 153581400, size 61432560 (29996 Meg), flag 80 (active)
         beg: cyl 1023/ head 255/ sector 63;
         end: cyl 1023/ head 254/ sector 63
The data for partition 4 is:
<UNUSED>

/root> bsdlabel /dev/ad0s3
bsdlabel: /dev/ad0s3: No such file or directory



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46B61F87.3080102>