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

Re: problem running lorax from distill on EFI (aarch64) systems



I'm not sure if lorax is creating the loop dev as write-protected, or if the loop-dev is provided to lorax, and then lorax falls victim.

The fact that the compose works when ran as root suggest that something outside of lorax is an influence to the outcome, as lorax runs as privileged root in mock.

This all began when aarch64.tmpl was enhanced to provide EFI support, it perhaps began to trigger code path that relates to loop-mounting with EFI.

Any insight you folks might have is appreciated. =)

Thanks,
-Jon Disnard 

 

----- Original Message -----
> From: "David A. Marlin" <dmarlin redhat com>
> To: "Discussion of Development and Customization of the Red Hat Linux Installer" <anaconda-devel-list redhat com>
> Cc: "Jon Disnard" <jdisnard redhat com>
> Sent: Thursday, March 27, 2014 10:45:54 AM
> Subject: problem running lorax from distill on EFI (aarch64) systems
> 
> When Jon is running distill for aarch64 he is getting an error.
> This does not occur if he runs it manually as root.
> The primary issue seems to be:
> 
>    /dev/loop0 is write-protected, mounting read-only
> 
> and we can't write the EFI directory to it.
> 
> 
> --------------------------------------
> 2014-03-27 10:00:15,662: preparing to build output tree and boot images
> preparing to build output tree and boot images
> 2014-03-27 10:00:15,664: rebuilding initramfs images
> rebuilding initramfs images
> 2014-03-27 10:00:15,670: rebuilding
> boot/initramfs-3.13.0-0.rc7.27.sa2.aarch64.img
> rebuilding boot/initramfs-3.13.0-0.rc7.27.sa2.aarch64.img
> No '/dev/log' or 'logger' included for syslog logging
> dracut module 'mlx4' depends on 'rdma', which can't be installed
> dracut module 'rdma' cannot be found or installed.
> dracut module 'rdma' cannot be found or installed.
> dracut module 'rdma' cannot be found or installed.
> dracut module 'rdma' cannot be found or installed.
> cat: write error: Broken pipe
> 2014-03-27 10:03:18,743: populating output tree and building boot images
> populating output tree and building boot images
> 2014-03-27 10:03:18,891: running aarch64.tmpl
> running aarch64.tmpl
> ERROR:program:mount: /dev/loop0 is write-protected, mounting read-only
> mount: /dev/loop0 is write-protected, mounting read-only
> Traceback (most recent call last):
>    File "/usr/sbin/mkefiboot", line 155, in <module>
>      mkefiboot(opt.bootdir, opt.outfile, opt.label)
>    File "/usr/sbin/mkefiboot", line 32, in mkefiboot
>      mkdosimg(None, outfile, label=label, graft={'EFI/BOOT':bootdir})
>    File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line 327, in
>    mkdosimg
>      mkfsargs=["-n", label], graft=graft)
>    File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line 319, in
>    mkfsimage
>      do_grafts(graft, mnt, preserve)
>    File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line 170, in
>    do_grafts
>      os.makedirs(targetdir)
>    File "/usr/lib64/python2.7/os.py", line 157, in makedirs
>      mkdir(name, mode)
> OSError: [Errno 30] Read-only file system: '/tmp/lorax.imgutils.PYH_RV/EFI'
> --------------------------------------
> 
> 
> The full log is:
> 
>    http://download.lab.bos.redhat.com/devel/candidates/Acadia/RHSA-2.0-20140327.1/logs/aarch64/buildinstall.aarch64.log
>   
> 
> Thank you,
> 
> d.marlin
> 
> 


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