Results 1 to 9 of 9

Thread: Live CD Install Dies During Boot

Hybrid View

  1. #1
    Join Date
    Aug 2005
    Beans
    117

    Live CD Install Dies During Boot (M2R32-MVP Issue)

    EDIT: For anyone who arrives through Search - I've edited the subject of this thread due to discovering part of the problem was the Asus M2R32-MVP Motherboard I have. This comes in later.

    Hi,

    I'm running Gutsy at the moment, I'm trying to do a fresh install of Hardy. I cannot get the live desktop CD to run (have tried multiple burns and CD passes its verification check).

    I turned on Safe Graphics mode and to get more information I also removed the Splash and Quiet options from the boot line. I don't know how I can get an actual log file from a live CD, so the best I could do was copy down the error messages by hand. I got the following:

    Code:
    end request: I/O error , dev fd0, sector 0
    end request: I/O error , dev fd0, sector 0
    Buffer I/O: I/O error , dev fd0, locical block 0
    ata1.00: qc timeout (cmd 0xec)
    ata1.00: failed to IDENTIFY (I/O error, err_mask 0x4)
    failed to recover some devices retrying in 5 secs
    I then get an endless cycle of repetition of the above with some minor variations for other ata numbers (ata2.00, ata3.00, ata4.00) along with the occasional message that a particular numbered SATA link is UP or DOWN.

    It may be significant that earlier in the message list (though apparently before it errors properly), I see the line:
    Code:
    floppy drive fd0 is 1.44M
    I have no floppy drive. Nor IDE drives. My hardware is as follows:AMD Barcelona Dual Core 5200 CPU, Asus M2R32-MVP motherboard, 4GB DDR800 RAM, Samsung SATA DVD-RW, Radeon 2600HD Pro Graphics card, 2x 160GB HDs with Ext3 filesystems.

    To the best of my knowledge, my hardware is good. I'd really appreciate any help with this as I'd really like to get the new Kubuntu on my machine. Also, as this is a problem right out of the box, I'd imagine that there are other people out there who have the same problem and are getting a very bad first impression of Kubuntu so fixing this might mean solving a bug in the actual Kubuntu install.

    Anybody?

    Thanks a lot,

    Harmony.
    Last edited by H4rm0ny; April 27th, 2008 at 04:27 PM.

  2. #2
    Join Date
    Jun 2007
    Location
    Essex ,U.K.
    Beans
    229
    Distro
    Hardy Heron (Ubuntu Development)

    Re: Live CD Install Dies During Boot

    Which image are you using?

    ubuntu.com/8.04/kubuntu-8.04-desktop-amd64.iso...........this one?
    Last edited by SnakeHips; April 26th, 2008 at 01:03 PM.
    Arch 2.6.28 on X86_64
    Hardy 2.6.24 on X86_64
    AMD Athlon(tm) 64 Processor 3200+
    Maxtor 6L160M0 (SATA) 160G ,NVIDIA G6200

  3. #3
    Join Date
    Aug 2005
    Beans
    117

    Re: Live CD Install Dies During Boot

    Thank you. I'm actually using the KDE4 Remix:

    kubuntu-kde4-8.04-desktop-amd64.iso

    I will go to the normal Kubuntu one and try that if I can't get any further with this, but a big part of why I want to upgrade is to start using KDE4.

    Based on where it falls over, however, I think possibly the problem occurs before we reach any distinction between the KDE3/KDE4 versions. I could be wrong though.

  4. #4
    Join Date
    Mar 2005
    Beans
    15

    Re: Live CD Install Dies During Boot

    I'm also experiencing the same problem.
    My laptop has only IDE drives and no floppy drive

    I tried the all_generic_ide switch without luck.

    I'm pretty sure that it has an unused fdd controller though.

    I'm also using the KDE4 remix version.

  5. #5
    Join Date
    Mar 2005
    Beans
    15

    Re: Live CD Install Dies During Boot

    OK, its working now.

    Apparently it's not actually hanging. It's stalling for some reason.

    If you wait a bit the boot process will continue.

    For me, I got the first i/o error at about 54 of the boot timer and it continued normally at 292.

  6. #6
    Join Date
    Aug 2005
    Beans
    117

    Re: Live CD Install Dies During Boot

    Yes - this is the case here also, but I have to say, it was stalling for a really long time. If I hadn't had to dig my laptop out of storage so I could read this forum whilst fiddling, I would never have come back and found that it had actually moved on from error messaging at me to something else.

    HOWEVER, this was not the end of the story. I had significant problems and now have my system set up in what I suspect is a half-gutsy, half-hardy - some mutant gibbon-heron chimera that is likely to die at some point.

    The desktop trial system never successfully booted. I tried to install from the alternate CD in the end. The first problem was (after the excrutiating wait, that is), that the system couldn't detect my SATA DVD drive (a Samsung Writemaster). As this was the DVD drive I'd booted the CD from in the first place, having the system suddenly lose it mid-install was problematic. I ended up plugging in an external drive and booting from that. (The internal Samsung drive is now working perfectly, however and lest anyone be put off by this, I'd like to say that it's the best DVD drive I've ever purchased).

    Unfortunatly, I then reached the second problem: Neither of my internal hard-drives were detected. I kid you not. Both SATA, as mentioned earlier. I got an error message telling me that no partitionable media was detected. Nor could the install script handle this as it firstly gave me blank menu options and the secondly dumped me in a blue screen with no menu at all, forcing me to reset. The Blue Screen of Death in Linux! Hideous! I couldn't find any way past this.

    So that brings me to where I am now. I managed to boot into the command line on my half-upgraded existing system and with a lot of manual dpkg -reconfigure, uninstalling and re-installing I managed to get a system up again. It's not worth me detailing the many commands I used to do this and nor can I remember them anyway. dpkg kept quitting on me with "too many errors" when I tried to use it automatically. I had to do packages by hand. dbus was problematic, though I found out that dpkg --reconfigure would work on it when dbus was running but not when it was not. How that comes about, I have no idea, but it really was the case!

    Now I'm up and running, but I need to reinstall the ATI drivers and I'm not at all confident that my mangled collection of packages can handle that right now. If you don't hear back from me, my computer is dead again!

    But I really, really would appreciate any suggestions from the experts here. I would strongly prefer to do a full re-install of Kubuntu on my system.

    Anyway, wish me luck, people.

    _harmony.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •