[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [linux-lvm] can't mount vfat fs on lvm created by winxp guest on xen
- From: Yann Boutin <yann boutin free fr>
- To: LVM general discussion and development <linux-lvm redhat com>
- Subject: Re: [linux-lvm] can't mount vfat fs on lvm created by winxp guest on xen
- Date: Sat, 28 Apr 2007 19:45:35 +0200
On 15:05 Sat 28 Apr , Bryn M. Reeves wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Yann Boutin wrote:
> > Greetings,
> > I've had no success with mounting a vfat file system created by a
> > Windows XP guest on a lvm volume. Windows XP guest is running under xen 3.0.5 rc3.
> >
> > # mount -t vfat /dev/vg1/win1 /mnt/
> > mount: wrong fs type, bad option, bad superblock on /dev/vg1/win1,
> > missing codepage or other error
> > In some cases useful info is found in syslog - try
> > dmesg | tail or so
> >
>
> Presumably, the windows install partitioned the raw storage?
>
> Try running "file -s /dev/vg1/win1". If it says something like this:
>
> /dev/sda: x86 boot sector; partition 1: ID=0x83, active, starthead 1,
> startsector 63, 208782 sectors; partition 2: ID=0x8e, starthead 0,
> startsector 208845, 195157620 sectors, code offset 0x48
>
> Then there's a partition table on the device and the VFAT file system is
> in a partition on it.
>
> You can map those partitions using kpartx. Run:
>
> kpartx -a /dev/vg1/win1
>
> And you should see some new entries in /dev/mapper like win1p1 win1p2
> etc. You can remove them with:
>
> kpartx -d /dev/vg1/win1
Actually I solved my problem the same way but by hand. I map the first inner partition with dmsetup with adding an offset of 63 blocks. But really thanks for your answer and Kpartx is much simplier.
I've started a similar thread here too :
http://lists.xensource.com/archives/html/xen-users/2007-04/msg00846.html
Best regards
Yann.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]