[EMAIL PROTECTED] wrote:
...
dangit... forgot to fix that. 8-/
yes, that was me...
Nick.
[EMAIL PROTECTED] wrote:
> Quoting Otto Moerbeek <[EMAIL PROTECTED]>:
>
>>
>> On Wed, 31 Jan 2007, Tony Abernethy wrote:
>>
>>> [EMAIL PROTECTED] wrote:
>>> 16 partitions:
>>> # sizeoffset fstype [fsize bsize cpg]
>>>a: 390721968 0 4.2BSD 2048 16384 32
Greg Thomas wrote:
>
> On 2/1/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Quoting Otto Moerbeek <[EMAIL PROTECTED]>:
> >
> > >
> > > On Wed, 31 Jan 2007, Tony Abernethy wrote:
> > >
> > >> [EMAIL PROTECTED] wrote:
> > >> 16 partitions:
> > >> # sizeoffset fstype [fsiz
On 2/1/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Quoting Otto Moerbeek <[EMAIL PROTECTED]>:
>
> On Wed, 31 Jan 2007, Tony Abernethy wrote:
>
>> [EMAIL PROTECTED] wrote:
>> 16 partitions:
>> # sizeoffset fstype [fsize bsize cpg]
>>a: 390721968 0 4
On Thu, 1 Feb 2007, [EMAIL PROTECTED] wrote:
> Quoting Otto Moerbeek <[EMAIL PROTECTED]>:
>
> >
> > On Wed, 31 Jan 2007, Tony Abernethy wrote:
> >
> > > [EMAIL PROTECTED] wrote:
> > > 16 partitions:
> > > # sizeoffset fstype [fsize bsize cpg]
> > >a: 390721968
Quoting Otto Moerbeek <[EMAIL PROTECTED]>:
On Wed, 31 Jan 2007, Tony Abernethy wrote:
[EMAIL PROTECTED] wrote:
16 partitions:
# sizeoffset fstype [fsize bsize cpg]
a: 390721968 0 4.2BSD 2048 16384 328 # Cyl 0
-387620
c: 390721968
Quoting Bryan Irvine <[EMAIL PROTECTED]>:
Obviously something is screwy. Try posting the output of 'fdisk wd1',
'disklabel wd1' and at *least* the portion of your dmesg corresponding
to the disk. No way to tell what's messed up just from df output.
I know this may sound dumb, but can you als
On Wed, 31 Jan 2007, Tony Abernethy wrote:
> [EMAIL PROTECTED] wrote:
> 16 partitions:
> # sizeoffset fstype [fsize bsize cpg]
>a: 390721968 0 4.2BSD 2048 16384 328 # Cyl 0
> -387620
>c: 390721968 0 unused 0 0 # C
On 01 Feb 2007 12:26:09 +0100, Artur Grabowski wrote:
>[EMAIL PROTECTED] writes:
>
>> I just moved a 200GB hard drive from a 3.7 box to a 4.0 box, and since
>> my data was all backed up, I decided to run disklabel, create a fresh
>> partition that spanned the whole disk, and then run newfs on that
I'll qoute Greg on this one:
"He's asking about the 38G, not the difference between 200 and 183."
/daniel
>> I just moved a 200GB hard drive from a 3.7 box to a 4.0 box, and since
>> my data was all backed up, I decided to run disklabel, create a fresh
>> partition that spanned the whole disk, a
[EMAIL PROTECTED] writes:
> I just moved a 200GB hard drive from a 3.7 box to a 4.0 box, and since
> my data was all backed up, I decided to run disklabel, create a fresh
> partition that spanned the whole disk, and then run newfs on that
> partition. I expect to not have all 200GB, between the wh
On 1/31/07, Mats O Jansson <[EMAIL PROTECTED]> wrote:
On Wed, 31 Jan 2007 [EMAIL PROTECTED] wrote:
> I just moved a 200GB hard drive from a 3.7 box to a 4.0 box, and since
> my data was all backed up, I decided to run disklabel, create a fresh
> partition that spanned the whole disk, and then ru
On Wed, 31 Jan 2007 [EMAIL PROTECTED] wrote:
> I just moved a 200GB hard drive from a 3.7 box to a 4.0 box, and since
> my data was all backed up, I decided to run disklabel, create a fresh
> partition that spanned the whole disk, and then run newfs on that
> partition. I expect to not have all
[EMAIL PROTECTED] wrote:
16 partitions:
# sizeoffset fstype [fsize bsize cpg]
a: 390721968 0 4.2BSD 2048 16384 328 # Cyl 0
-387620
c: 390721968 0 unused 0 0 # Cyl 0
-387620
Most likely, the disklabel or boot cod
Obviously something is screwy. Try posting the output of 'fdisk wd1',
'disklabel wd1' and at *least* the portion of your dmesg corresponding
to the disk. No way to tell what's messed up just from df output.
I know this may sound dumb, but can you also post the output of 'ls
-al /mnt'? :-)
--
On Wed, Jan 31, 2007 at 09:42:07PM -0500, [EMAIL PROTECTED] wrote:
I just moved a 200GB hard drive from a 3.7 box to a 4.0 box, and since
my data was all backed up, I decided to run disklabel, create a fresh
partition that spanned the whole disk, and then run newfs on that
partition. I expect to
On Wed, Jan 31, 2007 at 09:42:07PM -0500, [EMAIL PROTECTED] wrote:
> I just moved a 200GB hard drive from a 3.7 box to a 4.0 box, and since
> my data was all backed up, I decided to run disklabel, create a fresh
> partition that spanned the whole disk, and then run newfs on that
> partition. I e
I just moved a 200GB hard drive from a 3.7 box to a 4.0 box, and since
my data was all backed up, I decided to run disklabel, create a fresh
partition that spanned the whole disk, and then run newfs on that
partition. I expect to not have all 200GB, between the whole issue of
poorly labeled dis
18 matches
Mail list logo