Re: what is storage.protectedDevices?

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

 



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 <dlehman@xxxxxxxxxx> 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/__init__.py#L92)

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
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

Attachment: storage.rtf
Description: RTF file

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux