mirror-slackware-current fails to create iso's

BCarey · 08-14-2009, 09:59 PM

I'm trying to use mirror-slackware-current.sh to create install disks, but the second cd image fails with:

Code:

Warning: creating filesystem that does not conform to ISO-9660.
mkisofs 2.01.01a23 (i686-pc-linux-gnu)
Scanning ./slackware64/e
Scanning ./slackware64/f
Writing:   Initial Padblock                        Start Block 0
Done with: Initial Padblock                        Block(s)    16
Writing:   Primary Volume Descriptor               Start Block 16
Done with: Primary Volume Descriptor               Block(s)    1
Writing:   Joliet Volume Descriptor                Start Block 17
Done with: Joliet Volume Descriptor                Block(s)    1
Writing:   End Volume Descriptor                   Start Block 18
Done with: End Volume Descriptor                   Block(s)    1
Writing:   Version block                           Start Block 19
Done with: Version block                           Block(s)    1
Writing:   Path table                              Start Block 20
Done with: Path table                              Block(s)    4
Writing:   Joliet path table                       Start Block 24
Done with: Joliet path table                       Block(s)    4
Writing:   Directory tree                          Start Block 28
Done with: Directory tree                          Block(s)    4
Writing:   Joliet directory tree                   Start Block 32
Done with: Joliet directory tree                   Block(s)    4
Writing:   Directory tree cleanup                  Start Block 36
Done with: Directory tree cleanup                  Block(s)    0
Writing:   Extension record                        Start Block 36
Done with: Extension record                        Block(s)    1
Writing:   The File(s)                             Start Block 37
 28.12% done, estimate finish Fri Aug 14 02:56:51 2009
 56.12% done, estimate finish Fri Aug 14 02:56:52 2009
 84.13% done, estimate finish Fri Aug 14 02:56:54 2009
Total translation table size: 0
Total rockridge attributes bytes: 2789
Total directory bytes: 6144
Path table size(bytes): 50
Done with: The File(s)                             Block(s)    17644
Writing:   Ending Padblock                         Start Block 17681
Done with: Ending Padblock                         Block(s)    150
Max brk space used 21000
17831 extents written (34 MB)
tail: option used in invalid context -- 1
Fri Aug 14 02:56:54 MDT 2009 [6175]: CDROM ISO's created of slackware64-current.
Fri Aug 14 02:56:54 MDT 2009 [6175]: The combined exit code for ISO creation is '127'. A a non-zero number here means: something goofed along the way.
Fri Aug 14 02:56:54 MDT 2009 [6175]: Computing MD5 checksums of the ISO's (time consuming).
Fri Aug 14 02:57:14 MDT 2009 [6175]: Resulting ISO files:
-rw-r--r-- 1 carey users 543158272 2009-08-14 02:56 /media/BigChunk1/Slackware64/slackware64-current-iso/slackware64-current-install1.iso
-rw-r--r-- 1 carey users  36517888 2009-08-14 02:56 /media/BigChunk1/Slackware64/slackware64-current-iso/slackware64-current-install2.iso
Fri Aug 14 02:57:14 MDT 2009 [6175]: Done!

I've used this script successfully in the past. Could anyone help me with this?

Thanks,
Brian

GrapefruiTgirl · 08-14-2009, 10:49 PM

I've come across two things while Googling (one of which at least you probably saw in a related thread on LQ):

1) There may be a bug in the `tail` command, depending on exactly how that line in the script formats/executes the `tail`

and

2) Are you executing this on a Slackware system? If not, it may be an issue where the script thinks it's running under Bash, when in fact it isn't (Like on a Debian-esque machine, where /bin/sh is linked to Dash, not Bash).

Hmmmm

Sasha

BCarey · 08-14-2009, 11:05 PM

Sasha,

Thanks for the reply. I am executing it on a slackware system. I'm also thinking that the first error, the ominous "Warning: creating filesystem that does not conform to ISO-9660", occurs well before the tail command.

Brian

GrapefruiTgirl · 08-14-2009, 11:14 PM

Quote:

Originally Posted by BCarey

Sasha,

Thanks for the reply. I am executing it on a slackware system. I'm also thinking that the first error, the ominous "Warning: creating filesystem that does not conform to ISO-9660", occurs well before the tail command.

Brian

Yes, I agree with you about the respective timestamps of the errors; I decided not to mention that part about the "Warning:" because I (possibly incorrectly though) guessed that that warning was thrown because the second/subsequent CD images are not bootable, thereby being "non-conformant to the ISO9660 standard". It is after all a 'warning' rather than a '[fatal-]error'.

Disclaimer: I haven't researched ISO9660 compliance

so not 100% on whether bootable-ness affects compliance.

About the tail command though: if it is for example trying to use `tail` to gather up whatever files it is intending to put into the CD image, and the tail command is borking (hence the tail -- error) then anything from that point on will be borky too.

I currently use the DVD method when I run the mirror script, and have had no troubles. Maybe as a test-run, try that for the heck of it, and see what happens??

Sasha

onebuck · 08-15-2009, 09:32 AM

Hi,

Which version of the script are you using?

Quote:

my version of script;

#!/bin/sh
#
# $Id: mirror-slackware-current.sh,v 1.72 2009/05/20 20:05:59 root Exp root $

Quote:

Alien_Bob's newest script -mirror-slackware-current.sh;
#!/bin/bash
#
# $Id: mirror-slackware-current.sh,v 1.75 2009/06/17 20:52:47 root Exp root $

The difference from the levels of 1.72 & 1.75 are to support the newer releases along with modifications to support x64. I should update my version but I don't pass parameters but edit the script to suit my needs.

What happens when you switch mirrors? It could possibly be a mirror support problem. If the problems is persistent then I would try on another copy of the script if possible. Do you edit the script?

If you think the script is OK then what about changing to the 'DVD' format to see what happens?

BCarey · 08-15-2009, 09:42 AM

Updating to the latest version of the script solved the problem. Thanks all for your help.

Brian