Opened 7 years ago

Closed 6 years ago

#17 closed System Defect (fixed)

Error with install modifying hard disk.

Reported by: toomany Owned by: tim
Priority: critical Milestone: 1.5
Component: Installer Version: 1.4
Keywords: partition extraction error Cc:

Description (last modified by kris)

This was a bug with "tar" returning a non-0 exit status when using a lot of partitions apart from the default. I've fixed this in SVN now, and it'll be fixed in the 1.4.1 update here shortly. We've also switched to LZMA compression, which will improve the extraction speed as well :)

Attachments (3)

dmesg.txt (15.4 KB) - added by toomany 7 years ago.
Dmesg
dmesg.2.txt (15.4 KB) - added by toomany 7 years ago.
Dmesg
pciconf.txt (3.1 KB) - added by toomany 7 years ago.
Pciconf

Download all attachments as: .zip

Change History (13)

Changed 7 years ago by toomany

Dmesg

Changed 7 years ago by toomany

Dmesg

Changed 7 years ago by toomany

Pciconf

comment:1 Changed 7 years ago by tim

  • Version changed from 1.3.4 to 1.4-DEV / 1.4-BETA

comment:2 follow-up: Changed 7 years ago by tim

What was the error that you received?

comment:3 in reply to: ↑ 2 ; follow-up: Changed 7 years ago by dejamuse

  • Keywords partition extraction error added
  • Priority changed from major to critical
  • Version changed from 1.4-DEV / 1.4-BETA to 1.4

Replying to tim:

What was the error that you received?

I have the same problem with 1.4 and 1.4RC.
I'm using a Rocketraid 2310 RAID-1 with a pair of 250GB SATA drives (shows up as a single SCSI).

I modded my disk thusly for running Drupal on AMP:

/ 128MB
/swap 3GB
/var 50GB
/var/tmp 3GB
/usr remainder of disk; ~180GB

After a complete install, it barfed with an error about image extraction failure.

I reinstalled and this time I just upped the swap partition to 3GB and added no other partitions and it installed fine. I was using the entire disk and added no boot manager both times.

I did not have this problem with PCBSD1.3, though I can't recall how I partitioned it then.

...Jeff

comment:4 in reply to: ↑ 3 ; follow-up: Changed 7 years ago by dejamuse

Replying to dejamuse:

Replying to tim:

What was the error that you received?

I have the same problem with 1.4 and 1.4RC.
I'm using a Rocketraid 2310 RAID-1 with a pair of 250GB SATA drives (shows up as a single SCSI).

I modded my disk thusly for running Drupal on AMP:

/ 128MB
/swap 3GB
/var 50GB
/var/tmp 3GB
/usr remainder of disk; ~180GB

After a complete install, it barfed with an error about image extraction failure.

I reinstalled and this time I just upped the swap partition to 3GB and added no other partitions and it installed fine. I was using the entire disk and added no boot manager both times.

I did not have this problem with PCBSD1.3, though I can't recall how I partitioned it then.

...Jeff

Me again,

I noticed after install the KDE partitions utility reported a partition that wasn't there, obviously, when I was installing. Is it possible that I used up all the space when partitioning so these could not be installed?

Namely: linprocfs

I noted also that this utility did report partition size.

...Jeff

comment:5 in reply to: ↑ 4 ; follow-up: Changed 7 years ago by dejamuse

Replying to dejamuse:

Replying to dejamuse:

Replying to tim:

What was the error that you received?

I have the same problem with 1.4 and 1.4RC.
I'm using a Rocketraid 2310 RAID-1 with a pair of 250GB SATA drives (shows up as a single SCSI).

I modded my disk thusly for running Drupal on AMP:

/ 128MB
/swap 3GB
/var 50GB
/var/tmp 3GB
/usr remainder of disk; ~180GB

After a complete install, it barfed with an error about image extraction failure.

I reinstalled and this time I just upped the swap partition to 3GB and added no other partitions and it installed fine. I was using the entire disk and added no boot manager both times.

I did not have this problem with PCBSD1.3, though I can't recall how I partitioned it then.

...Jeff

Me again,

I noticed after install the KDE partitions utility reported a partition that wasn't there, obviously, when I was installing. Is it possible that I used up all the space when partitioning so these could not be installed?

Namely: linprocfs

I noted also that this utility did report partition size.

...Jeff

I just did this:

pcbsd# disklabel -r da0s1a
# /dev/da0s1a:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]

a: 482086912 0 4.2BSD 2048 16384 28552
b: 6144000 482086912 swap
c: 488231352 0 unused 0 0 # "raw" part, don't edit

partition b: partition extends past end of unit
partition c: partition extends past end of unit
disklabel: partition c doesn't cover the whole unit!
disklabel: An incorrect partition c may cause problems for standard system utilities


Not sure what all of this means...

I reinstalled PCBSD this time with the following:

/ 128MB
/SWAP 6000MB
/var 50000MB
/var/tmp 3000MB
/usr 170268MB

unused: 8998MB

The result was the same error - so much for that theory...

...Jeff

comment:6 in reply to: ↑ 5 ; follow-up: Changed 7 years ago by dejamuse

Replying to dejamuse:

Replying to dejamuse:

Replying to dejamuse:

Replying to tim:

What was the error that you received?

I have the same problem with 1.4 and 1.4RC.
I'm using a Rocketraid 2310 RAID-1 with a pair of 250GB SATA drives (shows up as a single SCSI).

I modded my disk thusly for running Drupal on AMP:

/ 128MB
/swap 3GB
/var 50GB
/var/tmp 3GB
/usr remainder of disk; ~180GB

After a complete install, it barfed with an error about image extraction failure.

I reinstalled and this time I just upped the swap partition to 3GB and added no other partitions and it installed fine. I was using the entire disk and added no boot manager both times.

I did not have this problem with PCBSD1.3, though I can't recall how I partitioned it then.

...Jeff

Me again,

I noticed after install the KDE partitions utility reported a partition that wasn't there, obviously, when I was installing. Is it possible that I used up all the space when partitioning so these could not be installed?

Namely: linprocfs

I noted also that this utility did report partition size.

...Jeff

I just did this:

pcbsd# disklabel -r da0s1a
# /dev/da0s1a:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]

a: 482086912 0 4.2BSD 2048 16384 28552
b: 6144000 482086912 swap
c: 488231352 0 unused 0 0 # "raw" part, don't edit

partition b: partition extends past end of unit
partition c: partition extends past end of unit
disklabel: partition c doesn't cover the whole unit!
disklabel: An incorrect partition c may cause problems for standard system utilities


Not sure what all of this means...

I reinstalled PCBSD this time with the following:

/ 128MB
/SWAP 6000MB
/var 50000MB
/var/tmp 3000MB
/usr 170268MB

unused: 8998MB

The result was the same error - so much for that theory...

...Jeff

Next...

I reinstalled again with:

/ 10000MB
/SWAP 6000MB
/var 50000MB
/var/tmp 3000MB
/usr 160000

unused: 9394

Barfed again.

Then tried:

/ 128MB
/SWAP 6000MB
/var 50000MB
/var/tmp 3000MB
/usr 179226

But didn't use whole disk. There was one slice called da0s2 with 6MB in it and I used the main slice da0s1.

Barf - same error.

Then I just left off /usr...

/ 179394MB
/SWAP 6000MB
/var 50000MB
/var/tmp 3000MB

It was ok with that. Seems I can't put /usr on a separate partition. Strange.

Help!

...Jeff

comment:7 in reply to: ↑ 6 Changed 7 years ago by dejamuse

Replying to dejamuse:

Replying to dejamuse:

Replying to dejamuse:

Replying to dejamuse:

Replying to tim:

What was the error that you received?

I have the same problem with 1.4 and 1.4RC.
I'm using a Rocketraid 2310 RAID-1 with a pair of 250GB SATA drives (shows up as a single SCSI).

I modded my disk thusly for running Drupal on AMP:

/ 128MB
/swap 3GB
/var 50GB
/var/tmp 3GB
/usr remainder of disk; ~180GB

After a complete install, it barfed with an error about image extraction failure.

I reinstalled and this time I just upped the swap partition to 3GB and added no other partitions and it installed fine. I was using the entire disk and added no boot manager both times.

I did not have this problem with PCBSD1.3, though I can't recall how I partitioned it then.

...Jeff

Me again,

I noticed after install the KDE partitions utility reported a partition that wasn't there, obviously, when I was installing. Is it possible that I used up all the space when partitioning so these could not be installed?

Namely: linprocfs

I noted also that this utility did report partition size.

...Jeff

I just did this:

pcbsd# disklabel -r da0s1a
# /dev/da0s1a:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]

a: 482086912 0 4.2BSD 2048 16384 28552
b: 6144000 482086912 swap
c: 488231352 0 unused 0 0 # "raw" part, don't edit

partition b: partition extends past end of unit
partition c: partition extends past end of unit
disklabel: partition c doesn't cover the whole unit!
disklabel: An incorrect partition c may cause problems for standard system utilities


Not sure what all of this means...

I reinstalled PCBSD this time with the following:

/ 128MB
/SWAP 6000MB
/var 50000MB
/var/tmp 3000MB
/usr 170268MB

unused: 8998MB

The result was the same error - so much for that theory...

...Jeff

Next...

I reinstalled again with:

/ 10000MB
/SWAP 6000MB
/var 50000MB
/var/tmp 3000MB
/usr 160000

unused: 9394

Barfed again.

Then tried:

/ 128MB
/SWAP 6000MB
/var 50000MB
/var/tmp 3000MB
/usr 179226

But didn't use whole disk. There was one slice called da0s2 with 6MB in it and I used the main slice da0s1.

Barf - same error.

Then I just left off /usr...

/ 179394MB
/SWAP 6000MB
/var 50000MB
/var/tmp 3000MB

It was ok with that. Seems I can't put /usr on a separate partition. Strange.

Help!

...Jeff

Now bsdlabel shows:

# /dev/da0s1:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]

a: 367398912 0 4.2BSD 2048 16384 28552
b: 12288000 367398912 swap
c: 488231352 0 unused 0 0 # "raw" part,

don't edit

e: 102400000 379686912 4.2BSD 2048 16384 28552
f: 6144440 482086912 4.2BSD 2048 16384 28552


comment:8 Changed 7 years ago by tim

  • Milestone set to 1.5

The problem has been tracked down to an issue with tar itself. For some reason it isn't playing nice with extracting to multiple partitions.

We'll look into it for the next release, possibly moving to another extraction method, 7zip?

comment:9 Changed 7 years ago by tim

  • Owner set to tim
  • Status changed from new to assigned

comment:10 Changed 6 years ago by kris

  • Description modified (diff)
  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.