Unbutu 7.04 installs but gets halted while re-starting

Asked by Kiko Barcelli

I've just downloaded ubuntu 7.04, burn the CD and followed the installation procedure.
The installations went through and asked for re-starting the system.
While restarting, it gets all the way to ubuntu splash screen and then it stops (even the HD light goes off) at about 1% of the boot bar.
The system does not recognise any key but re-starts again if I give ctrl-alt-del, however it'd stop at the same point again.
If I boot it in recovery mode (ESC and then second option) it goes all the way until the following last two lines:

[34.267557] EIP: [<ce8a5625] sis_init_one+0x75/0x3c0 [pata_sis] SS:ESP 0068:cdabfe0c
[34.267775] udev-event[1937] :run_program: '/sbin/modprobe' abnormal exit

Then it waits for some 3 to 5 minutes and then goes ahead with the following:

Done.
       Check root= bootarg car /proc/cmdline
       or missing modules, devices: car /proc/modules is /dev
ALERT! dev/disk/by-uuid/5a2e5ea7-0fe7-4f7e-b4c3-0704d65931d7 does not exist. Dropping to a Shell!

BusyBox v1.1.3 (Debian 1:1.1.3-3ubuntu3) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)

Could you help me out here? Greatly appreciated.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Kiko Barcelli
Solved:
Last query:
Last reply:
Revision history for this message
Rui Bernardo (epimeteo) said :
#1

Boot with a Desktop CD. On Gnome, click "Places" menu, and then "Computer". Double-click the drive that isn't booting so that it is mounted. This disk should be now mounted in /media/disk/. Open a Terminal clicking in the Gnome menu on Applications, Accessories, Terminal. Now type

sudo blkid

This will give you the UUIDs of all mounted drives. Check for the drive that you installed Ubuntu. Compare this UUID with the ones that are in the file /media/disk/etc/fstab, on the drive that isn't booting.

If there is any differences, then update the file /media/disk/etc/fstab in the drive. On the terminal type:

sudo nano /media/disk/etc/fstab

Press Ctrl+X to exit (press Y to save).

This is very strange, and if this doesn't help, I would suggest to install Ubuntu again.

Revision history for this message
Kiko Barcelli (kikobar) said :
#2

I reviewed the file fstab and the UUIDs matched, then I installed again and got the same problem... next I replace the hard drive and got the same problem again.

Any clue?

Revision history for this message
Kiko Barcelli (kikobar) said :
#3

Sorry, I forgot to clarify that I put a new hard drive, installed Ubuntu once again, and then got the same problem...

Revision history for this message
Rui Bernardo (epimeteo) said :
#4

Adding a new hard drive just makes the problem more confusing.

Please post here:

1) the output of "sudo blkid" after doing the steps from my previous post;

2) the content of /media/disk/etc/fstab;

3) the content of /media/disk/boot/grub/menu.lst;

Revision history for this message
Kiko Barcelli (kikobar) said :
#5

Here we go.... I hope you could help... thanks

1)
ubuntu@ubuntu:~$ sudo blkid
/dev/hda1: UUID="48148038-0c3f-4511-b586-f0fe86ad6a69" SEC_TYPE="ext2" TYPE="ext3"
/dev/hda5: TYPE="swap" UUID="b9e77bc4-b2d6-4faa-a702-dd8d9564b1b7"
ubuntu@ubuntu:~$

2)
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/hda1
UUID=48148038-0c3f-4511-b586-f0fe86ad6a69 / ext3 defaults,errors=remount-ro 0 1
# /dev/hda5
UUID=b9e77bc4-b2d6-4faa-a702-dd8d9564b1b7 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/hdd /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

3)
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=48148038-0c3f-4511-b586-f0fe86ad6a69 ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## ## End Default Options ##

title Ubuntu, kernel 2.6.20-15-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=48148038-0c3f-4511-b586-f0fe86ad6a69 ro quiet splash
initrd /boot/initrd.img-2.6.20-15-generic
quiet
savedefault

title Ubuntu, kernel 2.6.20-15-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=48148038-0c3f-4511-b586-f0fe86ad6a69 ro single
initrd /boot/initrd.img-2.6.20-15-generic

title Ubuntu, memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

Revision history for this message
Rui Bernardo (epimeteo) said :
#6

All UUID match, so it's not UUID mismatch. Like I posted previously, I would suggest a new install. But before you try install Ubuntu again, try one of this:

1) check if the md5sum of the ISO file you downloaded matches with the md5sum file from the site you downloaded. This file should be in the same folder where the ISO file was, with the name "MD5SUM". You can do this from the LiveCD Desktop, even if the ISO file is on a Windows partition.

After booting the Desktop CD, click on the menu "Places", then click the drive or partition were the ISO file is. Then click on the menu "Applications", "Accessories" and "Terminal". On the terminal type:

# /media/disk is an example
cd /media/disk
cd /path/to/where/the/iso/file/is
md5sum ubuntu-7.04-desktop-i386.iso

The output should be something like:

e296e3468358789904097fc8df29609a ubuntu-7.04-desktop-i386.iso

2) If the md5sum are equal, then you should test the CD and the computer memory for some defects. You can do this just after booting the CD. Select the following options to check:

Check CD for defects

and

Memory test

3) If all is ok, and you still want to try to "save" the installation you already did then, after booting the Desktop CD, click on the partition where you installed Ubuntu, the go to the /var/log/ folder inside that partition.

Check for the files

dmesg
messages
debug
syslog

to find what went wrong. If you try this last option, you can post the suspicious error messages here.

Revision history for this message
Kiko Barcelli (kikobar) said :
#7

1) Before doing the installation I checked the md5sums and the numbers were identical

2) Before doing the installation I check the CD and ran the memory tests

3) I've checked four files you suggested in the /var/log/ folder and the four of them are empty

I repeated the installation procedure several times with different options of partitioning, but always with the same result... any clue?

Revision history for this message
Rui Bernardo (epimeteo) said :
#8

If you used the Desktop CD and it worked, the installation should work too, unless there is some hardware related problem. Please can you post some hardware info, like motherboard, processor, disk types, sound board, is it a laptop?

Revision history for this message
Kiko Barcelli (kikobar) said :
#9

This is a desktop

Intel Pentium 4 - 2GHz

1.6GiB memory

65x/M650/740 PCI/AGP VGA Display Adapter

IDE (master) Hitachi HDT725050VLAT80

IDE (master) LG DVD-ROM DRD-8160B

IDE (slave) BENQ DVD DD DW1640

USB Scanner Genius ColorPage-HR6 V2

USB Microphone AK5370

USB Cordless telephone Linksys CIT200

AC'97 Sound Controller

AC'97 Modem Controller

SiS900 PCI Fast Ethernet

SiS961 MuTIOL Media IO

NV34 GeForce FX5200

Revision history for this message
Best Kiko Barcelli (kikobar) said :
#10

Thanks for all your help... you were right, it was some conflict of hardware... I remove all the USB devices and now the installation runs... now I am going to installed them one by one to see which is the one creating problems.

Thanks for your patience.

Revision history for this message
Kiko Barcelli (kikobar) said :
#11

For info, I didn't just remove the devices and boot it, I had to remove all the devices and install Ubuntu again with all the devices unplugged.

Revision history for this message
Amelia Hansen (hansen74) said :
#12

It seems like you're encountering a boot problem with Ubuntu 7.04 after installation. Here are some steps you can try to troubleshoot the issue:

1. Potential Hardware Incompatibility:
The error messages "sis_init_one" and "udev-event abnormal exit" might indicate an issue with the system's hardware, particularly the SATA controller. Check if your motherboard or chipset has known compatibility issues with Ubuntu 7.04. You can find information about compatible hardware on the Ubuntu website

2. Faulty Installation Media:
Re-download the Ubuntu 7.04 ISO file and ensure a clean burn onto a new CD. Download errors or a damaged CD can lead to installation problems.

3. Manual Module Loading (For Advanced Users):
The error mentions a missing module. If you're comfortable with terminal commands, you can try manually loading the required module during boot. However, this is a complex procedure and requires knowledge of your specific hardware. Refer to Ubuntu forums or communities for advanced troubleshooting steps.
You can also check here for more information: https://www.speedoautoteile.com/product-category/opel/