Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 5 May 2010 21:53:12 +0100
From:      krad <kraduk@googlemail.com>
To:        Polytropon <freebsd@edvax.de>
Cc:        FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: dangerously dedicated disks and 8-stable status
Message-ID:  <r2zd36406631005051353v105e8553rc27850405c0ddd19@mail.gmail.com>
In-Reply-To: <i2wd36406631005051328vfb63a729u1670cbac3d9ed515@mail.gmail.com>
References:  <z2td36406631005050917t1b7ea0bcwfb8ccb2487123846@mail.gmail.com> <20100505195544.be380d17.freebsd@edvax.de> <i2wd36406631005051328vfb63a729u1670cbac3d9ed515@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 5 May 2010 21:28, krad <kraduk@googlemail.com> wrote:

>
>
> On 5 May 2010 18:55, Polytropon <freebsd@edvax.de> wrote:
>
>> On Wed, 5 May 2010 17:17:09 +0100, krad <kraduk@googlemail.com> wrote:
>> > I updated a production box at work last night from freebsd 6.2 to
>> 8-stable,
>> > via 7-stable. The upgrade went ok just a minor glitch in jumping from 7
>> to
>> > 8. Basically all the device names changed from mfid0s1[a-g] to
>> mfid0[a-g]. I
>> > presume this is because the initial layout was  in dangerously dedicated
>> > mode.
>>
>> That's strange. "Dangerously" dedicated partitioning omits the
>> slicing part, so if you had mfid0s1[a-g] in 6 and 7, there was
>> a slice. Maybe the mfi driver is different in 8 in terms of
>> representing the disks?
>>
>>
>>
>> > Two issues here why did the naming scheme seem to indicate a more
>> > normal MBR disk layout in bsd 6 and 7.
>>
>> Very strange - if you can check booting from a live system CD
>> or DVD with FreeBSD 6 and 7, and the disks are mfid0s1[a-g],
>> and if you boot into FreeBSD 8, the disks are mfid0[a-g], that's
>> really strange...
>>
>> I agree, but it definitely happened, as i did the upgrade remotely.
> Luckily the data center was only a mile or so away from my home, so it
> wasn't a major disaster to console it, point the kernel at  the correct
> device and tweak fstab. COst me an hour more sleep than it had to though 8(
>
> I have another box to do in the next day or so. Is there anything you
> recommend me looking at/running? Hopefully this box will have a drac card in
> it 8)
>
>>
>>
>> > Second what is the current status of
>> > dangerously dedicated in 8-stable as i thought support was being
>> dropped.
>>
>> The support has been removed from sysinstall. You can't create
>> dedicated partitions (without slice) with sysinstall, but you
>> can create them manually (e. g. using bsdlabel and newfs). So
>> support isn't dropped at all - dedicated disks just is a new
>> special secret feature. :-)
>>
>>
>> This was the bit i was worried about, as i didnt want to get caught out in
> the future when I want to upgrade again
>
>>
>> --
>>
>> Polytropon
>> Magdeburg, Germany
>> Happy FreeBSD user since 4.0
>> Andra moi ennepe, Mousa, ...
>>
>
>

Hmm, things get a little strange

on a box I built from scratch

# bsdlabel /dev/mfid0
bsdlabel: /dev/mfid0: no valid label found

# bsdlabel /dev/mfid0s1
# /dev/mfid0s1:
8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:  4194304        0    4.2BSD     2048 16384 28528
  b:  8388608  4194304      swap
  c: 285458922        0    unused        0     0         # "raw" part, don't
edit
  d: 16777216 12582912    4.2BSD     2048 16384 28528
  e:  8388608 29360128    4.2BSD     2048 16384 28528
  f:  8388608 37748736    4.2BSD     2048 16384 28528
  g: 129954672 46137344    4.2BSD     2048 16384 28528
  h: 109366906 176092016    4.2BSD     2048 16384 28528

All fairly normal

One the next box I have to upgrade (built by a former employee who was well
known for his qwirky ways)

# bsdlabel /dev/mfid0s1
# /dev/mfid0s1:
8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:  2097152        0    4.2BSD     2048 16384 28528
  b: 16777216  2097152      swap
  c: 142082048        0    unused        0     0         # "raw" part, don't
edit
  d: 16777216 18874368    4.2BSD     2048 16384 28528
  e: 16777216 35651584    4.2BSD     2048 16384 28528
  f: 16777216 52428800    4.2BSD     2048 16384 28528
  g: 72876032 69206016    4.2BSD     2048 16384 28528

# bsdlabel /dev/mfid0
# /dev/mfid0:
8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:  2097152        0    4.2BSD     2048 16384 28528
  b: 16777216  2097152      swap
  c: 142082048        0    unused        0     0         # "raw" part, don't
edit
  d: 16777216 18874368    4.2BSD     2048 16384 28528
  e: 16777216 35651584    4.2BSD     2048 16384 28528
  f: 16777216 52428800    4.2BSD     2048 16384 28528
  g: 72876032 69206016    4.2BSD     2048 16384 28528

not sure what he has done fdisk output is fairly normal on this box as well

******* Working on device /dev/mfid0 *******
parameters extracted from in-core disklabel are:
cylinders=8844 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=8844 heads=255 sectors/track=63 (16065 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 0, size 142082048 (69376 Meg), flag 80 (active)
        beg: cyl 0/ head 0/ sector 1;
        end: cyl 1023/ head 50/ sector 38
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>

looks like i will have to change fstab again. At least I wont have to travel
this time though



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