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

Re: Stoped at binary stage.



Hi Fernando,


Am 27.06.2015 um 21:38 schrieb Fernando Toledo:
> El 23/06/15 a las 05:28, Jan Kowalsky escibió:
> 
>> Any idea?
>>
>> This is my auto-config:

....

>>
>>
> 
> can you try to clean all with "lb clean --purge" before start a new build?


thanks for this hint. Yes, now it builds the image

(it took me some time to find the image: it was inside the chroot:
./chroot/binary.img)

but the image seems to be damaged or not ready. Neither can I mount it
with mount -o loop binary.img /mnt nor it's bootable.

The end of the build log looks like:

[2015-06-30 11:28:24] lb binary_hdd
P: Begin building binary hdd image...
Reading package lists...
Building dependency tree...
Reading state information...
Recommended packages:
  syslinux-common
The following NEW packages will be installed:
  syslinux
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/188 kB of archives.
After this operation, 282 kB of additional disk space will be used.
Selecting previously unselected package syslinux.
(Reading database ... ^M(Reading database ... 5%^M(Reading database ...
10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading
database ... 25%
^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading
database ... 40%^M(Reading database ... 45%^M(Reading database ...
50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading
database ... 65%^M(Reading database ... 70%^M(Reading database ...
75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading
database ... 90%^M(Reading database ... 95%^M(Reading database ...
100%^M(Reading database ... 97863 files and directories currently
installed.)
Preparing to unpack .../syslinux_3%3a6.03+dfsg-5_i386.deb ...
Unpacking syslinux (3:6.03+dfsg-5) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up syslinux (3:6.03+dfsg-5) ...
0+0 records in
0+0 records out
0 bytes (0 B) copied, 6.7372e-05 s, 0.0 kB/s
!!! The following error/warning messages can be ignored !!!
P: Mounting /dev/loop0 with offset 0
dd: failed to open 'chroot/usr/lib/syslinux/mbr.bin': No such file or
directory
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists...
Building dependency tree...
Reading state information...


The 0 bytes copied after the setup of syslinux doesn't look very well.

Any idea?

Best Regards
Jan


Reply to: