On Sun, 21 Oct 2012 17:00:13 -1000, Al Plant wrote:
Aloha,
I cant find any How TO on writing the hardware devices into /etc/fstab
to mount and find how the DVD and CD players get connected.
Open the file in your favourite editor and add the lines according
to your needs, if this was the
Aloha,
I cant find any How TO on writing the hardware devices into /etc/fstab
to mount and find how the DVD and CD players get connected.
(This happens to be with a test box FreeBSD 10.* which has worked fine
other than that.) The BSD install I understand is also for FreeBSD 9.*
as well.
I added a label to my root fs some time ago. I really prefer the gpt
label and I have added it, but I can't figure out how to remove the
ufs label.
I boot single user and run 'tunefs -L /dev/ada1p2' but I get an
unable to write superblock error. This is before mounting the drive
RW
Hi,
On Sun, 9 Sep 2012 17:47:43 -0700
Kevin Oberman kob6...@gmail.com wrote:
I added a label to my root fs some time ago. I really prefer the gpt
label and I have added it, but I can't figure out how to remove the
ufs label.
I boot single user and run 'tunefs -L /dev/ada1p2' but I get
On Sun, 9 Sep 2012, Kevin Oberman wrote:
I added a label to my root fs some time ago. I really prefer the gpt
label and I have added it, but I can't figure out how to remove the
ufs label.
I boot single user and run 'tunefs -L /dev/ada1p2' but I get an
unable to write superblock error
On Sun, 9 Sep 2012, Warren Block wrote:
On Sun, 9 Sep 2012, Kevin Oberman wrote:
I added a label to my root fs some time ago. I really prefer the gpt
label and I have added it, but I can't figure out how to remove the
ufs label.
I boot single user and run 'tunefs -L /dev/ada1p2' but I get
On Sun, Sep 9, 2012 at 6:49 PM, Warren Block wbl...@wonkity.com wrote:
On Sun, 9 Sep 2012, Warren Block wrote:
On Sun, 9 Sep 2012, Kevin Oberman wrote:
I added a label to my root fs some time ago. I really prefer the gpt
label and I have added it, but I can't figure out how to remove
On Sun, 9 Sep 2012, Kevin Oberman wrote:
On Sun, Sep 9, 2012 at 6:49 PM, Warren Block wbl...@wonkity.com wrote:
On Sun, 9 Sep 2012, Warren Block wrote:
On Sun, 9 Sep 2012, Kevin Oberman wrote:
I added a label to my root fs some time ago. I really prefer the gpt
label and I have added
On Sun, Sep 9, 2012 at 8:00 PM, Warren Block wbl...@wonkity.com wrote:
On Sun, 9 Sep 2012, Kevin Oberman wrote:
On Sun, Sep 9, 2012 at 6:49 PM, Warren Block wbl...@wonkity.com wrote:
On Sun, 9 Sep 2012, Warren Block wrote:
On Sun, 9 Sep 2012, Kevin Oberman wrote:
I added a label to my
, but now i have to get the data from that slice and when i connect
the hdd to 9.1 box, it finds old corrupt GPT label (i suppose, it's
backup GPT header somewhere in the end of actual disk) and does not
recognize the MBR scheme there.
It sees no freebsd partitions (and one exists there, for sure :) ). So
On Thu, Aug 30, 2012 at 1:54 AM, Виталий Туровец core...@corebug.net wrote:
So
my question is: how do i force the system to ignore old corrupt GPT
header on this hdd, or how do i remove the header, or is there any
workaround possible?
dd if=/dev/zero of=/dev/ada1 bs=64k
2012/8/30 Michael Sierchio ku...@tenebras.com:
On Thu, Aug 30, 2012 at 1:54 AM, Виталий Туровец core...@corebug.net wrote:
So
my question is: how do i force the system to ignore old corrupt GPT
header on this hdd, or how do i remove the header, or is there any
workaround possible?
dd
On Thu, Aug 30, 2012 at 4:18 AM, Виталий Туровец core...@corebug.net wrote:
Well, i thought that my need to get files from hdd is easy enough to
understand from my original message:)
Извините, пожалуйста!
___
freebsd-questions@freebsd.org mailing
and one slice there. It worked fine in
7.2, but now i have to get the data from that slice and when i connect
the hdd to 9.1 box, it finds old corrupt GPT label (i suppose, it's
backup GPT header somewhere in the end of actual disk) and does not
recognize the MBR scheme there.
In case it has
scheme and one
single freebsd (165) partition and one slice there. It worked fine in
7.2, but now i have to get the data from that slice and when i connect
the hdd to 9.1 box, it finds old corrupt GPT label (i suppose, it's
backup GPT header somewhere in the end of actual disk) and does
change 'ada1p1' to read the gpt label? I've tried to offline it,
then online it via gpt label, that didn't work:
:#/sbin/zpool online data.zfs gpt/sam1tb
cannot online gpt/sam1tb: no such device in pool
yes, sam1tb is the gpt label for ada1p1.
zpool replace 'ada1p1' with gpt label?
]Peter
Hello,
I've just updated my laptop from 8.2-RELEASE to 9.0-RELEASE, everything
worked but the kernel complains about labels see :
g_dev_taste: make_dev_p() failed (gp-name=vol/root, error=17)
g_dev_taste: make_dev_p() failed (gp-name=vol/root, error=17)
g_dev_taste: make_dev_p() failed
The layout is as follows:
test# gpart status
Name Status Components
da0p1 OK da0
da0p2 OK da0
da0p3 OK da0
test# gpart list | grep label
label: (null)
label: (null)
label: (null)
Now i modified the gpart labels.
test# gpart modify -i1 -l bootpart da0
da0p1
is as follows:
test# gpart status
Name Status Components
da0p1 OK da0
da0p2 OK da0
da0p3 OK da0
test# gpart list | grep label
label: (null)
label: (null)
label: (null)
Now i modified the gpart labels.
test# gpart modify -i1 -l bootpart da0
da0p1
-l
The layout is as follows:
test# gpart status
Name Status Components
da0p1 OK da0
da0p2 OK da0
da0p3 OK da0
test# gpart list | grep label
label: (null)
label: (null)
label: (null)
Now i modified the gpart labels.
test# gpart modify -i1 -l
modify -i -l
The layout is as follows:
test# gpart status
Name Status Components
da0p1 OK da0
da0p2 OK da0
da0p3 OK da0
test# gpart list | grep label
label: (null)
label: (null)
label: (null)
Now i modified the gpart labels.
test# gpart modify -i1 -l
On Fri, 23 Dec 2011, Peter wrote:
When you ran the 'gpart' commands, did you set the sysctl geom debug
variable? [sysctl kern.geom.debugflags=17]
That should not be necessary, or advisable. The only time it would be
needed is to write to a partition that is mounted. If it is needed, the
'gpart show -l ad4' shows GPT labels on all the ad4 partitions. Is
there a reverse lookup, say to find out the GPT label for ad4p4?
Yes, it can be parsed out of 'gpart show -l' output, but anything more
direct?
___
freebsd-questions@freebsd.org
label kernel messages (FreeBSD 8.2
amd64). I understand why they happen - glabel metadata occupies the
last sector, so bsdlabel sees a device that is 1 sector smaller than
what the kernel sees. The question is whether there is some simple way
of suppressing these messages, since they come up every
On Mon, 21 Mar 2011 06:40:51 -0400, Maxim Khitrov m...@mxcrypt.com wrote:
I've been using 'dangerously dedicated' partitioning for years without
any issues. What problems have been reported by others?
I think those problems originate from some operating systems
not able to work with disks that
Hi all,
Executing the following commands on any valid storage device seems to
cause media size does not match label kernel messages (FreeBSD 8.2
amd64). I understand why they happen - glabel metadata occupies the
last sector, so bsdlabel sees a device that is 1 sector smaller than
what the kernel
On Sun, Mar 20, 2011 at 4:38 PM, Maxim Khitrov m...@mxcrypt.com wrote:
Hi all,
Executing the following commands on any valid storage device seems to
cause media size does not match label kernel messages (FreeBSD 8.2
amd64). I understand why they happen - glabel metadata occupies the
last
Maxim Khitrov m...@mxcrypt.com writes:
On Sun, Mar 20, 2011 at 4:38 PM, Maxim Khitrov m...@mxcrypt.com wrote:
Hi all,
Executing the following commands on any valid storage device seems to
cause media size does not match label kernel messages (FreeBSD 8.2
amd64). I understand why they happen
label and file system(s).
Scott
repost follows.
I just wrote:
A couple of days ago, I reorganized the internal hard drive of my machine
to reclaim space that used to be occupied by another
J. Porter Clark wrote:
I have an encrypted partition, /dev/da0s1d. I can use geli
attach da0s1d and obtain a device /dev/da0s1d.eli, which is a
UFS filesystem. All that works just fine.
I'd like to label /dev/da0s1d so that I don't have to refer to
the exact drive number, etc., which might
On Tue, Jan 25, 2011 at 10:45:52AM +0200, Nikos Vassiliadis wrote:
J. Porter Clark wrote:
I have an encrypted partition, /dev/da0s1d. I can use geli
attach da0s1d and obtain a device /dev/da0s1d.eli, which is a
UFS filesystem. All that works just fine.
I'd like to label /dev/da0s1d
.
I'd like to label /dev/da0s1d so that I don't have to refer to
the exact drive number, etc., which might change if I reboot
with a USB stick in the system or whatever. But glabel puts the
label in the last sector, which is where GELI stores metadata.
You don't have to worry about this. geli
On Tue, Jan 25, 2011 at 03:29:37PM +0100, Rolf Nielsen wrote:
Correct me if I'm wrong anyone.
You need to first label da0s1d
e.g. like so
glabel label data da0s1d
then geli init the labeled device
e.g. like so
geli init -l 256 -s 4096 label/data
Unfortunately, this step
2011-01-25 19:13, J. Porter Clark skrev:
On Tue, Jan 25, 2011 at 03:29:37PM +0100, Rolf Nielsen wrote:
Correct me if I'm wrong anyone.
You need to first label da0s1d
e.g. like so
glabel label data da0s1d
then geli init the labeled device
e.g. like so
geli init -l 256 -s 4096 label/data
On Tue, Jan 25, 2011 at 07:28:25PM +0100, Rolf Nielsen wrote:
X-Spam-Level:
2011-01-25 19:13, J. Porter Clark skrev:
On Tue, Jan 25, 2011 at 03:29:37PM +0100, Rolf Nielsen wrote:
Correct me if I'm wrong anyone.
You need to first label da0s1d
e.g. like so
glabel label data
2011-01-25 19:37, J. Porter Clark skrev:
On Tue, Jan 25, 2011 at 07:28:25PM +0100, Rolf Nielsen wrote:
X-Spam-Level:
2011-01-25 19:13, J. Porter Clark skrev:
On Tue, Jan 25, 2011 at 03:29:37PM +0100, Rolf Nielsen wrote:
Correct me if I'm wrong anyone.
You need to first label da0s1d
e.g
in the flow,
I'm reposting it below. I hope that someone who is more familiar with the
details of bsdlabels and glabels can help me understand how to correct the
problem because I'm loath at this point to embark upon an ill-informed trial-
and-error experimentation program to recover label and file
I have an encrypted partition, /dev/da0s1d. I can use geli
attach da0s1d and obtain a device /dev/da0s1d.eli, which is a
UFS filesystem. All that works just fine.
I'd like to label /dev/da0s1d so that I don't have to refer to
the exact drive number, etc., which might change if I reboot
in /dev/label
vanished, of course. I checked and discovered that the only external drive
for which I had not kept backup copies of the bsdlabel information was that
drive. :-( Fortunately, the full backups of the file systems that I needed
to reload onto the internal drive were in the first
. The moment I rewrote the bsdlabel
^
Yet another pair of mistakes on my part. Those should have said da0s1d
and da0s1e. Sorry for any confusion.
for the first slice by mistake, the two partitions' entries in /dev/label
vanished, of course. I checked and discovered that the only external
On 8 November 2010 12:19, Peter fb...@peterk.org wrote:
iH,
Is there any easy straight forward way to trace my /dev/gpt/data.zfs
disk to what ada device it is, and on what controller?
I've traced it manually by doing a gpart list adaX |grep data.zfs on each
adaX device, then somehow I found
iH,
Is there any easy straight forward way to trace my /dev/gpt/data.zfs
disk to what ada device it is, and on what controller?
I've traced it manually by doing a gpart list adaX |grep data.zfs on each
adaX device, then somehow I found out what controller it is on [I think by
manually looking
. The information you gave
does not point towards any problems. All looks good.
Also, the subject line mentions geometry does not match label, but
you did not mention anything it in your email about it. Again, it
by itself does not indicate a problem.
Thanks,
the kernel reboots and one of the last
camcontrol devlist
and atacontrol list. The latter allowed me to determine that
/dev/label/rootfs0 is ad2s1a based on the actual disk size
and a process of elimination.
Does anyone know a magic incantation to output this label-device
mapping?
Try looking at glabel(8). I don't know what
on /usr (ufs, local, soft-updates)
/dev/ad4s1d on /var (ufs, local, soft-updates)
bsdlabel ad4
bsdlabel: /dev/ad4: no valid label found
bsdlabel ad4s1
# /dev/ad4s1:
8 partitions:
#size offsetfstype [fsize bsize bps/cpg]
a: 2097152 634.2BSD0 0 0
b
looks good.
Also, the subject line mentions geometry does not match label, but
you did not mention anything it in your email about it. Again, it
by itself does not indicate a problem.
Thanks,
--
Marcel Moolenaar
xcl...@mac.com
___
freebsd-questions
-- the only way to get FreeBSD installed was to dedicate all of
the available space to FreeBSD.
The geometry warnings are mostly a cosmetic error and generally can be
ignored. Especially the one in sysinstall.
I've found a suggested solution to repair the mbr/label problem with
dd if=/dev/zero
/label/rootfs0 is ad2s1a based on the actual disk size
and a process of elimination.
Does anyone know a magic incantation to output this label-device
mapping?
Try looking at glabel(8). I don't know what option will list which is
mounted, but 'glabel status' shows the names and what partitions
Hi,
I've tried the mount, tunefs and df manuals, and don't know
where to look next.
I am trying to find out what device, in terms of /dev/ad0s1a
and so on, is actually 'connected' to a label mounted file
system. Here is my fstab (from PC-BSD, by the way):
# more /etc/fstab
# Device
Mark G. mark-fbsd-quest-10+20100...@giovannetti.ca writes:
Hi,
I've tried the mount, tunefs and df manuals, and don't know
where to look next.
I am trying to find out what device, in terms of /dev/ad0s1a
and so on, is actually 'connected' to a label mounted file
system. Here is my fstab
Hi!
Few days ago some annoying things happened. At first I had FreeBSD 7 box
with one disk(SATA). When i added another dish (SATA) my box stuck when
booting up.
Somethink like this comes up:
Mountroot
And i need manualy mount disk because disk label has beed changed and then
edit fstab file
On Sat, 16 Jan 2010 10:31:22 +0100 Roland Smith rsm...@xs4all.nl
wrote:
On Sat, Jan 16, 2010 at 12:38:14AM -0600, Scott Bennett wrote:
2) Create the geli device /dev/daXsYP.eli, and then create a label on th=
at,
yielding /dev/label/bar. [not sure what the utility of this is, since
On Fri, Jan 22, 2010 at 03:08:00AM -0600, Scott Bennett wrote:
Why is that stored in the last sector of the device, rather than in the
key file? What is the purpose of the key file if not to hold that type of
information?
All geom(4) providers use their last sector to store metadata;
On 1/14/10, Scott Bennett benn...@cs.niu.edu wrote:
I used glabel label to label each of the file systems I have on
external
disk drives. Unfortunately, afterward I am now unable to geli attach any
of
the GELI-encrypted file systems. The system is FreeBSD 7.2-STABLE. Is
there
a way
On Sat, 23 Jan 2010 02:34:31 +0100
Roland Smith rsm...@xs4all.nl wrote:
On Fri, Jan 22, 2010 at 03:08:00AM -0600, Scott Bennett wrote:
Why is that stored in the last sector of the device, rather
than in the key file? What is the purpose of the key file if not
to hold that type of
On Sat, Jan 16, 2010 at 12:38:14AM -0600, Scott Bennett wrote:
2) Create the geli device /dev/daXsYP.eli, and then create a label on that,
yielding /dev/label/bar. [not sure what the utility of this is, since the
label will only appear after the geil provider has been attached
on this was of the form glabel label fsname /dev/daXsYP, which I had
thought would produce a /dev/label/fsname device and that doing a geli
attach
afterward would produce a /dev/label/fsname.eli device.
You could have done two things to create a nested label/geli configuration;
1) Create a labeled
On Fri, Jan 15, 2010 at 01:25:50AM -0600, Scott Bennett wrote:
Check /var/backups. There should be *.eli files there. Those are the automa=
tic
No joy. :-(
metadata backups that 'geli init' makes (at least in 8.0). You can restore
those backups with 'geli restore'.
Those must
is the
partition identifier in slice Y of drive X. What I did when I screwed the
pooch on this was of the form glabel label fsname /dev/daXsYP, which I =
had
thought would produce a /dev/label/fsname device and that doing a geli a=
ttach
afterward would produce a /dev/label/fsname.eli device.
You could have
On Thu, 14 Jan 2010 10:55:35 +0300 Boris Samorodov b...@ipt.ru
wrote:
Thanks so much for responding so fast!
On Thu, 14 Jan 2010 01:31:55 -0600 (CST) Scott Bennett wrote:
hellas# geli attach -k work.key /dev/label/work
geli: Cannot read metadata from /dev/label/work: Invalid argument
Scott Bennett wrote:
I used glabel label to label each of the file systems I have on external
disk drives. Unfortunately, afterward I am now unable to geli attach any of
the GELI-encrypted file systems. The system is FreeBSD 7.2-STABLE.
Hmm, did you say you had geli-encrypted drives
On Thu, 14 Jan 2010 10:30:00 +0100 Ivan Voras ivo...@freebsd.org
wrote:
Scott Bennett wrote:
I used glabel label to label each of the file systems I have on
external
disk drives. Unfortunately, afterward I am now unable to geli attach any
of
the GELI-encrypted file systems
Scott Bennett wrote:
As noted above, that would not work because then the label would not
be readable at boot time.
Yes it would. What you would have is a nested configuration, geli within
a label.
The label would be read when the device is present, then you would be
able to attach
On Thu, Jan 14, 2010 at 01:31:55AM -0600, Scott Bennett wrote:
I used glabel label to label each of the file systems I have on
external
disk drives. Unfortunately, afterward I am now unable to geli attach any of
the GELI-encrypted file systems. The system is FreeBSD 7.2-STABLE
On Thu, 14 Jan 2010 18:42:32 +0100 Roland Smith rsm...@xs4all.nl
On Thu, Jan 14, 2010 at 01:31:55AM -0600, Scott Bennett wrote:
I used glabel label to label each of the file systems I have on ex=
ternal
disk drives. Unfortunately, afterward I am now unable to geli attach a=
ny
I used glabel label to label each of the file systems I have on external
disk drives. Unfortunately, afterward I am now unable to geli attach any of
the GELI-encrypted file systems. The system is FreeBSD 7.2-STABLE. Is there
a way to get this to work? Or have I just lost everything
On Thu, 14 Jan 2010 01:31:55 -0600 (CST) Scott Bennett wrote:
hellas# geli attach -k work.key /dev/label/work
geli: Cannot read metadata from /dev/label/work: Invalid argument.
Did you try to mount it via geom consumer (/dev/daX)?
Can you show apropriate glabel list?
--
WBR, bsam
like to use
the glabel label method of labeling each of these partitions, so that I do
not always have to disconnect all but one external drive when rebooting the
system and then reconnect them one by one in order to get the proper device
files assigned to them for use with /etc/fstab entries
file systems with lots of files in them. I would like to
use
the glabel label method of labeling each of these partitions, so that I
do
not always have to disconnect all but one external drive when rebooting the
system and then reconnect them one by one in order to get the proper device
files
have quite a few partitions on them, nearly all of
which
already contain file systems with lots of files in them. I would like to
use
the glabel label method of labeling each of these partitions, so that I
do
not always have to disconnect all but one external drive when rebooting the
system
. In
dmesg I see
..
GEOM_MIRROR: Device mirror/gm0 launched (1/2).
GEOM_MIRROR: Device gm0: rebuilding provider ad1.
GEOM: mirror/gm0s1: geometry does not match label (16h,63s != 255h,63s).
..
Trying to mount root from ufs:/dev/mirror/gm0s1a
..
anyone know if I should worry about the geometry
than
ad0/ad2. In dmesg I see
..
GEOM_MIRROR: Device mirror/gm0 launched (1/2).
GEOM_MIRROR: Device gm0: rebuilding provider ad1.
GEOM: mirror/gm0s1: geometry does not match label (16h,63s != 255h,63s).
..
Trying to mount root from ufs:/dev/mirror/gm0s1a
..
anyone know if I
Michael Powell wrote:
[snip]
You should know that the ad0/ad1 will result in a fairly drastic
performance hit. This is a master/slave arrangement on the same channel.
You really really should get another cable and do the ad0/ad2 arrangement.
And, of course, as soon as I hit the Send
What are the meaning of the messages below when I boot 8.0-RELEASE-p1 and how
can I prevent that?
GEOM: ad6s1: geometry does not match label (255h,63s != 16h,63s).
...
GEOM: ad6s2: geometry does not match label (255h,63s != 16h,63s).
GEOM: ufsid/478e98a7fe5111d0: geometry does not match label
I see this too. I even went so far as to edit the labels
and start again and then I got the opposite:
geometry does not match label (16h,63s != 255h,63s)
..so I gave up. Google didnt turn anything up but I dont
see this on FreeBSD 7.x at all. Only 8
So far, it has not been any issue from what
-questions@freebsd.org; regis505
Subject: Re: geometry does not match label (255h,63s != 16h,63s)
J.D. Bronson:
I see this too. I even went so far as to edit the labels and start
again and then I got the opposite:
I see that too on 8.0
geometry does not match label (16h,63s != 255h,63s
What if we tried a custom kernel and removed these lines:
options GEOM_PART_GPT # GUID Partition Tables.
options GEOM_LABEL # Provides labelization
I think that might remove these 'errors'.
--
J.D. Bronson
Information Technology
Hi--
On Dec 9, 2009, at 10:44 AM, Peter Steele wrote:
Add my name to the list--we get tons of these messages since upgrading to
8.0
This isn't new with 8.x; it's been around since 4.0, if not earlier.
For a long time, BIOSes using the older C/H/S addressing mechanism were limited
to
J.D. Bronson wrote:
What if we tried a custom kernel and removed these lines:
options GEOM_PART_GPT # GUID Partition Tables.
options GEOM_LABEL # Provides labelization
I think that might remove these 'errors'.
My kernel already has these removed
Well then so much for my idea of removing those options from the kernel.
Darn.
Well if they have 'been' there since earlier FreeBSD
I wonder why we never saw them until 8.x now ?
There must be some reason...
They do not appear to be anything but cosmetic but still
annoying and worrisome for
On Wed, 09 Dec 2009 10:59:51 -0800
Chuck Swiger cswi...@mac.com wrote:
Hi--
On Dec 9, 2009, at 10:44 AM, Peter Steele wrote:
Add my name to the list--we get tons of these messages since
upgrading to 8.0
This isn't new with 8.x; it's been around since 4.0, if not earlier.
Something
On Thu, 10 Dec 2009 01:36:53 +
RW rwmailli...@googlemail.com wrote:
On Wed, 09 Dec 2009 10:59:51 -0800
Chuck Swiger cswi...@mac.com wrote:
Hi--
On Dec 9, 2009, at 10:44 AM, Peter Steele wrote:
Add my name to the list--we get tons of these messages since
upgrading to 8.0
: geometry does not match label (225h,63s != 16h63s)
Sysinstall (with 7.2) says: A geometry of 484521/16/63 for ad0 is
incorrect. Using a more likely geometry.
The next screen says: DISK Geometry: 30401 cyls/255 heads/63 sectors =
488392065 sectors (238472MB)
fdisk
*** Working on device /dev/ad0
Hi,
I have installed my laptop with FreeBSD 8.0-RC1 first (now I'm on
8.0-Release-p1) and in dmesg I got this error message :
GEOM: ad0s1: geometry does not match label (255h,63s != 16h,63s).
I have search on the Web about the method to resolv this, but I haven't found
anything that helps me
I have a USB disk that I partitioned with fdisk and bsdlabel. I used the -w
option of bsdlabel to write a standard label. The label itself looks fine:
# bsdlabel da0s1
# /dev/da0s1:
8 partitions:
#size offsetfstype [fsize bsize bps/cpg]
a: 7823576 164.2BSD 2048
mode?
# shutdown now
# umount /home /usr /var /tmp
# mount -r /
# glabel label rootfs /dev/ad0s1a
That did not work for the 3-4 times I had tried on 6.[2-4]-STABLE.
Booting regulary in single user mode (choice 4 or 5) also did not
allow glabel'ing (for root
If I understand correctly from the manual, giving the labels their slice
name (/dev/label/rootfs rather than /dev/ad4s1a) will assure that
regardless of the disk, the boot will be from the disk being booted and
not from another disk as happened to me recently - the fstab on disk ad4
was referncing
PJ wrote:
If I understand correctly from the manual, giving the labels their slice
name (/dev/label/rootfs rather than /dev/ad4s1a) will assure that
regardless of the disk, the boot will be from the disk being booted and
not from another disk as happened to me recently - the fstab on disk ad4
Manolis Kiagias wrote:
PJ wrote:
If I understand correctly from the manual, giving the labels their slice
name (/dev/label/rootfs rather than /dev/ad4s1a) will assure that
regardless of the disk, the boot will be from the disk being booted and
not from another disk as happened to me
PJ wrote:
Manolis Kiagias wrote:
PJ wrote:
If I understand correctly from the manual, giving the labels their slice
name (/dev/label/rootfs rather than /dev/ad4s1a) will assure that
regardless of the disk, the boot will be from the disk being booted and
not from another disk
Manolis Kiagias wrote:
PJ wrote:
Manolis Kiagias wrote:
PJ wrote:
If I understand correctly from the manual, giving the labels their slice
name (/dev/label/rootfs rather than /dev/ad4s1a) will assure that
regardless of the disk, the boot will be from the disk
NOW THIS SUCKS.
SUM
# glabel label rootfs/dev/ad12s1a
glabel: Can't store metadata on /dev/ad12s1a: Operation not permitted
This is direct from the manual what the $#*(@)! is going on?
No identical post on web, but similar say to ignore: it's harmless?
I so, why is it there?
There seem
PJ wrote:
NOW THIS SUCKS.
SUM
# glabel label rootfs/dev/ad12s1a
glabel: Can't store metadata on /dev/ad12s1a: Operation not permitted
This is direct from the manual what the $#*(@)! is going on?
No identical post on web, but similar say to ignore: it's harmless?
I so, why
Manolis Kiagias wrote:
PJ wrote:
NOW THIS SUCKS.
SUM
# glabel label rootfs/dev/ad12s1a
glabel: Can't store metadata on /dev/ad12s1a: Operation not permitted
This is direct from the manual what the $#*(@)! is going on?
No identical post on web, but similar say to ignore: it's
/
# glabel label rootfs /dev/ad0s1a
# glabel label tmp /dev/ad0s1d
# glabel label var /dev/ad0s1e
# glabel label usr /dev/ad0s1f
# glabel label home /dev/ad0s1g
For example like this?
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi
Polytropon wrote:
On Sat, 17 Oct 2009 00:43:37 +0300, Manolis Kiagias son...@otenet.gr wrote:
Is this your normal '/' filesystem, and is it mounted?
If it is reboot your system and select 'single user mode' from the
loader.menu
Then use glabel in the single user mode prompt.
This will
displayed under /dev.
However, when I get to the disk label editor it shows up as ad0a, and slice
partitions as ad0as1a, ad0as1b, ad0as1e, .. , etc. I've tried changing
these, even with the Fdisk editor but they seem to persist, perhaps when I
restore the dump files.
NOTE: ad0a or add0asx ... etc does
Hi all:
when i try to boot the system using FreeBSD 8.0 i386 200905
bootonly CD, the following line is shown.
GEOM: ad4: geometry does not match label (255h,63S != 16h, 63s)
i just selected the entire disk and marked it bootable in the
fdisk partition editor option.
The system has a 160GB SATA
Hello,
Does anyone know how to retrieve a DVD's UDF volume label from the
CLI? I'm trying to write a script that will catalog a DVD's contents
and automatically assign it a filename based on the UDF label. Things
I've tried so far:
The file -s /dev/acd0 command.
cdrtools-devel's cdrecord
the system boot
from it OK?
Or is it just that the mounts are switched.
The mount points are not written in to the label. That comes after
booting. If it boots, I wonder if it really is switched on the
partitions or if it is just that the partitions are mounted backwards
(probably due to editing
1 - 100 of 174 matches
Mail list logo
