From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n3LGFr5s006727 for ; Tue, 21 Apr 2009 12:15:53 -0400 Received: from mail.brunson.com (www.brunson.com [72.249.20.185]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n3LGFd4i006446 for ; Tue, 21 Apr 2009 12:15:39 -0400 Received: from [172.20.11.71] (unknown [12.109.229.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.brunson.com (Postfix) with ESMTP id 8377D6C37B for ; Tue, 21 Apr 2009 10:15:38 -0600 (MDT) Message-ID: <49EDF12A.8@brunson.com> Date: Tue, 21 Apr 2009 10:15:38 -0600 From: Eric Brunson MIME-Version: 1.0 Subject: Re: [linux-lvm] re-activate lv after reboot ? References: <49EDEA93.1090406@sivell.com> <49EDED3C.4060608@brunson.com> <49EDEEA5.6060409@sivell.com> In-Reply-To: <49EDEEA5.6060409@sivell.com> Content-Transfer-Encoding: 7bit Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: LVM general discussion and development On 04/21/2009 10:04 AM, vu pham wrote: > Eric Brunson wrote: >> On 04/21/2009 09:47 AM, vu pham wrote: >>> My server uses iscsiadm to access a remote iscsi device. VG and LV >>> are created on that device and can be accessed just fine. >>> The problem is after reboot, the LVs are in inactive mode and I have >>> to run vgchange -a y to activate the VG on the iscsi device or to >>> put that command /etc/rcd./rc.local. >> >> In RH and Fedora you need to updated your initrd image to have the >> drivers for the disk access available before the real filesystems are >> mounted. You don't mention what distro you're using, so I'll avoid >> boring you with details that may not be pertinent to your situation. >> > > Hi Eric, thanks for your reply. I am using RHEL5.3 > In Fedora (and I assume RH) you can specify additional kernel modules to include in the initrd image: foxtrot(~)$ cat /etc/sysconfig/mkinitrd MODULES="usb-storage" This will also "stick" across kernel upgrades as mkinitrd is part of the kernel post-install process. I don't know anything about iscsiadm, if it's simply a kernel module, then you can add it as I added usb-storage, if it's a process that has to be running, that may be more difficult to add to your boot process. That's the extent of my expertise, so maybe someone familiar with iscsiadm may chime in. Hope that helps, e.