Craig Hagerman [EMAIL PROTECTED] writes:
But sdb1 had ALREADY been set up. Actually I had formatted it with
ext3, then followed the howto (pvcreate, vgcreate, lvcreate, mount) to
set up LVM and then copied all my old data over. So I then set the
partition type to LVM on a disc that already
On 10/20/05, Matthias Julius [EMAIL PROTECTED] wrote:
LVM does not find sda2.What does pvdisplay /dev/sda2 say?
% pvdisplay /dev/sda2
No physical volume label read from /dev/sda2
Failed to read physical volume /dev/sda2
I guess LVM only scans devices that have its type set to LVM.So itmight be
Craig Hagerman [EMAIL PROTECTED] writes:
On 10/20/05, Matthias Julius [EMAIL PROTECTED] wrote:
LVM does not find sda2. What does pvdisplay /dev/sda2
say?
% pvdisplay /dev/sda2
No physical volume label read from /dev/sda2
Failed to read physical volume /dev/sda2
On Thu, Oct 20, 2005 at 03:54:12PM +0200, Goswin von Brederlow wrote:
Mounting totaly ignores the partition type anyway. So that did
nothing. But running pvcreate will have overwritten some data.
Well if pvcreate was run, and that is all, perhaps looking at the lvm
backup data in /etc can tell
On 10/20/05, Goswin von Brederlow [EMAIL PROTECTED] wrote:
Mounting totaly ignores the partition type anyway. So that did
nothing. But running pvcreate will have overwritten some data.
Try mounting with an alternate superblock and mount read-only and save
whatever you can.
What does it mean
On Thu, Oct 20, 2005 at 08:35:22PM +0200, Goswin von Brederlow wrote:
If I read that very confusing mail right then he did run pvcreate on
an ext3 filesystem. So the first superblock is probably wiped.
Oh on a disk he already had data on and didn't want to use for lvm?
Yeah taht would be bad.
Craig Hagerman [EMAIL PROTECTED] writes:
On 10/20/05, Matthias Julius [EMAIL PROTECTED] wrote:
LVM does not find sda2. What does pvdisplay /dev/sda2 say?
% pvdisplay /dev/sda2
No physical volume label read from /dev/sda2
Failed to read physical volume /dev/sda2
I guess LVM only scans
Craig Hagerman [EMAIL PROTECTED] writes:
Hi,
I recently bought a new hard drive. I alread have another big hard
drive for files so altogether they have 450 GB. I decided to set up
LVM on my system to make it easy to access both together and be able
to add more space in the future, but I am
Thanks for the reply and explanation. I understand better now. Are you
sure that Debian takes care of mounting the new LVM share on boot? It
didn't work for me. From what I have read online you have to create
your own startup script.
I had LVM set up successfully on my new HD, copied all the data
Craig Hagerman [EMAIL PROTECTED] writes:
WARNING: Re-reading the partition table failed with error 16: Device
or resource busy.
The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.
This just means what is says. The disk is in use and the kernel
Debian will activate the VG but it will not mount the LVs automatically.
You still have to add them to /etc/fstab.
If you're using root-on-lvm you may also need to regenerate your initrd before
rebooting.
Paul
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
On 10/20/05, Matthias Julius [EMAIL PROTECTED] wrote:
This just means what is says. The disk is in use and the kernel can
not reread the partition table. You have to reboot to do that.
Unfortunately I did reboot before I noticed the typo. After the reboot
neither disc can be seen.
12 matches
Mail list logo
