Author Topic: 1.6GB shows 974MB iso (SOLVED) [Automatically]  (Read 572 times)

Tommylee567

  • Guest
1.6GB shows 974MB iso (SOLVED) [Automatically]
« on: October 23, 2010, 08:40:53 AM »
I don't know how but strangely after running mylivecd command and finishing the remaster make it puts a 970 something megabytes. but inside the sqfs file is 1.6 GB.
i can't write using k3b or i get errors.

Using KDE 4 minime version, downloaded all KDE packages and some needed sw, and created a remaster. the script runs without ANY error. it goes ok. and system is to date (last one week)

what have i done wrong in here?
Thanks!
Tim

Code: [Select]
[root@localhost tim]# mylivecd --verbose --md5sum --nodir ^/var/cache/apt/archives,^/home/tim livecdkde.iso
mylivecd, version 0.9.3, 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: /sbin/chkconfig --list
running: /sbin/chkconfig --list
running: /sbin/chkconfig --list
running: /sbin/chkconfig --list


Creating initrd:                                   [100.00% 00:00:04/00:00:04]
Setting filesystem parameters:                     [100.00% 00:00:08/00:00:13]
Creating compressed image:                         [100.00% 00:16:08/00:16:20]
Creating isolinux boot:                            [100.00% 00:00:01/00:00:01]
Creating final iso:                                [100.00% 00:00:31/00:00:31]
Embedding MD5 checksum:                            [100.00% 00:00:20/00:00:20]
                                                                              
Restoring Services on the installed system


Created 'livecdkde.iso' (1020,006,400 bytes) in 00:17:12

[root@localhost tim]#
« Last Edit: October 29, 2010, 07:15:05 AM by Tommylee567 »

Offline Neal ManBear

  • Administrator
  • Super Villain
  • *****
  • Posts: 15845
  • LXDE! Coffee, Bacon and Cheesecake!
Re: 1.6GB shows 974MB iso
« Reply #1 on: October 23, 2010, 09:37:15 AM »
Quote
1020,006,400 bytes
Quote
970 something megabytes

Looks about right.

I think the 1.6 GB does not look right, though.

Quote
i can't write using k3b or i get errors.

Be more exact, please. What errors? You need to tell us this. Error messages need to be quoted here, or we have no way to help you figure it out.


Tommylee567

  • Guest
Re: 1.6GB shows 974MB iso
« Reply #2 on: October 23, 2010, 10:13:41 AM »
Bro,
im sorry because i deleted the iso. i have no evidence to prove that.
but k3b said "the file size is different than the....(something here)" like that.

and i cant run using VBox. it get stuck at mount loop. [remember the days we got errors for SATA drives that state there is no mount point upon live cd boot? thats the same here too]
i cant extract the file either. i used poweriso and 7zip to extract the file, and they ran into checksum or some file errors.

i can't tell anything exactly. i will create a iso and prove to you what it is doing.
Thanks,
Tim

now off to bed

Offline T6

  • Super Villain
  • ******
  • Posts: 19077
  • xmas is comming!
Re: 1.6GB shows 974MB iso
« Reply #3 on: October 23, 2010, 10:16:24 AM »
i have burned other isos reporting this error, it offers the option of burn or cancel, i let it burn

next time you can test with a dvd-rw and brasero, k3b is not the only tool available
"If you wish to make an apple pie from scratch, you must first invent the universe."

Carl Sagan

Tommylee567

  • Guest
Re: 1.6GB shows 974MB iso (SOLVED) [Automatically]
« Reply #4 on: October 29, 2010, 08:12:42 AM »
GOOD NEWS!
sorry i had no net connection on weekdays.

after I updated to the latest kde version and the kernel pclos6.bfs. then unbelievably it works as usual. it didn't put out a 970 mb but 1.6GB.
Correctly i don't know which was the error. the old kernel pclos5.bfs or kde. peculiarly i still used the previous kernel version, and it again did a 1.6Gb.
Now i don't know which was giving the problem.
but now it is solved!

Thanks!
Tim