Re: Now Working... but...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I finally managed to have a working system.

What now happens is that after the initrd finishes, there is no /dev/mapper/sil... but just /dev/mapper and "control".

I have to manually do a "dmraid -ay" to get the drive back, and this sounds strange to me since the system is just up and running, how can it access the disk if it is not seen in /dev/mapper? this should apply to swap space also.

How can I workaround this? what is a safe place to put the dmraid command?

Initrd usually places the /dev/mapper/sil* nodes in a ramdisk, which gets unmounted after the system boots. On my fedora system, I put another dmraid command in /etc/rc.d/rc.sysinit, just after lvm initialization.

Dmraid is in a lot of ways similar to lvm. If you look at lvm, it also gets setup in both initrd and again in rc.sysinit. Lvm2 (used by fc2, fc3 and fc4) also uses /dev/mapper/* devices.

Kind regards,

Mark

_______________________________________________

Ataraid-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ataraid-list

[Index of Archives]     [Linux RAID]     [Linux Device Mapper]     [Linux IDE]     [Linux SCSI]     [Kernel]     [Linux Books]     [Linux Admin]     [GFS]     [RPM]     [Yosemite Campgrounds]     [AMD 64]

  Powered by Linux