error when attempting to restart after install of Edgy

Bug #67274 reported by wpshooter
6
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I am still getting this error when attempting to install Edgy (what I take to be the RC) from the DESKTOP CD.

This occurs after the install has finished and when I get the prompt to either keep using the live CD or to restart the machine.

When I choose to restart the machine, the display goes to the splash screen a couple of times and then goes to a blank/black screen with cursor blinking at the top left hand corner of screen. The CD is ejected. I remove the CD and close the drawer and nothing further happens, the machine just sets at the blank/black screen with the cursor blinking in the top left hand corner of the screen. After about five minutes of this I hit ctrl, alt, del combination.

This brings up the following to display:

Init: rc6 process (17916) killed by signal 15

The system has reached a state where there are no jobs running.
A shell will be spawned so that you may start such jobs that are
necessary.

Type 'exit' when finished

[17181379.736000] buffer I/O error on device hda, logical block 304603
[17181379.736000] buffer I/O error on device hda, logical block 304604
[17181379.736000] buffer I/O error on device hda, logical block 304605
[17181379.736000] buffer I/O error on device hda, logical block 304606
[17181379.736000] buffer I/O error on device hda, logical block 304607
[17181379.736000] buffer I/O error on device hda, logical block 304608
[17181379.736000] buffer I/O error on device hda, logical block 304609
[17181379.736000] buffer I/O error on device hda, logical block 304610
[17181379.736000] buffer I/O error on device hda, logical block 304611
[17181379.736000] buffer I/O error on device hda, logical block 304612
[17181379.752000] squashfs error: sb_bread failed reading block 0x88f4b
[17181379.752000] squashfs error: unable to read fragment cache block [223ccd3f]
[17181379.752000] squashfs error: unable to read page, block 223ccd3f, size 5ecc

Not knowing what I should do at this point I hit the reset button on machine tower and machine reboots and Ubuntu seems to boot fine to the best of my knowlege, get to the desktop and indicator comes up notifying of available downloads.

Please let me know if you need any further info.

Thanks.

Revision history for this message
towsonu2003 (towsonu2003) wrote :

Could you please attach /var/log/installer/syslog, /var/log/syslog, and /var/log/partman to this bug as separate files (i.e. not copy-pasting)? Thanks in advance.

Revision history for this message
wpshooter (joverstreet1) wrote : Re: [Bug 67274] Re: error when attempting to restart after install of Edgy

Yes, I will attempt to post these shortly.

But please note that I have just downloaded and installed all of the
available updates to the install. I don't know whether that would
affect anything in these locations you are asking for.

Thanks.

On Sat, 2006-10-21 at 05:52 +0000, towsonu2003 wrote:
> Could you please attach /var/log/installer/syslog, /var/log/syslog, and
> /var/log/partman to this bug as separate files (i.e. not copy-pasting)?
> Thanks in advance.
>
> ** Changed in: Ubuntu
> Sourcepackagename: None => ubiquity
> Status: Unconfirmed => Needs Info
>

Revision history for this message
wpshooter (joverstreet1) wrote :
Revision history for this message
wpshooter (joverstreet1) wrote :

I added just the one file.

According to the message that came up when trying to add the other two "Cannot upload empty file".

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

This is unlikely to be an installer problem. casper or usplash perhaps? The syslog you uploaded does not contain any information from the installer session (as that gets wiped when you reboot). Is the system otherwise working fine now?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for casper (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.