mylivecd failed - what did I do wrong?

[aguila]

Hi all,

I'm about to migrate my PCLOS install to a 256 GB SSD, so I wanted to make a remaster of my HDD to install on the SSD.

So I followed Neals instructions here: http://www.pclinuxos.com/forum/index.php/topic,74418.msg610806.html#msg610806

Did a

Code: [Select]

umount -a and then

Code: [Select]

[root@localhost andreas]# df
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda6              30G  6,5G   22G  24% /
/dev/sda7             107G   86G   22G  80% /home
[root@localhost andreas]#

Code: [Select]

[root@localhost andreas]# mylivecd --nodir /home/andreas/Bilder/ PCLOS_2012.03_Remaster.iso
mylivecd, version 0.9.4, http://pclinuxos.com/
Copyright (C) 2010, Texstar <texstar at gmail.com>

This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.

Disabling Services not needed on the LiveCD

running: /sbin/chkconfig --list
running: chkconfig --del atd
running: /sbin/chkconfig --list
running: chkconfig --del crond
running: /sbin/chkconfig --list
running: chkconfig --del syslog
Warning: syslog is needed by script(s) in runlevel 2: freshclam(start) freshclam(stop) messagebus(start) messagebus(stop) smartd(start) smartd(stop) shorewall(start)
Warning: syslog is needed by script(s) in runlevel 3: freshclam(start) freshclam(stop) messagebus(start) messagebus(stop) smartd(start) smartd(stop) shorewall(start)
Warning: syslog is needed by script(s) in runlevel 4: freshclam(start) freshclam(stop) messagebus(start) messagebus(stop) smartd(start) smartd(stop) shorewall(start)
Warning: syslog is needed by script(s) in runlevel 5: freshclam(start) freshclam(stop) messagebus(start) messagebus(stop) smartd(start) smartd(stop) shorewall(start)
Warning: syslog is needed by script(s) in runlevel 7: messagebus(start) messagebus(stop)
running: /sbin/chkconfig --list
running: chkconfig --del kheader
running: /sbin/chkconfig --list
running: chkconfig --del xinetd


Creating initrd:                                   [ 26.83% 00:00:00/00:00:00]cp: cannot stat `/usr/lib/libpng.so': No such file or directory==================                                                        ]
                                                   [100.00% 00:00:08/00:00:08]
Setting filesystem parameters:                     [100.00% 00:00:25/00:00:25]
Creating compressed image:                         [100.00% 02:53:11/02:53:11]
Creating isolinux boot:                            [100.00% 00:00:01/00:00:01]
Creating final iso:                                [100.00% 00:00:00/00:00:00]
                                                                             
Restoring Services on the installed system

running: chkconfig --add atd
running: chkconfig --add crond
Warning: syslog is needed by crond in runlevel 2
Warning: syslog is needed by crond in runlevel 3
Warning: syslog is needed by crond in runlevel 4
Warning: syslog is needed by crond in runlevel 5
Warning: syslog is needed by crond in runlevel 2
Warning: syslog is needed by crond in runlevel 3
Warning: syslog is needed by crond in runlevel 4
Warning: syslog is needed by crond in runlevel 5
Warning: syslog is needed by crond in runlevel 2
Warning: syslog is needed by crond in runlevel 3
Warning: syslog is needed by crond in runlevel 4
Warning: syslog is needed by crond in runlevel 5
Warning: syslog is needed by crond in runlevel 2
Warning: syslog is needed by crond in runlevel 3
Warning: syslog is needed by crond in runlevel 4
Warning: syslog is needed by crond in runlevel 5
Warning: syslog is needed by crond in runlevel 2
Warning: syslog is needed by crond in runlevel 3
Warning: syslog is needed by crond in runlevel 4
Warning: syslog is needed by crond in runlevel 5
Warning: syslog is needed by crond in runlevel 2
Warning: syslog is needed by crond in runlevel 3
Warning: syslog is needed by crond in runlevel 4
Warning: syslog is needed by crond in runlevel 5
running: chkconfig --add syslog
running: chkconfig --add kheader
running: chkconfig --add xinetd
ls: cannot access PCLOS_2012.03_Remaster.iso: No such file or directory
Argument "" isn't numeric in division (/) at /usr/sbin/mylivecd line 244.

Created 'PCLOS_2012.03_Remaster.iso' (0,000 bytes) in 02:53:50

[root@localhost andreas]#
What did I do wrong? I'm really lost.... 

[AS]

You did nothing wrong, I did it! 

as a workaround, simply install libpng-devel.
mylivecd-0.9.4-12 fix the issues, already sent to dropbox. 

http://www.pclinuxos.com/forum/index.php/topic,103184.0.html

AS

[aguila]

Hi as,

thanks, I'll try again.

btw - how much time will the remaster take (per gb)? is three hours for about 8 gb okay?

[AS]

Hi as,

thanks, I'll try again.

btw - how much time will the remaster take (per gb)? is three hours for about 8 gb okay?

It depend from your CPU. The compression phase require a lot of power, multicore CPUs help a lot as the compressor can and use all available cores.

For less powerful CPUs I would suggest to use the --gzip option, that will speed up the process  (approx. 3x faster compared to the default compression), at a price of a little larger final ISO image.

Additionally, systems with low amount of RAM (< 1 GB) may also experience performance problems, in this case --gzip is also suggested.

I'm using a Core2 T8100, 2.1Ghz and can remaster 10 GB in 1 hour  using default compression, or 20 minutes using gzip compression.

Other factors can affect overall performance of mylivecd, but on average, is a CPU bound process.

Also, if possible umount the filesystem not to be included, the --nodir option is not very efficient and (from my tests) it appear to slow down the process in case of lot of excluded files ....

AS

[ternor]

I have mylivecd version 0.9.5-2.  Should I also install libpng-devel as mentioned in the other thread?

I ask because, for the first time ever in about 6 years, two disks I burnt from the remaster .iso failed the md5sum test.  Each disk provided a different md5sum and neither equalled the md5sum of the iso itself.  The procedure I use has always provided correct md5sums for years.

Where can I get a link to the dropbox?

[AS]

I have mylivecd version 0.9.5-2.  Should I also install libpng-devel as mentioned in the other thread?

no, it was fixed in 0.9.4-12 and later.

I ask because, for the first time ever in about 6 years, two disks I burnt from the remaster .iso failed the md5sum test.  Each disk provided a different md5sum and neither equalled the md5sum of the iso itself.  The procedure I use has always provided correct md5sums for years.

Where can I get a link to the dropbox?

did you used mylivecd --md5sum ?  if yes, the md5sum is embedded in the ISO and you could verify it using mediacheck.

AS

[ternor]

Thanks for replying.  An md5sum is embedded in the iso but the two disks I burnt do not have the same md5sum as the iso, nor the same md5sum as each other.  mediacheck only tells you whether the disk has an md5sum, not what the disk's md5sum is.

I have been using the same procedure to read a disk's md5sum for about 6 years and these are the first and second times it has returned the wrong md5sum.

[AS]

Thanks for replying.  An md5sum is embedded in the iso but the two disks I burnt do not have the same md5sum as the iso, nor the same md5sum as each other.  mediacheck only tells you whether the disk has an md5sum, not what the disk's md5sum is.

I have been using the same procedure to read a disk's md5sum for about 6 years and these are the first and second times it has returned the wrong md5sum.

Mediacheck recalculate the md5sum and verify that the result match the embedded md5sum, so if you can successfully run mediacheck on the original ISO, and you can't on the burned image the only conclusion is bad-media or bad-burn.

[ternor]

Thank you.  The first faulty disk has now passed the mediacheck.

Code: [Select]

$ mediacheck /dev/sr0
That is no help at all.

[AS]

Thank you.  The first faulty disk has now passed the mediacheck.

Code: [Select]

$ mediacheck /dev/sr0
That is no help at all.

please expand "faulty"... what problem are you encountering ?

[ternor]

Thank you again.  I was editing my previous post when or after you posted.  The disk is faulty because its md5sum is wrong.  I have therefore tried another disk which also returned the wrong md5sum.  My conclusion is that the iso itself is faulty but that doesn't stack up either.

To illustrate what I mean, this is a history of md5sum checks of isos and disks, in descending order.  The first entry is the latest and shows what happened when I checked the md5sums of the iso and two disks burned from it.  You will see that the md5sum checks of previous isos and disks returned valid results:

12.03.2012 8:25 AM 120312
4e210f69c57194e02ccc04f63f6b8b6a  /data/isos/remaster-2010.iso
d9e2d60607038400312e7b4902c0f5ed  - no good
29688a7744bd972ce66f6d197df6e402  - no do another iso

26.02.2012 7:36 AM 120225
be6f15ce44fdeaeab07e639b5ce3de56  /data/isos/remaster-2010.iso
be6f15ce44fdeaeab07e639b5ce3de56  - dvd

25.01.2012 10:05 AM 120124remaster-2010-sda2.iso
f0bac23ba0d684f657d57103221c1372  /data/isos/remaster-2010.iso
f0bac23ba0d684f657d57103221c1372  - dvd

25.12.2011 7:44 AM 111224 sda2
11dcd0b5e33f469138a3c3b90d97e082  /data/isos/remaster-2010.iso
11dcd0b5e33f469138a3c3b90d97e082  - dvd

13.11.2011 1:09 PM 111113-sda2
4d828d4bbf0fe6735b817ebebb427338  /data/isos/remaster-2010.iso
4d828d4bbf0fe6735b817ebebb427338  - dvd

05.11.2011 11:47 AM 111105-sda2
c4a8fcf453418797a629d1cf253adec0  /data/isos/remaster-2010.iso
c4a8fcf453418797a629d1cf253adec0  - dvd

15.10.2011 5:46 AM 111014-sda2
47ab6b37a771acb5061dc5c1e6f7c125  /data/isos/remaster-2010.iso
47ab6b37a771acb5061dc5c1e6f7c125  - dvd

30.09.2011 8:41 AM sda2 110929
5a5f5896d3ff3d1f9c6f09084f12767c  /data/isos/remaster-2010.iso
5a5f5896d3ff3d1f9c6f09084f12767c  - dvd

25.09.2011 11:48 AM sda2 110925
e288551a4fe2d88d23bcb73708d03c36  /data/isos/remaster-2010.iso
e288551a4fe2d88d23bcb73708d03c36  - dvd

03.09.2011 7:53 AM sda2 110902
875713e1f5eab108f4699843970d7cbe  /data/isos/remaster-2010.iso
875713e1f5eab108f4699843970d7cbe  - dvd

20.08.2011 8:20 PM sda2
dbc1d5309f1536c08d52dfc1b4480018  /data/isos/remaster-2010.iso
dbc1d5309f1536c08d52dfc1b4480018  - dvd

13.08.2011 11:45 AM sda2
3bee5d9c492b5a5f2ef2ef7b7c47d1eb  /data/isos/remaster-2010.iso
3bee5d9c492b5a5f2ef2ef7b7c47d1eb  - dvd

It occurs to me that I have unintentionally hijacked this thread.  Would someone please report my first post so that it and subsequent posts are moved to a new thread.

[AS]

Thank you again.  I was editing my previous post when or after you posted.  The disk is faulty because its md5sum is wrong.  I have therefore tried another disk which also returned the wrong md5sum.  My conclusion is that the iso itself is faulty but that doesn't stack up either.

One thing at a time please: 

The ISO itself cannot be faulty, not in respect of md5sum at least, because the md5um is calculated independently from the ISO image content.
You may "implant" the md5sum inside the ISO at time of mylivecd using the option --md5sum, or later using implantisomd5.
Can you confirm you used mylivecd with the option --md5sum ? Or you used implantisomd5 ?

Once you have implanted the md5sum, if you try to calculate it again on the same ISO, you will get a different result from that one implanted.
No matter if it is different, it should be equal to that one obtained from the media directly:

what return the following two commands ?

Code: [Select]

md5sum /data/isos/remaster-2010.iso
md5sum /dev/sr0


[ternor]

Thanks again.

This is the line I have been using for several years to remaster:

Code: [Select]

mylivecd --nodir ^/data --nofile ^/tmp/* --nofile ^dead.letter --tmp=/data/rem --workdir=/data/workdir --md5sum  /data/isos/remaster-2010.iso
Because of the present failure, I have changed the line to conform with that used by 'remasterme':

Code: [Select]

mylivecd --md5sum --lzma --bootloader iso --nodir ^/data --nofile ^/tmp/* --nofile ^dead.letter --tmp=/data/rem --workdir=/data/workdir /data/isos/remaster-2010.iso
The md5sum of the iso:

$ md5sum /data/isos/remaster-2010.iso
4e210f69c57194e02ccc04f63f6b8b6a  /data/isos/remaster-2010.iso

The md5sum of the disk:

$ md5sum /dev/sr0
dac8ae1018f08d8aa5435702ef412c9e  /dev/sr0

The md5sum of the disk is different from that which I have obtained previously.  This is the disk which passed mediacheck.

[AS]

Thanks again.

This is the line I have been using for several years to remaster:

Code: [Select]

mylivecd --nodir ^/data --nofile ^/tmp/* --nofile ^dead.letter --tmp=/data/rem --workdir=/data/workdir --md5sum  /data/isos/remaster-2010.iso
Because of the present failure, I have changed the line to conform with that used by 'remasterme':

Code: [Select]

mylivecd --md5sum --lzma --bootloader iso --nodir ^/data --nofile ^/tmp/* --nofile ^dead.letter --tmp=/data/rem --workdir=/data/workdir /data/isos/remaster-2010.iso

Except for compression, they look equal.
Please consider that LZMA is deprecated, either use the the default, --xz, or use --gzip.
The content of /tmp is always excluded from the remaster, you can safely omit --nofile ^/tmp/*

The md5sum of the iso:

$ md5sum /data/isos/remaster-2010.iso
4e210f69c57194e02ccc04f63f6b8b6a  /data/isos/remaster-2010.iso

The md5sum of the disk:

$ md5sum /dev/sr0
dac8ae1018f08d8aa5435702ef412c9e  /dev/sr0

The md5sum of the disk is different from that which I have obtained previously.  This is the disk which passed mediacheck.

Yes, I have understood that your result was something like that. A few question, just to understand the whole context:

what kernel are you running ? (uname -r)
how large is the ISO image, expressed in bytes ? (ls -l /data/isos/remaster-2010.iso)
do you have the package isomd5sum installed ?

[ternor]

Thank you.

Please consider that LZMA is deprecated, either use the the default, --xz, or use --gzip.

I copied the LZMA parameter from 'remasterme'.  However, I will change my script to --xz as you suggest.

The kernel version in use at the time was 2.6.38.8-pclos1.bfs  I have since installed 2.6.38.8-pclos3.bfs

The size of the iso:

$ ls -l /data/isos/remaster-2010.iso
-rw-r--r-- 1 root root 1030637568 Mar 12 07:45 /data/isos/remaster-2010.iso

isomd5sum  No, that package is NOT installed.