On 2012.10.08 18:22, Robert Bonomi wrote:
> 'cached' is not _technically_ exactly accurate, but you have the concept
> basically correct.
Thanks for the detailed explanation, Robert. Maybe "shadowed" would be
have been a more accurate term. But "in-core" also has a nice ring to it!
___
> Date: Mon, 08 Oct 2012 17:14:20 +0200
> From: "Lucas B. Cohen"
> Subject: what is an "in-core" disklabel ?
>
> Hi,
>
> I've seen the term "in-core" a couple times while reading up about BSD
> disk labels. Does it refer to
Hi,
I've seen the term "in-core" a couple times while reading up about BSD
disk labels. Does it refer to data that is cached in kernel memory ?
Context examples :
- fdisk(8) outputs "parameters extracted from in-core disklabel"
- bsdlabel(8)'s manual explains t
On Thu, Dec 10, 2009 at 09:23:30PM -0500, Nick Dalsheimer wrote:
> So we are saying, that bsdlabel and fdisk are broken? This is *very*
> disappointing.
Huh?
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo
So we are saying, that bsdlabel and fdisk are broken? This is *very*
disappointing.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@
bsdlabel: Class not found
re-edit the label? [y]:
You cant edit it. You can only say "N" and it exits w/o
saving any changes.
This is very annoying, because you cannot do anything with the label
unlike the old days..
I had to mount an older drive and then I was able to edit the bsdlabel
on th
Hello all! I've found many references to this error on Google: "fdisk: Class
not found, bsdlabel: Class not found" but none explain what this error
*means*. Could someone explain this error and possible remedies? I'm using a
custom 8.0-RELEASE-p1 kernel. I don't even need to edit the label in order
On Thu, Apr 30, 2009 at 08:51:13PM +0300, Anonymous wrote:
>
> Using disklabel -A /dev/da0s1 I would like to see the sizes in G or M
> format, how can I do this?
> Also, googling arround i found output showing the cylinder space occupied
> by a partition (like :
> #
On Thu, Apr 30, 2009 at 12:51 PM, Anonymous wrote:
> Also, googling arround i found output showing the cylinder space occupied
> by a partition (like :
> # cyl* X - Y ). How do I see that ?
I think that fdisk will show you this.
Good luck--
___
Using disklabel -A /dev/da0s1 I would like to see the sizes in G or M
format, how can I do this?
Also, googling arround i found output showing the cylinder space occupied
by a partition (like :
# cyl* X - Y ). How do I see that ?
PS: i did man disklabel and bsdlabel but i didnt find
retty pointless without anything else.
init's needed, and everything else to make a full MUM (Multi User Mode)
environment...
Keep note that not only does the MBR need bootable code, so does the
bsdlabel/disklabel
newfs will set the proper fstype in the bsdlabel if it's partition is &
ot: F1
Not ufs
Not ufs
No /boot/loader
When I investigated the flash's disklabel, I saw:
8 partitions:
#size offsetfstype [fsize bsize bps/cpg]
a: 4000106 16unused0 0
c: 40001220unused0 0 # "raw" pa
://ezine.daemonnews.org/200111/growfs.html
My primary issue right now is that when I attempt to run disklabel on
the volume (/dev/da0) in order to get my calculations for fdisk, i get:
# disklabel /dev/da0
disklabel: disks with more than 2^32-1 sectors are not supported
and when I attempt it on the s
best of which is here:
http://ezine.daemonnews.org/200111/growfs.html
My primary issue right now is that when I attempt to run disklabel on
the volume (/dev/da0) in order to get my calculations for fdisk, i get:
# disklabel /dev/da0
disklabel: disks with more than 2^32-1 sectors are not supported
and when I
1 on xpt0 bus 0:
< > at scbus-1 target -1 lun -1 (xpt0)
disklabel -A amrd0s1:
# /dev/amrd0s1:
type: ESDI
disk: amrd0s1
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 65535
sectors/unit: 292967424
On Tue, Oct 21, 2008 at 09:53:52AM +0200, Per olof Ljungmark wrote:
> Hi,
>
> I think sysinstall? got it wrong here and I get the complaint in the
> subject line on boot. This is amd64 if that matters. Nothing edited by hand.
>
> I must admit I don't fully understand what is going on here, "foun
flag 80 (active)
Now let us look at the label on this slice:
lilas# disklabel ad0s1
# /dev/ad0s1:
8 partitions:
#size offsetfstype [fsize bsize bps/cpg]
a: 104857604.2BSD 2048 16384 8
b: 4126240 1048576 swap
c: 81915372
Hi,
I think sysinstall? got it wrong here and I get the complaint in the
subject line on boot. This is amd64 if that matters. Nothing edited by hand.
I must admit I don't fully understand what is going on here, "found 32"
but the offsets are 63...
Filesystem on LSI controller amr(4):
# /dev/amr
Good day all,
I am trying to install 7.0 RC1 on an old Dell laptop.
However it fails to create the swap partition.
The message I keep getting is: "Unable to find device
node for /dev/ad0s1b in /dev!. The creation of
filesystem will be aborted."
Is there a way around it?
Thanks in advance,
Michae
bsdlabel: partition c doesn't cover the whole unit!
bsdlabel: An incorrect partition c may cause problems for standard system
probably because of that.. other reason - the device is open by other
process
___
freebsd-questions@freebsd.org mailing lis
Hello guys!
I tried to recover my partitions, which I remeved by accident. I used
scan_ffs to create a new disklabel, which found all partitions, but when
I use disklabel with -e or -R it does not write the table down.
I think there's something I forgot or did wrong perhaps, but I'm n
On Wed, Jul 18, 2007 at 12:44:02PM +0200, Gabriel Linder wrote:
> Hi,
>
> This may sound as a dumb question, but during my 6.2-RELEASE (i386) setup I
> notice the following in the handbook :
> > Remember [...] that partitions b, c, and d have conventional meanings
> that you should adhere to.
>
Hi,
This may sound as a dumb question, but during my 6.2-RELEASE (i386)
setup I notice the following in the handbook :
> Remember [...] that partitions b, c, and d have conventional meanings
that you should adhere to.
But the partition d is used by sysinstall (with both automatic defaults
an
On Tue, Apr 10, 2007 at 01:21:18PM -0700, fbsd bsd wrote:
> Hey *, having a bit of a problem with disklabel. A bit of background.
>
> I'm building a lab with Olive boxes in it
> (http://juniper.cluepon.net/index.php/Olive), which are basically i386
> machines running JunO
At 03:21 PM 4/10/2007, fbsd bsd wrote:
Hey *, having a bit of a problem with disklabel. A bit of background.
I'm building a lab with Olive boxes in it
(http://juniper.cluepon.net/index.php/Olive), which are basically i386
machines running JunOS. Please note that this whole procedu
Hey *, having a bit of a problem with disklabel. A bit of background.
I'm building a lab with Olive boxes in it
(http://juniper.cluepon.net/index.php/Olive), which are basically i386 machines
running JunOS. Please note that this whole procedure is entirely unsupported
by Juniper and I
This is not a question, just for the archives if someone encountered
a similar problem. Perhaps there's an easier way to recover a lost
bsdlabel / disklabel though...
While trying to rip a DVD with sysutils/vobcopy on 6.2-RC1, the system
suddenly froze and could not reboot anymore. Not eve
On Mon, Dec 11, 2006 at 09:26:31PM -0500, Peter Matulis wrote:
> I am having trouble viewing my USB compact flash reader with my FBSD
> 5.5 system. I have done so in the past. For some reason I can no
> longer do so.
>
> This is what I'm getting:
>
> # disklabel /d
I am having trouble viewing my USB compact flash reader with my FBSD
5.5 system. I have done so in the past. For some reason I can no
longer do so.
This is what I'm getting:
# disklabel /dev/da0s1
disklabel: /dev/da0s1: no valid label found
# fdisk /dev/da0s1
*** Working on device
On Mon, Dec 11, 2006 at 09:34:59PM +0100, Joerg Pernfuss wrote:
> On Mon, 11 Dec 2006 14:17:29 -0500
> Jerry McAllister <[EMAIL PROTECTED]> wrote:
>
> > > Is there an easy way to force the device to work as something like:
> > >
> > > /dev/da1s1d
> > >
> > > on all of the servers, including one
On Mon, 11 Dec 2006 14:17:29 -0500
Jerry McAllister <[EMAIL PROTECTED]> wrote:
> > Is there an easy way to force the device to work as something like:
> >
> > /dev/da1s1d
> >
> > on all of the servers, including ones that do not already have a
> > SCSI disk subsystem and existing /dev/da0 device
On Mon, Dec 11, 2006 at 02:26:42PM -0500, [EMAIL PROTECTED] wrote:
> On Mon, 11 Dec 2006, Jerry McAllister wrote:
>
> > On Mon, Dec 11, 2006 at 02:05:27PM -0500, [EMAIL PROTECTED] wrote:
> >
> > >
> > > I just got an external USB drive that I want to use for disk-based
> > > backups. It is impor
On Mon, Dec 11, 2006 at 02:05:27PM -0500, [EMAIL PROTECTED] wrote:
>
> I just got an external USB drive that I want to use for disk-based
> backups. It is important that this drive be useable on different FreeBSD
> servers that we have.
>
> I got it working on a test server ok, but I noticed th
I just got an external USB drive that I want to use for disk-based
backups. It is important that this drive be useable on different FreeBSD
servers that we have.
I got it working on a test server ok, but I noticed that the sysinstall
utility labeled the device as:
/dev/da0s1d
Since the test se
On 10/30/06 12:05, Reuben A. Popp wrote:
Good morning everyone,
Recently, we've been looking at purchasing a SAN here and I came across this
site while doing some research. Seeing as how we just met with reps from
Apple to discuss their offerings, I thought that the article was well worth
re
Good morning everyone,
Recently, we've been looking at purchasing a SAN here and I came across this
site while doing some research. Seeing as how we just met with reps from
Apple to discuss their offerings, I thought that the article was well worth
reading ;)
http://www.mostlygeek.com/node/39
sed0 0 # "raw" part, don't
> edi
> t
> d: 1228800 33259524.2BSD 2048 16384 11272
> e: 1228800 45547524.2BSD 2048 16384 11272
> f: 4096 57835524.2BSD 2048 16384 28552
> g: 55654695 467435524.2BSD 2048 163
4.2BSD 2048 16384 11272
e: 1228800 45547524.2BSD 2048 16384 11272
f: 4096 57835524.2BSD 2048 16384 28552
g: 55654695 467435524.2BSD 2048 16384 28552
as single user i run: disklabel -e /dev/ad6s1 and i add:
h: 53903178 0 4.2BSD 2048 16384 28552
is this
On 6/30/06, Morten A. Middelthon <[EMAIL PROTECTED]> wrote:
Hi,
long story short, I have a partition on a RAID5 array which after an accident
where I had to rebuild the array became smaller than it originally was. Here's
the original size:
amrd1: 1430505MB (2929674240 sectors) RAID 5 (degraded)
Hi,
long story short, I have a partition on a RAID5 array which after an accident
where I had to rebuild the array became smaller than it originally was. Here's
the original size:
amrd1: 1430505MB (2929674240 sectors) RAID 5 (degraded)
and the new size after the rebuild:
amrd1: 1430400MB (29294
Hi,
I have FreeBSD 6.1 and NetBSD 3.0 on my machine. I can make disklabel
entries (in NetBSD) for the FreeBSD partitions, and that way mount
them in NetBSD. Just a matter of giving the absolute offset values of
the partitions. But I cant find any straight forward way of mounting
NetBSD
On 3/11/06, Steve P. <[EMAIL PROTECTED]> wrote:
> I have been reading up on how to "clone" a disk, so I can boot into a copy.
> Seems like some say tar can do it, but I have seen a place that said to only
> use dump.
I tend to use pax, since it's a bit more straightforward* than tar for copying,
y tar can do it, but I have seen a place that said to only
use dump. Oh, well. I am not quite there yet, working on baby steps.
- Original Message -
From: "[EMAIL PROTECTED]"
To: "Steve P."
Subject: Re: disklabel messup.
Date: Sat, 11 Mar 2006 04:33:25 -0600
O
On 3/10/06, Steve P. <[EMAIL PROTECTED]> wrote:
> I was using sysinstall's disklabel facility to poke around. I
> accidentally did "Undo" on my installed 6.0 working slice.
Are you sure you actually did anything?
If /etc/fstab shows them correctly still
and running &#
I was using sysinstall's disklabel facility to poke around. I
accidentally did "Undo" on my installed 6.0 working slice.
Now, the mount points for my partitions fail to appear, even though I did
not "write" them. I just exited sysinstall.
The odd thing is that the system
On 2006-03-03 10:02, Grant Peel <[EMAIL PROTECTED]> wrote:
> This drive is a SCSI 74 GIG drive.
>
> The machine has been freezing on me lately, out of the blue,
> with no log errors enetered. No crash dumps created. The only
> fix is to cold boot.
>
> Here is the d
This drive is a SCSI 74 GIG drive.
The machine has been freezing on me lately, out of the blue, with no log
errors enetered. No crash dumps created. The only fix is to cold boot.
Here is the disklabel output Should I be worried?
root on s1# disklabel /dev/da0s1
# /dev/da0s1:
8 partitions
incorrect super block
>
> How can I properly re-create the disklabel? It seems this is what I need
> to do in order to get to my data. Any help would be greatly appreciated.
Silly question: did you: newfs -U /dev/ad4s1a ?
--
___
freebsd-questions
Joe,
If you did not touch ad4 the disklabel it should still have been there, but
I presume that you have destroyed it by now. Did you make any kind of backup
? such as a dump of the filesystem ? How did you try to mount ad4s1a ? ( I
am assuming you tried to mount the 'partition' a
disklabel. It starts out like this:
# /dev/ad4s1:
8 partitions:
#size offsetfstype [fsize bsize bps/cpg]
a: 586099316 16unused0 0
c: 5860993320unused0 0
I changed it to this:
# /dev/ad4s1:
8 partitions:
#size offset
disklabels by scanning my drive
for partitions. Great!
Here is the output of scan_ffs on ad4:
[EMAIL PROTECTED] scan_ffs -l /dev/ad4
X: 584002180 2097215 4.2BSD 2048 16384 0 # /data
Good. That is my /data partition. Its UFS2, created in FBSD 5.4.
Next, I tried editing the disklabel. It starts
Hi Anish,
Thanks for the reply -- scan_ffs did exactly what I needed it to do!
For those who encounter a similar problem (damaged disklabel on a FreeBSD
slice), it's not as simple as one might hope, since I was limited to the
"Fixit" shell on the FreeBSD 6.0-RELEASE CD.
scan_ff
slice 3 (FreeBSD 6) is fine, but
> for some reason I'm not concerned with now, is unbootable.
>
> PROBLEM: bsdlabel showed me that slice 1 (FreeBSD 5.4) is damaged
> and only partition c existed and was incorrect. I do not have /
> cannot find a written copy of my disk
unbootable.
PROBLEM: bsdlabel showed me that slice 1 (FreeBSD 5.4) is damaged and only
partition c existed and was incorrect. I do not have & cannot find a
written copy of my disklabel for that disk (a good suggestion to *strongly
emphasize* in the installation manual for newbies!). I did reca
OBLEM: bsdlabel showed me that slice 1 (FreeBSD 5.4) is damaged and only
partition c existed and was incorrect. I do not have / cannot find a
written copy of my disklabel for that disk (a good suggestion to *strongly
emphasize* in the installation manual for newbies!). I did recall that
ad1s1a ('/&
The problem is resolved. I did a "dump, newfs, restore" and now the
disklabel looks more reasonable:
# disklabel da1s1
# /dev/da1s1:
8 partitions:
#size offsetfstype [fsize bsize bps/cpg]
c: 29271714570unused0 0 # "raw"
I have recently installed a big disk (1.4 TB sata raid with scsi
interface) on an i386 computer running FreeBSD 5.4-RELEASE-p1. I have 3
partitions on the FreeBSD slice. The disk is working OK, but the disklabel
seem a little strange. For one of the partitions the "fsize bsize bps/cpg"
Hi,
I was trying to put an alternative boot2 on a freebsd 5.4 box.
With the -s option disappeared from 5.4 disklabel, how do I put a
customized boot2 to a slice on FreeBSD 5.4?
Regards,
Ming
___
freebsd-questions@freebsd.org mailing list
http
On Thu, Mar 10, 2005 at 04:32:30PM -0500, Carl J wrote:
> Hi all! To all your FS guru's outthere, I desperately need
> to know where the disklabel is stored (since my disk is in trouble!)
>
> Situation:
>
> My /dev/ad0s1 has 2 partitions: "a" (FS) fol
Hi all! To all your FS guru's outthere, I desperately need
to know where the disklabel is stored (since my disk is in trouble!)
Situation:
My /dev/ad0s1 has 2 partitions: "a" (FS) followed by "b" (swap).
By using "disklabel -r", I see my "a"
Thank you very much for the quick response!
> > After a sudden power loss, one of the disks (ad2) can not
> > recover.
> What does `fdisk ad2' say?
Some nonsense -- as if I had only a 30Mb partition-4...
> What does `disklabel ad2' say?
Something about "am
Hello!
This is a 4.11-STABLE from Dec 24.
After a sudden power loss, one of the disks (ad2) can not recover.
It was "dangerously dedicated" and had two partitions -- swap (ad2b) and
data (ad2e). Any attempts to use either (swapon, fsck, mount) now result
in EINVAL.
`disklabel ad2&#
Hi,
I'm having some issues installing FreeBSD from the
Disc-1 CDROM. I'm using a Dell SC420 PowerEdge with
two 80GB drives in a RAID level-1 array.
When I get to the Disklabel Editor, both drives are
shown at top, and I can configure the first using auto
defaults, but when I sele
r and /var (that's
where the data reside) are empty.
Then I tried:
#fdisk da0
and it returns
*** Working on device /dev/da0 ***
parameters extracted from in-core disklabel are:
cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for parti
Pete Yandell wrote:
$ disklabel -r ad6 ~
disklabel: bad pack magic number (label is damaged, or pack is unlabeled)
The disklabel is on ad6s1, not on ad6. The kernel does automatically
generate "fictitious" labels for unlabeled disks, no
I have a disk which apparently has no disklabel, but still boots and
mounts several partitions, and I'm puzzled as to how this can be. Where
is it pulling the partition information from if not the disklabel?
$ df
Filesystem 1K-blocksUsed Avail Capacity Mounted on
/dev/ad6s1a1
Good suggestion on using bsdlabel. Unfortunately I am required to use
FreeBSD 4.6.2 which does not contain this utility and disklabel
requires one to invoke an editor to define the new label.
What I resorted to doing was having netboot create /usr100 and then
later overwrite the /etc/fstab via
On Tue, 4 Jan 2005 17:23:05 -0600, Curtis Almond <[EMAIL PROTECTED]> wrote:
> I would like to be able to do the following
>
> 1. Create a / partition of x size
> 2. Create a swap partition of x size
> 3. Create a /usr partition of x size
> 4. Create a ufs partition of the rest of the disk but it i
Curtis Almond wrote:
Anyone know how to make /usr100 not mounted at boot time?
Edit /etc/fstab and add the 'noauto' flag to the appropriate line.
Something like this:
/dev/ad0s2f /usr100 ufs rw,noauto 2 2
Or even better
How can I create the ad0s2-4 (ad0s2f after boot) label but hav
I would like to be able to do the following
1. Create a / partition of x size
2. Create a swap partition of x size
3. Create a /usr partition of x size
4. Create a ufs partition of the rest of the disk but it is not mounted at boot.
What I have thus far is:
# label disk 1
# IDE
ad0s2-1=ufs 396900
Your disks slice tables holding different values for C/H/S geometry.
> You can wipe out the slice tables with the dd(1) command and
> re-initialize them with fdisk and bsdlabel or sysinstall. There is an
> example written on this in 'man 8 bsdlabel'.
I dd'd both drive
2-master UDMA100 Dec 18 15:59:23 /kernel: ad5:
> 238475MB [484521/16/63] at ata2-slave UDMA100
>
> So you can see it's identifying them the same at startup. Now:
>
> su-2.05b# disklabel ad4
> # /dev/ad4c:
> bytes/sector: 512
> sectors/track: 63
> tracks/cylinder: 2
27;s
IDE controller -- same thing every time. Here's from
/var/log/messages:
Dec 18 15:59:23 /kernel: ad4: 238475MB [484521/16/63] at
ata2-master UDMA100
Dec 18 15:59:23 /kernel: ad5: 238475MB [484521/16/63] at
ata2-slave UDMA100
So you can see it's identifying them the same at start
ese will become ad1s1a, ad1s1b etc. which
> > will be a problem. You'll need to fix /etc/fstab and arrange for a
> > booting MBR on the new disk and arrange for the boot sequence to find
> > your / partition.
>
> But not in my case since this disk is just storage I thi
> the new disk and arrange for the boot sequence to find your / partition.
But not in my case since this disk is just storage I think, right. Actually,
when I run the disklabel do I need to use -B at all. I don't need a bootstrap
since its not a boot disk, right?
Thanks,
Alex
aster on
> that controller. Will I need to change the disklabel of ad1 to ad0 at that
> point, or will FreeBSD automagically know what to do?
If you mean to move the disk containing ads1s1e from primary slave to the
primary master then the partition will automatically become ad0s1e.
Hello,
I am adding a new disk to the system to make my /home partition bigger.
Currently I have /home on ad0s1e. I will be adding ad1s1e. After I copy all
the data from ad0 to ad1 I want to remove ad0 and make ad1 the master on that
controller. Will I need to change the disklabel of ad1 to ad0
with.
the devices are:
ad4ad11
All drives have been fdisk'd and such,
ad4s1d.ad11s1d
The first step of setting up vinum is changing the disklabel
disklabel -e /dev/ad4
The disk label says it has 8 partitions, but only the A and C
partitions are shown...
******MY DISKLABEL***
with.
>>> the devices are:
>>> ad4ad11
>>> All drives have been fdisk'd and such,
>>> ad4s1d.ad11s1d
>>> The first step of setting up vinum is changing the disklabel
>>> disklabel -e /dev/ad4
>>> The disk label says it has 8
s are:
ad4ad11
All drives have been fdisk'd and such,
ad4s1d.ad11s1d
The first step of setting up vinum is changing the disklabel
disklabel -e /dev/ad4
The disk label says it has 8 partitions, but only the A and C
partitions are shown...
******MY DISKLABEL
# /dev/ad
nobody ???
matt virus wrote:
Hi all!
I have (8) maxtor 160gb drives I plan on constructing a vinum raid5
array with.
the devices are:
ad4ad11
All drives have been fdisk'd and such,
ad4s1d.ad11s1d
The first step of setting up vinum is changing the disklabel
disklabel -e /dev/ad
Hi all!
I have (8) maxtor 160gb drives I plan on constructing a vinum raid5
array with.
the devices are:
ad4ad11
All drives have been fdisk'd and such,
ad4s1d.ad11s1d
The first step of setting up vinum is changing the disklabel
disklabel -e /dev/ad4
The disk label says it
Ok, thanks I managed to rescue my disk from /usr/sbin/sysinstall
Freebsd Disklabel Editor in combination with fdisk.
It automatically fsck'd my filesystem in write of disklabel...
Thanks :)
-d
Subhro wrote:
Y means a new file system would be created
Regards
S.
On Wed, 29 Sep 2004 11:45:26
Y means a new file system would be created
Regards
S.
On Wed, 29 Sep 2004 11:45:26 +0200, didi <[EMAIL PROTECTED]> wrote:
>
> Does :
>
> UFS2+S N
>
> in "freebsd disklabel editor"
>
> mean that no newfs will be created i.e that only the disklabel wil
Does :
UFS2+S N
in "freebsd disklabel editor"
mean that no newfs will be created i.e that only the disklabel will be
written and the acyual filesystem be left alone?
as opposed to
UFS+S Y
?
d-tail
(I'm a bit worried :| )
Subhro wrote:
There is a key for toggling new filesys
; So, I guess I could:
>
> use fdisk and/or disklabel from within sysinstall again. But how do I
> prevent sysinstall from making 'newfs' ?
>
> Thanks & Regards D-tail
>
>
>
>
> Subhro wrote:
> > If you have partitioned your disk as UFS2, th
It's partitioned and mounted from sysinstall in 5.2.1
And the machine rins 5.2.1 again :(
So, I guess I could:
use fdisk and/or disklabel from within sysinstall again. But how do I
prevent sysinstall from making 'newfs' ?
Thanks & Regards D-tail
Subhro wrote:
If you have parti
ith FreeBSD 5.2.1 so I downgraded to 4.10.
> Problem is the disklabel on my second drive somehow got corrupt, on this
> drive i backed up all home/* folders etc and so on, but now I can't get
> to my backup.
> I really need a way to restore the disklabel.
>
> I have tried sc
I did what you shouldn't do. I have two disks one 80gb and one 100gb
I was not happy with FreeBSD 5.2.1 so I downgraded to 4.10.
Problem is the disklabel on my second drive somehow got corrupt, on this
drive i backed up all home/* folders etc and so on, but now I can't get
to my backup
Hi all,
I have 6 GB left on an already production disk drive, that I want to
label and use. In sysinstall, using disklabel, I get the following:
Disk: ar0 Partition name: ar0s1 Free: 12218275 blocks (5965MB)
Part Mount Size Newfs Part Mount Size Newfs
I am attempting to set up network installs of FreeBSD 5.2.1 for a project
I am working on.
I can boot kern.flp and mfsroot.flp over the network with no problems and
do a manual install.
I can configure install.cfg to automatically set the distribution, network
card, install method and so on.
Wha
On Sat, 17 Jan 2004 15:22:40 +0200
Ion-Mihai Tetcu <[EMAIL PROTECTED]> wrote:
> See growfs(8).
All ready figured out a way of moving stuff around to fix the prob =]
btw growfs is not useful here becuase it is a diskslice that was the
prob, not a fs.
_
On Fri, 16 Jan 2004 17:20:09 -0600
kitsune <[EMAIL PROTECTED]> wrote:
> On Fri, 16 Jan 2004 17:05:35 -0600
> kitsune <[EMAIL PROTECTED]> wrote:
>
> > Is it possible to use disklabel to enlarge a diskslice?
> >
> > I have been doing a fresh install of fbsd
On Fri, 16 Jan 2004 17:05:35 -0600
kitsune <[EMAIL PROTECTED]> wrote:
> Is it possible to use disklabel to enlarge a diskslice?
>
> I have been doing a fresh install of fbsd and I
> forgot I have a 40GB instead of a 20GB drive. Can this be fixed
> using disklabel or do I ha
Is it possible to use disklabel to enlarge a diskslice?
I have been doing a fresh install of fbsd and I
forgot I have a 40GB instead of a 20GB drive. Can this be fixed using
disklabel or do I have to copy everything to another drive, reslice
it, and then copy the stuff back over
2.7G 946M74%/usr
> procfs4.0K 4.0K 0B 100%/proc
>
> new:
> FilesystemSize Used Avail Capacity Mounted on
> /dev/ad4s1e 984M 534M 372M59%/
> /dev/ad4s1f36G 2.2G31G 6%/usr
> procfs4.0K 4.0K 0B
4M 372M59%/
/dev/ad4s1f36G 2.2G31G 6%/usr
procfs4.0K 4.0K 0B 100%/proc
so Im thinking I need to do something with disklabel but I want to make
sure that I dont destroy my "so far working" efforts.
regards,
Jason
__
Hi, I am reposting this in hopes poeple who have disklabel and RAID perc
3DCL / SCSI experience see it tonight.
Hi,
I had a crash tonight. Server rebooted and everything seemed to restart OK.
Interesting disklabel output though. Should I be worried about all the "*"s?
:
If this helps
Hi,
I had a crash tonight. Server rebooted and everything seemed to restart OK.
Interesting disklabel output though. Should I be worried about all the "*"s?
:
If this helps, the disk below is a 10,000 spin RAID 5 Dell Perc DC/L (3
Fujitu disks).
enterprise# disklabel /dev/amrd0
#
FreeBSD <[EMAIL PROTECTED]>
Subject:Re: Disklabel problem IBM SCSI3 disks, vinum too
[Format recovered--see http://www.lemis.com/email/email-format.html]
Single-line paragraphs.
On Sunday, 23 November 2003 at 13:03:47 -0500, Bob Collins wrote:
> At 07:30 PM 11/21/2003, you wrot
1 - 100 of 165 matches
Mail list logo
