VMware 8 PCLOS Remaster with 3.2.18-pclos2.pae.bsf fails to load livecd.sqfs

[x2611]

VMware 8 PCLOS using 2.6.33.7-pclos6.bfs install remastered to load on other PC's

The 2.6.33.7 remasters have been flawless on every machine since I installed it originally.
Upgraded kernel to 3.2.18-pclos2.pae.bsf, now the remaster of this fails while loading livecd.sqfs.
I am using Universal-USB-Installer-1.9.1.5.exe to make bootable pendrives.

Error: Unable to mount loop filesystem
Commands were:
losetup /dev/loop0 initrd/cdrom/livecd.sqfs
mount -t -t squashfs /dev/loop0 initrd/loopfs
Most likely caused by bad burn or bad download
Please run mediacheck on livecd

livecd.sqfs size is 1,75 GB (1 890 029 568 bytes)

Tried writing it out to DVD and the same thing happens. I vaguely remember reading somewhere that remasters with non original kernels will not work, but I can't find the thread.

Thanks

[pags]

It could, of course, be a bad re-master...could try another (perhaps with lighter compression?) to see if that is any better.

The other consideration is the hardware you are trying to boot on.  Not only did you change the kernel version, you've also opted to upgrade it to the "pae" model.  This will no boot on older CPUs if they do not support (or, do not have enabled in the BIOS) the required PAE extensions.

Additionally, have you considered using the PCLOS LiveUSB creator?

[x2611]

Thanks Pags.

Tried it on ASUS-K73SD, Eeepc-1000hab and a desktop with Core2duo. None are too old. Same results. The ISO with 2.6.33.7-pclos6.bfs from the same PCLOS install works great. I tried the non PAE version as well, still no good.

So I guess it's the 3.2 kernel they don't like. Oh well I guess I have to stick with 2.6.

So much for upgrading 

[TerryN]

The 2.6.33.7 remasters have been flawless on every machine since I installed it originally.
Upgraded kernel to 3.2.18-pclos2.pae.bsf, now the remaster of this fails while loading livecd.sqfs.

What was the exact command-line you used to create the remaster ?

Terry.

[Just17]

Thanks Pags.

Tried it on ASUS-K73SD, Eeepc-1000hab and a desktop with Core2duo. None are too old. Same results. The ISO with 2.6.33.7-pclos6.bfs from the same PCLOS install works great. I tried the non PAE version as well, still no good.

So I guess it's the 3.2 kernel they don't like. Oh well I guess I have to stick with 2.6.

So much for upgrading 

On the assumption there was no error message when creating the remaster, it could be that the media you are using is not good.
Have you checked the MD5sum of the livecd squash file on the boot media against the file in the ISO?

[x2611]

The 2.6.33.7 remasters have been flawless on every machine since I installed it originally.
Upgraded kernel to 3.2.18-pclos2.pae.bsf, now the remaster of this fails while loading livecd.sqfs.

What was the exact command-line you used to create the remaster ?

Terry.

default remasterme

[x2611]

Thanks Pags.

Tried it on ASUS-K73SD, Eeepc-1000hab and a desktop with Core2duo. None are too old. Same results. The ISO with 2.6.33.7-pclos6.bfs from the same PCLOS install works great. I tried the non PAE version as well, still no good.

So I guess it's the 3.2 kernel they don't like. Oh well I guess I have to stick with 2.6.

So much for upgrading  

On the assumption there was no error message when creating the remaster, it could be that the media you are using is not good.
Have you checked the MD5sum of the livecd squash file on the boot media against the file in the ISO?

No errors during remaster. I make a livecd PENDRIVE, like I mentioned in original post, with Universal-USB-Installer-1.9.1.5.exe. I'm done with cd's exactly because of this bullshit. It's a $100 Kingston Digital DataTraveler 101 Generation 2 - 32 GB Flash Drive. The ISOs boot fine on the VM.

[TerryN]

default remasterme

That will be a problem because remasterme calls mylivecd with --lzma which will not work with kernels newer than 2.6.37.
Your options are to use the mylivecd command directly as recommended here which will use the correct option by default. Alternatively you can edit the remasterme script to remove the --lzma option.

Terry.

[Just17]

Thanks Pags.

Tried it on ASUS-K73SD, Eeepc-1000hab and a desktop with Core2duo. None are too old. Same results. The ISO with 2.6.33.7-pclos6.bfs from the same PCLOS install works great. I tried the non PAE version as well, still no good.

So I guess it's the 3.2 kernel they don't like. Oh well I guess I have to stick with 2.6.

So much for upgrading  

On the assumption there was no error message when creating the remaster, it could be that the media you are using is not good.
Have you checked the MD5sum of the livecd squash file on the boot media against the file in the ISO?

No errors during remaster. I make a livecd PENDRIVE, like I mentioned in original post, with Universal-USB-Installer-1.9.1.5.exe. I'm done with cd's exactly because of this bullshit. It's a $100 Kingston Digital DataTraveler 101 Generation 2 - 32 GB Flash Drive. The ISOs boot fine on the VM.

You did not answer the question ... I wasn't interested in the cost of the media 

[mr-roboto]

I'm uncertain if this is the same problem, but I posted this a while back, about my issues with 3.2.18-pclos2.bfs.   My conclusion was that a certain package (Java in my case) induced the failure you describe.  I too had many successes with the previous 2.6-based remasters and suddenly I was making coaster after coaster.  I'm still uncomfortable about making a correlation between installation of a package and a failed remaster, but this is the information I've compiled.  I'm posting this msg from a live CD session, based on one of my successes.

I zeroed in on my problem child via VMWare, incrementally adding pkgs to the system, and not committing to media til I could boot under VMWare from an ISO.  HTH....

[x2611]

Thanks Pags.

Tried it on ASUS-K73SD, Eeepc-1000hab and a desktop with Core2duo. None are too old. Same results. The ISO with 2.6.33.7-pclos6.bfs from the same PCLOS install works great. I tried the non PAE version as well, still no good.

So I guess it's the 3.2 kernel they don't like. Oh well I guess I have to stick with 2.6.

So much for upgrading  

On the assumption there was no error message when creating the remaster, it could be that the media you are using is not good.
Have you checked the MD5sum of the livecd squash file on the boot media against the file in the ISO?

No errors during remaster. I make a livecd PENDRIVE, like I mentioned in original post, with Universal-USB-Installer-1.9.1.5.exe. I'm done with cd's exactly because of this bullshit. It's a $100 Kingston Digital DataTraveler 101 Generation 2 - 32 GB Flash Drive. The ISOs boot fine on the VM.

You did not answer the question ... I wasn't interested in the cost of the media  

No Just17 I didn't. I don't have time for such crap. But I will do so just to get this out of the way. I don't understand how my images could get corrupt "all of a sudden". As I said before all previous 2.6.x remasters were perfect. Same VM, same install, same pendrive. I like TerryN's suggestion with the --lzma option. He might be onto something because it's definitely a kernel issue. I will give it a try and get back on it...

[x2611]

I'm uncertain if this is the same problem, but I posted this a while back, about my issues with 3.2.18-pclos2.bfs.   My conclusion was that a certain package (Java in my case) induced the failure you describe.  I too had many successes with the previous 2.6-based remasters and suddenly I was making coaster after coaster.  I'm still uncomfortable about making a correlation between installation of a package and a failed remaster, but this is the information I've compiled.  I'm posting this msg from a live CD session, based on one of my successes.

I zeroed in on my problem child via VMWare, incrementally adding pkgs to the system, and not committing to media til I could boot under VMWare from an ISO.  HTH....

I'll check this out too, roboto, thanks.

[Just17]

Thanks Pags.

Tried it on ASUS-K73SD, Eeepc-1000hab and a desktop with Core2duo. None are too old. Same results. The ISO with 2.6.33.7-pclos6.bfs from the same PCLOS install works great. I tried the non PAE version as well, still no good.

So I guess it's the 3.2 kernel they don't like. Oh well I guess I have to stick with 2.6.

So much for upgrading  

On the assumption there was no error message when creating the remaster, it could be that the media you are using is not good.
Have you checked the MD5sum of the livecd squash file on the boot media against the file in the ISO?

No errors during remaster. I make a livecd PENDRIVE, like I mentioned in original post, with Universal-USB-Installer-1.9.1.5.exe. I'm done with cd's exactly because of this bullshit. It's a $100 Kingston Digital DataTraveler 101 Generation 2 - 32 GB Flash Drive. The ISOs boot fine on the VM.

You did not answer the question ... I wasn't interested in the cost of the media  

No Just17 I didn't. I don't have time for such crap. Besides, I don't understand how my images could get corrupt "all of a sudden". As I said before all previous 2.6.x remasters were perfect. Same VM, same install, same pendrive. I like TerryN's suggestion with the --lzma option. He might be onto something because it's definitely a kernel issue. I will give it a try and get back on it...

What a lovely attitude.

Someone attempts to help and they get this response .....  real nice!

Hopefully you will begin to understand a lot more in the future and won't have to put up with crappy suggestions!

Have a nice day!

[x2611]

Thanks Pags.

Tried it on ASUS-K73SD, Eeepc-1000hab and a desktop with Core2duo. None are too old. Same results. The ISO with 2.6.33.7-pclos6.bfs from the same PCLOS install works great. I tried the non PAE version as well, still no good.

So I guess it's the 3.2 kernel they don't like. Oh well I guess I have to stick with 2.6.

So much for upgrading  

On the assumption there was no error message when creating the remaster, it could be that the media you are using is not good.
Have you checked the MD5sum of the livecd squash file on the boot media against the file in the ISO?

No errors during remaster. I make a livecd PENDRIVE, like I mentioned in original post, with Universal-USB-Installer-1.9.1.5.exe. I'm done with cd's exactly because of this bullshit. It's a $100 Kingston Digital DataTraveler 101 Generation 2 - 32 GB Flash Drive. The ISOs boot fine on the VM.

You did not answer the question ... I wasn't interested in the cost of the media  

No Just17 I didn't. I don't have time for such crap. Besides, I don't understand how my images could get corrupt "all of a sudden". As I said before all previous 2.6.x remasters were perfect. Same VM, same install, same pendrive. I like TerryN's suggestion with the --lzma option. He might be onto something because it's definitely a kernel issue. I will give it a try and get back on it...

What a lovely attitude.

Someone attempts to help and they get this response .....  real nice!

Hopefully you will begin to understand a lot more in the future and won't have to put up with crappy suggestions!

Have a nice day!

Oh Just! Get over yourself. I wasn't trying to be rude and I appreciate your input. I'm just frustrated with the constant battle with this stupid operating system, things breaking every time there is a change somewhere.

For example, lets say Terry is right about the compression. WHY will --lzma not work with kernels newer than 2.6.37???
WHY WHY WHY? It's freakin' lzmw compression for crying out loud!! It should work!

See what I mean?
No worries mate..

[TerryN]

For example, lets say Terry is right about the compression. WHY will --lzma not work with kernels newer than 2.6.37???
WHY WHY WHY? It's freakin' lzmw compression for crying out loud!! It should work!

A simple search of the forum would reveal the answer http://www.pclinuxos.com/forum/index.php/topic,89314.msg747855.html#msg747855

Terry.