Member Avatar for Killer_Typo

So i downloaded the ISO, used an md5sum checker to see if the file was good, and it was. so i went to install and this is what happens.

After it gets 100% done i get a message that all packages returned errors during the install (WTH i thought the file was a good file) now when it continues the install (dunno y if the packages all returned errors but hey im gonna go with it) it freezes when writing the boot file, just hangs and doesnt do a thing.

Any help would be greatly appreciated.

  • 3 Contributors
  • 5 Replies
  • 110 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by Surtsey

Dani AI

Generated

reported that the SuSE 9.1 ISO passed an MD5 check but the installer later showed "all packages returned errors" and then hung while writing the boot file. and raised hardware and package-management points; the next steps are targeted diagnostics rather than switching distributions.

An MD5 on the downloaded ISO only proves the file was correct before burning. Corruption can be introduced while burning or during CD reads. Use the installer’s "Check installation media" option at boot. If that is not available or it fails, reburn the ISO at the slowest supported speed and try a different brand of blank media or another drive. To verify the burned disc back to an image for comparison:

dd if=/dev/cdrom of=/tmp/suse91.iso bs=2048 conv=sync
md5sum /tmp/suse91.iso

Package-install failures and an installer hang while writing the boot record commonly point to read/write I/O problems (bad media, bad optical drive, failing HDD, or bad RAM). Run the bootable memtest86 (usually on the CD boot menu) for at least one full pass. While the installer is running, switch to a console (Ctrl+Alt+F2) and inspect kernel and system logs for I/O errors:

dmesg | egrep -i 'io|error|fail|read'
tail -n 200 /var/log/messages

If the bootloader write stalls, skip installing the bootloader during the installer and finish the install. Then use a rescue shell to chroot into the new system and install GRUB manually (replace hdaX with the root partition):

mount /dev/hdaX /mnt
mount --bind /dev /mnt/dev
chroot /mnt
grub-install /dev/hda

Note: YaST2 does perform dependency checks for RPMs, so the package errors are more likely I/O-related than unresolved RPM dependencies. If problems persist after trying a different burn/drive and running memtest, test the HDD SMART data from a rescue environment or try a network/FTP install to avoid the optical media path.

Recommended Answers

All 5 Replies

Member Avatar for Surtsey

1) I think you should check your partitions and make sure you've got them setup properly. Perhaps try another filesystem than you're already using?

2) This sounds stupid, but are you positive your HDD works fine? Have you recently had other operating systems on it?

3) This is slightly stupid as well - are you sure your CD drive doesn't have any issues? I've had problems before where my CD drive would work fine in short burst situations like moving files in Windows, but when installing an OS it would just die right then and there.

Member Avatar for Killer_Typo

1) I think you should check your partitions and make sure you've got them setup properly. Perhaps try another filesystem than you're already using?

2) This sounds stupid, but are you positive your HDD works fine? Have you recently had other operating systems on it?

3) This is slightly stupid as well - are you sure your CD drive doesn't have any issues? I've had problems before where my CD drive would work fine in short burst situations like moving files in Windows, but when installing an OS it would just die right then and there.

1. partitions should be fine. i just had linux redhat fedora core on it

2. same as above.

3. wouldnt be suprized cd drive sucks.

Member Avatar for Surtsey

Yet another rubbish sort of answer (I really don't know crap about Linux) but what are you selecting on the CD boot menu? Your case sounds just like a guy I know who was selecting 'manual install' rather than just 'install'.

Member Avatar for Member #2466

Why SuSe? SuSe uses RPM's which don't resolve dependencies...this makes software installation a huge headache if you don't have the right software already installed.

If you want a kick butt, easy to install, easy to upgrade distro with dependency resolution in the package management scheme...try MEPIS.

Download from

Member Avatar for Surtsey

What are you talking about? YaST2 checks dependencies AND makes almost every single install easy. YaST2's included with SuSE.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.