Find the answer to your Linux question:
Results 1 to 2 of 2
Hello everyone, I'm having trouble getting the debian installer to detect an existing LVM I installed Lenny on LVM on top of RAID 1. My system looks like this 2x ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jun 2010
    Posts
    1

    Debain installer not detecting LVM


    Hello everyone,
    I'm having trouble getting the debian installer to detect an existing LVM

    I installed Lenny on LVM on top of RAID 1.
    My system looks like this

    2x 500GB RAID 1
    /boot - /dev/md0
    / - /dev/md1
    swap
    LVM rest of the disk:
    /home - /dev/vg0/home
    /usr - /dev/vg0/usr
    /var - /dev/vg0/var
    /tmp - /dev/vg0/tmp

    I just added two 1.5 TB drives in raid 1 to the logical volume group home

    100% added to /home /dev/md3

    I went to reinstall the system from the lenny disc and now the installer does not recognize the LVM. It did recognize the LVM before I added md3 to the LVM.

    During the partition editor, if i go to a terminal (by going to another window/console) and give the command vgdisplay it says that physical volume with UUID V0S1Yx-361r-NZaE-w1Fy-kCFQ-9MmH-g287vh cannot be found. You will see below that the UUID refers to /dev/md3 (the added 1.5 raid 1 array)

    Below is the output of "pvdisplay" and "mdadm --detail /dev/md3"

    pvdisplay
    --- Physical volume ---
    PV Name /dev/md2
    VG Name vg0
    PV Size 459.06 GB / not usable 1.69 MB
    Allocatable yes (but full)
    PE Size (KByte) 4096
    Total PE 117518
    Free PE 0
    Allocated PE 117518
    PV UUID SeY6O1-TCvr-vNKO-prse-7z6t-d4wf-O83y5j

    --- Physical volume ---
    PV Name /dev/md3
    VG Name vg0
    PV Size 1.36 TB / not usable 832.00 KB
    Allocatable yes (but full)
    PE Size (KByte) 4096
    Total PE 357699
    Free PE 0
    Allocated PE 357699
    PV UUID V0S1Yx-361r-NZaE-w1Fy-kCFQ-9MmH-g287vh


    mdadm --detail /dev/md3

    /dev/md3:
    Version : 00.90
    Creation Time : Tue Jun 8 13:29:03 2010
    Raid Level : raid1
    Array Size : 1465135936 (1397.26 GiB 1500.30 GB)
    Used Dev Size : 1465135936 (1397.26 GiB 1500.30 GB)
    Raid Devices : 2
    Total Devices : 2
    Preferred Minor : 3
    Persistence : Superblock is persistent

    Update Time : Sat Jun 12 19:07:11 2010
    State : clean
    Active Devices : 2
    Working Devices : 2
    Failed Devices : 0
    Spare Devices : 0

    UUID : 3eb52192:2d027e5f:8f1e2ef1:3f825f45 (local to host yield)
    Events : 0.6

    Number Major Minor RaidDevice State
    0 8 33 0 active sync /dev/sdc1
    1 8 49 1 active sync /dev/sdd1


    I don't know if this has to do with it but /dev/md3 is the only array that says local to host yield [yield is my hostname] next to its UUID after the mdadm --detail command

    Please let me know if you have any ideas or if should provide more info/commands

    Thanks in advance

  2. #2
    Linux Newbie
    Join Date
    Jan 2007
    Location
    Arizona
    Posts
    139

    I hope someone answers this....

    I hope someone with the right knowledge base answers this because I need to attempt the same thing soon. I don't think that this is so much a Debian issue as a hardware (recognition) issue though.

Posting Permissions

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