I still get this error when remastering from 1.0.5final - if I had OpenOffice to try & make a chubby:
"mkdir: cannot create directory '/new_root': No space left on device"
which then causes all sorts of failures through the boot sequence..
Seems like the size is a problem.
It tells me to set ramdisk_size=12614 in isolinux.cfg since it's 12288 max
I tried this but to no avail.
I looked at Chubby 1.0.4 & that doesn't have any such entry in isolinux.cfg.
It doesn't seem to have much bigger files either:
Chubby_1.0.4: 6.8Mb image.gz & 92Mb usr_cram.fs
1.0.5+OO.o PupGet via PCCC: 7.2 Mb image.gz & 74 Mb usr_cram.fs
Am I doing something wrong?
How did you create the real Chubby?
- via unleashed, I guess?
- so this is probably my only option...
Would be good to know what's going on here, though...
F
1.0.5rc: PCCC bugs (partitions, menus, etc)
It fails even with ramdisk_size=15000
I see that the sizes of the 1.0.5 Chubby (which I'm seeding now) are:
image.gz 7.4Mb
usr_cram.fs 87Mb
What determines the size needed for the ramdisk?
Just size of image.gz?
- uncompressed, rather than compressed?
I see that the 1.0.5 chubby has an uncompresed image of 13631 - same size as ramdisk.
My failed image was 12916, so the calculation seems correct...but a ramdisk_size of 15000 is insufficient
Can it be too large as well as too small?
F
I see that the sizes of the 1.0.5 Chubby (which I'm seeding now) are:
image.gz 7.4Mb
usr_cram.fs 87Mb
What determines the size needed for the ramdisk?
Just size of image.gz?
- uncompressed, rather than compressed?
I see that the 1.0.5 chubby has an uncompresed image of 13631 - same size as ramdisk.
My failed image was 12916, so the calculation seems correct...but a ramdisk_size of 15000 is insufficient
Can it be too large as well as too small?F
-
kirk
I'm having the same problem. I added xine extra codecs, nmap, monkey web server dot pup, and abiword us-dict dot pup. I added a couple printers using the printer wizard and ran the ethernet wizard. Then I ran PCCC. everything seemed to go fine, it said to set ramdisk_size = 13147. I set it to 18000. When I tried to boot the CD it gave the message "/new_root': No space left on device". I'll try it again, maybe I had a typo with the ramdisk_size or could I have made it too big? I put the ramdisk_size on a line right before the line with "say 2 no APCI ....".
Almost forgot,on the boot screen, right before the line with the boot options it posts this message twice "Missing parameter in config file."
Almost forgot,on the boot screen, right before the line with the boot options it posts this message twice "Missing parameter in config file."
-
BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Okay guys,
try this one!
It should correctly resize the ramdisk.
Also:
When the script asks you to edit isolinux.cfg with "ramdisk_size="
be sure to insert it for every boot option, in the same line as the
PFILE parameter.
let me know if it works.
try this one!
It should correctly resize the ramdisk.
Also:
When the script asks you to edit isolinux.cfg with "ramdisk_size="
be sure to insert it for every boot option, in the same line as the
PFILE parameter.
let me know if it works.
- Attachments
-
- createpuppyonline.gz
- (16.11 KiB) Downloaded 398 times
ok, will get this script tested.
re: the 'remaster from remaster' issue, I'm pretty sure I've licked it!
It's because I've removed rxvt (to replace it with mrxvt)
Placing a symlink from rxvt to mrxvt has resolved it
It was affecting the whole Pupget package manager, running from CLI (as you mentioned in another thread) allowed me to debug it...
Thx,
F
re: the 'remaster from remaster' issue, I'm pretty sure I've licked it!
It's because I've removed rxvt (to replace it with mrxvt)
Placing a symlink from rxvt to mrxvt has resolved it
It was affecting the whole Pupget package manager, running from CLI (as you mentioned in another thread) allowed me to debug it...
Thx,
F
Spoke too early :/
Pupget now works fine (with the symlink) but PCCC exhibits the same behaviour when doing 'remaster from remaster'.
Running 'createpuppyonline' from the CLI, I see the following output:
ls: /root/.packages/*.files: No such file or directory
/tmp/rettags.txt has all the tags (package names) chosen to be in Puppy.
/usr/sbin/createpuppyonline: line 589: 3372 Terminated xmessage -center -bg "orange" -title "Puppy Custom CD" -buttons "" "Processing package choices, please wait..."
ls: /root/.packages/*.files: No such file or directory
mount: /dev/hdc is write-protected, mounting read-only
Copying vmlinuz, image.gz, isolinux.bin, isolinux.cfg off CD...
Uncompressing /livecd/image.gz to /root/image...
26624+0 records in
26624+0 records out
Also copying boot.msg, goofy.16 off CD...
Mounting /root/image on /mnt/image...
/usr/sbin/createpuppyonline: line 807: 5941 Terminated xmessage -center -bg "orange" -title "Puppy Custom CD" -buttons "" "Reading files from CD, please wait..."
/usr/sbin/createpuppyonline: line 816: 6001 Terminated xmessage -center -bg "orange" -title "Puppy Custom CD" -buttons "" "Copying usr_cram.fs files, please wait..."
cp: cannot stat `/tmp/sshd.files': No such file or directory
cp: cannot stat `/tmp/mrxvt-0.4.1.files': No such file or directory
mkdir: cannot create directory `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/.packages': File exists
cp: cannot stat `/tmp/less-382.files': No such file or directory
mkdir: cannot create directory `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/.packages': File exists
mkdir: cannot create directory `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/.packages': File exists
cp: cannot stat `/tmp/flash.files': No such file or directory
mkdir: cannot create directory `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/.packages': File exists
mkdir: cannot create directory `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/.packages': File exists
cp: cannot stat `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/*': No such file or directory
ls: /root/.packages/*.files: No such file or directory
/usr/sbin/createpuppyonline: line 979: 6050 Terminated xmessage -center -bg "orange" -title "Puppy Custom CD" -buttons "" "Moving PupGets, please wait..."
The /tmp/<package>.files are the DotPups installed into my remaster, which work fine.
- no problems in this area, so 'error' can safely be ignored, I think.
My guess as to why PCCC fails to download new packages scheduled for removal is either:
mkdir: cannot create directory `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/.packages': File exists
OR
cp: cannot stat `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/*': No such file or directory
I'm going to do another remaster from fresh, so I'll capture the output from that one...
F
Pupget now works fine (with the symlink) but PCCC exhibits the same behaviour when doing 'remaster from remaster'.
Running 'createpuppyonline' from the CLI, I see the following output:
ls: /root/.packages/*.files: No such file or directory
/tmp/rettags.txt has all the tags (package names) chosen to be in Puppy.
/usr/sbin/createpuppyonline: line 589: 3372 Terminated xmessage -center -bg "orange" -title "Puppy Custom CD" -buttons "" "Processing package choices, please wait..."
ls: /root/.packages/*.files: No such file or directory
mount: /dev/hdc is write-protected, mounting read-only
Copying vmlinuz, image.gz, isolinux.bin, isolinux.cfg off CD...
Uncompressing /livecd/image.gz to /root/image...
26624+0 records in
26624+0 records out
Also copying boot.msg, goofy.16 off CD...
Mounting /root/image on /mnt/image...
/usr/sbin/createpuppyonline: line 807: 5941 Terminated xmessage -center -bg "orange" -title "Puppy Custom CD" -buttons "" "Reading files from CD, please wait..."
/usr/sbin/createpuppyonline: line 816: 6001 Terminated xmessage -center -bg "orange" -title "Puppy Custom CD" -buttons "" "Copying usr_cram.fs files, please wait..."
cp: cannot stat `/tmp/sshd.files': No such file or directory
cp: cannot stat `/tmp/mrxvt-0.4.1.files': No such file or directory
mkdir: cannot create directory `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/.packages': File exists
cp: cannot stat `/tmp/less-382.files': No such file or directory
mkdir: cannot create directory `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/.packages': File exists
mkdir: cannot create directory `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/.packages': File exists
cp: cannot stat `/tmp/flash.files': No such file or directory
mkdir: cannot create directory `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/.packages': File exists
mkdir: cannot create directory `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/.packages': File exists
cp: cannot stat `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/*': No such file or directory
ls: /root/.packages/*.files: No such file or directory
/usr/sbin/createpuppyonline: line 979: 6050 Terminated xmessage -center -bg "orange" -title "Puppy Custom CD" -buttons "" "Moving PupGets, please wait..."
The /tmp/<package>.files are the DotPups installed into my remaster, which work fine.
- no problems in this area, so 'error' can safely be ignored, I think.
My guess as to why PCCC fails to download new packages scheduled for removal is either:
mkdir: cannot create directory `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/.packages': File exists
OR
cp: cannot stat `/mnt/home/puppy/puppy-unleashed/rootfs-complete/root/*': No such file or directory
I'm going to do another remaster from fresh, so I'll capture the output from that one...
F
-
BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Running createpuppyonline from the commandline spits out lots of messages
that may seem like errors but they aren't.
The important thing is, the script fixes the size of image.gz problem.
Previously, you would have seen lots of error messages about not enough
room, "No space left on device".
So, previously the iso file itself was corrupted, that is, files missing from
image.gz.
I successfully created a iso with OO.
I didn't have any problem with downloading packages that are to be removed
-- that's a different problem, and so far I can't reproduce it.
that may seem like errors but they aren't.
The important thing is, the script fixes the size of image.gz problem.
Previously, you would have seen lots of error messages about not enough
room, "No space left on device".
So, previously the iso file itself was corrupted, that is, files missing from
image.gz.
I successfully created a iso with OO.
I didn't have any problem with downloading packages that are to be removed
-- that's a different problem, and so far I can't reproduce it.
-
kirk
pccc
Barry,
I tried the script. That took care of the out of space problem, but now I'm getting this:
Mounting /proc: Can't find /proc in /etc/fstab
Pausing for 60 seconds...
Remounting root rw: can't find / in /etc/fstab
Pausing for 60 seconds...
I tried it twice, same result both times. I'm still adding these options to the 105 image: xine extra codecs, nmap, Abiword US dictionary Dotpup, Monkey web server Dotpup and now the "SP1" patch.
thanks,
kirk
I tried the script. That took care of the out of space problem, but now I'm getting this:
Mounting /proc: Can't find /proc in /etc/fstab
Pausing for 60 seconds...
Remounting root rw: can't find / in /etc/fstab
Pausing for 60 seconds...
I tried it twice, same result both times. I'm still adding these options to the 105 image: xine extra codecs, nmap, Abiword US dictionary Dotpup, Monkey web server Dotpup and now the "SP1" patch.
thanks,
kirk