Mylivecd and /home (solved )

[Neal ManBear]

Run bleachbit and bleachbit-root to clean up your system. Delete those files you saved. Try again.

[pclinmike]

It failed again  .

Do you think / is too small ?

Before I started.
df
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1              11G  4.0G  6.5G  38% /
/dev/sdb6              51G   22G   30G  42% /home

  After I did the mylivecd.
df
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1              11G  8.3G  2.2G  80% /
/dev/sdb6              51G   22G   30G  42% /home

If it is I will try with GParted to move a bit more over from /home.

This is the output.

Creating initrd:                                   [100.00% 00:00:13/00:00:13]
Setting filesystem parameters:                     [100.00% 00:01:07/00:01:07]
Creating compressed image:                         [100.00% 07:16:50/07:16:50]
Creating isolinux boot:                            [100.00% 00:00:00/00:00:00]
Creating final iso:                                [100.00% 00:00:00/00:00:00]
ls: cannot access kitchen1262011.iso: No such file or directory
Embedding MD5 checksum:
[                                                                            ]Argument "" isn't numeric in division (/) at /usr/sbin/mylivecd line 278.                                                 [  0.00% 00:00:00/00:00:00]Error - Unable to open file kitchen1262011.iso

Illegal division by zero at /usr/sbin/mylivecd line 296.

[Neal ManBear]

Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1              11G  8.3G  2.2G  80% /

Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1              11G  4.0G  6.5G  38% /

Size matters. 80% used means there's not enough space. How did you get from 38% to 80%?

Run bleachbit root.

[Just17]

Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1              11G  8.3G  2.2G  80% /

Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1              11G  4.0G  6.5G  38% /

Size matters. 80% used means there's not enough space. How did you get from 38% to 80%?

Run bleachbit root.

The left over files which were not deleted on failure to complete the remaster perhaps?

**

It would help if the command used to remaster was posted so we could see if there is anything odd going on.

From the sizes posted it might seem that you are trying to remaster too much .....

I would suggest that the /home partition be used for the temp for the remaster .....  using a specific directory in /home, which should itself be excluded from the remaster.
With 30GB of space at least the available space question would be eliminated.

A lot of space is needed for the remaster ......

...  all the files to be included are copied, so if you wish to remaster 9GB of files then they will be copied.
In addition you should allow space for the ISO itself ....  which can be up to 4.3GB

As you have lots of space on the home partition, creating a "remaster" directory there, and using the options in mylivecd to keep its working files and the output ISO there also, will unsure space is not a consideration. The 'remaster' directory would need to be specifically excluded (^nodir) from the remaster.

regards.

[pclinmike]

Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1              11G  8.3G  2.2G  80% /

Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1              11G  4.0G  6.5G  38% /

Size matters. 80% used means there's not enough space. How did you get from 38% to 80%?

Run bleachbit root.

The failed 'livecd' folder in /tmp is 4.3G so 4.3+2.2 = 6.5G
 
If my / folder only contains 4G of data why is the finished (failed) mylivecd 4.3G in size , what has it been trying to compress in 7hrs 15min.?

I used both of these in this format (but putting our real user names in).

mylivecd --nodir=^/home/pclinmike,^/home/user2,^/home/user3 kitchen1262011.iso
mylivecd --md5sum --nodir=^/home/pclinmike,^/home/user2,^/home/user3 kitchen1262011.iso

Both failed.

Going to try and make / larger, I also will delete failed mylivecd and run bleachbit.
 

[Just17]

Going to try and make / larger, I also will delete failed mylivecd and run bleachbit.

There is no need to make  /  larger .......  just direct the mylivecd temp directory to where the space exists -- on the /home partition, and exclude that directory from the remaster.

Have you checked how much space is used in /home outside of the user directories?
There are likely lots of files and copies of files there, which may be increasing the ISO size appreciably.

There is also the much faster -gzip compression available if you are updated and have a recent kernel installed.

I would suggest you give the following a try ....  create a directory called  /home/remasters, then use the following command .....

mylivecd --md5sum --nodir=^/home/   --gzip   --tmp /home/remasters     kitchen1262011.iso

regards.

[pclinmike]

Going to try and make / larger, I also will delete failed mylivecd and run bleachbit.

There is no need to make  /  larger .......  just direct the mylivecd temp directory to where the space exists -- on the /home partition, and exclude that directory from the remaster.

Too late, by the time I have seen your post I could not make/ larger because of an extended partition, so I made /tmp larger by 10G  .

df
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb1              11G  4.0G  6.5G  38% /
/dev/sdb6              40G   22G   19G  54% /home
/dev/sdb8              11G   47M   11G   1% /tmp

Have you checked how much space is used in /home outside of the user directories?
There are likely lots of files and copies of files there, which may be increasing the ISO size appreciably.

You hit the nail on the head  .I forgot about the 'VirtualBox' 8G of files

There is also the much faster -gzip compression available if you are updated and have a recent kernel installed.

I would suggest you give the following a try ....  create a directory called  /home/remasters, then use the following command .....

mylivecd --md5sum --nodir=^/home/   --gzip   --tmp /home/remasters     kitchen1262011.iso

regards.

I will have another go later tonight.
I will do it  .

[Neal ManBear]

BTW, adding the --md5sum option is unnecessary. The md5sum will be included anyway.

[Texstar]

BTW, adding the --md5sum option is unnecessary. The md5sum will be included anyway.

Not anymore. It has been depreciated with the latest version of mylivecd because it doesn't work on DVDs and just takes up extra space that can be used for more programs.

All you need to do for kernel 2.6.38.8 with maximum xz compression is mylivecd name-of-iso. If you want normal xz compression (faster) then mylivecd --xz name-of-iso or for fastest iso creation with minimum compression mylivecd --gzip name-of-iso.

If you have an old kernel you need mylivecd --lzma name-of-iso.


You can still do mylivecd --md5sum but the menu entry has been commented out in the /usr/sbin/mylivecd script.

Tex

[Neal ManBear]

BTW, adding the --md5sum option is unnecessary. The md5sum will be included anyway.

Not anymore. It has been depreciated with the latest version of mylivecd because it doesn't work on DVDs and just takes up extra space that can be used for more programs.

All you need to do for kernel 2.6.38.8 with maximum xz compression is mylivecd name-of-iso. If you want normal xz compression (faster) then mylivecd --xz name-of-iso or for fastest iso creation with minimum compression mylivecd --gzip name-of-iso.

If you have an old kernel you need mylivecd --lzma name-of-iso.


You can still do mylivecd --md5sum but the menu entry has been commented out in the /usr/sbin/mylivecd script.

Tex

I missed that somehow. So the --md5sum option needs to be added, when we want it included?

[Texstar]

BTW, adding the --md5sum option is unnecessary. The md5sum will be included anyway.

Not anymore. It has been depreciated with the latest version of mylivecd because it doesn't work on DVDs and just takes up extra space that can be used for more programs.

All you need to do for kernel 2.6.38.8 with maximum xz compression is mylivecd name-of-iso. If you want normal xz compression (faster) then mylivecd --xz name-of-iso or for fastest iso creation with minimum compression mylivecd --gzip name-of-iso.

If you have an old kernel you need mylivecd --lzma name-of-iso.


You can still do mylivecd --md5sum but the menu entry has been commented out in the /usr/sbin/mylivecd script.

Tex

I missed that somehow. So the --md5sum option needs to be added, when we want it included?

Sorry about that. Things are moving pretty quick around and and changes happening overnight. You would have to edit /usr/sbin/mylivecd because it is no longer in the boot menu. No need to have something there that isn't working properly.

[Neal ManBear]

BTW, adding the --md5sum option is unnecessary. The md5sum will be included anyway.

Not anymore. It has been depreciated with the latest version of mylivecd because it doesn't work on DVDs and just takes up extra space that can be used for more programs.

All you need to do for kernel 2.6.38.8 with maximum xz compression is mylivecd name-of-iso. If you want normal xz compression (faster) then mylivecd --xz name-of-iso or for fastest iso creation with minimum compression mylivecd --gzip name-of-iso.

If you have an old kernel you need mylivecd --lzma name-of-iso.


You can still do mylivecd --md5sum but the menu entry has been commented out in the /usr/sbin/mylivecd script.

Tex

I missed that somehow. So the --md5sum option needs to be added, when we want it included?

Sorry about that. Things are moving pretty quick around and and changes happening overnight. You would have to edit /usr/sbin/mylivecd because it is no longer in the boot menu. No need to have something there that isn't working properly.

Okay. No "Media Check" in the boot menu.
But I was talking about checking against a downloaded ISO. Line #66 in /usr/sbin/mylivecd --
my $md5sum      = undef;

[pclinmike]

Good copy this time (1.2G size), burned ok, It will boot into same machine but not any others  .