[SOLVED] Mounting an NTFS RAID-0 stripe in Ubuntu 9.04 64 bit
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Mounting an NTFS RAID-0 stripe in Ubuntu 9.04 64 bit
Hi, so I have Windows installed and set up a RAID stripe a while back. I've got all my data there and I would like to access it via Ubuntu, mainly because I'd like to share it on my network (and not have to cut everyone in my house off) while I'm in Ubuntu. Both OS's are installed on separate disks.
I can't get the drive to mount. I keep getting this
"NTFS signature is missing.
Failed to mount '/dev/mapper/nvidia_facfcied': Invalid argument
The device '/dev/mapper/nvidia_facfcied' 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?"
Here are the steps I've taken (I already created the mount point /media/Z):
Code:
ziyad@DesktopzUbuntu:~$ sudo fdisk -l
Disk /dev/sda: 150.0 GB, 150039945216 bytes
255 heads, 63 sectors/track, 18241 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xf9fe0643
Device Boot Start End Blocks Id System
/dev/sda1 * 1 18242 146521088 7 HPFS/NTFS
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
256 heads, 63 sectors/track, 121126 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 266306 2147483647+ ee GPT
Disk /dev/sdc: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000df395
Device Boot Start End Blocks Id System
/dev/sdc1 1 7460 59922418+ 83 Linux
/dev/sdc2 7461 7783 2594497+ 5 Extended
/dev/sdc5 7461 7783 2594466 82 Linux swap / Solaris
WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdd1 1 121602 976762583+ ee GPT
Disk /dev/sde: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xffa2f4e7
Device Boot Start End Blocks Id System
/dev/sde1 1 243202 1953512448 7 HPFS/NTFS
ziyad@DesktopzUbuntu:~$ sudo lspci | grep -i raid
00:0e.0 RAID bus controller: nVidia Corporation MCP55 SATA Controller (rev a2)
00:0e.1 RAID bus controller: nVidia Corporation MCP55 SATA Controller (rev a2)
00:0e.2 RAID bus controller: nVidia Corporation MCP55 SATA Controller (rev a2)
ziyad@DesktopzUbuntu:~$ sudo dmraid -r
/dev/sdd: nvidia, "nvidia_facfcied", stripe, ok, 1953525166 sectors, data@ 0
/dev/sdb: nvidia, "nvidia_facfcied", stripe, ok, 1953525166 sectors, data@ 0
ziyad@DesktopzUbuntu:~$ sudo dmraid -ay -v
RAID set "nvidia_facfcied" already active
INFO: Activating stripe raid set "nvidia_facfcied"
ziyad@DesktopzUbuntu:~$ sudo mount -t ntfs-3g /dev/mapper/nvidia_facfcied /media/Z
NTFS signature is missing.
Failed to mount '/dev/mapper/nvidia_facfcied': Invalid argument
The device '/dev/mapper/nvidia_facfcied' 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?
The drives I've highlighted are the ones that make up the RAID. The only thing that I can see is that Linux is not recognizing which drives make up that RAID...? Theres no mention anywhere that /dev/sdd and /dev/sdb form /dev/mapper/nvidia_facfcied.
Anyway, if anyone can help in anyway I'd really appreciate it. And honestly, I have the RAID backed up so I'm really willing to try anything at this point (short of formatting it because that wouldn't solve why its doing this in the first place).
Maybe you need to change this to the following (note the "1")
sudo mount -t ntfs-3g /dev/mapper/nvidia_facfcied1 /media/Z
If that doesn't work could you list the output of ls /dev/mapper?
BTW I take it you're using Vista or 7 given the GPT disk label...
Maybe you need to change this to the following (note the "1")
sudo mount -t ntfs-3g /dev/mapper/nvidia_facfcied1 /media/Z
If that doesn't work could you list the output of ls /dev/mapper?
BTW I take it you're using Vista or 7 given the GPT disk label...
Hi thanks for the reply! You're right I'm using Vista (sorry for not mentioning), I actually plan on installing 7 soon, I've already bought it just want to figure this out first. And nope, I've already tried adding the 1. This is the output
Code:
ziyad@DesktopzUbuntu:~$ sudo mount -t ntfs-3g /dev/mapper/nvidia_facfcied1 /media/Z
ntfs-3g: Failed to access volume '/dev/mapper/nvidia_facfcied1': No such file or directory
Please type '/sbin/mount.ntfs-3g --help' for more information.
Heres is output of /dev/mapper
Code:
ziyad@DesktopzUbuntu:~$ ls /dev/mapper
control nvidia_facfcied
I'm really stumped... I'm about to try running live cd's of other distros to see if they mount the RAID, I'll let you know if that works.
What's interesting is that there are no partitions visible in your raid set, which maybe is normal for GPT; I don't know much about it as I'm still strictly 32-bit.
But maybe dmraid is only seeing the so-called protective mbr part of the disklabel. I suppose you could see if you have the latest version of dmraid or whether upgrading that makes any difference. I think 9.04 has rc15 and that you might need rc16.
Last edited by mostlyharmless; 11-14-2009 at 08:59 PM.
What's interesting is that there are no partitions visible in your raid set, which maybe is normal for GPT; I don't know much about it as I'm still strictly 32-bit.
But maybe dmraid is only seeing the so-called protective mbr part of the disklabel. I suppose you could see if you have the latest version of dmraid or whether upgrading that makes any difference. I think 9.04 has rc15 and that you might need rc16.
I'm not sure what you mean by no visible partitions? Is there supposed to be something else in my /dev/mapper folder? The thing is, with mount manager it shows that the two drives are RAID members. I've attached a screen shot.
I have the rc15 version of dmraid, how do I upgrade it? When I go to Synaptics it doesn't allow me to mark for upgrade.
In Linux a storage devices that are going to be mounted have to be mounted based on the partition of the raw device. Mounting a raw device like /dev/sda can not be done. You have state the partition number after the raw device. The raw device is also stated as a device node. Your device node /dev/mapper/nvidia_facfcied is just a raw device. You will need a partition number like /dev/mapper/nvidia_facfcied1. If this is not shown, there could be an incompatible data buried in the RAID array. From what I read from the Internet, if there is space for your label, this can cause a problem. Disk labels with spaces are not valid. Try comply to DOS labels if you can. This means create a label with no more than eleven (11) characters. It is best to start out with a letter if you can.
The device mapper for RAID in Linux does not support all software RAID controllers and the reliability and stability is not good. It is best to not use this type of software RAID and go with hardware RAID. You can do this cheap with out adding software by using a hardware port multiplier from Addonics like the following.
Do not get the 5 port version because I do not think is not as fast and not compatible with Linux and your controller.
I do not recommend using NTFS if you are switching between Windows and Linux. FAT is better if you are switching between the two. If you need support for than 4 GB of file storage, use EXT2 or EXT3. There is EXT2 IFS that gives EXT2 support to Windows. Since EXT2 is known to the open source community very, very well compared to NTFS, so the chances of data corruption is much lower than using something like ntfs-3g to access NTFS. Nobody will ever know the difference except you will.
If the software RAID array is where Windows is stored, I strongly recommend do not access it in Linux with device mapper and with ntfs-3g. If you are going to use WINE to run Windows programs, it will hurt your Windows installation. Just do not attempt.
From what I read from the Internet, if there is space for your label, this can cause a problem. Disk labels with spaces are not valid. Try comply to DOS labels if you can. This means create a label with no more than eleven (11) characters. It is best to start out with a letter if you can.
I have named the volume "Media" on Windows, so it definitely complies with the naming convention. It can't be that.
Quote:
Originally Posted by Electro
The device mapper for RAID in Linux does not support all software RAID controllers and the reliability and stability is not good. It is best to not use this type of software RAID and go with hardware RAID. You can do this cheap with out adding software by using a hardware port multiplier from Addonics like the following.
I'm using my motherboards RAID controller, its not a software RAID. My motherboard is a NVIDIA 680i SLI.
Quote:
Originally Posted by Electro
If you need support for than 4 GB of file storage, use EXT2 or EXT3. There is EXT2 IFS that gives EXT2 support to Windows. Since EXT2 is known to the open source community very, very well compared to NTFS, so the chances of data corruption is much lower than using something like ntfs-3g to access NTFS. Nobody will ever know the difference except you will.
I may just have to do that, but I don't want to resort to it yet, I'd really like to solve this problem.
I'm not sure what you mean by no visible partitions? Is there supposed to be something else in my /dev/mapper folder? The thing is, with mount manager it shows that the two drives are RAID members. I've attached a screen shot.
Well, when one mounts a raid set on dev/mapper/gaghajgkghwhatever and that raid set has an mbr instead of gpt, then usually the disk volumes/partitions show up in /dev/mapper as /dev/mapper/gadghdfgjhwhatever1 and 2. You HAVE to have at least one partition on an mbr disk, I presume it's the same for gpt.
Quote:
I have the rc15 version of dmraid, how do I upgrade it? When I go to Synaptics it doesn't allow me to mark for upgrade.
If the software RAID array is where Windows is stored, I strongly recommend do not access it in Linux with device mapper and with ntfs-3g.
Well, it really it works quite well and I've never had a problem, but to each is own, and I can't really argue with your advice, but that's not what the OP is looking for yet.
Quote:
If you are going to use WINE to run Windows programs, it will hurt your Windows installation. Just do not attempt.
I don't think he was going to do that, just wanted to serve up the array. Wine apps need their own install, I agree.
Well, when one mounts a raid set on dev/mapper/gaghajgkghwhatever and that raid set has an mbr instead of gpt, then usually the disk volumes/partitions show up in /dev/mapper as /dev/mapper/gadghdfgjhwhatever1 and 2. You HAVE to have at least one partition on an mbr disk, I presume it's the same for gpt.
That makes sense, but I don't know for sure this is my first time using Linux and in windows it shows up as one volume/partition... One thing I want to remind is that this array has NO operating systems, its strictly a media share.
"GPT stores all partitions in a single partition table (with backup), so there's no need for extended or logical partitions. By default, 128 partitions are supported, although you can change the partition table size if the partitioning software supports such changes."
Quote:
Originally Posted by mostlyharmless
I don't think he was going to do that, just wanted to serve up the array. Wine apps need their own install, I agree.
In regards to WINE, I'm not even sure what you mean. You're right, all I want to do is serve the array, I don't wish to install anything on it, or run anything from it. Like I said, Windows is not installed on this array, its strictly a media serving partition.
I'm going to install dmraid rc16 and see what happens. If that doesn't work I just found an article here that may be useful. I'll post back with my results, thanks guys for all your help really!! I've been searching left and right for a solution, hopefully we can figure it out
By the way I ran fdisk on the RAID and this is the results:
Code:
ziyad@DesktopzUbuntu:~$ sudo fdisk /dev/mapper/nvidia_facfcied
WARNING: GPT (GUID Partition Table) detected on '/dev/mapper/nvidia_facfcied'! The util fdisk doesn't support GPT. Use GNU Parted.
The number of cylinders for this disk is set to 242252.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Not sure if this is useful or not, but I just installed Gparted and it recognizes the /dev/mapper/nvidia_facfcied partition :-) I think thats good news?
UPDATE:
ACTUALLY VERY GOOD NEWS... when I opened up Gparted, it like I said it shows /dev/mapper/nvidia_facfcied partition, but when I click on it, it shows (see attachment photo) two partition! However, i still ran into problems mounting, here are my results:
Code:
ziyad@DesktopzUbuntu:~$ sudo mount -t ntfs-3g /dev/mapper/nvidia_facfcied2 /media/Z
ntfs-3g: Failed to access volume '/dev/mapper/nvidia_facfcied2': No such file or directory
Please type '/sbin/mount.ntfs-3g --help' for more information.
I believe the problem here is GPT. I have once tried to use an Ubuntu LiveCD. (not sure which version) to mount a GPT partitioned disk. I found that the kernel that shipped with Ubuntu did not have GPT support compiled in at all. The symptom is exactly like yours, the device node for the raw disk was created, but not for the GPT partitions.
I gave up at this point & used my CentOS system instead which worked fine. I do remember reading somewhere that I could use the Ubuntu server kernel. (it was some time ago, so check this out first)
BTW, don't ever interact with GPT partitions using fdisk. You should only use parted when it comes to GPT.
I'm using my motherboards RAID controller, its not a software RAID. My motherboard is a NVIDIA 680i SLI.
BTW, just wanted to clarify this point of why people call this software raid. A raid controller is considered hardware only if there is a physical dedicated controller chip performing all RAID operations in hardware without using the PCs CPU for anything.
Most motherboard RAID controllers are actually controllerless, and they implement RAID in software, using a software interface in the BIOS, drivers in the OS and the CPU to perform the RAID operations. They seem to function like hardware RAID (by having a BIOS interface) but is in fact software RAID. Some like to call this "BIOS RAID" or "quasi-hardware RAID" but they are a form of software RAID where some parts of the interface are embeded in the hardware.
Sorry about that, just had to get that off my chest.
BTW, just wanted to clarify this point of why people call this software raid. A raid controller is considered hardware only if there is a physical dedicated controller chip performing all RAID operations in hardware without using the PCs CPU for anything.
Most motherboard RAID controllers are actually controllerless, and they implement RAID in software, using a software interface in the BIOS, drivers in the OS and the CPU to perform the RAID operations. They seem to function like hardware RAID (by having a BIOS interface) but is in fact software RAID. Some like to call this "BIOS RAID" or "quasi-hardware RAID" but they are a form of software RAID where some parts of the interface are embeded in the hardware.
Sorry about that, just had to get that off my chest.
Thanks for clearing that up
So I guess I'm not going to have any luck mounting this thing then
So I guess I'm not going to have any luck mounting this thing then
Don't give up yet.
Quote:
when I opened up Gparted, it like I said it shows /dev/mapper/nvidia_facfcied partition, but when I click on it, it shows (see attachment photo) two partition!
Well, this is good, you do need to mount partition 2 using mount, but the device hasn't been made yet by dmraid, which is why you need dmraid rc16, which I *think* supports GPT.
Opening up /dev/mapper/aghajkhgdwhatever with gparted doesn't create the /dev/mapper/ghadkghlksdhwhatever2, and as the message says, fdisk doesn't support GPT, but that doesn't matter, you don't neeed fdisk as long as the kernel is compiled to support GPT.
I'm pretty sure GPT/EFID is compiled into Ubuntu 9.04 c64 bit, so that isn't a worry, though clearly it would have been with the older ubuntu liveCD.
Last edited by mostlyharmless; 11-16-2009 at 09:54 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.