Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a system hdd

then two raid1 hard drives

I see that sda1 is the system drive

but when i do a fdisk -l I get the following results

so which of the following do i need to mount to get the "raid" drive and not the individual hdd?

root@Mxxxx-PDC:/etc/samba# fdisk -l

Disk /dev/sda: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000762dc

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       30328   243609628+  83  Linux
/dev/sda2           30329       30515     1502077+   5  Extended
/dev/sda5           30329       30515     1502046   82  Linux swap / Solaris

Disk /dev/sdb: 400.0 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       48641   390708801   83  Linux

Disk /dev/sdc: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0009f4b2

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1         255     2048256   fd  Linux raid autodetect
/dev/sdc2             256       30401   242147745   fd  Linux raid autodetect

Disk /dev/sdd: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000b7f4c

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1   *           1         255     2048256   fd  Linux raid autodetect
/dev/sdd2             256       30401   242147745   fd  Linux raid autodetect
share|improve this question

3 Answers 3

e) None of the above

You want one of the /dev/md* or /dev/mapper/* entries instead.

share|improve this answer
    
Kudos for making me laugh. –  Chris S Jun 17 '10 at 18:49
    
+1 for the idea –  Crash893 Jun 17 '10 at 19:42
    
as for your comment below. I dont have these entries when i do a search what do you suggest –  Crash893 Jun 24 '10 at 21:29

You can cat /proc/mdstat to identify the md device, which is what you will want to mount.

share|improve this answer
    
i have a proc dir but no mdstat –  Crash893 Jun 17 '10 at 19:09
    
Do you have software RAID compiled in the kernel or modules loaded? Is there data on this RAID, was it ever actually created or are they simply partitions? –  Warner Jun 17 '10 at 19:25
    
Who knows. I got this box as part of my new job . I went a head and mounted sdb1 and it seems to be working fine –  Crash893 Jun 17 '10 at 19:31
1  
It will work but now your RAID is effectively broken. Any changes made to the data have the potential to be lost upon rebuild if you accessed as a RAID. –  Warner Jun 17 '10 at 19:42
1  
@Crash893 by mounting sdb1, you are mounting one of the individual hard disks instead of the RAID drive. –  Phil Ross Jun 17 '10 at 20:20
up vote 0 down vote accepted

may not have done this right but i just mounted sdb1 and it seems fine

share|improve this answer
3  
That is a separate 400GB partition, and not the RAID array. –  Ignacio Vazquez-Abrams Jun 17 '10 at 20:17

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.