Hi,
I've just tried to upgrade my mythbox with a larger SATA drive and lvm. I attempted to follow the LVM how-to from the wiki and messed up.

After backing up my current config, I ran fsdick to create an additional partition. It didn't recognise my new harddrive, so instead (and rather foolishly I can see now) I ran create_lvm.sh /dev/hda3 /dev/sdb1 expecting this to sort it out.

It didn't and a little later after a reboot I realised I could no longer connect to the backend.

Ah-ha, I thought, I know I've a good back up. I'll autoupgrade and that will sort everything out. Unfortunately not.

Although I've a good backup somewhere I can't upgrade to it.

I got some messages about not being able to start apache2, which I think I've solved by editing /etc/fstab to remove the lines dev/vg/myth /myth/auto defaults,auto 0 2
Still can't bring up the backend.
I've taken some ideas from here: http://mysettopbox.tv/phpBB2/viewtopic.php?t=15478&highlight=lvm
but to no avail.
Help please. Really, help...

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

Such as?

Need much more information:

What is getting mounted?
What happens if you try to mount the LV manually (do you still have an LV configured)?
What do you see in /var/log/mythtv/mythbackend.log?
Is there a filesystem defined on /dev/sdb1?

I don't think anything is getting mounted.
I've not a LVM working, so I decided to go on a different tack.
The most telling line in the /var/log/mythtv/mythbackend.log is No settings found for this machine's BackendserverIP
I don't think there is a /dev/sbd1
And from that thread I took:
update-rc.d -f lvm remove

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

You need to provide much more specific information:

Use mount and post the output.


Use cfdisk /dev/sdb and post the output.

That's it? That will remove the LVM startup scripts, that's all.

Are you trying to setup an LV or revert back? Do you still have the /dev/hda3 line in /etc/fstab? And what, if anything, is still on /dev/hda3 (probably mounted into /myth, so do an ls -la /myth)

Sorry for the spartan replies.
I am trying to revert back to the earlier state.Have been trying to get this to work while appeasing the other half who wanted feeding and to watch some of her shows... (Appologies dear...)
Anyhow, mount brings back:

root@mythtv:/home/mythtv# mount
/dev/hda1 on / type ext3 (rw,errors=remount-ro)
usbfs on /proc/bus/usb type usbfs (rw,devmode=0666)
tmpfs on /dev/shm type tmpfs (rw)

cfdisk /dev/sdb produces a fatal error and cfdisk exits.

And ls -la /myth produces

root@mythtv:/home/mythtv# ls -la /myth
total 80
dr-xr-xr-x 20 root root 4096 Jun 8 16:39 .
drwxr-xr-x 24 root root 4096 Jun 8 16:38 ..
drwxrwxr-x 2 mythtv mythtv 4096 Jun 8 16:38 archive
drwxrwxr-x 2 mythtv mythtv 4096 Jun 8 16:38 backup
drwxr-xr-x 2 mythtv mythtv 4096 Jun 8 16:38 democracy
drwxr-xr-x 3 mythtv mythtv 4096 Jun 8 19:12 folding@home
drwxrwxr-x 2 mythtv mythtv 4096 Jun 8 16:38 gallery
drwxrwxr-x 6 root root 4096 Jun 8 16:38 games
drwxrwxrwx 2 www-data www-data 4096 Jun 8 16:38 image_cache
drwxrwxr-x 2 mythtv mythtv 4096 Jun 8 16:38 ipodfeed
drwxrwxr-x 2 mythtv mythtv 4096 Jun 8 16:38 motion
drwxrwxr-x 2 mythtv mythtv 4096 Jun 8 16:38 music
drwxrwxr-x 4 mythtv mythtv 4096 Jun 8 17:02 phone
drwxr-xr-x 2 mythtv mythtv 4096 Jun 8 16:39 pretty
drwxr-xr-x 4 root root 4096 Jun 8 16:39 rrd
drwxrwxr-x 2 mythtv mythtv 4096 Jun 8 16:38 stream
drwxrwxrwx 2 mythtv mythtv 4096 Jun 8 16:39 streamtv
drwxrwxr-x 2 mythtv mythtv 4096 Jun 8 16:38 tmp
drwxrwxr-x 2 mythtv mythtv 4096 Jun 8 16:38 tv
drwxrwxr-x 4 mythtv mythtv 4096 Jun 8 16:39 video

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

Actually, I've just checked the contents of myth/tv an its empty, as is the contents of /myth/restore. Looks like game over?

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

Assuming what you have already tried hasn't whacked the original /dev/hda3 partition, try re-adding the /dev/hda3 line to your /etc/fstab. Should look something like

Then reboot. This should restore your original /myth stuff. If it doesn't, try mount /dev/hda3 /myth and post whatever that spits out...

Hi slowtolearn,
Thanks for the advice so far....
Adding this to fstab didn't allow the backend to connect..

While mount produced this:

root@mythtv:/home/mythtv# mount /dev/hda3 /myth
mount: /dev/hda3 already mounted or /myth busy
mount: according to mtab, /dev/hda3 is already mounted on /myth

I'm still not connecting to the back end, could this stil be the problem?

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

Was this after the reboot, with /dev/hda3 in your fstab? If so, then the mount worked as expected. Unfortunately, I suspect that if you check your /myth/tv, /myth/restore directories you will find them empty (?). If so, Looks like it, I'm afraid.

BUM.

Thanks anyway.

If it's any constellation I've learnt something... mostly if it ain't broke don't mess with it. More, about where things are.
Still, I'll reinstall on my 500g sata drive and play with that... change the file system, add several other hdds before I start recording etc. (and she says get it'll be easier... whatever....)

Really though, thanks for the help. If you're ever over this way, pm me and I'll buy you a pint.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)

This was where my stomach hit bottom.

You're most likely hosed. You basically replaced the exisiting volume information with the volume information appropriate for an LVM drive. The partition types, possibly superblocks, ... This is a destructive operation, which is why it's generally recommended as part of a fresh install. There may still be intact data there, but I'm not sure how feasable recovery is.

tjc - Thanks for the explanation. I Will have a fresh build shortly. Well, on the plus side a clean install will get rid of any residue from previous installs that were causing some slightly irregular behaviour.

_________________
Version:R8
Intel C2D 7400, Nvidia 5600 via HDMI to Samsung B37B650TW (PAL), Asus P5QL-E mobo, 4Gb PC6400 DDR2 ram, Samsung Spinpoint 500 Gb & 1Tb drive, Nova-HD-S2 (x2)