Re: dmraid mkinitrd under F10 x86_64 (No Puppies Harmed)

2008-12-16 Thread 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 sinful...@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 /   
ext3defaults1 1
UUID=9f0b2cc8-7c0e-49f6-8366-483af19fca89 /boot   
ext3defaults1 2

tmpfs   /dev/shmtmpfs   defaults0 0
devpts  /dev/ptsdevpts  gid=5,mode=620  0 0
sysfs   /syssysfs   defaults0 0
proc/proc   procdefaults0 0
UUID=d4c09963-7244-413b-9d85-26ad476b66d6 swap
swapdefaults0 0

/dev/VolGroup00/LogVol01 swapswapdefaults0 0
/dev/sdc1/media/primentfs-3gdefaults0 0
/dev/mapper/nvidia_gdedfbbjp5 /media/safehousentfs-3gdefaults0 0
//192.168.0.107/share/media/linkstationcifs
users,gid=users,file_mode=0666,dir_mode=07770 0
//192.168.0.107/sharedmedia/media/linkstation_mediacifs
users,gid=users,file_mode=0666,dir_mode=07770 0


*/dev/mapper before activating dmraid manually:*
[r...@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)*

[r...@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
[r...@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
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: dmraid mkinitrd under F10 x86_64 (No Puppies Harmed)

2008-12-16 Thread Robert L Cochran


Raymond C. Rodgers wrote:
 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 sinful...@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 /  
 ext3defaults1 1
 UUID=9f0b2cc8-7c0e-49f6-8366-483af19fca89 /boot  
 ext3defaults1 2
 tmpfs   /dev/shmtmpfs  
 defaults0 0
 devpts  /dev/ptsdevpts 
 gid=5,mode=620  0 0
 sysfs   /syssysfs  
 defaults0 0
 proc/proc   proc   
 defaults0 0
 UUID=d4c09963-7244-413b-9d85-26ad476b66d6 swap   
 swapdefaults0 0
 /dev/VolGroup00/LogVol01 swapswap   
 defaults0 0
 /dev/sdc1/media/primentfs-3gdefaults0 0
 /dev/mapper/nvidia_gdedfbbjp5 /media/safehousentfs-3g   
 defaults0 0
 //192.168.0.107/share/media/linkstationcifs   
 users,gid=users,file_mode=0666,dir_mode=07770 0
 //192.168.0.107/sharedmedia/media/linkstation_mediacifs   
 users,gid=users,file_mode=0666,dir_mode=07770 0

 */dev/mapper before activating dmraid manually:*
 [r...@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)*
 [r...@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
 [r...@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

I'm too tired tonight to study this carefully, but tomorrow night I
will. I might not have anything helpful to say though.

Bob

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: dmraid mkinitrd under F10 x86_64 (No Puppies Harmed)

2008-12-16 Thread Charles Crayne
On Tue, 16 Dec 2008 11:25:59 -0500
Raymond C. Rodgers sinful...@gmail.com wrote:

 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.

With the info you provided, I think that I now understand what you are
trying to do. However, in order to understand why it isn't working, I
would still like to see the output from parted -l.

-- 
Chuck 
http://www.pacificsites.com/~ccrayne/charles.html

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: dmraid mkinitrd under F10 x86_64 (No Puppies Harmed)

2008-12-15 Thread Raymond C. Rodgers

Raymond C. Rodgers wrote:

Robert L Cochran wrote:

http://ubuntuforums.org/showthread.php?t=526151


 
I already have it in /etc/fstab, but /dev/mapper/ device isn't getting 
created at boot, and so F10 just goes on and auto-mounts the 
individual drives as separate devices instead of jointly as a dmraid 
device.



Raymond

No other suggestions?

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: dmraid mkinitrd under F10 x86_64 (No Puppies Harmed)

2008-12-15 Thread Charles Crayne
On Mon, 15 Dec 2008 16:05:17 -0500
Raymond C. Rodgers sinful...@gmail.com wrote:

 No other suggestions?

Although I have used software raid for several years now, I am not an
expert in the subject. In particular, I have never needed to use
mkinitrd, because I do not boot from the raid device. Nor have I used
the dmraid program because, on the few occasions where I have had to
invervene with the process, I have used mdadm. However, since none of
the other responses have been useful, perhaps something in my own
experience might help.

I do not have any of the raid partitions in my fstab,
nor do I have /dev/mapper. What I do have is /dev/md0. The individual
partitions have the raid flag turned on in the partition table, and the
kernel creates the md0 device, which is then mounted as specified in
fstab.

-- 
Chuck 
http://www.pacificsites.com/~ccrayne/charles.html

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: dmraid mkinitrd under F10 x86_64 (No Puppies Harmed)

2008-12-15 Thread Robert L Cochran


Charles Crayne wrote:
 On Mon, 15 Dec 2008 16:05:17 -0500
 Raymond C. Rodgers sinful...@gmail.com wrote:

   
 No other suggestions?
 

 Although I have used software raid for several years now, I am not an
 expert in the subject. In particular, I have never needed to use
 mkinitrd, because I do not boot from the raid device. Nor have I used
 the dmraid program because, on the few occasions where I have had to
 invervene with the process, I have used mdadm. However, since none of
 the other responses have been useful, perhaps something in my own
 experience might help.

 I do not have any of the raid partitions in my fstab,
 nor do I have /dev/mapper. What I do have is /dev/md0. The individual
 partitions have the raid flag turned on in the partition table, and the
 kernel creates the md0 device, which is then mounted as specified in
 fstab.
   
The OP wants to automatically partitions. I thought you do that either
through autofs or fstab.

Bob

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: dmraid mkinitrd under F10 x86_64 (No Puppies Harmed)

2008-12-15 Thread Raymond C. Rodgers

Robert L Cochran wrote:

Charles Crayne wrote:
  

On Mon, 15 Dec 2008 16:05:17 -0500
Raymond C. Rodgers sinful...@gmail.com wrote:

  


No other suggestions?

  

Although I have used software raid for several years now, I am not an
expert in the subject. In particular, I have never needed to use
mkinitrd, because I do not boot from the raid device. Nor have I used
the dmraid program because, on the few occasions where I have had to
invervene with the process, I have used mdadm. However, since none of
the other responses have been useful, perhaps something in my own
experience might help.

I do not have any of the raid partitions in my fstab,
nor do I have /dev/mapper. What I do have is /dev/md0. The individual
partitions have the raid flag turned on in the partition table, and the
kernel creates the md0 device, which is then mounted as specified in
fstab.
  


The OP wants to automatically partitions. I thought you do that either
through autofs or fstab.

Bob

  
From what I've seen, this can be done through initrd/mkinitrd some how, 
but I apparently don't know the magic well enough to make it happen. As 
I already stated, it was working under F8 and F9, with no entries for 
the /dev/mapper/ device in /etc/fstab , and currently with the 
appropriate device in fstab, the dmraid functionality is not getting 
enabled resulting in the individual partition members of the raid 
getting mounted automatically and magically by F10.


Raymond

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: dmraid mkinitrd under F10 x86_64 (No Puppies Harmed)

2008-12-15 Thread Charles Crayne
On Mon, 15 Dec 2008 22:09:44 -0500
Raymond C. Rodgers sinful...@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.

-- 
Chuck 
http://www.pacificsites.com/~ccrayne/charles.html

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: dmraid mkinitrd under F10 x86_64 (No Puppies Harmed)

2008-12-15 Thread Robert L Cochran
And the output of `ls /dev/mapper`



Charles Crayne wrote:
 On Mon, 15 Dec 2008 22:09:44 -0500
 Raymond C. Rodgers sinful...@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.

   

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: dmraid mkinitrd under F10 x86_64 (No Puppies Harmed)

2008-12-14 Thread Raymond C. Rodgers

Raymond C. Rodgers wrote:

Raymond C. Rodgers wrote:
Under F8 or F9, I had managed to build an initrd image that would 
automatically mount my non-boot dmraided drives without any effort on 
my part; this was obviously a while ago, and I'm no expert on 
mkinitrd. When I installed F10, it wiped out that configuration, and 
is instead intent upon mounting the individual drives and not 
initialize dmraid at all. I've been trying to get this fixed for a 
few days now, but can't seem to come up with an answer. Can any one 
give me an answer?


After unmounting the individual drives, I currently activate the 
dmraid as root with:


dmraid -a yes  nvidia_gdedfbbj

Then mount the desired partitions. The device mapper device files for 
the partitions are in my /etc/fstab with an appropriate mounted path, 
which makes it a simple mount /media/drive command possible once 
dmraid has been activated.


But mkinitrd seems to be where I'm having the problem. I just tried 
using --force-raid-probe which is listed in the usage notes (mkinitrd 
-h), but apparently it isn't actually available as a command line 
option. Would using --with=dmraid work?


Thanks,
Raymond
I hope this was just lost amid the packagekit threads... Any one got 
an answer for me?

Thanks,
Raymond
This is my second attempt to get the message noticed and possibly get a 
response. I'd like to note that no puppies, partitions, or disks were 
harmed in the making of this email, or in the upgrade from F9 to F10.


Raymond

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: dmraid mkinitrd under F10 x86_64 (No Puppies Harmed)

2008-12-14 Thread Robert L Cochran


http://ubuntuforums.org/showthread.php?t=526151




Raymond C. Rodgers wrote:
 Raymond C. Rodgers wrote:
 Raymond C. Rodgers wrote:
 Under F8 or F9, I had managed to build an initrd image that would
 automatically mount my non-boot dmraided drives without any effort
 on my part; this was obviously a while ago, and I'm no expert on
 mkinitrd. When I installed F10, it wiped out that configuration, and
 is instead intent upon mounting the individual drives and not
 initialize dmraid at all. I've been trying to get this fixed for a
 few days now, but can't seem to come up with an answer. Can any one
 give me an answer?

 After unmounting the individual drives, I currently activate the
 dmraid as root with:

 dmraid -a yes  nvidia_gdedfbbj

 Then mount the desired partitions. The device mapper device files
 for the partitions are in my /etc/fstab with an appropriate mounted
 path, which makes it a simple mount /media/drive command possible
 once dmraid has been activated.

 But mkinitrd seems to be where I'm having the problem. I just tried
 using --force-raid-probe which is listed in the usage notes
 (mkinitrd -h), but apparently it isn't actually available as a
 command line option. Would using --with=dmraid work?

 Thanks,
 Raymond
 I hope this was just lost amid the packagekit threads... Any one got
 an answer for me?
 Thanks,
 Raymond
 This is my second attempt to get the message noticed and possibly get
 a response. I'd like to note that no puppies, partitions, or disks
 were harmed in the making of this email, or in the upgrade from F9 to
 F10.

 Raymond


-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: dmraid mkinitrd under F10 x86_64 (No Puppies Harmed)

2008-12-14 Thread Raymond C. Rodgers

Robert L Cochran wrote:

http://ubuntuforums.org/showthread.php?t=526151


  

I already have it in /etc/fstab, but /dev/mapper/ device isn't getting 
created at boot, and so F10 just goes on and auto-mounts the individual 
drives as separate devices instead of jointly as a dmraid device.



Raymond

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines