Info To Upstream CentOS Mirror: File CentOS/7.0.1406/os/x86_64/LiveOS/squashfs.img IS CORRUPT !

Home » CentOS » Info To Upstream CentOS Mirror: File CentOS/7.0.1406/os/x86_64/LiveOS/squashfs.img IS CORRUPT !
CentOS 2 Comments

Hello,

i’ve been struggling hard to setup our automated PXE/kickstart system using various local mirrors but it alway hung after partitioning with no further exception. When I
encountered squshfs errors on the Console (text based / kickstart installation) I re-synced (rsync)
with CERN mirror afterwards with switch.ch mirror and fh-esslingen – But the squashfs image remained corrupt.

To prove my suspicion i’ve finally copied the file from Netboot.iso into our local mirror and voil

2 thoughts on - Info To Upstream CentOS Mirror: File CentOS/7.0.1406/os/x86_64/LiveOS/squashfs.img IS CORRUPT !

  • Well, what would be good is to give the checksum of your local file before claiming it’s corrupt everywhere :-)
    The sha1sum from that squashfs image on the master mirror and on the DVD
    iso is the same :
    693a52b00ac5a6d2e6e2a645352a3c2649578c5f squashfs.img

    So probably you got it corrupted during you transfer. I guess also that you have not it anymore, but this hasn’t changed on the CentOS controlled mirrors.

    Cheers,

  • Of course you are right regarding my statement and I should have been more modest with my words and claim – but indeed I’ve stored a backup named .bak in the mirror directory without thinking about rsync that obviously deleted the file during it’s next scheduled sync that same night –

    BUT I’ve tried 3 different local mirrors to sync with before making this claim and as of today the file and checksum I find on my disk and local mirror indeed is the same I have checking the same file from a freshly downloaded NetInstall.iso – the same you do:

    693a52b00ac5a6d2e6e2a645352a3c2649578c5f (checked using sha1sum)

    But friday night it was not! But let’s stop to worry about that now and I’ll choose my words a little wiser next time.

    Best regards and thank you trying to confirm this issue nevertheless.

    Best regards Andreas Balg