dmraid & mkinitrd under F10 x86_64 (No Puppies Harmed)

[Raymond C. Rodgers]

Robert L Cochran wrote:
> And the output of `ls /dev/mapper`
>
>
>
> Charles Crayne wrote:
>   
>> On Mon, 15 Dec 2008 22:09:44 -0500
>> "Raymond C. Rodgers" <sinful622 at gmail.com> wrote:
>>
>>   
>>     
>>> From what I've seen, this can be done through initrd/mkinitrd some
>>> how,
>>>     
>>>       
>> Apparently, I don't understand what you are trying to do. I am running
>> software raid on three i386 machines and one x86_64 machine, and I have
>> never needed any magic.
>>
>> Perhaps if you posted your fstab, and the output of parted -l, I would
>> understand your problem well enough to offer some useful advice.
>>
>>   
>>     
>
>   
*fstab:*
UUID=b601345c-1a2f-464a-ab3d-9a25d528df8d /                       
ext3    defaults        1 1
UUID=9f0b2cc8-7c0e-49f6-8366-483af19fca89 /boot                   
ext3    defaults        1 2
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
UUID=d4c09963-7244-413b-9d85-26ad476b66d6 swap                    
swap    defaults        0 0
/dev/VolGroup00/LogVol01 swap                    swap    defaults        0 0
/dev/sdc1        /media/prime        ntfs-3g    defaults    0 0
/dev/mapper/nvidia_gdedfbbjp5 /media/safehouse    ntfs-3g    defaults    0 0
//192.168.0.107/share    /media/linkstation    cifs    
users,gid=users,file_mode=0666,dir_mode=0777    0 0
//192.168.0.107/sharedmedia    /media/linkstation_media    cifs    
users,gid=users,file_mode=0666,dir_mode=0777    0 0

*/dev/mapper before activating dmraid manually:*
[root at localhost etc]# ls -l /dev/mapper/
total 0
crw-rw---- 1 root root  10, 63 2008-12-16 03:31 control
brw-rw---- 1 root disk 253,  0 2008-12-16 08:31 VolGroup00-LogVol00
brw-rw---- 1 root disk 253,  1 2008-12-16 03:31 VolGroup00-LogVol01

*/dev/mapper after activating dmraid manually (with the command line 
I've been using since installing F10)*
[root at localhost etc]# dmraid -a yes  nvidia_gdedfbbj
RAID set "nvidia_gdedfbbj" was activated
RAID set "nvidia_gdedfbbjp2" was activated
RAID set "nvidia_gdedfbbjp5" was activated
[root at localhost etc]# ls -l /dev/mapper/
total 0
crw-rw---- 1 root root  10, 63 2008-12-16 03:31 control
brw-rw---- 1 root disk 253,  2 2008-12-16 11:16 nvidia_gdedfbbj
brw-rw---- 1 root disk 253,  3 2008-12-16 11:16 nvidia_gdedfbbjp2
brw-rw---- 1 root disk 253,  4 2008-12-16 11:16 nvidia_gdedfbbjp5
brw-rw---- 1 root disk 253,  0 2008-12-16 08:31 VolGroup00-LogVol00
brw-rw---- 1 root disk 253,  1 2008-12-16 03:31 VolGroup00-LogVol01


The goal is to get dmraid activated automatically on boot like it once 
was, and not need to manually activate it and mount the 
nvidia_gdedfbbjp5 partition. As you might notice from the fstab, the 
individual partitions that make up nvidia_gdedfbbjp5 are not listed in 
the fstab file, yet Fedora is mounting them automatically everytime I 
boot. From what I learned in the past, that may be related to how the 
F10 installer saw the machine configured during installation, it decided 
to build an initrd with them mounted individually. From what I recall 
from F8 or F9, I had to use mkinitrd with dmraid activated and the 
nvidia_gdedfbbjp5 device mounted to get it to behave the same way; there 
was no need to modify /etc/fstab. But I have not been able to duplicate 
that, nor have I been able to find the instructions that I used previously.

Raymond
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20081216/0924eecc/attachment-0001.htm>