Actually windows is seeing the raid as 1 HD 240 Gigs C 25 Gigs and D 200 and 15 Gigs unknown format (Linux EXT3)
|
I am guessing you have either enbedded or hardware raid, If that is the case then that won't matter since fedora will need to be able to read that for it's only partitions anyways. I am assuming c: is sda1 and d: is sda2, do you have the same problem mounting sda1 as you do sda2? also can you confirm that c: and d: aren't mirroring each other or raided in any form to each other?
|
yes same problem with sda1 and nop they are not mirroring each other as this is Raid 0 not 1
|
But are they connected to each other in a raid 0 or not? I should not think so since they look to be different sizes... but worth checking. I do not know why you can't seem to mount these, their shouldn't be any reason you can't since the raid drivers must be installed in fedora for fedora to even work...
|
sure they are connected to each other.sda1 is the C and sda2 is the D.as i said before 2 SATA HD each one is 120 Gigs,connected as Raid 0 through the Mother Board and Operating Systems see the both HD as 1 240 Gigs HD.
|
1 Attachment(s)
Here is the fdisk -l
|
now you can see the C NTFS=25 Gigs,D NTFS=200 Gigs, Boot=88 Mega ,Ext3 Linux=12 Gigs
|
That seems strange, it should not see sda and sdb as seperate if they are raided on a hardware or embedded level. I dunno what to suggest now =/.
|
:( :(
|
According to the fdisk output, you have two 120Gb drives (sda and sdb) connected to your system. One of those (sda) contains three partitions, and an invalid partition table; the other (sdb) has no partitions on it.
I suspect that both the "invalid partition table" and the "empty partition table" are artifacts of the hardware hardware RAID controller you're using. I also suspect that the problem occurs because you're using an inappropriate device driver in your Fedora system which is not correctly accessing the RAID controller. Have you looked for appropriate Linux hardware drivers that you could add to your Linux system? Note that GRUB may not be able to boot from a hardware RAID configuration, so you may need to boot from GRUB on a USB memory stick or similar device, and you'll probably need to create an Initial RAM Disk Image linking in the correct driver. The Fedora 10 Installation Guide remarks: Quote:
Since you are not seeing a single drive, clearly -- as you've told us -- your systems not working correctly. |
Silly question: Did you try just
$mount windows who knows, you may get lucky. EDIT: You ever post thinking it's stil on the first page, and all this fun stuff hasn't happened? Yeah. |
1st i am thanking all of you for such support,but if my system not working correctly then how my fedora installed without any problems and i got a normal dual boot for Fedora and windows?and if this is the problem and i delete fedora from this RAID and i installed it on other IDE HD then i will got same problem,so it must something here make the fedora see 2 HD (physically) as a 1 Big HD 240 Gigs(RAID).
|
$ mount windows...no such command do something but thanks for this and yeah sometimes very small far awy things works and solve big problems,but here didn't work :)
|
If you want your NTFS drives automatically mounted when your Fedora system is booted, you can add the mounting instructions to /etc/fstab. Here, for example, are the NTFS mount lines from this laptop's Fedora /etc/fstab:
Code:
UUID=342D7D7923AC4107 /Vista ntfs-3g rw,defaults 0 0 |
1 Attachment(s)
actually when i did that i didnt found anything by-uuid ,i only found by-id and by-patch.and here is the output of both.
|
All times are GMT -5. The time now is 03:45 AM. |