Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

IO Failure


  • Please log in to reply
7 replies to this topic

#1 sausage

sausage

  • Members
  • 389 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Colorado
  • Local time:11:10 PM

Posted 09 February 2010 - 11:54 AM

I have no idea what went wrong, flash player started failing on me like it usually does after about 3 weeks of my computer constantly being on, it stops playing sound and the video stops after a few seconds, so I restarted like I always do, it didn't restart so I held the power button, that didn't work so I pulled the battery, now when I turn it on in normal mode it takes forever to boot, then goes to what looks like a terminal screen but you can't enter commands.

I restarted went into recovery mode and it does its scrolling text thing, then it says Done. Done. then flashes a 9-line error with stuff about IO and random crap.

Memory test was fine and im checking my OS disk for errors now.

any insight as to what happened/how I can fix it?

EDIT, also, when I get to the screen to choose which OS to boot to, I went into command line, couldn't figure anything out, then typed exit

at the top was my HDD, which had "No valid Operating System Installed" and then the boot order below that.

Edited by sausage, 09 February 2010 - 11:56 AM.


BC AdBot (Login to Remove)

 


#2 sausage

sausage
  • Topic Starter

  • Members
  • 389 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Colorado
  • Local time:11:10 PM

Posted 09 February 2010 - 01:24 PM

UPDATE: So, after about 10 minutes of letting it run through its retarded errors, I got access to the terminal, however few commands I have left, I can still do something.

Are there any diagnostics I should run?

Also, I got into some sort of BIOS thing during its errors. I tried to repair broken packages, which said it couldn't remove files.

this is the error list I got:

exception Emask 0x0 SAct 0x0 action 0x0
irq_stat 0x40000001
cmd c8/00:08:e7:a4:a8/00:00:00:00:00/e0 tag 0 dma 4096 in
res 51/40:08:e7:a4:a8/00:00:00:00:00/e0 Emask 0x9 (media error)
status: { DRDY ERR }
error: { UNC }

then it repeats until it shows:

end_request: I/O error, dev sda, sector 11052263 Traceback (most recent call last): //(the number 11052263 changes almost every time)
File "/usr/lib/command-not-found", line 5, in <module>
__version__ = "0.2.21"
KeyboardInterrupt

then it goes back to terminal

#3 MadDawg

MadDawg

  • Members
  • 453 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Houston, TX
  • Local time:12:10 AM

Posted 09 February 2010 - 03:07 PM

It sounds like your filesystem is corrupt or your drive is dying. I doubt it's the latter, though.

im checking my OS disk for errors now.

Was this with fsck?

Edited by MadDawg, 09 February 2010 - 03:16 PM.

A penguin broke my windows with a half-eaten apple!

#4 sausage

sausage
  • Topic Starter

  • Members
  • 389 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Colorado
  • Local time:11:10 PM

Posted 09 February 2010 - 04:34 PM

I have no idea why my file system would be dying.

no it wasn't with fsck, I put the disk in and it had a little button saying check disk for errors.

is there anything I should check with command line?

#5 MadDawg

MadDawg

  • Members
  • 453 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Houston, TX
  • Local time:12:10 AM

Posted 09 February 2010 - 05:12 PM

I have no idea why my file system would be dying.

This is why:

... it didn't restart so I held the power button, that didn't work so I pulled the battery


no it wasn't with fsck, I put the disk in and it had a little button saying check disk for errors.

is there anything I should check with command line?

This is for checking the installation CD, not the hard drive.

What I recommend doing is putting the install CD in and booting it to the desktop. Once there, go to System > Administration > Disk Utility. When it opens, click on the Linux partition and go to Edit > Check File System. Hopefully this will resolve the issue.

Edited by MadDawg, 09 February 2010 - 05:43 PM.

A penguin broke my windows with a half-eaten apple!

#6 sausage

sausage
  • Topic Starter

  • Members
  • 389 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Colorado
  • Local time:11:10 PM

Posted 09 February 2010 - 07:34 PM

ok so, I got to desktop. I see my new partition, which is clean, then my other partition contains 3 partitions, 3.1GB swap space, 40GB filesystem, and 1.7GB swap space. the filesystem is Linux 0x83. the two swap spaces are Linux swap 0x82.

I can only check the filesystem which it says its clean.

advice?

Edited by sausage, 09 February 2010 - 07:45 PM.


#7 sausage

sausage
  • Topic Starter

  • Members
  • 389 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Colorado
  • Local time:11:10 PM

Posted 09 February 2010 - 08:04 PM

I can mount the old partition with the new partition, so I don't really think I need to fix the old one, although it may be annoying reinstalling everything and tweaking my settings.

I would like to fix the old partition if possible, but it isn't imperative anymore.

#8 MadDawg

MadDawg

  • Members
  • 453 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Houston, TX
  • Local time:12:10 AM

Posted 09 February 2010 - 10:29 PM

After a little searching I found this: http://ubuntuforums.org/showthread.php?t=937872

This is what you'll want to try:

Post 6:

sudo e2fsck -f -c -v /dev/sda1

substituting /dev/sda1 with your device with the error.

This will force a check of the drive even if fsck believes the drive is ok.

For this and more tips see http://linux.chrissweeney.co.uk/


Post 8:

Like Chris-man said in the previous post, it's so much easier to fix than replace.

Boot from Live CD. Do not mount hard-drive!

ubuntu@ubuntu:/etc$ sudo e2fsck -c /dev/sda5
e2fsck 1.41.3 (12-Oct-2008 )
Checking for bad blocks (read-only test): done
/dev/sda5: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes

-----
-----

/dev/sda5: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda5: 234203/843648 files (2.6% non-contiguous), 1278754/1684809 blocks

I had to run it twice and deleted rather than fix a few files that I kept note of. I think this is so much better than replacing the hard-drive right now!


Replace "/dev/sda5" with the problematic partition in post 8 (quoted directly above)

Edited by MadDawg, 09 February 2010 - 10:32 PM.

A penguin broke my windows with a half-eaten apple!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users