On 12/15/2011 10:02 AM, per...@pluto.rain.com wrote:
> I suppose if someone wanted to track down the "official" way of
> solving this problem, they could look into how Windows handles it.
To my knowledge, Windows (XP, at least; probably others) labels the boot
filesystem on install, and just probe
CyberLeo Kitsana wrote:
> On 12/14/2011 03:18 PM, Rob wrote:
> > Case in point. I have a system with 15 drives in it. I decided
> > I wanted to install on the 2nd device instead of the 1st, but
> > I partitioned all the other 14 drives. I completed installation
> > and when to boot the system a
On 12/14/11 8:05 PM, CyberLeo Kitsana wrote:
The other option seems to be to use tunefs or a partitioning tool to
label each partition, which is even more ugly imo.
Ugly how? Labels appear a lot more semantically elegant than the opaque
'ada4s1a' moniker.
Ugly in that the driver has created a
On 12/14/2011 03:18 PM, Rob wrote:
> On 12/3/11 11:04 AM, CyberLeo Kitsana wrote:
>> To answer your question, though: You cannot combine GPT with glabel (or
>> any other geom class that writes data to the first or last 34 sectors of
>> a disk, like gmirror) due to layout conflicts. MBR and BSD sche
On 12/14/2011 03:20 PM, Rob wrote:
> Can glabels, gpt, and zfs all work together? I have a system where I
> have disks with 4 gpt partitions. Partitions 2 and 3 are part of gmirror
> arrays, and partition 4 is part of a zfs pool. glabel says it writes to
> the end of the partition, which I believ
Can glabels, gpt, and zfs all work together? I have a system where I
have disks with 4 gpt partitions. Partitions 2 and 3 are part of gmirror
arrays, and partition 4 is part of a zfs pool. glabel says it writes to
the end of the partition, which I believe zfs also writes to doesn't it?
Rob
On 12/3/11 11:04 AM, CyberLeo Kitsana wrote:
To answer your question, though: You cannot combine GPT with glabel (or
any other geom class that writes data to the first or last 34 sectors of
a disk, like gmirror) due to layout conflicts. MBR and BSD schemes can
be used, since they occupy only the
On 12/04/2011 04:28 AM, per...@pluto.rain.com wrote:
> CyberLeo Kitsana wrote:
>
>> You cannot combine GPT with glabel (or any other geom class
>> that writes data to the first or last 34 sectors of a disk,
>> like gmirror) due to layout conflicts.
>
> This is overstated.
Thanks for the clarifi
CyberLeo Kitsana wrote:
> You cannot combine GPT with glabel (or any other geom class
> that writes data to the first or last 34 sectors of a disk,
> like gmirror) due to layout conflicts.
This is overstated. Since a GPT ordinarily is intended to be booted
from, and so must be recognized by the
> I was getting ready to install the latest FreeBSD 9-RCs image, and I
> found that 9 now defaults to using the ahci driver for sata disks. This
> would be great if it weren't for the fact that the ahci driver seems to
> do dynamic device name assignment as opposed to the static ones used
> with
On 12/03/2011 10:04 AM, Rob wrote:
> glabel looks to place a label on the whole disk, but the manpage is
> unclear (to me) how the partitions are handled. If I use glabel to
> label a disk "test" and this disk has 4 partitions on it, then how is
> each partition accessed? testp1...testp4 for gpt?
Is there a loader.conf entry to enable the static ids, or will the ahci
driver always use static ids if "options ATA_STATIC_ID" is in the kernel
config? I desire to use stock kernels and the 9-rc2 boot iso seems to
not have ATA_STATID_ID set (unless there's a loader.conf value to enable
the fu
glabel looks to place a label on the whole disk, but the manpage is
unclear (to me) how the partitions are handled. If I use glabel to
label a disk "test" and this disk has 4 partitions on it, then how is
each partition accessed? testp1...testp4 for gpt?
The other option seems to be to use t
On 2011/12/03 at 10:51, Rob wrote:
>
> I was getting ready to install the latest FreeBSD 9-RCs image, and I
> found that 9 now defaults to using the ahci driver for sata disks.
> This would be great if it weren't for the fact that the ahci driver
> seems to do dynamic device name assignment as o
ebsd-questions@freebsd.org; d...@nagual.nl
>> Onderwerp: Re: AHCI driver
>>
>> On Tue, Aug 10, 2010 at 02:37:42PM +0200, Victor Ophof wrote:
>> >
>> > Its better to enable,
>> >
>> > but AD4 can get renamed to ada0
>>
>> I think you
On Tue, 10 Aug 2010, Victor Ophof wrote:
There is a trick on the web,
Something with mount -u then mount -a .. but the next link sounds better :)
http://www.wonkity.com/~wblock/docs/html/ahci.html
Hey, I'm famous!
Arthur Chance's message finally explains how labeling the rootfs fails,
or at
> -Oorspronkelijk bericht-
> Van: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-
> questi...@freebsd.org] Namens Roland Smith
> Verzonden: dinsdag 10 augustus 2010 15:14
> Aan: Victor Ophof
> CC: freebsd-questions@freebsd.org; d...@nagual.nl
> Onder
On 08/10/10 15:52, Roland Smith wrote:
On Tue, Aug 10, 2010 at 03:23:29PM +0100, Arthur Chance wrote:
[snip]
Alternatively, before switching to the ahci driver, label all your
partitions and mount them using their labels rather than device names.
This is probably a better idea.
But people sh
On Tue, Aug 10, 2010 at 03:23:29PM +0100, Arthur Chance wrote:
> If you're in single user mode "mount -uw /" will make / (and thus
> /etc/fstab) writable, although your choice of editors is restricted to
> /bin/ed and /rescue/{ex,vi}.
Of course I tried that, and it did _not_ work! I'm not sure w
On 08/10/10 14:13, Roland Smith wrote:
On Tue, Aug 10, 2010 at 02:37:42PM +0200, Victor Ophof wrote:
Its better to enable,
but AD4 can get renamed to ada0
I think you should change "can" to "will". :-)
but it's easy to fix
you just need to edit the /etc/fstab to point to the newly named dr
On Tue, Aug 10, 2010 at 02:37:42PM +0200, Victor Ophof wrote:
>
> Its better to enable,
>
> but AD4 can get renamed to ada0
I think you should change "can" to "will". :-)
> but it's easy to fix
> you just need to edit the /etc/fstab to point to the newly named drives ..
Do this _before_ reb
>Is it really better to enable AHCI driver?
Almost certainly, yes. If your BIOS and SATA controller use AHCI, and
are recognized by the ahci(4), mvs(4), or siis(4) drivers (I think
that these drivers are built as kernel modules by default in the
recent versions of FreeBSD, and don't require the
Its better to enable,
but AD4 can get renamed to ada0
but it's easy to fix (when reboot keep a 2nd computer handy to google the
solution)
you just need to edit the /etc/fstab to point to the newly named drives ..
> Date: Tue, 10 Aug 2010 13:36:11 +0200
> From: d...@nagual.nl
> To: freebs
23 matches
Mail list logo
