2007
05.07

i foobar’d a fedora 4 machine a couple of days ago and when i went to mount the disk into another machine i get this beautiful error:

mount: unknown filesystem type 'LVM2_member'

here was the syntax used:

termcb:~ # mount /dev/hda2 /mnt/old/
mount: unknown filesystem type 'LVM2_member'

and here was the drive :

termcb:~ # fdisk -l

Disk /dev/hda: 30.0 GB, 30005821440 bytes
255 heads, 63 sectors/track, 3648 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 3648 29198137+ 8e Linux LVM

so using lvm2 tools, we do a disk scan:

termcb:~ # lvmdiskscan
/dev/ram0 [ 62.50 MB]
/dev/ram1 [ 62.50 MB]
/dev/hda1 [ 101.94 MB]
/dev/sda1 [ 39.19 MB]
/dev/ram2 [ 62.50 MB]
/dev/hda2 [ 27.85 GB] LVM physical volume
/dev/sda2 [ 2.01 GB]
/dev/ram3 [ 62.50 MB]
/dev/sda3 [ 60.00 GB]
/dev/ram4 [ 62.50 MB]
/dev/sda4 [ 86.96 GB]
/dev/ram5 [ 62.50 MB]
/dev/ram6 [ 62.50 MB]
/dev/ram7 [ 62.50 MB]
/dev/ram8 [ 62.50 MB]
/dev/ram9 [ 62.50 MB]
/dev/ram10 [ 62.50 MB]
/dev/ram11 [ 62.50 MB]
/dev/ram12 [ 62.50 MB]
/dev/ram13 [ 62.50 MB]
/dev/ram14 [ 62.50 MB]
/dev/ram15 [ 62.50 MB]
0 disks
21 partitions
0 LVM physical volume whole disks
1 LVM physical volume

then we do a lvdisplay so we can get the LV Name and VG Name:

termcb:~ # lvdisplay
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID WBjpH6-Jezl-aI1z-XVSp-WzvW-qTDi-c1jkUv
LV Write Access read/write
LV Status NOT available
LV Size 26.06 GB
Current LE 834
Segments 1
Allocation inherit
Read ahead sectors 0

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID Zykaw3-WBHU-oink-38W9-KylN-7u5j-PKx8qT
LV Write Access read/write
LV Status NOT available
LV Size 1.75 GB
Current LE 56
Segments 1
Allocation inherit
Read ahead sectors 0

and also a vgdisplay to make sure it was the right drive:

termcb:~ # vgdisplay
--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 27.84 GB
PE Size 32.00 MB
Total PE 891
Alloc PE / Size 890 / 27.81 GB
Free PE / Size 1 / 32.00 MB
VG UUID ryYRi4-mXOd-XFaW-4xnR-h1cl-hphh-5QQnlM

so at this point i re-tried to mount but using the VG Name:

termcb:~ # mount /dev/VolGroup00/LogVol00 /mnt/old/
mount: special device /dev/VolGroup00/LogVol00 does not exist

still failure

so i did an lvscan next to see what the status of the lv drive is:

termcb:~ # lvscan
inactive '/dev/VolGroup00/LogVol00' [26.06 GB] inherit
inactive '/dev/VolGroup00/LogVol01' [1.75 GB] inherit

fuck…. still inactive
thats when i stumbled across this post :
http://www.fedoraforum.org/forum/archiv … 64964.html

now the rest was pretty self explanatory:

modprobe dm-mod

vgchange -ay

termcb:~ # lvscan
ACTIVE '/dev/VolGroup00/LogVol00' [26.06 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol01' [1.75 GB] inherit

mount /dev/VolGroup00/LogVol00 /mount/point

Success!!

this was done on a suse 10.1 box trying to mount a fedora 4 drive.

if this was gentoo it probably would have been much easier.

The following two tabs change content below.

charlie root

VP of keeping it real / HNIC at pissedoffadmins.com
I bring the cold coffee.

Latest posts by charlie root (see all)

150 comments so far

Add Your Comment
  1. Major props for this. Saved me the encrypted keepass file that was in there… Which had my password to my PIVX wallet!

    If you have a PIVX donation address, I would like to buy u a beer sir.

  2. [quote]if this was gentoo it probably would have been much easier.[/quote]

    but you would still be waiting for the entire system to recompile with the latest mega-fast CLFAGS ;)

    Thanks, this helped.

  3. I think i will be naming my first child after you

  4. Finally! Can you post a btc address so I can tip you?

  5. i LOVE you. thank you <3

  6. You are awesome! Thanks for sharing

  7. in my scenario: my issue is here.

    [root@SurEKilL ~]# mount /dev/sda2 /home/SurEKilL/
    mount: you must specify the filesystem type

    i manage to resolved the issue after searching in some blogs site of RHEL6.

    below are the steps i have done

    step1-

    [root@SurEKilL ~]# lvdisplay | more

    output should be look like below:
    [root@SurEKilL ~]# lvdisplay | more
    — Logical volume —
    LV Path /dev/vg_surekill/lv_root
    LV Name lv_root
    VG Name vg_surekill
    LV UUID 2a0d5K-Pdes-nKiD-ucZK-OB7f-vNR0-Ip5169
    LV Write Access read/write
    LV Creation host, time SurEKilL.mydomain, 2017-05-06 04:59:27 +0800
    LV Status available
    # open 1
    LV Size 8.04 GiB
    Current LE 2058
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    – currently set to 256
    Block device 253:0

    — Logical volume —
    LV Path /dev/vg_surekill/lv_swap
    LV Name lv_swap
    VG Name vg_surekill
    LV UUID 3T8rE2-N9Xy-5vNd-o4EN-ScdC-teLj-0KtaC3
    LV Write Access read/write
    LV Creation host, time SurEKilL.mydomain, 2017-05-06 04:59:31 +0800
    LV Status available
    # open 1
    LV Size 1.47 GiB
    Current LE 376
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    – currently set to 256
    Block device 253:1

    — Logical volume —
    LV Path /dev/vg1/vg1lv1
    LV Name vg1lv1
    VG Name vg1
    LV UUID tz64YC-CyNx-oqEN-bmLC-MKkU-n9y3-4V3Exa
    LV Write Access read/write
    LV Creation host, time SurEKilL.mydomain, 2017-05-06 14:04:53 +0800
    LV Status available
    # open 0

    [root@SurEKilL ~]# vgs
    VG #PV #LV #SN Attr VSize VFree
    vg1 2 1 0 wz–n- 3.81g 2.81g
    vg_surekill 1 2 0 wz–n- 9.51g 0
    [root@SurEKilL ~]#

    [root@SurEKilL ~]# lvscan
    ACTIVE ‘/dev/vg_surekill/lv_root’ [8.04 GiB] inherit
    ACTIVE ‘/dev/vg_surekill/lv_swap’ [1.47 GiB] inherit
    ACTIVE ‘/dev/vg1/vg1lv1’ [1.00 GiB] inherit

    since i have vg1 and inside of vg1 i have vg1lv1 to be mounting.

    and error is specify the file system type. i converted my vg1lv1 to ext4

    [root@SurEKilL ~]# mkfs.ext4 /dev/vg1/vg1lv1
    mke2fs 1.41.12 (17-May-2010)
    Filesystem label=
    OS type: Linux
    Block size=4096 (log=2)
    Fragment size=4096 (log=2)
    Stride=0 blocks, Stripe width=0 blocks
    65536 inodes, 262144 blocks
    13107 blocks (5.00%) reserved for the super user
    First data block=0
    Maximum filesystem blocks=268435456
    8 block groups
    32768 blocks per group, 32768 fragments per group
    8192 inodes per group
    Superblock backups stored on blocks:
    32768, 98304, 163840, 229376

    Writing inode tables: done
    Creating journal (8192 blocks): done
    Writing superblocks and filesystem accounting information: done

    This filesystem will be automatically checked every 30 mounts or
    180 days, whichever comes first. Use tune2fs -c or -i to override.

    after converting i manage to mount the vg1lv1 into my home directory

    [root@SurEKilL ~]# df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/mapper/vg_surekill-lv_root
    8.0G 2.7G 4.9G 36% /
    tmpfs 372M 72K 372M 1% /dev/shm
    /dev/sdc1 485M 33M 427M 8% /boot

    [root@SurEKilL ~]# mount /dev/vg1/vg1lv1 /home/
    [root@SurEKilL ~]#
    [root@SurEKilL ~]#
    [root@SurEKilL ~]# df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/mapper/vg_surekill-lv_root
    8.0G 2.7G 4.9G 36% /
    tmpfs 372M 72K 372M 1% /dev/shm
    /dev/sdc1 485M 33M 427M 8% /boot
    /dev/mapper/vg1-vg1lv1
    1008M 34M 924M 4% /home

    • sorry on the first line or error

      its
      [root@SurEKilL ~]# mount /dev/vg1/vg1lv1 /home/

      then followed by error

  8. Thank you very much.
    It helps a lot.

  9. Thanks a lot! Very structured and informative. U r a gud guy.

  10. thanks

  11. THANK YOU!!!! YOU SAVED MY LIFE TOO!!

  12. …and another life saved :) Thank you for sharing!

  13. Olá, bom dia.
    Eu fiz exatamente como o seu tutorial, perceba que o volumes estão ativos
    [root@srv01 ~]# lvscan
    ACTIVE ‘/dev/EXEMPLO2/lv_swap’ [8,00 GiB] inherit
    ACTIVE ‘/dev/EXEMPLO2/lv_root’ [457,27 GiB] inherit
    ACTIVE ‘/dev/EXEMPLO/lv_swap’ [8,00 GiB] inherit
    ACTIVE ‘/dev/EXEMPLO/lv_root’ [923,02 GiB] inherit

    E ao tentar montar a partição desejada acontece o seguinte:

    [root@srv01 ~]# mount /dev/EXEMPLO2/lv_root /DeusBackup/
    mount: wrong fs type, bad option, bad superblock on /dev/mapper/EXEMPLO2-lv_root,
    missing codepage or helper program, or other error
    In some cases useful info is found in syslog – try
    dmesg | tail or so

    Me ajude, não sei o que fazer.

  14. Thanks.

  15. Thanks for sharing this. Way to go

  16. That was a great help. Thank you. I like the way you ran through the stages. I have mounted and am just getting into the home directory with ecrypt-recover-private using ecrypt-utils.

  17. thank your. really helpful. saved me too.

  18. you are my hero!!!! tnks!!!

  19. Very very help full.. thanks dud!!

  20. Perfect!!! Thanks so much, saved me too :)

  21. Bravo! Saved me a lot of hair pulling

  22. Thank you very much for this post! It saved me from pulling out my hair. :)

  23. dude you are a god

  24. Helpful and precise. Easy to follow too.
    Great guide.

  25. Thank you bro! You save my life (:

  26. I tried mount using volume group and logical volume (active), and its showing
    “mount: you must specify the filesystem type”

    Can you help me out

  27. Thank you! Worked great

  28. same scenario – you saved me!

  29. Thank you very much for your post. Followed your steps, and thought I had my own problem solved, but then I got one complication further. I posted my question on StackExchange:

    https://unix.stackexchange.com/questions/282591/mount-unrecognised-segment-type-thin

    If you know any badass system administrators willing to help with this problem, maybe you can let them know.

  30. Thanks :) I was facing same issue, it helped me.Thanks

  31. Thank you! Worked with a disk with Ubuntu 14.04 installed.

  32. LVM is active now. but when i try to mount it , it says

    mount: you must specify the filesystem type

  33. Very helpful….thankyou

  34. you did it!

  35. Thanksyou so much

  36. Thank you! saved me tons of time

  37. thanks solution, finally saved my data

  38. Very nice.
    Helpfull, this article helps me to access my LVM.

  39. Thank you!!!! You saved my life!:-)