Extract tar error

Message

rth · Post by **rth** » Tue Sep 24, 2002 3:13 am

When I extract the tarball that I download during the install process, I get an error saying that it's a delayed exit from errors. I can continue the install, which is what I'm doing now, but I don't know what the errors were when I extracted the stage3 tar file.

This is for 1.4_rc1 optimized for the Athlon XP.

Edit:
Once I get farther along (Step 28), I can't copy the bzImage because it's a read-only file system?

Edit2:
The stage2 tarball gives the same error...

"tar: Error exit delayed from previous errors"

Edit3:
Taking off the v option from the extraction, I get:
"tar: ./boot/boot: Cannot create symlink to '.': Read-only file system"

Taking a look at what has been mounted, everything is rw except the cdrom, which is ro.

Any ideas?

rac · Post by **rac** » Tue Sep 24, 2002 5:03 am

It sounds like either your target partition is not mounted unter /mnt/gentoo, or you did not "cd /mnt/gentoo" before executing the tar unpack command, so it is trying to unpack into the root file system from the CD, and running out of space. Does this sound plausible?

rth · Post by **rth** » Tue Sep 24, 2002 5:06 am

No, not really. I did the mount /dev/hdc3 /mnt/gentoo and /dev/hdc1 /mnt/gentoo/boot without errors. I also did the cd /mnt/gentoo before opening lynx, and then again afterwards for good measure.

rth · Post by **rth** » Tue Sep 24, 2002 5:13 am

Checking what was mounted, I noticed that /dev/hdc1 on /mnt/gentoo/boot was mounted as type vfat. So, I forced it to ext2 with the -t switch. I then tried the tarball again and I got no errors? Interesting...

Curious · Post by **Curious** » Tue Sep 24, 2002 5:21 am

rth wrote:I noticed that /dev/hdc1 on /mnt/gentoo/boot was mounted as type vfat.

Bloody heck.

I had a scope of mounts file system detection code earlier... nothing relevant has changed in the four releases of linux-utils that are in portage. I wonder if the problem is in mke2fs....

-- Curious.

rth · Post by **rth** » Tue Sep 24, 2002 5:39 am

I had to force ext3 with the -t switch as well, otherwise it wouldn't mount.

frog1980 · Post by **frog1980** » Tue Sep 24, 2002 7:49 am

After 3 failed attempts, I discovered this as well. Quite frustrating. Perhaps it is something that could be included in the install guide?

hmm · Post by **hmm** » Sun Feb 23, 2003 2:25 pm

frog1980 wrote:After 3 failed attempts, I discovered this as well. Quite frustrating. Perhaps it is something that could be included in the install guide?

yes it definently should be included in the install guide, took me some time to figure that it didnt like FAT fs..

I posted here too: http://forums.gentoo.org/viewtopic.php? ... highlight=

I think that they need to revise that install guide thouroughly...

cyrillic · Post by **cyrillic** » Sun Feb 23, 2003 6:41 pm

Actually, the solution to this problem is already in the installation instructions :

Before creating filesystems, you may want to initialize the beginning of your HD using dd. Doing this will ensure that your new filesystem will not be mis-indentified by Linux's mounting code. This can be done as follows:

Code listing 6.1: Initializing first 1024 Sectors of HD

# dd if=/dev/zero of=/dev/hdxy bs=1K count=1
Replace /dev/hdxy with the device you wish to "clean."

Warning: The command above will destroy all data from /dev/hdxy. Be careful and check twice which partition you specify for zeroing. If you make a mistake it might result in a loss of data.

hmm · Post by **hmm** » Sun Feb 23, 2003 9:41 pm

cyrillic wrote:Actually, the solution to this problem is already in the installation instructions :

Before creating filesystems, you may want to initialize the beginning of your HD using dd. Doing this will ensure that your new filesystem will not be mis-indentified by Linux's mounting code. This can be done as follows:

Code listing 6.1: Initializing first 1024 Sectors of HD

# dd if=/dev/zero of=/dev/hdxy bs=1K count=1
Replace /dev/hdxy with the device you wish to "clean."

Warning: The command above will destroy all data from /dev/hdxy. Be careful and check twice which partition you specify for zeroing. If you make a mistake it might result in a loss of data.

yes that is correct but they dont mention that FAT can not be used as a BOOT fs before unpacking the stages...

ixion · Post by **ixion** » Sat Mar 15, 2003 8:53 pm

I'm sorry for the topic resurrection (as it's been dead for a month), but I ran into this same issue, and I DID do the 'dd if=/dev/zero of=/dev/hda bs=1k count=1' which did NOT fix the problem. Forcing mount to mount the partition with '-t ext2' seemed to fix it.

And if you get this error and proceed with the install as usual, you will run into problems. I have no clue what causes this issue other than the fact that I've never used this particular hard drive (it came from the office).

edit: I see the 'of=/dev/hdxy', is this partition specific? Could this be my problem? As you see from what I had been doing, I assigned an entire device (hda), and it would wipe the whole drive (at least I thought so). This very well could've been my problem. I'm very sorry for my failure to fully read the instructions. My fault...

Extract tar error

Extract tar error

Re: Extract tar error

same here

Re: same here