* [linux-lvm] lvm lost after debian upgrade
@ 2004-12-11 2:25 Daniel Roth
2004-12-12 17:48 ` Alasdair G Kergon
2004-12-12 23:15 ` Alex Owen
0 siblings, 2 replies; 5+ messages in thread
From: Daniel Roth @ 2004-12-11 2:25 UTC (permalink / raw)
To: linux-lvm
Hi all!
I got this nice idea today to do a apt-get update/upgrade on my system.
when it was done I moved the box, and upon reboot my lvm was gone. I
think I had lvm1 before, but now it seems like I have
LVM version: 2.00.29 (2004-11-27)
Is this maybe what is causing the problem?
My lvm is at /dev/volume_group/mylv, my lvm consisted of hde,g,i
I noticed from dmesg that
LVM version 1.0.5+(22/07/2002) module loaded
and that devfs wouldn't be started... (no volumes or equiv)
Please advice, I got pretty much schoolwork on it...
Daniel
Some shelldumps
roth:~# lvmdiskscan
/dev/hda1 [ 2.05 GB]
/dev/hde1 [ 76.69 GB]
/dev/hdg1 [ 1.00 KB]
/dev/hdi1 [ 149.05 GB]
/dev/hda2 [ 1.00 KB]
/dev/hda5 [ 346.47 MB]
/dev/hdg5 [ 57.25 GB]
0 disks
7 partitions
0 LVM physical volume whole disks
0 LVM physical volumes
roth:~# vgcfgrestore -ll -n mylv
Please specify a *single* volume group to restore.
roth:~# vgcfgrestore -n mylv /dev/hdg
/etc/lvm/backup/hdg: stat failed: No such file or directory
Couldn't read volume group metadata.
Restore failed.
roth:~# vgcfgrestore -n mylv /dev/hdg1
/etc/lvm/backup/hdg1: stat failed: No such file or directory
Couldn't read volume group metadata.
Restore failed.
roth:~# vgcfgrestore -n mylv /dev/hdg5
/etc/lvm/backup/hdg5: stat failed: No such file or directory
Couldn't read volume group metadata.
Restore failed.
roth:~# vgscan
Reading all physical volumes. This may take a while...
/dev/hdf: open failed: No such device or address
/dev/hdh: open failed: No such device or address
/dev/hdj: open failed: No such device or address
/dev/hdb1: open failed: No such device or address
/dev/hdf1: open failed: No such device or address
...
/dev/hdb20: open failed: No such device or address
/dev/hdf20: open failed: No such device or address
/dev/hdh20: open failed: No such device or address
No volume groups found
roth:~# lvscan
No volume groups found
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [linux-lvm] lvm lost after debian upgrade
2004-12-11 2:25 [linux-lvm] lvm lost after debian upgrade Daniel Roth
@ 2004-12-12 17:48 ` Alasdair G Kergon
2004-12-13 3:10 ` Daniel Roth
2004-12-12 23:15 ` Alex Owen
1 sibling, 1 reply; 5+ messages in thread
From: Alasdair G Kergon @ 2004-12-12 17:48 UTC (permalink / raw)
To: LVM general discussion and development
On Sat, Dec 11, 2004 at 03:25:03AM +0100, Daniel Roth wrote:
> My lvm is at /dev/volume_group/mylv, my lvm consisted of hde,g,i
Known issues with Debian:
lvm.conf detect_md_component should be set to 1 not 0
lvm.conf filters - check if cdrom drive is excluded correctly:
sometimes the cdrom exclusion points to a real hard disk by mistake
Use pvscan -P to check what LVM2 actually sees.
Alasdair
--
agk@redhat.com
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [linux-lvm] lvm lost after debian upgrade
2004-12-11 2:25 [linux-lvm] lvm lost after debian upgrade Daniel Roth
2004-12-12 17:48 ` Alasdair G Kergon
@ 2004-12-12 23:15 ` Alex Owen
2004-12-13 3:11 ` Daniel Roth
1 sibling, 1 reply; 5+ messages in thread
From: Alex Owen @ 2004-12-12 23:15 UTC (permalink / raw)
To: LVM general discussion and development
Have you tried booting with the old kernel and old initrd?
Alex Owen
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [linux-lvm] lvm lost after debian upgrade
2004-12-12 17:48 ` Alasdair G Kergon
@ 2004-12-13 3:10 ` Daniel Roth
0 siblings, 0 replies; 5+ messages in thread
From: Daniel Roth @ 2004-12-13 3:10 UTC (permalink / raw)
To: LVM general discussion and development
Alasdair G Kergon wrote:
>On Sat, Dec 11, 2004 at 03:25:03AM +0100, Daniel Roth wrote:
>
>
>>My lvm is at /dev/volume_group/mylv, my lvm consisted of hde,g,i
>>
>>
>
>Known issues with Debian:
>
> lvm.conf detect_md_component should be set to 1 not 0
>
> lvm.conf filters - check if cdrom drive is excluded correctly:
> sometimes the cdrom exclusion points to a real hard disk by mistake
>
>Use pvscan -P to check what LVM2 actually sees.
>
>Alasdair
>
>
lvm.conf and cdrom exclusion: checked and confirmed
pvscan -P gives me the following(scroll down). Seems ok for actual
devices (/dev/hdb,f,h,j does not exist)
I am currently in status of what is described in thread "Can't mount
after crash"
Regards Daniel
roth:/disk# pvscan -P
Partial mode. Incomplete volume groups will be activated read-only.
/dev/loop0: ioctl BLKGETSIZE64 failed: No such device or address
/dev/loop1: ioctl BLKGETSIZE64 failed: No such device or address
/dev/loop2: ioctl BLKGETSIZE64 failed: No such device or address
/dev/loop3: ioctl BLKGETSIZE64 failed: No such device or address
/dev/loop4: ioctl BLKGETSIZE64 failed: No such device or address
/dev/loop5: ioctl BLKGETSIZE64 failed: No such device or address
/dev/loop6: ioctl BLKGETSIZE64 failed: No such device or address
/dev/loop7: ioctl BLKGETSIZE64 failed: No such device or address
/dev/hdf: open failed: No such device or address
/dev/hdh: open failed: No such device or address
/dev/hdj: open failed: No such device or address
/dev/hdb1: open failed: No such device or address
/dev/hdf1: open failed: No such device or address
/dev/hdh1: open failed: No such device or address
/dev/hdj1: open failed: No such device or address
/dev/hdb2: open failed: No such device or address
/dev/hdf2: open failed: No such device or address
/dev/hdh2: open failed: No such device or address
/dev/hdj2: open failed: No such device or address
/dev/hdb3: open failed: No such device or address
/dev/hdf3: open failed: No such device or address
/dev/hdh3: open failed: No such device or address
/dev/hdj3: open failed: No such device or address
/dev/hdb4: open failed: No such device or address
/dev/hdf4: open failed: No such device or address
/dev/hdh4: open failed: No such device or address
/dev/hdj4: open failed: No such device or address
/dev/hdb5: open failed: No such device or address
/dev/hdf5: open failed: No such device or address
/dev/hdh5: open failed: No such device or address
/dev/hdj5: open failed: No such device or address
/dev/hdb6: open failed: No such device or address
/dev/hdf6: open failed: No such device or address
/dev/hdh6: open failed: No such device or address
/dev/hdj6: open failed: No such device or address
/dev/hdb7: open failed: No such device or address
/dev/hdf7: open failed: No such device or address
/dev/hdh7: open failed: No such device or address
/dev/hdj7: open failed: No such device or address
/dev/hdb8: open failed: No such device or address
/dev/hdf8: open failed: No such device or address
/dev/hdh8: open failed: No such device or address
/dev/hdj8: open failed: No such device or address
/dev/hdb9: open failed: No such device or address
/dev/hdf9: open failed: No such device or address
/dev/hdh9: open failed: No such device or address
/dev/hdj9: open failed: No such device or address
/dev/hdb10: open failed: No such device or address
/dev/hdf10: open failed: No such device or address
/dev/hdh10: open failed: No such device or address
/dev/hdb11: open failed: No such device or address
/dev/hdf11: open failed: No such device or address
/dev/hdh11: open failed: No such device or address
/dev/hdb12: open failed: No such device or address
/dev/hdf12: open failed: No such device or address
/dev/hdh12: open failed: No such device or address
/dev/hdb13: open failed: No such device or address
/dev/hdf13: open failed: No such device or address
/dev/hdh13: open failed: No such device or address
/dev/hdb14: open failed: No such device or address
/dev/hdf14: open failed: No such device or address
/dev/hdh14: open failed: No such device or address
/dev/hdb15: open failed: No such device or address
/dev/hdf15: open failed: No such device or address
/dev/hdh15: open failed: No such device or address
/dev/hdb16: open failed: No such device or address
/dev/hdf16: open failed: No such device or address
/dev/hdh16: open failed: No such device or address
/dev/hdb17: open failed: No such device or address
/dev/hdf17: open failed: No such device or address
/dev/hdh17: open failed: No such device or address
/dev/hdb18: open failed: No such device or address
/dev/hdf18: open failed: No such device or address
/dev/hdh18: open failed: No such device or address
/dev/hdb19: open failed: No such device or address
/dev/hdf19: open failed: No such device or address
/dev/hdh19: open failed: No such device or address
/dev/hdb20: open failed: No such device or address
/dev/hdf20: open failed: No such device or address
/dev/hdh20: open failed: No such device or address
PV /dev/hdi1 VG my_volume_group lvm2 [149.05 GB / 0 free]
PV /dev/hde1 VG my_volume_group lvm2 [76.69 GB / 0 free]
PV /dev/hdg5 VG my_volume_group lvm2 [57.25 GB / 964.00 MB free]
Total: 3 [282.99 GB] / in use: 3 [282.99 GB] / in no VG: 0 [0 ]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [linux-lvm] lvm lost after debian upgrade
2004-12-12 23:15 ` Alex Owen
@ 2004-12-13 3:11 ` Daniel Roth
0 siblings, 0 replies; 5+ messages in thread
From: Daniel Roth @ 2004-12-13 3:11 UTC (permalink / raw)
To: LVM general discussion and development
Alex Owen wrote:
>Have you tried booting with the old kernel and old initrd?
>
>Alex Owen
>
>
>
Yes, didn't make any difference. Downgraded lvm as well, no difference.
I am currently in status of what is described in thread "Can't mount
after crash"
Regards Daniel
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-12-13 3:11 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-11 2:25 [linux-lvm] lvm lost after debian upgrade Daniel Roth
2004-12-12 17:48 ` Alasdair G Kergon
2004-12-13 3:10 ` Daniel Roth
2004-12-12 23:15 ` Alex Owen
2004-12-13 3:11 ` Daniel Roth
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox