0

I was using Windows for a bit because I'm still seeing up all the programs on it following a hard drive failure. One thing Seagate said to do was run SeaTools. When I did, it didn't really say which drive was which (I have two, a 1TB with Win7 and a 250GB for Ubuntu) So I ran the smallest scan on both drives. I haven't done anything else with that tool. Then I restarted, trying to get back to Ubuntu. But it fails to boot. It says something like disk error.

I have the install disk for both OSes. What can I do to repair my Ubuntu install? I ran boot repair from a live disk. Result is here : http://paste.ubuntu.com/8169843/

1

Based on this, it looks as though your 250GB hard drive has failed:

File descriptor 9 (/proc/12881/mounts) leaked on lvscan invocation. Parent PID 20834: bash File descriptor 63 (pipe:[82571]) leaked on lvscan invocation. Parent PID 20834: bash /dev/sdb: read failed after 0 of 4096 at 0: Input/output error /dev/sdb: read failed after 0 of 4096 at 250059227136: Input/output error /dev/sdb: read failed after 0 of 4096 at 250059341824: Input/output error /dev/sdb: read failed after 0 of 4096 at 4096: Input/output error /dev/sdb1: read failed after 0 of 4096 at 228585308160: Input/output error /dev/sdb1: read failed after 0 of 4096 at 228585365504: Input/output error /dev/sdb1: read failed after 0 of 4096 at 0: Input/output error /dev/sdb1: read failed after 0 of 4096 at 4096: Input/output error /dev/sdb5: read failed after 0 of 4096 at 21471625216: Input/output error /dev/sdb5: read failed after 0 of 4096 at 21471682560: Input/output error /dev/sdb5: read failed after 0 of 4096 at 0: Input/output error /dev/sdb5: read failed after 0 of 4096 at 4096: Input/output error

You will want to recover any files you can using a live disc, then replace the hard drive. After you reinstall Ubuntu, you can restore the remaining files from your latest backup.

Good luck.

| improve this answer | |
  • That's not possible, it can't just fail like that because of a scan. And there wasn't any bad sectors, either. I checked with the live disk by using fsck and disk manager. Is there anything else it could be? I can't remember off the top of my head, but it might not have been a seagate drive. Would using seagate tools mess up a non seagate drive like that? – Dana LaBerge Aug 29 '14 at 14:50
  • That's true--a scan wouldn't per se cause it to fail. But bad sectors is only a single type of failure. I/O errors could just mean the hard drive isn't responding. I don't know what Seagate tools do. If it's just a SMART scan like most diagnostics, it should've been fine. – Nathan Haines Aug 29 '14 at 18:43
  • Then what would I do to figure it out? – Dana LaBerge Aug 29 '14 at 20:37
  • Never mind. Apparently running it a third time or a fsck or checking for bad sectors did it. At least it works now, even though I have no idea how. – Dana LaBerge Aug 29 '14 at 22:09
  • Glad you found the problem; sorry it was the drive. Get off the failing drive as soon as possible (it can permanently fail without notice) and you should otherwise be all set. – Nathan Haines Aug 29 '14 at 23:43

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.