This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Astaro Install Package Checksums Error

Hello, everybody  [:)]

I'm working a brand new astaro install from the ground up and I've run into a problem.
I just bought a bare bones system from Mwave.com.
Here's the skinny:

Pentium Celeron 1000MHz(a)
256MB RAM
20GB Maxtor HDD
Asus TUSI-M Motherboard w/ built in LAN SIS chipset
Netgear FA311 NIC for second
ACER/BEnQ 56x CDROM
Floppy

So, I start the install.  Everything seems to be going just fine.  All hardware is recognized.
Astaro begins to partion and format.
When it gets to the Package Checksum Verification
I get an error of: Oops:0000
CPU: 0
EIP: 0010
EFLAGS: 00010202
and then a bunch of gobbledy gook that looks like memory channels or something...

Any ideas alive out there for this one?  Is there a hardware conflict?  Does astaro not like Maxtor HDDs?  I know Maxtor is real weird when DOS is loaded on it, but this is Linux??? Do I need to load drivers for my NICs? If so, how do I do that before the install?

Thanks in advance for all your help

Vinny

This thread was automatically locked due to age.

0 vleo over 23 years ago

PS to the above post

the Maxtor HDD is a 20GB ATA133 7200 RPM
Cancel
Vote Up 0 Vote Down

Cancel
0 Andy_01 over 23 years ago in reply to vleo

you should check the MD5sum of the ISO file you downloaded if it matches with the one on Astaro's ftp server. Also try another CD or burning software, i heared about problems with nero.
Cancel
Vote Up 0 Vote Down

Cancel
0 vleo over 23 years ago in reply to Andy_01

Thanks man, my version is 3.2.07
I did burn it on Nero but it worked fine on another machine. Do you think the burn would work differntly on different CDROMs?
Cancel
Vote Up 0 Vote Down

Cancel
0 Andy_01 over 23 years ago in reply to vleo

there where some real strange posts about nero burned CDs...
Cancel
Vote Up 0 Vote Down

Cancel
0 vleo over 23 years ago in reply to Andy_01

hmm... well I did read a couple of other posts that stated similar problems. So I procure some other burning software and give it another go...

Thanks for the quick response.

Vinny
Cancel
Vote Up 0 Vote Down

Cancel
0 vleo over 23 years ago in reply to vleo

One other quick question. When I do check the md5sum on the disk what exactly am I looking for as far as defects go? In other words, how do I know mine is bad?
Cancel
Vote Up 0 Vote Down

Cancel
0 vleo over 23 years ago in reply to vleo

Per the other post about the same problem...

Bad RAM...
Cancel
Vote Up 0 Vote Down

Cancel