Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I have had a similar problem with attempting to build Fedora 10 on a Dell PowerEdge with a hardware RAID configuration. I installed Fedora 10 using a complete install (not an upgrade) and initialized the partitions completely. It appears to build correctly from the Fedora 10 DVD. However, after the end of the installation, the system reboot will give the error message
Volume Group "VolGroup00" not found
Unable to access remote device (/dev/VolGroup00/LogVol01)
mount error mounting /dev/root on /sysroot as ext3: no such file or directory
At this point, it locks up and I cannot even get into grub.
The problem seems similar and may point to the difficulty here as well. Fedora 7 and Fedora9 both install and boot properly. Does anyone know why Fedora 10 would no longer build?
Your sda and sdb are raid0 together. The second disk in a firmware raid0 set gets reported as having no partition table by fdisk, which is what you see. The first disk has the table for both, but the numbers may appear screwy. Don't worry about it, just don't mess with the partition table at this point.
Your raid is firmware raid or "fakeraid". It has already been setup by dmraid as listed by you:
Quote:
control via_cgddjifhah via_cgddjifhahp1 via_cgddjifhahp2 via_cgddjifhahp3 via_cgddjifhahp4 via_cgddjifhahp5 via_cgddjifhahp6
which shows that you have a via Raid controller. Typing dmraid -s will show you the raid set.
As Quakeboy02 pointed out, you need merely mount the appropriate partitions such as /dev/mapper/via_cgddjifhahp1 using mount and the ntfs or ntfs-3g filesystem. eg.
Quote:
mount -t ntfs /dev/mapper/via_cgddjifhahp1 /mnt
Sabba Hillel: you have a different problem and probably need your own thread.
Last edited by mostlyharmless; 03-02-2009 at 02:51 PM.
mostlyharmless....you did it man,actually I did this before (not me,but a friend works in our data centre but he didn't told me how he did it.)now i did the last command you said and i can see my windows files.thanks a lot.
where the numbers after the UUID= can be found in the output of ls -l /dev/disk/by-uuid/
Note that the mount point names are almost completely arbitrary, and can by in any directory you want to place them. I like to mount hard drives directly under / with name that start with an upper-case letter, but that's not a standard *nix convention. As mostelyharmless has suggested, the "conventional" mount point is a directory created under /mnt. (Although one way to read his suggestion is to mount the drive on /mnt which would preclude mounting more than one drive.) Bottom line: Where you decide to mount your NTFS drives is entirely up to you.
Last edited by PTrenholme; 07-27-2009 at 03:33 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.