(which is what I now run) it will not label through
/stand/sysinstall.
I can now newfs the drive and mount it and copy files to and fro, however I
cannot use it with vinum. I did umount the drive and then disklabel -e da4
and changed the e: to h: and the filesystem type to vinum. It was da4s1e
,
however I cannot use it with vinum. I did umount the drive and
then disklabel -e da4 and changed the e: to h: and the filesystem
type to vinum. It was da4s1e.
When I create the vinum configuration, I either get that drive d
(da4s1h) is referenced and in the down state while the other three
SCSI3 disks 9G each, however one of those 4
will not disklabel. The other three will. This leads to troubles then,
obviously, to setting the 4 drives for vinum use. Was using these 4 drives
on 5.0-RELEASE with vinum previously no troublesdowngraded for some
backup software (bacula
/stand/sysinstall.
I can now newfs the drive and mount it and copy files to and fro, however I
cannot use it with vinum. I did umount the drive and then disklabel -e da4
and changed the e: to h: and the filesystem type to vinum. It was da4s1e.
When I create the vinum configuration, I either
will not disklabel. The other three will. This leads to troubles then,
obviously, to setting the 4 drives for vinum use. Was using these 4 drives
on 5.0-RELEASE with vinum previously no troublesdowngraded for some
backup software (bacula) compatibility reasons.
In dmesg, da1, da2, da3, da4 all
Running FBSD 4.9 on an Intel SMP mobo w/ 2 Intel PII 350s. Onboard SCSI is
recognized and sees all my drives. One SCSI 3 drive is 4.5G for the OS and
/usr. I have 4 identical IBM SCSI3 disks 9G each, however one of those 4
will not disklabel. The other three will. This leads to troubles
ecsd [EMAIL PROTECTED] writes:
The transition to using devfs versus MAKEDEV is not very well documented,
and I find no way to create /dev/ad3-anything although I have a /dev/ad3
and have used disklabel -w -r ad3 auto to initialize it.
I wish there were an example section for devfs(8
The transition to using devfs versus MAKEDEV is not very well documented,
and I find no way to create /dev/ad3-anything although I have a /dev/ad3
and have used disklabel -w -r ad3 auto to initialize it.
I wish there were an example section for devfs(8) that showed how to use
devfs to do what
I have an existing FreeBSD v4.7 installation and want to delete a small
filesystem that I had designated for email (/var/mail), and want to freeup
that unused space to the '/usr/home' filesystem. If I use DISKLABEL to
delete '/var/mail', and then re-write '/usr/home' to reflect the added
space
On Tue, Sep 16, 2003 at 06:19:28AM -0400, Michael A. Alestock typed:
I have an existing FreeBSD v4.7 installation and want to delete a small
filesystem that I had designated for email (/var/mail), and want to freeup
that unused space to the '/usr/home' filesystem. If I use DISKLABEL to
delete
I have an existing FreeBSD v4.7 installation and want to delete a small
filesystem that I had designated for email (/var/mail), and want to freeup
that unused space to the '/usr/home' filesystem. If I use DISKLABEL to
delete '/var/mail', and then re-write '/usr/home' to reflect the added
FreeBSD
to fit into it with as little damage to the existing OSs
as
possible. The setup I have (as reported by OpenBSD
disklabel)
is:
a: 262144 2570404.2BSD 1024 819216
b:16384 519184 swap
c: 498015 257040unused0 0
, to answer my own questions, in case others have
the same questions:
1) The 'unit' size in bsdlabel/disklabel is the size of
the individual slice. You can only create BSD-partitions
within that slice, and you can't extend beyond that.
However, you shouldn't need to, as:
2) FreeBSD supports DOS-style
as
possible. The setup I have (as reported by OpenBSD
disklabel)
is:
a: 262144 2570404.2BSD 1024 819216
b:16384 519184 swap
c: 498015 257040unused0 0
d: 219487 5355684.2BSD 1024 819216
e: 4000122
hello
i am trying to add some more hd space to my system.
I have an extra disk wich is /dev/sda0s2.
I used disklabel to partition it into seven partitions. Now i want to
insert these partitions to my system, but i can not find all the device
files /dev/sda0s2a - /dev/sda0s2h
But disklabel -r
hello
i am trying to add some more hd space to my system.
I have an extra disk wich is /dev/sda0s2.
I used disklabel to partition it into seven partitions. Now i want to
insert these partitions to my system, but i can not find all the device
files /dev/sda0s2a - /dev/sda0s2h
By default
Sorry, I should have included this output as well:
fs3# disklabel -r ad4
disklabel: bad pack magic number (label is damaged, or pack is unlabeled)
--Bill McMilleon
quoting previous posting below:
-
I have a Pentium 233 that was running 4.5-RELEASE whose boot drive went
Hi.
I have an old system that has hpt366 card on it. I have connected 4 drive
connected to it. But after connecting those drives to that hpt366 I can not
do disklabel on them but i can if i connect it to normal ide connectors.
I am using GENERIC 4.8 kernel that ships with 4.8Release
On Sat, May 31, 2003 at 07:05:56PM +0200 or thereabouts, Herbert seemed to write:
Hei!
On Thursday May 29th I installed FreeBSD 5.1 Beta2. The next day I've
update to CURRENT from May 30th. I have a 60 GB ATA harddisk and during
installation I created only 1 20 GB slice for FreeBSD. Today I
.
Is there a way of fixing it?
If you have the starting sector for each partition as well, you can
fix it. You need to use disklabel to set those two numbers. See the
disklabel man page for details.
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html
I just blew the label of my disk.
I do not know how I did it but you know that
we can make amazing things without even be aware
of what we are doing.
I have a paper on my desk where I write down
the sizes of my partitions.
Is there a way of fixing it?
Thanks in advance.
I'm running 4.8RC1, I have a ~345Gb drive (RAID), that I am partitioning
into 43Gb chunks (8 of them).. I'm using sysinstall.. on my last chunk,
it shows X as the partition name and the rest is ok. The other
partitions are amrd0s1e,f,g,h,a,b,d.. Am I out of letters? What
about i? What can
Siegbert Baude wrote:
I'm running 4.8RC1, I have a ~345Gb drive (RAID), that I am
partitioning into 43Gb chunks (8 of them).. I'm using sysinstall.. on
my last chunk, it shows X as the partition name and the rest is ok.
The other partitions are amrd0s1e,f,g,h,a,b,d.. Am I out of
letters?
Hi Eric,
The partitions within a FreeBSD slice are numberd from a to h, where c
is always reserved for the complete disk.
So you will need two (or more) slices. Then create up to 7 (abdefgh)
partitions within each slice.
Thanks Siegbert.. Do you have any idea why this limit would be placed?
to use (in DOS-terms) logical partitions within an
extended partition. This is possible, if you do the math and creation
of partition tables by hand, but is not supported by the FreBSD tools.
No, you don't need to do anything by hand. Just disklabel /dev/amr0s5
and so on, and create
Hi Mike,
I once tried to use (in DOS-terms) logical partitions within an
extended partition. This is possible, if you do the math and creation
of partition tables by hand, but is not supported by the FreBSD tools.
No, you don't need to do anything by hand. Just disklabel /dev/amr0s5
and so
to do anything by hand. Just disklabel /dev/amr0s5
and so on, and create the partitions in it. I will note that on
5.0-RELEASE, the extended slice devices didn't get created for me.
Yes, disklabel worked o.k., I talked about potential problems with
(DOS-term) partition tables, aka slice tables
Mike Meyer wrote:
[..snip..]
Of course, one has to wonder why anyone needs as many as seven
partitions on a single disk. It's far more common to want to go the
other way, and have multiple disks in a single partition.
mike
Separating the 350Gb up into smaller chunks makes dividing the space for
In [EMAIL PROTECTED], Eric Anderson [EMAIL PROTECTED] typed:
Mike Meyer wrote:
[..snip..]
Of course, one has to wonder why anyone needs as many as seven
partitions on a single disk. It's far more common to want to go the
other way, and have multiple disks in a single partition.
Separating
Mike Meyer wrote:
In [EMAIL PROTECTED], Eric Anderson [EMAIL PROTECTED] typed:
Mike Meyer wrote:
[..snip..]
Of course, one has to wonder why anyone needs as many as seven
partitions on a single disk. It's far more common to want to go the
other way, and have multiple disks in a single partition.
and creation
of partition tables by hand, but is not supported by the FreBSD tools.
No, you don't need to do anything by hand. Just disklabel /dev/amr0s5
and so on, and create the partitions in it. I will note that on
5.0-RELEASE, the extended slice devices didn't get created for me.
Yes
synrat wrote:
I can't delete 2 linux partitions from a drive using disklabel.
No matter what /dev/ad0 slices I try to edit, linux partitions don't show
up, but fdisk thinks differently. I can easily delete and recreate the
first 2 partitions as slices 1 and 2, but can't get rid of the other 2
I can't delete 2 linux partitions from a drive using disklabel.
No matter what /dev/ad0 slices I try to edit, linux partitions don't show
up, but fdisk thinks differently. I can easily delete and recreate the
first 2 partitions as slices 1 and 2, but can't get rid of the other 2.
Thanx in advance
hey
i am trying to create a script to automatically detect the size of a
drive,run fdisk then disklabel and allocate the partitions in a similar way
to the sysinstall disklabel program, but i can't seem to find any
documentation to help. the script is for a boot disk that will set up all
wrote:
On Sunday, 2 February 2003 at 13:50:20 -0500, Pete wrote:
==
[root@archive 13:44:07 root]# disklabel ar2
# /dev/ar2:
[snip]
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 3737
sectors/unit
On Monday, 10 February 2003 at 23:11:02 -0500, Pete wrote:
On Mon, 03 Feb 2003, Pete wrote:
On Mon, 03 Feb 2003, Greg 'groggy' Lehey wrote:
On Sunday, 2 February 2003 at 13:50:20 -0500, Pete wrote:
What does this mean? Whichever drive is last, that's the one I cannot
disklabel -e to set
Hello... I have three hard drives in my system. One of them (the first)
is the system disk. I'm trying to get the other two ready to be a
mirrored volume. No matter which of the last two drives is last, that
one always is listed as amnesiac when I do a disklabel
as amnesiac when I do a disklabel on it:
==
[root@archive 13:44:07 root]# disklabel ar2
# /dev/ar2:
type: unknown
disk: amnesiac
label: fictitious
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 3737
sectors
as amnesiac when I do a disklabel on it:
P ==
P [root@archive 13:44:07 root]# disklabel ar2
P # /dev/ar2:
P type: unknown
P disk: amnesiac
P label: fictitious
P flags:
P bytes/sector: 512
P sectors/track: 63
P tracks/cylinder: 255
P sectors/cylinder: 16065
P cylinders: 3737
P
which of the last two drives is last, that
P one always is listed as amnesiac when I do a disklabel on it:
P ==
P [root@archive 13:44:07 root]# disklabel ar2
P # /dev/ar2:
P type: unknown
P disk: amnesiac
Maybe I'm being obvious here but have you tried a different
the other two ready to be a
P mirrored volume. No matter which of the last two drives is last, that
P one always is listed as amnesiac when I do a disklabel on it:
P ==
P [root@archive 13:44:07 root]# disklabel ar2
P # /dev/ar2:
P type: unknown
P disk: amnesiac
Maybe
of them (the first)
P is the system disk. I'm trying to get the other two ready to be a
P mirrored volume. No matter which of the last two drives is last, that
P one always is listed as amnesiac when I do a disklabel on it:
P ==
P [root@archive 13:44:07 root
on /v1 (ufs, local, soft-updates)
/dev/ar2s1e on /v2 (ufs, local, soft-updates)
==
I have read that the next step involves using disklabel to edit the
label of each disk and change the 4.2BSD fstype to vinum. I wanted
to see the labels first, so I typed disklabel ar1
I ran into a snag using my HD backup script that works like a charm on
FBSD-4.5-4.7, but won't when I just tried it on 4.4. The script uses Fdisk,
Disklabel and Newfs. Seems to fdisk disklabel okay, but when I try to
then run the newfs on a partition, like /dev/ad2s1a, it says, no such file
At 03:12 PM 1.21.2003 -0600, Jack L. Stone wrote:
I ran into a snag using my HD backup script that works like a charm on
FBSD-4.5-4.7, but won't when I just tried it on 4.4. The script uses Fdisk,
Disklabel and Newfs. Seems to fdisk disklabel okay, but when I try to
then run the newfs
and mounted
them.
==
/dev/ar1s1e on /v1 (ufs, local, soft-updates)
/dev/ar2s1e on /v2 (ufs, local, soft-updates)
==
I have read that the next step involves using disklabel to edit the
label of each disk and change the 4.2BSD fstype to vinum
# [EMAIL PROTECTED] / 2003-01-04 11:20:22 -0500:
I'm trying to set up a vinum mirrored plex on my 4.7-STABLE (cvsup-ed as
of yesterday, 1/3) system. I have 3 30GB drives. Currently, only the
first disk is being used. This disk has all the system along with all
my digital photos and videos.
-in as
possible.
Granted, 1 is my primary reason, but 2 and 3 are factors (albeit minor).
I'm using the RAID card because it was (at the time) the only IDE
adapter that I had that supported UDMA 100. I bought this other adapter
hoping that this disklabel problem I'm seeing is a hardware problem. It
doesn't
:
# disklabel -e /dev/ad0s1e
disklabel: Device busy
Second try (completely empty disk):
# disklabel -e /dev/ad2s1f
disklabel: Device busy
Then I tried 'disklabel -e -r' for each of these and still: Device busy.
Could someone point me in the right direction?
Thanks,
-Jason
To Unsubscribe: send
):
http://org.netbase.org/vinum-mirrored.html
Anyway, I have come to the point where I have to label my disks and I
am getting the following:
First try:
# disklabel -e /dev/ad0s1e
disklabel: Device busy
Second try (completely empty disk):
# disklabel -e /dev/ad2s1f
disklabel: Device
Hello,
After an unfortunate sequence of events, my newly successfully upgraded FreeBSD 4.7
machine would not boot anymore and gave me a boot: prompt. Returning
to the install CD disklabel program, I saw that the only partition it
seemed be to finding was the swap partition.
I recreated and wrote
On Sun, 1 Dec 2002, Mark Stosberg wrote:
After an unfortunate sequence of events, my newly successfully upgraded FreeBSD 4.7
machine would not boot anymore and gave me a boot: prompt. Returning
to the install CD disklabel program, I saw that the only partition it
seemed be to finding
On Sun, 1 Dec 2002, Mark Stosberg wrote:
On Sun, 1 Dec 2002, Mark Stosberg wrote:
After an unfortunate sequence of events, my newly successfully upgraded FreeBSD 4.7
machine would not boot anymore and gave me a boot: prompt. Returning
to the install CD disklabel program, I saw
I posted about this a few weeks ago but didn't get many responses
and I really have to fix it now.
Somewhere in the course of using sysinstall it blew away part of my
disklabel. This box has an AMI RAID controller on it which I want to
replace. (not least because of its horrible error
I somehow wiped out my disklabel and while I am backing up my home
directory in the event I need to start from scratch, I would like
know if I can somehow extract a valid disklabel from a running
system and re-apply it?
If you can get disklabel to print out the incore version
yup, I got the part about the incore label but too late: I wish
there was some way to refresh it. It is active as far as df -k
or the mechanism in the kernel that tracks filesystems knows.
Hmmm. I just thought of something. You say the disklabel starts
at 0. Do you mean the offset
I seem not to have that anymore: the disklabel that I get back
starts at 0. I seem to have trashed that as well while I was
thrashing around with this. grumble
Oh Oh, Sounds suspiciosly like it be gone then. Well, this is
your opportunity to be creative...
jerry
I take
Assuming I work out the partition sizes with the output of df -k,
is there a way to determine the starting point for the slice that
contains all my BSD partitions?
As long as I don't reboot, things seem to be hunky-dory, but
that's not the most practical way to continue.
--
Paul Beard / 8040
I have recently had a problem with the disklabel on a drive in one of my
servers. I had just installed an additional hard drive and was running a
backup when the system halted due to a kernel fault (caused by dead RAM,
as I later found out) and fsck managed to clobber my disklabel. The
drive
101 - 159 of 159 matches
Mail list logo
