[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Can't mount ntfs, says: unknown filesystem type 'LVM2_member'



Reposting to the list, OP, obey REPLY-TO headers or use 'Reply All'.
On Wed, Apr 27, 2011 at 6:37 PM, Jose Legido <jose@legido.com> wrote:
On Wed, Apr 27, 2011 at 6:45 PM, Chris Brennan <xaero@xaerolimit.net> wrote:
> On Wed, Apr 27, 2011 at 12:36 PM, Jose Legido <jose@legido.com> wrote:
>>
>> Hello
>> I had windows with ntfs
>> I installed ubuntu. All ok. Gurb with 2 os, can ran windows and uvuntu and
>> can mount windows partition in ubuntu
>> I installed debian with lvm over ubuntu partition.
>> I can't mount windows partition now, and windows doesn't appears in gurb
>>
>> # mount /dev/sda1 /mnt/windows/
>> mount: unknown filesystem type 'LVM2_member'
>>
>> # pvs --all
>>  PV         VG    Fmt  Attr PSize   PFree
>>  /dev/dm-1             --        0       0
>>  /dev/dm-2             --        0       0
>>  /dev/root             --        0       0
>>  /dev/sda1        lvm2 a-   113,25g 113,25g
>>  /dev/sda2             --        0       0
>>  /dev/sda5  vol64 lvm2 a-   113,25g      0
>>
>> I can't active vg because haven't name, but is not lvm, is only ntfs
>> partition
>> Maybe ubuntu puts in lvm and grub? Any idea? I have a lot of usefull
>> information in
>> Thanks!
>
> What does 'vgscan' produce?
only shows the debian LVM
# vgscan
 Reading all physical volumes.  This may take a while...
 Found volume group "vol64" using metadata type lvm2


> Was windows installed on it's own LVM?

No. I don't know who created this LVM!

> did you load the ntfs module (from the kernel) or did you try to use ntfs3g? 'Ware
> the user though, NTFS write support with either module is flaky at best,
> some have reported success, some have not, YMMV.
>

I use ntfs3g:
# mount -t ntfs /dev/sda1 /mnt/windows/
NTFS signature is missing.
Failed to mount '/dev/sda1': invalid argument
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?


On Wed, Apr 27, 2011 at 6:45 PM, shawn wilson <ag4ve.us@gmail.com> wrote:
> do an 'fdisk -l /dev/sda' and confirm everything,

# fdisk -l /dev/sda

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xfce09344

  Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       14784   118752448+  8e  Linux LVM
/dev/sda2           29570       30401     6683040   12  Compaq diagnostics
/dev/sda3           14785       29569   118759425    5  Extended
/dev/sda5           14785       29569   118759424   8e  Linux LVM

Partition table entries are not in disk order


> but, 'mount -t ntfs
> .... ' should work for you. it is possible that sda on ubuntu is
> showing up as sdb in debian - why you should use labels if you don't.
>

The same problem:

# mount -t ntfs /dev/sda1 /mnt/windows/
NTFS signature is missing.
Failed to mount '/dev/sda1': Argumento inválido
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?


A lot of thanks!


post the output of the following commands

mount
df -h
cat /proc/partitions
lsmod | grep ntfs
uname -a

file /dev/sdxX (where 'x' is sda and sdb and 'X' is for each partition.


-- 
> A: Yes. > >Q: Are you sure? > >>A: Because it reverses the logical flow of conversation. > >>>Q: Why is top posting frowned upon?

Reply to: