what is storage.protectedDevices?

[Kun Huang]

Hi, all

https://github.com/pyKun/install.img/blob/master/usr/lib/anaconda/storage/__...

this is an old version anaconda, but I just need know the meaning of this
line.

In my case, I used 'repo=hd:......' so anaconda.protected here valuate as
true in L93, so when run to L97( my case is not livecd, and "not
storage.protectedDevices"), the program looks me as upgrade case, so it
checks anaconda.id.getUpgrade().

My case is installing a system from usb. Kickstart files, and repo are all
from usb device. But how storage.protectedDevices means here?

Thanks
Gareth

[Kun Huang]

My boot options is:

initrd=initrd.img text stage2=hd:xxxx:/images/install.img ip=static
ks=hd:xxxxx:/node.ks repo=hd:xxxxx:/os

On Tue, Jul 30, 2013 at 1:54 PM, Kun Huang  wrote:
> Hi, all
>
> https://github.com/pyKun/install.img/blob/master/usr/lib/anaconda/storage/__...
>
> this is an old version anaconda, but I just need know the meaning of this
> line.
>
> In my case, I used 'repo=hd:......' so anaconda.protected here valuate as
> true in L93, so when run to L97( my case is not livecd, and "not
> storage.protectedDevices"), the program looks me as upgrade case, so it
> checks anaconda.id.getUpgrade().
>
> My case is installing a system from usb. Kickstart files, and repo are all
> from usb device. But how storage.protectedDevices means here?
>
> Thanks
> Gareth

[David Lehman]

On Tue, 2013-07-30 at 13:54 +0800, Kun Huang wrote:
> Hi, all
>
> https://github.com/pyKun/install.img/blob/master/usr/lib/anaconda/storage/__...
>
> this is an old version anaconda, but I just need know the meaning of
> this line.
>
> In my case, I used 'repo=hd:......' so anaconda.protected here valuate
> as true in L93, so when run to L97( my case is not livecd, and "not
> storage.protectedDevices"), the program looks me as upgrade case, so
> it checks anaconda.id.getUpgrade().
>
> My case is installing a system from usb. Kickstart files, and repo are
> all from usb device. But how storage.protectedDevices means here?

anaconda.protected is non-empty, meaning there is a block device that
contains your installation media. That partition must be protected in
order to prevent removal of the device/filesystem containing the
installation media. The call to storage.reset() should have found the
block device that contains your installation media and identified it as
such, but it did not. That is a serious problem except in the case of
live media or an upgrade.

Does that answer your question?

[Kun Huang]

Thanks David, nice answer

But my case went more weird. I have 2 usb drives to run test, using same
generate scripts, with same files (except the extlinux.conf because of the
different UUID).
And one runs perfectly, another failed at the step of validating L92 at (
https://github.com/pyKun/install.img/blob/master/usr/lib/anaconda/storage/__...
)

On Wed, Jul 31, 2013 at 6:46 AM, David Lehman  wrote:
> On Tue, 2013-07-30 at 13:54 +0800, Kun Huang wrote:
> > Hi, all
>
> https://github.com/pyKun/install.img/blob/master/usr/lib/anaconda/storage/__...
> > this is an old version anaconda, but I just need know the meaning of
> > this line.
> >
> > In my case, I used 'repo=hd:......' so anaconda.protected here valuate
> > as true in L93, so when run to L97( my case is not livecd, and "not
> > storage.protectedDevices"), the program looks me as upgrade case, so
> > it checks anaconda.id.getUpgrade().
> >
> > My case is installing a system from usb. Kickstart files, and repo are
> > all from usb device. But how storage.protectedDevices means here?
>
> anaconda.protected is non-empty, meaning there is a block device that
> contains your installation media. That partition must be protected in
> order to prevent removal of the device/filesystem containing the
> installation media. The call to storage.reset() should have found the
> block device that contains your installation media and identified it as
> such, but it did not. That is a serious problem except in the case of
> live media or an upgrade.
>
> Does that answer your question?
>
> Anaconda-devel-list mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[David Lehman]

On Thu, 2013-08-01 at 17:27 +0800, Kun Huang wrote:
> Thanks David, nice answer
>
> But my case went more weird. I have 2 usb drives to run test, using
> same generate scripts, with same files (except the extlinux.conf
> because of the different UUID).
> And one runs perfectly, another failed at the step of validating L92
> at
> (https://github.com/pyKun/install.img/blob/master/usr/lib/anaconda/storage/__...)

That means either something is wrong with the media you generated or
something went wrong during storage.reset(). Read
through /tmp/storage.log and correlate the messages you see there with
the code and you can figure out what the problem is.

[Kun Huang]

Hello David

I found some errors, but it is out of my knowledge
Below is the failed part:

09:46:37,844 INFO    : failed to unlink /etc/mdadm.conf
09:46:37,857 INFO    : edd: collected mbr signatures: {'sdc': '0x000850ec'}
09:46:37,858 DEBUG   : edd: data extracted from 0x80:
type: None, ata_device: None
channel: None, mbr_signature: 0x00083ec4
pci_dev: None, scsi_id: None
scsi_lun: None, sectors: 15633072
09:46:37,858 ERROR   : edd: unable to match edd entry 0x80
09:46:37,858 DEBUG   : edd: data extracted from 0x81:
type: SCSI, ata_device: None
channel: 0, mbr_signature: 0x000850ec
pci_dev: 02:0e.0, scsi_id: 0
scsi_lun: 0, sectors: 3905945600
09:46:37,858 INFO    : edd: matched 0x81 to sdc using MBR sig
09:46:37,892 DEBUG   : looking up parted Device: /dev/sda
09:46:37,896 DEBUG   :          Iso9660FS.supported: supported: True ;
09:46:37,898 DEBUG   :           Ext3FS.supported: supported: True ;
09:46:37,900 DEBUG   :           Ext3FS.supported: supported: True ;
09:46:37,903 DEBUG   :           XFS.supported: supported: True ;
09:46:37,905 DEBUG   :          OpticalDevice.mediaPresent: sr0 ; status:
True ;
09:46:37,912 DEBUG   :          OpticalDevice.mediaPresent: sr1 ; status:
True ;

But I don't know what is the 'edd' in DEBUG log. It seems anaconda failed
to remove the file '/etc/mdadm.conf'.
And when I went to my environment, I didn't find that file. I'm not sure
that file has already been deleted or never exists.

The total log file is in my attachment. (sda is virtual floopy on the
server, sdb is the usb drive, sdc is logic hard drive)

On Thu, Aug 1, 2013 at 10:16 PM, David Lehman  wrote:
> On Thu, 2013-08-01 at 17:27 +0800, Kun Huang wrote:
> > Thanks David, nice answer
> >
> > But my case went more weird. I have 2 usb drives to run test, using
> > same generate scripts, with same files (except the extlinux.conf
> > because of the different UUID).
> > And one runs perfectly, another failed at the step of validating L92
> > at
> > (
>
> https://github.com/pyKun/install.img/blob/master/usr/lib/anaconda/storage/__...
> )
>
> That means either something is wrong with the media you generated or
> something went wrong during storage.reset(). Read
> through /tmp/storage.log and correlate the messages you see there with
> the code and you can figure out what the problem is.
>
> Anaconda-devel-list mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list