mylivecd fails again: can't access tty; job control turned off

[Klinux]

And again, PClinuxOS 2010 together with mylivecd fail with me.

What have I done?

Installed PClinuxOS2010 XFCE in VirtualBox (ISO is not a bad download because it has been working other times, around other 100 times!!)
Changed wallpaper, theme, icons, removed some programs, installed other programs,....
Run:

Code: [Select]

umount -a
mylivecd --lzma --md5sum live.iso

Image created is fine, no errors.

Burned image (trying with both Brasero and XFburn) on:
1 used DVD-RW = nogo
2 brand new DVD-RW = nogo

Burning is fine on all three media
When I reboot with one of these just created livecd in both VirtualBox and on real hardware i get:

Code: [Select]

ERROR: Unabel to mount loop filesystem
  Commands where:
  losetup /dev/loop0 initrd/cdrom/livecd.sqf
  mount -r -t squashfs /dev/loop0 initrd/loopfs
  Most likely cause is bad burn or bad download
  Please run mediacheck on livecd

      Dropping you to a limited shell
  Loading /initrd/bin/ash
/initrd/bin/ash: can't access tty; job control turned off
$_

These solutions are not the solutions for me:

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

System is up to date


So, what is the problem this time?
I cannot permit myself to loose so much time in configuring something which takes day and then throw it all away.

Please I really need this working

mylivecd and the radically simple to use are the 2 main reason I use this distro since years now.

Thanks

[Was_Just19]

First question is ............  does the ISO boot in VBox without burning it to any media?

[Klinux]

If you mean the original ISO:
The ISO works in VirtualBox without burning it anywhere, and the ISO works also when burned cause that's the way I have installed my 2nd PC.

[Texstar]

If you mean the original ISO:
The ISO works in VirtualBox without burning it anywhere, and the ISO works also when burned cause that's the way I have installed my 2nd PC.

Does the new ISO file you created boot in Virtualbox?

Such as copying the ISO file out of virtualbox to your hard drive via shared folders then telling Virtualbox to boot from it.

[Klinux]

I am going to try this now, but how can I find the shared folders in Linux? I know how to do what you mea if using a windows host, but not in Linux

[rubentje1991]

Or put it on a USB flash drive
=> then you need the PUEL version of VirtualBox, which you can get by installing "getvirtualbox" from Synaptic, and then running that script (PCMenu >> More Programs >> Emulators >> Get Oracle VM VirtualBox

Your virtual machines don't get lost by doing this (changing from OSE to PUEL)

Then you can copy it from the flash drive to your real hard disk, and add a new vm which starts up from the iso...
(I also don't know anything about network shares in PCLinuxOS - never had to use them...)

[rubentje1991]

Remastering from VirtualBox frequently gives problems,
(ISO's that doesn't start, etc...), so try indeed as the others stated first if the ISO works in VirtualBox...

[Klinux]

I still cannot find how to do what you ment,
Host is Windows XP guest PCLOS.

I updated the kernel to the latest version (kernel-2.6.33.7-pclos6.bfs) but now I cannot even create a mylivecd.
The kernels I have installed in synaptic are:
kernel-2.6.32.11-pclos2.bfs
kernel-2.6.32.24-pclos1.bfs
kernel-2.6.33.7-pclos6.bfs

and other kernel-devel

can somebody also explaine me how the kernel works? Why so many kernels? What is bfs? What is the pclos number?

Now when creating the mylivecd i get this error:
mod: cannot access `/tmo/mylivecd.3475/livecd/livecd.sqfs No such file or directory
DIE
FATAL: Execution of chmod 644 /tmo/mylivecd.3475/livecd/livecd.sqfs failed

[Texstar]

Now when creating the mylivecd i get this error:
mod: cannot access `/tmo/mylivecd.3475/livecd/livecd.sqfs No such file or directory
DIE
FATAL: Execution of chmod 644 /tmo/mylivecd.3475/livecd/livecd.sqfs failed

That means you either don't have enough free space to create the ISO OR the ISO you are trying to create is exceeding the maximum size of a squashfs filesystem of 4 gigs. In other words you can't expect to compress 15-20 gigs of data into a 4 gig compressed image. Also is that a typo for your /tmp folder (tmo)?

[Texstar]

I still cannot find how to do what you ment,
Host is Windows XP guest PCLOS.

I updated the kernel to the latest version (kernel-2.6.33.7-pclos6.bfs) but now I cannot even create a mylivecd.
The kernels I have installed in synaptic are:
kernel-2.6.32.11-pclos2.bfs
kernel-2.6.32.24-pclos1.bfs
kernel-2.6.33.7-pclos6.bfs

and other kernel-devel

can somebody also explaine me how the kernel works? Why so many kernels? What is bfs? What is the pclos number?

The kernel is what runs boots and runs. It is the heart of Linux. You only need one kernel. BFS is a modified kernel that uses a special scheduler designed for the best desktop performance in a multi-tasking environment. You should boot into the 2.6.33.7 kernel and remove the other two as they are not needed.  The pclos6 means that is the 6th version of this kernel series and contains additional security/bug patches to make it secure and stable.

[parnote]

And again, PClinuxOS 2010 together with mylivecd fail with me.

What have I done?

Installed PClinuxOS2010 XFCE in VirtualBox (ISO is not a bad download because it has been working other times, around other 100 times!!)
Changed wallpaper, theme, icons, removed some programs, installed other programs,....
Run:

Code: [Select]

umount -a
mylivecd --lzma --md5sum live.iso


BPSoftware,

Try altering your mylivecd command to exclude your /home and /tmp directory, like this:

Code: [Select]

[b]mylivecd --lzma --nodir=^/home,^/tmp --md5sum live.iso[/b]
It will result in a much smaller ISO file. If you need/want the info in your /home directory, it'll probably be best to either burn the files to a CD/DVD (great, cuz you have a backup then), or put the data into a .tar.gz file and transfer it to a USB flash drive.

parnote

[Klinux]

I have removed the kernels and only have one type of kernel (I hope):

kernel-2.6.33.7-pclos6.bfs
kernel-2.6.33.7-pclos6.pae
kernel-2.6.33.7-pclos6.a64
kernel-2.6.33.7-pclos6. (another I don't remember now)

Are this modules of the kernel, or just literally different kernels?

However, the image creation goes fine again now, I now have an image created of 900 MB ~
But on reboot the livecd still gives the same errors

[rubentje1991]

I have removed the kernels and only have one type of kernel (I hope):

kernel-2.6.33.7-pclos6.bfs
kernel-2.6.33.7-pclos6.pae
kernel-2.6.33.7-pclos6.a64
kernel-2.6.33.7-pclos6. (another I don't remember now)

Are this modules of the kernel, or just literally different kernels?

However, the image creation goes fine again now, I now have an image created of 900 MB ~
But on reboot the livecd still gives the same errors

That all are separate kernels... 

[Klinux]

I fixed all the kernel stuff, now there only is one up to date kernel.
There is enough free space for creating the image, the image is created successfully.
VirtualBox on my Windows XP host is up to date to the latest version.

What can I do now?

[Klinux]

Yesterday magically I recreated the mylivecd image and reburned using XFburn on one of the same media's cited above.
Now it works.
The only things I have done in between are:
- Updating VirtualBox
- Removing all the other kernels and using the latest BFS kernel

I think it was VirtualBox, probably the older version had a bug in the burning process, but am not sure, hope I don't get this anymore.
Thanks for your help guys.