Ubuntu 5.04 failing to install

The place to post if you need help or advice

Moderators: ChrisThornett, LXF moderators

Ubuntu 5.04 failing to install

Postby EchoBeach » Tue Jun 28, 2005 11:33 pm

I have created an image for installing Ubuntu 5.04 from the LXF68 DVD.
This boots me into the Linux Ubuntu install (on a P4 3GHz that normally runs Win MCE 2005).
I have a USB 2.0 attached 20Gb HDD (in an external caddy).
The process gets as far as creating the Lnux partition on the USB drive, but fails while attempting to install the base 'system'.
At the time of failure, it tells me to look for /var/lib/messages, but when I boot up with the Live CD, I can see the '/var/lib' folder but no 'messages'.
This is my first attempt to install Linux, although I have used Knoppix 3.n Live CDs :D and more recently the Ubuntu 5.04 Live CD.
I am definitely a newbie, and would appreciate any assistance available.
If there might be a problem with the CD, how do I go about checking the files? I've heard (and read) a lot about md5sum, but I have not understood it or how to run the checks.
Is there anything else I should be checking?
Regards
Echo
EchoBeach
 
Posts: 33
Joined: Tue Jun 28, 2005 11:02 pm

RE: Ubuntu 5.04 failing to install

Postby toby_tyke » Wed Jun 29, 2005 1:52 am

Hi

Not too sure why it's falling over at the base system install stage. Does it give you a specific error message?

Installing Ubuntu to a USB drive IS possible, and this thread:

http://www.ubuntuforums.org/showthread.php?t=5151

on the official Ubuntu site has some very good instructions on how to do it (5th comment down).

Having looked at those instructions, I have to say it looks like a world of pain. Have you considered freeing up some space on your internal HDD? If that's out of the question, you might want to try Puppy linux, included on the same DVD. Puppy is designed to run from a USB drive.

Hope that helps.
toby_tyke
 
Posts: 2
Joined: Tue Jun 28, 2005 1:34 pm

RE: Ubuntu 5.04 failing to install

Postby nelz » Wed Jun 29, 2005 8:17 am

/var will be mounted as a ramdisk, so rebooting will clear it. Also, it is normally /var/log/messages.

With most Linux installers, you can get to a command prompt by pressing Ctrl-Alt-F1/2/3/4/5, try them in sequence until you get a prompt. Then type "cat /var/log/messages".
"Insanity: doing the same thing over and over again and expecting different results." (Albert Einstein)
User avatar
nelz
Site admin
 
Posts: 8546
Joined: Mon Apr 04, 2005 11:52 am
Location: Warrington, UK

Postby EchoBeach » Wed Jun 29, 2005 8:32 pm

Thanks toby_tyke, Nelz
I've had another go with pen and paper to hand.
The installation reaches the 'Install base system' step.
It does the checking, receiving/validating OK.
Installing base-system ...
Message:
Code: Select all
Base System Installation error
The debootstrap program exited with an error (return value 1)
Check /var/log/messages or see virtual console 3 for the details.
      <go back>         <continue>

Based on Nelz's comment, I tried Ctrl+Alt+F3 and saw the following:
Code: Select all
...
insmod /lib/modules/2.6.10-5-386/kernel/fs/isofs.ko
insmod /lib/modules/2.6.10-5-386/kernel/drivers/ieee1394/sbp2.ko
insmod /lib/modules/2.6.10-5-386/kernel/drivers/scsi/sc_mod.ko
File descriptor 3 left open
File descriptor 4 left open
File descriptor 5 left open
File descriptor 6 left open
   /dev/sdc: open failed: no module found
   /dev/sdd: open failed: no module found
   /dev/sde: open failed: no module found
   /dev/sdf: open failed: no module found
No matching physical volumes found
File descriptor 3 left open
File descriptor 4 left open
File descriptor 5 left open
File descriptor 6 left open
   /dev/sdc: open failed: no module found
   /dev/sdd: open failed: no module found
   /dev/sde: open failed: no module found
   /dev/sdf: open failed: no module found
No volume groups found
   Reading all physical volumes.  This may take a while ...
mke2fs 1.35 (28-Feb-2004)
tar: ./usr/sbin/update-passwd: Read-only file system

My USB drive had been identified as sdb; so that would explain the other 'sdx' entries - I assume the installer is just checking for other drives.
I then returned to the installer screen and ran the last-but-one step to open a shell.
I could see the file in total including the following two lines at the top:
Code: Select all
insmod /lib/modules/2.6.10-5-386/kernel/drivers/block/floppy.ko
FATAL: Error inserting floppy (/lib/modules/2.6.10-5-386/kernel/drivers/block/floppy.ko): No such device

This is correct because my PC doesn't have a floppy drive.
Is the problem that the installer thinks the disk is read-only?
What do I need to do, to make it read-write?
Echo
EchoBeach
 
Posts: 33
Joined: Tue Jun 28, 2005 11:02 pm

Faulty HDD

Postby EchoBeach » Wed Jul 27, 2005 5:27 am

I tried another distro and saw lots of IO errors. I concluded that the disk itself had problems and so switched to another drive. All OK.
Does Linux have the ability to format a disk so that it can avoid bad sectors/blocks?
EchoBeach
 
Posts: 33
Joined: Tue Jun 28, 2005 11:02 pm

RE: Faulty HDD

Postby nelz » Wed Jul 27, 2005 7:56 am

mke2fs with the -c option. You can do it with reiserfs but it's a two stage process; sdend the output of badblocks to a file then pass that file to mkreiserfs.

See the man pages for plenty more information.
"Insanity: doing the same thing over and over again and expecting different results." (Albert Einstein)
User avatar
nelz
Site admin
 
Posts: 8546
Joined: Mon Apr 04, 2005 11:52 am
Location: Warrington, UK


Return to Help!

Who is online

Users browsing this forum: Exabot [Bot] and 1 guest