Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 15 of 15
Hi LVM seems to be redhat specific, not ext3. And even if at low level LVM elements are ext3 they cannot be access as ext3 : below result of df ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Just Joined!
    Join Date
    Aug 2005
    Location
    Cyprus
    Posts
    8

    hard disk recovery using USB drive box


    Hi

    LVM seems to be redhat specific, not ext3.

    And even if at low level LVM elements are ext3 they cannot be access as ext3 :
    below result of df on a standard fedora4 disk :

    {venus:root} df
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/mapper/VolGroup00-LogVol00
    29900668 10186624 18170672 36% /
    /dev/hda2 93327 9963 78545 12% /boot
    /dev/shm 452644 0 452644 0% /dev/shm
    /dev/sda2 101105 9951 85933 11% /media/usbdisk1

    As you see the LVM part is known as :
    /dev/mapper/VolGroup00-LogVol00
    Which is the LVM partition over ext3.

    fdisk on this disk give :

    {venus:root} fdisk -l

    Disk /dev/hda: 60.0 GB, 60011642880 bytes
    255 heads, 63 sectors/track, 7296 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

    Device Boot Start End Blocks Id System
    /dev/hda1 1 3206 25744131+ 7 HPFS/NTFS
    /dev/hda2 * 3207 3218 96390 83 Linux
    /dev/hda3 3219 7296 32756535 8e Linux LVM

    As you see some space is loosen between 32756535 for hda3 and 29900668 for /dev/mapper/VolGroup00-LogVol00
    it is because in /dev/hda3 it creats first some ext3 elements plus some others to finally get /dev/mapper/VolGroup00-LogVol00

    The partition I want to recover as exatctly the same structure.

    Andre

  2. #12
    Linux Engineer
    Join Date
    Apr 2005
    Location
    Belgium
    Posts
    1,429
    LVM is not Redhat specific either . Logical Volume Manager can be used on any distro that supports it (more recent ones do, like Fedora Core, SuSE 9, Slackware 10, and so on. I think it depends on the kernel).
    ** Registered Linux User # 393717 and proud of it ** Check out www.zenwalk.org
    ** Zenwalk 2.8 - Xfce 4.4 beta 2- 2.6.17.6 kernel = Slack on steroids! **

  3. #13
    Just Joined!
    Join Date
    Jul 2006
    Posts
    2
    Did you ever figure this out? I have the same problem...

  4. #14
    Just Joined!
    Join Date
    Jul 2006
    Posts
    2
    I figured it out, this helped a lot
    http://www.novell.com/products/linux...papers/LVM.pdf

    Here's what helped me (bottom of page 15)

    Automatic server setup from stored LVM setup

    The LVM of the server can be reset using lvmchange. This is a last resort if something goes wrong. It
    does not change the LVM setup stored on the physical devices, only the data in the running system is reset.
    To restore an LVM setup from the one stored on disk, run first vgscan to find all VGs and then
    vgchange −a y to activate them. This is what happens at each boot time, see init file /etc/init.d/boot
    (look for vcgscan). You can completely delete the local LVM setup information with rm −rf
    /etc/lvm*, including all device files for accessing the LVs (/dev/vg−name/lv−name), and it will
    automatically be recreated next time you boot or issue the vgscan command manually. This means that you
    do not have to do anything after a reboot to be able to use your LVs again, the runtime LVM setup happens
    automatically during a system boot, if any LVM setup is detected on any of the attached physical devices.

  5. #15
    Just Joined!
    Join Date
    Aug 2006
    Posts
    1

    Post

    Quote Originally Posted by andleg
    Hi

    I am using fedora 4 on a hp laptop.
    My motherboard burned out..

    I wanted to get bak my data's puting my hard disk in an USB box and connecting it to another machine.

    When I had installed fedora on this machine I took the automatic partition option. I kept windows in a smaller partition and fedora used the rest.

    I get 3 devices /dev/sda1 /dev/sda2 /dev/sda3
    I can acce boot partition from the hard disk but not windows and not main fedora patition. (VolGroup00-LogVol00)

    I crated 3 directory : sda1 sda2 sda3
    {venus:{root} mount -t auto /dev/sda1 sda1
    mount: unknown filesystem type 'ntfs'
    {venus:root} mount -t auto /dev/sda2 sda2
    {venus:root} mount -t auto /dev/sda3 sda3
    mount: you must specify the filesystem type

    I get boot partion in sda2
    From suse I can access windows partition in sda1 : ntfs filesystem type seems to be reconised
    I cannot access main partition (which is in sda3) using suse or fedora.

    I need to access main partition.

    Any help welcome.

    Andre
    Have you tried Nucleus Kernel software

    this is really great tool to recover your data, to download this tool click the following link:
    http://www.nucleustechnologies.com/D...y-Software.php

Page 2 of 2 FirstFirst 1 2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •