<b><i>"gLaNDix (Jesse Kaufman)" <glandix@lloydnet.org></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> Tom+Dale wrote:<br><br>> Right, I believe that we grown the volume group to include the new <br>> drive. I did not say that in my first message because LVM is all new to <br>> me so I'm not really sure how far we got, technically. Functionally, I <br>> know that we gave up before figuring out why MythTV only recognized the <br>> original disk space (excluding the new drive).<br><br>that makes sense that myth (and the os in general) would not see the <br>space on that drive yet, since the logical volume has grown, but the <br>filesystem has not yet ... think of it as kinda similar to the <br>"standard" partitioning schemes ... let's say you have a 100GB drive and <br>create a 75GB partition on it ... that 25GB left over is still there, <br>but since it's unpartitioned
space, nothing will "see" it ...<br><br><br>> As newbies struggling to get a clue in the wee hours of Saturday <br>> morning, we adjourned at that point, planning to do more research <br>> later. When I checked things Saturday afternoon, I discovered the <br>> clicking sound of the new drive and suspected other trouble.<br><br>yeah, i know how that goes ... until this weekend, all i knew about lvm <br>was copy/paste of commands from http://www.tldp.org/HOWTO/LVM-HOWTO (a <br>very good resource, by the way). when i had the missing physical volume <br>error, i googled and that's how i found out about the --removemissing <br>argument to vgreduce.<br><br>you can actually run 'vgreduce -t [volumeGroup] /dev/sda' (-t means <br>"test") and it will tell you if it can't remove the physical volume <br>because it is still used... you can also run 'vgreduce -t <br>--removemissing [volumeGroup]' and it will tell you what exactly will be <br>removed (according to the man
page)...<br><br>also, according to the man page, it mentions a '--partial' option which <br>will do it's best to use the physical volumes it is able to find and <br>will use /dev/ioerror in place of any missing drives ... that may let <br>you be able to at least access your data ... maybe 'vgchange -ay <br>--partial [volumeGroup]' will let you activate it to make sure all your <br>data is there and do any backups? if it's all there, you could most <br>likely replace /dev/sda with a new drive and give it the old drive's <br>UUID (make sure to write down what it is before doing anything!) it's <br>definitely worth a shot! :)<br><br>anyway, i'm in no way claiming to be an expert on this ... after this <br>weekend, i had to read and read and read all the man pages and docs on <br>lvm to fix my problem and i at least think i have a decent understanding <br>... remember, almost any lvm command will accept the --test/-t option so <br>you can do a "dry-run" to see what might
have happened if you did it for <br>real ...<br><br>when googling, i ran across this nice "simple introduction to lvm" ... <br>you might find it helpful, too: <br>http://www.debian-administration.org/articles/410<br><br>-g-<br>_______________________________________________<br>mythtv-users mailing list<br>mythtv-users@mythtv.org<br>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users<br></blockquote>Well, that nasty thing called "work" got in the way of my troubleshooting until now. I have tried a few of your suggestions with what appears to be limited success, though I cannot be sure.<br><br>First, I tried "vgreduce --removemissing VolGroup00" which seemed to work. Then, I tried "vgchange -ay --partial VolGroup00" which also appeared to complete successfully. Next I tried "ls /video" which reported nothing in the directory (this would not be correct if the volume group was working). Next, I tried:<br><br>[root@mythserver ~]# mount -a<br>mount:
special device /dev/VolGroup00/LogVol00 does not exist<br><br>Now I didn't know what else to try so I guessed at a few commands without any succes. I'm floundering here...can anyone suggest anything else to try? Did I somehow lose the data? It seems to me that I should be able to access it still. I feel like I just need to tell the system how to find the logical volume LogVol00. It doesn't show up under /dev, but I don't know if that matters.<br><br>Thanks everyone!<br><br>Other commands and responses that I got today:<br><br>[root@mythserver ~]# vgchange -a y VolGroup00<br> 0 logical volume(s) in volume group "VolGroup00" now active<br><br>[root@mythserver ~]# pvdisplay<br> --- Physical volume ---<br> PV Name /dev/hda5<br> VG Name VolGroup00<br> PV
Size 66.12 GB / not usable 0 <br> Allocatable yes <br> PE Size (KByte) 4096<br> Total PE 16926<br> Free PE 16926<br> Allocated PE 0<br> PV UUID 317l2C-oay1-TWFG-5NTX-XJS3-vLal-Xh5bBL<br> <br> --- Physical volume ---<br> PV Name /dev/hdb<br> VG Name
VolGroup00<br> PV Size 298.09 GB / not usable 0 <br> Allocatable yes <br> PE Size (KByte) 4096<br> Total PE 76311<br> Free PE 76311<br> Allocated PE 0<br> PV UUID nfLxS1-0u3t-5Zr9-57iu-1oZe-Bkkd-75SERQ<br><br>[root@mythserver ~]# vgscan<br> Reading all physical volumes. This may take a while...<br> Found volume group "VolGroup00" using metadata type lvm2<br><br>[root@mythserver ~]# vgck -vv
VolGroup00<br> Setting global/locking_type to 1<br> Setting global/locking_dir to /var/lock/lvm<br> File-based locking enabled.<br> Using volume group(s) on command line<br> Locking /var/lock/lvm/V_VolGroup00 RB<br> Finding volume group "VolGroup00"<br> /dev/sda: No label detected<br> /dev/hda1: No label detected<br> /dev/hda2: No label detected<br> /dev/hda3: No label detected<br> /dev/hda5: lvm2 label detected<br> /dev/hdb: lvm2 label detected<br> /dev/hda5: lvm2 label detected<br> /dev/hdb: lvm2 label detected<br> /dev/hda5: lvm2 label
detected<br> /dev/hdb: lvm2 label detected<br> /dev/hda5: lvm2 label detected<br> /dev/hdb: lvm2 label detected<br> Unlocking /var/lock/lvm/V_VolGroup00<br><br><p> 
<hr size=1>Yahoo! Messenger with Voice. <a href="http://us.rd.yahoo.com/mail_us/taglines/postman1/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com">Make PC-to-Phone Calls</a> to the US (and 30+ countries) for 2¢/min or less.