Mailing List
Home
Linux - General Red Hat Linux discussion list
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Installation - Getting started with Red Hat Linux
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Red Hat Linux 8.0 - Discussion of Red Hat Linux 8.0 (Psyche)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Red Hat Linux 7.1 - Discussion of Red Hat Linux 7.1 (Seawolf)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
X Windows problem (xauth)
Upgrading openoffice 1 1 rpm
FTP: connection refused
FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
broadcom network interface
make mrproper
sendmail configuration on redhat
Couldn 't open PID file /var/run/named/named pid Permission denied
Promise 378 controller
kernel 2 6 and /dev/sound/mixer not found
Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
Lotus Notes under Wine
/etc/security/limits conf question
Intel E/1000 driver
Command stream end of file while reading
rpm database corrupt
qla2300 modules
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Moving /var to larger disk HOW TO LOCATE NEW DISK

Moving /var to larger disk HOW TO LOCATE NEW DISK

2004-10-16       - By James Marcinek

 Back
Reply:     1     2     3     4     5     6     7     8     9  

OK,

I had to acquire an ultra ATA 133 pci card as the disk was over 200G. I left the
original disk in it 's orginal configuration. The system comes up and the BIOS
detects the hard drive as I can see it...

Now I have to figure out what device it is recognized as? I presumed /dev/hdb
but when I issue an fdisk I get the following error:
fdisk /dev/hdb

Unable to open /dev/hdb


So I tried the pvcreate command:
pvcreate /dev/hdb
pvcreate -- can 't open physical volume "/dev/hdb " to get its size

If I can locate the disk I can do the rest. Can anyone help me out here?

James Marcinek <jmarc1@(protected)>,"Discussion of Red Hat
Enterprise Linux 3 (Taroon)" <taroon-list@(protected)> wrote:
> "Discussion of Red Hat Enterprise Linux 3 (Taroon)"
> <taroon-list@(protected)> wrote:
> > On Sat 16 October 2004 13:45, James Marcinek wrote:
> > > I 'm familiar with Logical volumes and volume groups, etc. Just haven 't
> > > implemented one on a Red Hat system(mostly AIX). If you look at my example
> > > I am concerned with the pvcreate and vgcreate process. If you look at the
> > > example I took from the 'man pages ' they created.
> > >
> > > /dev/hdk1 (before pvcreate) - > /dev/sdk1 (after pvcreate)
> > The device names should have been the same in both the text and the example.
> > This would appear to be a typo in the man page.
> > Initialising physical volumes categorically does *not* change their device
> > names.
> > /dev/hdk1 and /dev/sdk1 will _always_ be different devices, LVM or not.
> >
> No problem at all... I actually had thought that what I had been told was
> referring to RAID partitions...
>
> I just installed the drive. I haven 't done anything to it yet. Do I have to do
> anything to it before the pvcreate (like fdisk)? I 'm going to add the whole
disk
> to the PV. Now I 'm a little rusty with this so bear with me. When I issued the
> fdisk -l and I cannot see the new drive. I also tried the fdisk /dev/hdb. I
> installed the drive on a new ultra 133 pci card and I have to find the device
> before I can make a PV out of it.
>
> > Apologies if I misinterpreted your question.
> > ( I must have misread the quotes you gave from the manpage)
> >
> > :-(
> >
> > Stuart.
> >
> > >
> > > This is what I am concerned about... You 'll notice that the vgcreate
> > > creates the volume group test_vg; however they do not call /dev/hdk1, etc
> > > they refer to /dev/sdk1, etc) which is what I 'm trying to determine. I
> > > could swear that this had been discussed during my RHCE course. Thanks
> >
> >
> >
> > --
> > Stuart Sears RHCE, RHCX
> > Quidquid latine dictum sit, altum viditur
> >
> > --
> > Taroon-list mailing list
> > Taroon-list@(protected)
> > http://www.redhat.com/mailman/listinfo/taroon-list
> >
>
>
> --
> Taroon-list mailing list
> Taroon-list@(protected)
> http://www.redhat.com/mailman/listinfo/taroon-list
>

--
Taroon-list mailing list
Taroon-list@(protected)
http://www.redhat.com/mailman/listinfo/taroon-list