Unable to mount JBOD NVRAID using dmraid in Ubuntu Server 10.10

Asked by Andrew Phillips

I have Ubuntu Server 10.10 installed on an Asus M2NPV-VM motherboard with four hard drives being combined in a JBOD. Originally, I had these installed on Windows Server 2003 and a single partititon (not sure if it was a primary or logical) created on this JBOD.

It appears that the RAID set is already active:

root@afs:/home/andrew# dmraid -s
*** Active Set
name : nvidia_ebdfedde
size : 625205760
stride : 128
type : linear
status : ok
subsets: 0
devs : 4
spares : 0

But when I try to mount, I get the following error:

root@afs:/home/andrew# mount -t ntfs /dev/mapper/nvidia_ebdfedde /media/store
NTFS signature is missing.
Failed to mount '/dev/dm-2': Invalid argument
The device '/dev/dm-2' 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?

If I try to reactivate I get "ERROR: dos: partition address past end of RAID device":

root@afs:/dev/mapper# dmraid -ay -vvvv
WARN: locking /var/lock/dmraid/.lock
NOTICE: /dev/sde: asr discovering
NOTICE: /dev/sde: ddf1 discovering
NOTICE: /dev/sde: hpt37x discovering
NOTICE: /dev/sde: hpt45x discovering
NOTICE: /dev/sde: isw discovering
NOTICE: /dev/sde: jmicron discovering
NOTICE: /dev/sde: lsi discovering
NOTICE: /dev/sde: nvidia discovering
NOTICE: /dev/sde: nvidia metadata discovered
NOTICE: /dev/sde: pdc discovering
NOTICE: /dev/sde: sil discovering
NOTICE: /dev/sde: via discovering
NOTICE: /dev/sdc: asr discovering
NOTICE: /dev/sdc: ddf1 discovering
NOTICE: /dev/sdc: hpt37x discovering
NOTICE: /dev/sdc: hpt45x discovering
NOTICE: /dev/sdc: isw discovering
NOTICE: /dev/sdc: jmicron discovering
NOTICE: /dev/sdc: lsi discovering
NOTICE: /dev/sdc: nvidia discovering
NOTICE: /dev/sdc: nvidia metadata discovered
NOTICE: /dev/sdc: pdc discovering
NOTICE: /dev/sdc: sil discovering
NOTICE: /dev/sdc: via discovering
NOTICE: /dev/sdd: asr discovering
NOTICE: /dev/sdd: ddf1 discovering
NOTICE: /dev/sdd: hpt37x discovering
NOTICE: /dev/sdd: hpt45x discovering
NOTICE: /dev/sdd: isw discovering
NOTICE: /dev/sdd: jmicron discovering
NOTICE: /dev/sdd: lsi discovering
NOTICE: /dev/sdd: nvidia discovering
NOTICE: /dev/sdd: nvidia metadata discovered
NOTICE: /dev/sdd: pdc discovering
NOTICE: /dev/sdd: sil discovering
NOTICE: /dev/sdd: via discovering
NOTICE: /dev/sdb: asr discovering
NOTICE: /dev/sdb: ddf1 discovering
NOTICE: /dev/sdb: hpt37x discovering
NOTICE: /dev/sdb: hpt45x discovering
NOTICE: /dev/sdb: isw discovering
NOTICE: /dev/sdb: jmicron discovering
NOTICE: /dev/sdb: lsi discovering
NOTICE: /dev/sdb: nvidia discovering
NOTICE: /dev/sdb: nvidia metadata discovered
NOTICE: /dev/sdb: pdc discovering
NOTICE: /dev/sdb: sil discovering
NOTICE: /dev/sdb: via discovering
NOTICE: /dev/sda: asr discovering
NOTICE: /dev/sda: ddf1 discovering
NOTICE: /dev/sda: hpt37x discovering
NOTICE: /dev/sda: hpt45x discovering
NOTICE: /dev/sda: isw discovering
NOTICE: /dev/sda: jmicron discovering
NOTICE: /dev/sda: lsi discovering
NOTICE: /dev/sda: nvidia discovering
NOTICE: /dev/sda: pdc discovering
NOTICE: /dev/sda: sil discovering
NOTICE: /dev/sda: via discovering
NOTICE: added /dev/sde to RAID set "nvidia_ebdfedde"
NOTICE: added /dev/sdc to RAID set "nvidia_ebdfedde"
NOTICE: added /dev/sdd to RAID set "nvidia_ebdfedde"
NOTICE: added /dev/sdb to RAID set "nvidia_ebdfedde"
RAID set "nvidia_ebdfedde" already active
INFO: Activating linear raid set "nvidia_ebdfedde"
NOTICE: discovering partitions on "nvidia_ebdfedde"
NOTICE: /dev/mapper/nvidia_ebdfedde: dos discovering
NOTICE: /dev/mapper/nvidia_ebdfedde: dos metadata discovered
ERROR: dos: partition address past end of RAID device
NOTICE: created partitioned RAID set(s) for /dev/mapper/nvidia_ebdfedde
WARN: unlocking /var/lock/dmraid/.lock

Here's some general info about the NVRAID set:

root@afs:/home/andrew# fdisk -l /dev/mapper/nvidia_ebdfedde

Disk /dev/mapper/nvidia_ebdfedde: 1503.2 GB, 1503242620928 bytes
255 heads, 63 sectors/track, 182758 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: 0xde854eab

                      Device Boot Start End Blocks Id System
/dev/mapper/nvidia_ebdfedde1 * 1 182758 1468003603+ 42 SFS

More info:

root@afs:/home/andrew# dmraid -V
dmraid version: 1.0.0.rc16 (2009.09.16) shared
dmraid library version: 1.0.0.rc16 (2009.09.16)
device-mapper version: 4.17.0

root@afs:/home/andrew# lshw -C disk
  *-disk
       description: ATA Disk
       product: WDC WD400BB-32CJ
       vendor: Western Digital
       physical id: 0.0.0
       bus info: scsi@0:0.0.0
       logical name: /dev/sda
       version: 16.0
       serial: WD-WMAAE1103510
       size: 37GiB (40GB)
       capabilities: partitioned partitioned:dos
       configuration: ansiversion=5 signature=00086ebe
  *-disk:0
       description: ATA Disk
       product: WDC WD800JB-00CR
       vendor: Western Digital
       physical id: 0
       bus info: scsi@2:0.0.0
       logical name: /dev/sdb
       version: 17.0
       serial: WD-WMA8E2725523
       size: 74GiB (80GB)
       capabilities: partitioned partitioned:dos
       configuration: ansiversion=5 signature=de854eab
  *-disk:1
       description: ATA Disk
       product: ST3300822AS
       vendor: Seagate
       physical id: 1
       bus info: scsi@3:0.0.0
       logical name: /dev/sdc
       version: 3.AA
       serial: 3NF1DW2Q
       size: 279GiB (300GB)
       configuration: ansiversion=5
  *-disk:0
       description: ATA Disk
       product: Maxtor 6Y120P0
       vendor: Maxtor
       physical id: 0
       bus info: scsi@4:0.0.0
       logical name: /dev/sdd
       version: YAR4
       serial: Y36YR7QE
       size: 114GiB (122GB)
       configuration: ansiversion=5
  *-disk:1
       description: ATA Disk
       product: WDC WD10EARS-00Y
       vendor: Western Digital
       physical id: 1
       bus info: scsi@5:0.0.0
       logical name: /dev/sde
       version: 80.0
       serial: WD-WMAV51521205
       size: 931GiB (1TB)
       configuration: ansiversion=5

I thought this might be a similar error to the situation reported here: https://bugzilla.redhat.com/show_bug.cgi?id=500322
and here: http://www.linuxquestions.org/questions/linux-hardware-18/mounting-an-ntfs-raid-0-stripe-in-ubuntu-9-04-64-bit-769017/page2.html

I tried activating the partitions using kpartx, but no luck:

root@afs:/dev/mapper# kpartx -a nvidia_ebdfedde
root@afs:/dev/mapper# mount -t ntfs nvidia_ebdfedde1 /media/store
ntfs_mst_post_read_fixup: magic: 0x05e5b867 size: 1024 usa_ofs: 31245 usa_count: 14563: Invalid argument
ntfs_mst_post_read_fixup: magic: 0x82c832e9 size: 1024 usa_ofs: 36494 usa_count: 54383: Invalid argument
ntfs_mst_post_read_fixup: magic: 0x731526db size: 1024 usa_ofs: 5852 usa_count: 58242: Invalid argument
ntfs_mst_post_read_fixup: magic: 0x3fd96d0e size: 1024 usa_ofs: 29901 usa_count: 3777: Invalid argument
$MFTMirr error: Invalid mft record for '$MFT'.
Failed to mount '/dev/dm-4': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.

Any ideas how to resolve this issue?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu dmraid Edit question
Assignee:
No assignee Edit question
Solved by:
Phillip Susi
Solved:
Last query:
Last reply:
Revision history for this message
Andrew Phillips (theampersand) said :
#1

Here's the output of fdisk -l:

root@afs:/dev/mapper# fdisk -l

Disk /dev/sda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 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: 0x00086ebe

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 32 248832 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 32 4866 38831105 5 Extended
/dev/sda5 32 4866 38831104 8e Linux LVM

Disk /dev/dm-0: 38.1 GB, 38080086016 bytes
255 heads, 63 sectors/track, 4629 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: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 1681 MB, 1681915904 bytes
255 heads, 63 sectors/track, 204 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: 0x00000000

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 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: 0xde854eab

   Device Boot Start End Blocks Id System
/dev/sdb1 * 1 182758 1468003603+ 42 SFS

Disk /dev/sdd: 122.9 GB, 122942324736 bytes
255 heads, 63 sectors/track, 14946 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: 0x5cb1a05b

Disk /dev/sdd doesn't contain a valid partition table

Disk /dev/sdc: 300.1 GB, 300069052416 bytes
255 heads, 63 sectors/track, 36481 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: 0xe9e290ef

Disk /dev/sdc doesn't contain a valid partition table

Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 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: 0xf240f93f

Disk /dev/sde doesn't contain a valid partition table

Disk /dev/dm-2: 1503.2 GB, 1503242620928 bytes
255 heads, 63 sectors/track, 182758 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: 0xde854eab

     Device Boot Start End Blocks Id System
/dev/dm-2p1 * 1 182758 1468003603+ 42 SFS

Disk /dev/dm-3: 1503.2 GB, 1503242620928 bytes
255 heads, 63 sectors/track, 182758 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: 0x6ad4ebdb

Disk /dev/dm-3 doesn't contain a valid partition table

Disk /dev/dm-4: 1503.2 GB, 1503235689984 bytes
255 heads, 63 sectors/track, 182757 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: 0x69205244

This doesn't look like a partition table
Probably you selected the wrong device.

     Device Boot Start End Blocks Id System
/dev/dm-4p1 ? 13578 119522 850995205 72 Unknown
Partition 1 does not end on cylinder boundary.
/dev/dm-4p2 ? 45382 79243 271987362 74 Unknown
Partition 2 does not end on cylinder boundary.
/dev/dm-4p3 ? 10499 10499 0 65 Novell Netware 386
Partition 3 does not end on cylinder boundary.
/dev/dm-4p4 167628 167631 25817+ 0 Empty
Partition 4 does not end on cylinder boundary.

Partition table entries are not in disk order
root@afs:/dev/mapper#

Revision history for this message
Danny Wood (danwood76) said :
#2

Hi Andrew,

The mount command (according to the fdisk output) you need to use is:
mount -t ntfs /dev/mapper/nvidia_ebdfedde1 /media/store
Note the partition number in the above command!

If that doesnt work please post the output of ls /dev/mapper

Danny

On 27/01/11 19:23, Andrew Phillips wrote:
> New question #143098 on dmraid in ubuntu:
> https://answers.launchpad.net/ubuntu/+source/dmraid/+question/143098
>
> I have Ubuntu Server 10.10 installed on an Asus M2NPV-VM motherboard with four hard drives being combined in a JBOD. Originally, I had these installed on Windows Server 2003 and a single partititon (not sure if it was a primary or logical) created on this JBOD.
>
> It appears that the RAID set is already active:
>
> root@afs:/home/andrew# dmraid -s
> *** Active Set
> name : nvidia_ebdfedde
> size : 625205760
> stride : 128
> type : linear
> status : ok
> subsets: 0
> devs : 4
> spares : 0
>
> But when I try to mount, I get the following error:
>
> root@afs:/home/andrew# mount -t ntfs /dev/mapper/nvidia_ebdfedde /media/store
> NTFS signature is missing.
> Failed to mount '/dev/dm-2': Invalid argument
> The device '/dev/dm-2' 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?
>
> If I try to reactivate I get "ERROR: dos: partition address past end of RAID device":
>
> root@afs:/dev/mapper# dmraid -ay -vvvv
> WARN: locking /var/lock/dmraid/.lock
> NOTICE: /dev/sde: asr discovering
> NOTICE: /dev/sde: ddf1 discovering
> NOTICE: /dev/sde: hpt37x discovering
> NOTICE: /dev/sde: hpt45x discovering
> NOTICE: /dev/sde: isw discovering
> NOTICE: /dev/sde: jmicron discovering
> NOTICE: /dev/sde: lsi discovering
> NOTICE: /dev/sde: nvidia discovering
> NOTICE: /dev/sde: nvidia metadata discovered
> NOTICE: /dev/sde: pdc discovering
> NOTICE: /dev/sde: sil discovering
> NOTICE: /dev/sde: via discovering
> NOTICE: /dev/sdc: asr discovering
> NOTICE: /dev/sdc: ddf1 discovering
> NOTICE: /dev/sdc: hpt37x discovering
> NOTICE: /dev/sdc: hpt45x discovering
> NOTICE: /dev/sdc: isw discovering
> NOTICE: /dev/sdc: jmicron discovering
> NOTICE: /dev/sdc: lsi discovering
> NOTICE: /dev/sdc: nvidia discovering
> NOTICE: /dev/sdc: nvidia metadata discovered
> NOTICE: /dev/sdc: pdc discovering
> NOTICE: /dev/sdc: sil discovering
> NOTICE: /dev/sdc: via discovering
> NOTICE: /dev/sdd: asr discovering
> NOTICE: /dev/sdd: ddf1 discovering
> NOTICE: /dev/sdd: hpt37x discovering
> NOTICE: /dev/sdd: hpt45x discovering
> NOTICE: /dev/sdd: isw discovering
> NOTICE: /dev/sdd: jmicron discovering
> NOTICE: /dev/sdd: lsi discovering
> NOTICE: /dev/sdd: nvidia discovering
> NOTICE: /dev/sdd: nvidia metadata discovered
> NOTICE: /dev/sdd: pdc discovering
> NOTICE: /dev/sdd: sil discovering
> NOTICE: /dev/sdd: via discovering
> NOTICE: /dev/sdb: asr discovering
> NOTICE: /dev/sdb: ddf1 discovering
> NOTICE: /dev/sdb: hpt37x discovering
> NOTICE: /dev/sdb: hpt45x discovering
> NOTICE: /dev/sdb: isw discovering
> NOTICE: /dev/sdb: jmicron discovering
> NOTICE: /dev/sdb: lsi discovering
> NOTICE: /dev/sdb: nvidia discovering
> NOTICE: /dev/sdb: nvidia metadata discovered
> NOTICE: /dev/sdb: pdc discovering
> NOTICE: /dev/sdb: sil discovering
> NOTICE: /dev/sdb: via discovering
> NOTICE: /dev/sda: asr discovering
> NOTICE: /dev/sda: ddf1 discovering
> NOTICE: /dev/sda: hpt37x discovering
> NOTICE: /dev/sda: hpt45x discovering
> NOTICE: /dev/sda: isw discovering
> NOTICE: /dev/sda: jmicron discovering
> NOTICE: /dev/sda: lsi discovering
> NOTICE: /dev/sda: nvidia discovering
> NOTICE: /dev/sda: pdc discovering
> NOTICE: /dev/sda: sil discovering
> NOTICE: /dev/sda: via discovering
> NOTICE: added /dev/sde to RAID set "nvidia_ebdfedde"
> NOTICE: added /dev/sdc to RAID set "nvidia_ebdfedde"
> NOTICE: added /dev/sdd to RAID set "nvidia_ebdfedde"
> NOTICE: added /dev/sdb to RAID set "nvidia_ebdfedde"
> RAID set "nvidia_ebdfedde" already active
> INFO: Activating linear raid set "nvidia_ebdfedde"
> NOTICE: discovering partitions on "nvidia_ebdfedde"
> NOTICE: /dev/mapper/nvidia_ebdfedde: dos discovering
> NOTICE: /dev/mapper/nvidia_ebdfedde: dos metadata discovered
> ERROR: dos: partition address past end of RAID device
> NOTICE: created partitioned RAID set(s) for /dev/mapper/nvidia_ebdfedde
> WARN: unlocking /var/lock/dmraid/.lock
>
> Here's some general info about the NVRAID set:
>
> root@afs:/home/andrew# fdisk -l /dev/mapper/nvidia_ebdfedde
>
> Disk /dev/mapper/nvidia_ebdfedde: 1503.2 GB, 1503242620928 bytes
> 255 heads, 63 sectors/track, 182758 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: 0xde854eab
>
> Device Boot Start End Blocks Id System
> /dev/mapper/nvidia_ebdfedde1 * 1 182758 1468003603+ 42 SFS
>
> More info:
>
> root@afs:/home/andrew# dmraid -V
> dmraid version: 1.0.0.rc16 (2009.09.16) shared
> dmraid library version: 1.0.0.rc16 (2009.09.16)
> device-mapper version: 4.17.0
>
> root@afs:/home/andrew# lshw -C disk
> *-disk
> description: ATA Disk
> product: WDC WD400BB-32CJ
> vendor: Western Digital
> physical id: 0.0.0
> bus info: scsi@0:0.0.0
> logical name: /dev/sda
> version: 16.0
> serial: WD-WMAAE1103510
> size: 37GiB (40GB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=00086ebe
> *-disk:0
> description: ATA Disk
> product: WDC WD800JB-00CR
> vendor: Western Digital
> physical id: 0
> bus info: scsi@2:0.0.0
> logical name: /dev/sdb
> version: 17.0
> serial: WD-WMA8E2725523
> size: 74GiB (80GB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 signature=de854eab
> *-disk:1
> description: ATA Disk
> product: ST3300822AS
> vendor: Seagate
> physical id: 1
> bus info: scsi@3:0.0.0
> logical name: /dev/sdc
> version: 3.AA
> serial: 3NF1DW2Q
> size: 279GiB (300GB)
> configuration: ansiversion=5
> *-disk:0
> description: ATA Disk
> product: Maxtor 6Y120P0
> vendor: Maxtor
> physical id: 0
> bus info: scsi@4:0.0.0
> logical name: /dev/sdd
> version: YAR4
> serial: Y36YR7QE
> size: 114GiB (122GB)
> configuration: ansiversion=5
> *-disk:1
> description: ATA Disk
> product: WDC WD10EARS-00Y
> vendor: Western Digital
> physical id: 1
> bus info: scsi@5:0.0.0
> logical name: /dev/sde
> version: 80.0
> serial: WD-WMAV51521205
> size: 931GiB (1TB)
> configuration: ansiversion=5
>
> I thought this might be a similar error to the situation reported here: https://bugzilla.redhat.com/show_bug.cgi?id=500322
> and here: http://www.linuxquestions.org/questions/linux-hardware-18/mounting-an-ntfs-raid-0-stripe-in-ubuntu-9-04-64-bit-769017/page2.html
>
> I tried activating the partitions using kpartx, but no luck:
>
> root@afs:/dev/mapper# kpartx -a nvidia_ebdfedde
> root@afs:/dev/mapper# mount -t ntfs nvidia_ebdfedde1 /media/store
> ntfs_mst_post_read_fixup: magic: 0x05e5b867 size: 1024 usa_ofs: 31245 usa_count: 14563: Invalid argument
> ntfs_mst_post_read_fixup: magic: 0x82c832e9 size: 1024 usa_ofs: 36494 usa_count: 54383: Invalid argument
> ntfs_mst_post_read_fixup: magic: 0x731526db size: 1024 usa_ofs: 5852 usa_count: 58242: Invalid argument
> ntfs_mst_post_read_fixup: magic: 0x3fd96d0e size: 1024 usa_ofs: 29901 usa_count: 3777: Invalid argument
> $MFTMirr error: Invalid mft record for '$MFT'.
> Failed to mount '/dev/dm-4': Input/output error
> NTFS is either inconsistent, or there is a hardware fault, or it's a
> SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
> then reboot into Windows twice. The usage of the /f parameter is very
> important! If the device is a SoftRAID/FakeRAID then first activate
> it and mount a different device under the /dev/mapper/ directory, (e.g.
> /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
> for more details.
>
>
> Any ideas how to resolve this issue?
>

Revision history for this message
Andrew Phillips (theampersand) said :
#3

Thanks for your response Danny. I've tried using the mount -t ntfs /dev/mapper/nvidia_ebdfedde1 /media/store command. Please look at the bottom of my OP to see its output. /dev/mapper/nvidia_ebdfedde1 was created after I ran kpartx -a nvidia_ebdfedde.

Here's the output of ls /dev/mapper:

root@afs:/dev/mapper# ls
afs-root afs-swap_1 control cryptswap1 nvidia_ebdfedde nvidia_ebdfedde1

Revision history for this message
Best Phillip Susi (psusi) said :
#4

From the SFS type in the partition table, it looks like you have a dynamic disk, which is Windows only.

Revision history for this message
Andrew Phillips (theampersand) said :
#5

Thanks Phillip Susi, that solved my question.